I'm trying to set up a Linksys WPC54Gv2 PCMCIA wireless card on suse 10. It was working beautifully on suse 9.3 but since switching to 10 I haven't been able to make it work. I figured out the the acx_pci driver is somehow "locking" the card so that no other drivers can claim it. There is no package with the word acx in the name or description so it's not as simple as simply uninstalling an rpm. I have found acx_pci.ko in /lib/modules/2.6.13-15.8-default/source/net and references to it in modules.alias, modules.dep and modules.pcimap, so I'm assuming that it was included in the kernel. I've tried removing all references to the driver in these files and doing an rmmod acx_pci but when I reboot, the module is loaded again and the references have been magically rewritten into those files. My question is how do I disabled the acx driver so that it will no longer claim the card? -- -Allen -- Allen Seelye Allen@huggingtheblackbox.org http://www.huggingtheblackbox.org A Linux user since 1999. --------------- "That which does not kill me postpones the inevitable."
On Monday 17 April 2006 08:50, Allen Seelye wrote: <snip>
My question is how do I disabled the acx driver so that it will no longer claim the card?
Hi Allen, Try putting acx_pci in /etc/hotplug/blacklist *and* running rmmod acx_pci regards, Carl
Thanks for the response, but no good there either. The acx driver is still loading somehow and showing up in lsmod. One other piece of info, when I insert the card and do a "dmesg", I get this: ---------- PCI: Enabling device 0000:07:00.0 (0000 -> 0002) ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:07:00.0 to 64 ACPI: PCI interrupt for device 0000:07:00.0 disabled acx_pci: probe of 0000:07:00.0 failed with error -5 ---------- This has been the issue from the beginning and much googling has suggested that the acx_pci driver is at fualt. I could be wrong about that. Any other suggestions would be greatly appreciated. -Allen Carl Hartung wrote:
On Monday 17 April 2006 08:50, Allen Seelye wrote: <snip>
My question is how do I disabled the acx driver so that it will no longer claim the card?
Hi Allen,
Try putting acx_pci in /etc/hotplug/blacklist *and* running rmmod acx_pci
regards,
Carl
-- -Allen -- Allen Seelye Allen@huggingtheblackbox.org http://www.huggingtheblackbox.org A Linux user since 1999. --------------- "That which does not kill me postpones the inevitable."
On Monday 17 April 2006 09:59, Allen Seelye wrote:
Thanks for the response, but no good there either. The acx driver is still loading somehow and showing up in lsmod.
I wonder if this could have something to do with preloading in 10.0? Carl
On Monday 17 April 2006 09:59, Allen Seelye wrote:
Thanks for the response, but no good there either. The acx driver is still loading somehow and showing up in lsmod. One other piece of info, when I insert the card and do a "dmesg", I get this:
Hi again, Allen. Have you been to this page? http://www.houseofcraig.net/acx100_howto.php Excerpt: "... First, let's see if a driver is already installed, so type: find /lib/modules/`uname -r` -name "*acx*", (those are not single-quotes around uname -r, they are backtics and are the lower-case of the "~" key on my keyboard). If there is no output from that command and you are simply returned to your command prompt, then no driver is already installed and you should proceed on to the next section. If you get something back... with "acx_pci" in it, then it's possible that the already-installed driver will work, and all you need to do now is install the firmware, to give that a try, you can jump to this [link]section. Suse users: If you are going to use Suse's built-in acx_pci module, then understand that it's compiled to look for the firmware in /lib/firmware, not /usr/share/acx, so please bear this is mind and modify your firmware location accordingly. Some other distros that provide pre-compiled acx_pci modules compile them to look for the firmware in /usr/lib/firmware. ..." regards, Carl
Yes, but I'm using kernel 2.6.13-15.8-default and that guide is for 2.6.14 and earlier. I tried to follow some of it's suggestions anyway but the file structure is different than the way he describes it. I'm still pretty green about recompiling modules. I suppose there is some way to do it and leave out the acx_pci module but I have no idea how to go about doing that. Carl Hartung wrote:
On Monday 17 April 2006 09:59, Allen Seelye wrote:
Thanks for the response, but no good there either. The acx driver is still loading somehow and showing up in lsmod. One other piece of info, when I insert the card and do a "dmesg", I get this:
Hi again, Allen.
Have you been to this page? http://www.houseofcraig.net/acx100_howto.php
Excerpt: "... First, let's see if a driver is already installed, so type: find /lib/modules/`uname -r` -name "*acx*", (those are not single-quotes around uname -r, they are backtics and are the lower-case of the "~" key on my keyboard). If there is no output from that command and you are simply returned to your command prompt, then no driver is already installed and you should proceed on to the next section. If you get something back... with "acx_pci" in it, then it's possible that the already-installed driver will work, and all you need to do now is install the firmware, to give that a try, you can jump to this [link]section. Suse users: If you are going to use Suse's built-in acx_pci module, then understand that it's compiled to look for the firmware in /lib/firmware, not /usr/share/acx, so please bear this is mind and modify your firmware location accordingly. Some other distros that provide pre-compiled acx_pci modules compile them to look for the firmware in /usr/lib/firmware. ..."
regards,
Carl
-- -Allen -- Allen Seelye Allen@huggingtheblackbox.org http://www.huggingtheblackbox.org A Linux user since 1999. --------------- "That which does not kill me postpones the inevitable."
On Monday 17 April 2006 10:42, Allen Seelye wrote:
Yes, but I'm using kernel 2.6.13-15.8-default and that guide is for 2.6.14 and earlier.
2.6.13-* is before 2.6.14, isn't it? ;-)
I tried to follow some of it's suggestions anyway but the file structure is different than the way he describes it. I'm still pretty green about recompiling modules. I suppose there is some way to do it and leave out the acx_pci module but I have no idea how to go about doing that.
I didn't provide that link as a "guide" for you to explicitly follow, but as an entry point for learning more about the problem driver and it's installation/removal. After a bit more poking around I've rediscovered (remembered) :-) that the automatic loading of modules in 10.0 is controlled in /etc/modprobe.conf. You can also check /lib/modules/<version>-default/modules.dep to see what module dependencies have been defined... maybe acx-pci is being pulled in by another module? Carl
Ok, things seem to be progressing fine now. I did find something usedul on that link you sent me. :) I did an rmmod acx_pci, removed the acx_pci.ko and ran depmod -a. After that, it quit loading the acx100 driver. I installed ndiswrapper from the suse 10 cds but it wouldn't load the module that way for some reason. I downloaded the sources from sourceforge and compiled it myself and now the card seems to be running fine. Thanks! -Allen Allen Seelye wrote:
Yes, but I'm using kernel 2.6.13-15.8-default and that guide is for 2.6.14 and earlier. I tried to follow some of it's suggestions anyway but the file structure is different than the way he describes it. I'm still pretty green about recompiling modules. I suppose there is some way to do it and leave out the acx_pci module but I have no idea how to go about doing that.
Carl Hartung wrote:
On Monday 17 April 2006 09:59, Allen Seelye wrote:
Thanks for the response, but no good there either. The acx driver is still loading somehow and showing up in lsmod. One other piece of info, when I insert the card and do a "dmesg", I get this:
Hi again, Allen.
Have you been to this page? http://www.houseofcraig.net/acx100_howto.php
Excerpt: "... First, let's see if a driver is already installed, so type: find /lib/modules/`uname -r` -name "*acx*", (those are not single-quotes around uname -r, they are backtics and are the lower-case of the "~" key on my keyboard). If there is no output from that command and you are simply returned to your command prompt, then no driver is already installed and you should proceed on to the next section. If you get something back... with "acx_pci" in it, then it's possible that the already-installed driver will work, and all you need to do now is install the firmware, to give that a try, you can jump to this [link]section. Suse users: If you are going to use Suse's built-in acx_pci module, then understand that it's compiled to look for the firmware in /lib/firmware, not /usr/share/acx, so please bear this is mind and modify your firmware location accordingly. Some other distros that provide pre-compiled acx_pci modules compile them to look for the firmware in /usr/lib/firmware. ..."
regards,
Carl
--
-Allen
--
Allen Seelye Allen@huggingtheblackbox.org http://www.huggingtheblackbox.org A Linux user since 1999.
--------------- "That which does not kill me postpones the inevitable."
-- -Allen -- Allen Seelye Allen@huggingtheblackbox.org http://www.huggingtheblackbox.org A Linux user since 1999. --------------- "That which does not kill me postpones the inevitable."
On Monday 17 April 2006 13:06, Allen Seelye wrote:
Ok, things seem to be progressing fine now. I did find something usedul on that link you sent me. :) I did an rmmod acx_pci, removed the acx_pci.ko and ran depmod -a. After that, it quit loading the acx100 driver. I installed ndiswrapper from the suse 10 cds but it wouldn't load the module that way for some reason. I downloaded the sources from sourceforge and compiled it myself and now the card seems to be running fine. Thanks!
Cool! Then please disregard the PM I just sent! And you're welcome, but you did all the work. - Carl
participants (2)
-
Allen Seelye -
Carl Hartung