[driverloader] Ubuntu Hardy - driverloader says no devices detected because ssb still loaded
Linuxant support (Jonathan)
support at linuxant.com
Wed Jun 18 12:04:28 EDT 2008
if I understand the problem correctly, I guess that both DriverLoader
and the ssb driver claim to support the same USB ID(s) so it's the first
one that is loaded that will take over the device.
In this case, it will be necessary to determine which USB ID(s) are
conflicting and either remove the IDs from the ssb driver or modify the
INF file you uploaded to the Web Configurator to remove the conflicting
IDs. The most straightforward way would be to modify the INF file (it's
a simple text file) and reload it with the Web Configurator since
recompiling the ssb module is likely a more delicate operation and will
not survive a kernel update.
Technical specialist / Linuxant
support at linuxant.com
Brian Burch wrote:
> I updated the kernel to 2.6.24-19-rt and ran dldrinstall. The generic
> driver compiled OK (version 2.41), but the driverloader configuration
> panel said that my broadcom bcm43xx driver was not working because
> "module ssb is still loaded".
> I found a lot of confusing stuff when googling, but nothing very clearly
> relevant. I have a circumvention, but perhaps you can help me fix this
> problem properly?
> I did two things to get my driver running properly:
> 1. edit /etc/modprobe.d/blacklist. Comment out the line "blacklist
> bcm43xx". (I also added new blacklist lines for b43 and ssb, but I am
> not sure these are necessary - this change was not enough on its own
> because ssb is apparently loaded earlier than driverloader).
> 2. issue the following sequence of commands:
> sudo rmmod ohci_hcd
> sudo rmmod ssb
> sudo rmmod driverloader
> sudo modprobe driverloader
> sudo modprobe ssb
> sudo modprobe ohci_hcd
> After this my wlan connection works AND I can still access usb devices.
> After refreshing the Linuxant configuration display I can see the
> correct driver is loaded and working.
> I found the blacklist idea from a lot of posts, many of which were old
> or for other linux distributions - especially fedora.
> I found the rmmod sequence in
> The bug refers to ndiswrapper, so I substituted driverloader. However,
> the proposed circumvention suggests creating a new file with these
> commands in /etc/init.d/ndiswrapper. I looked at
> /etc/init.d/driverloader -> /usr/sbin/rcdriverloader and decided not to
> kludge it without your advice. I presume I'll have to re-issue this
> sequence of commands every time I boot the system.
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader