[driverloader] Problem with driverloader loading at startup

Linuxant support (Jonathan) support at linuxant.com
Mon Jan 3 11:03:44 EST 2005


Hi,

it seems that when the DriverLoader module is inserted into the kernel, 
it is unable to find the Windows driver you have uploaded. Since 
re-inserting the DriverLoader module in the kernel when the machine is 
fully booted (dldrconfig --dumpdiag does re-load the DriverLoader 
module), it is quite possible that the problem is that the partition 
holding the '/var/lib/driverloader' directory is not mounted at the 
moment the 'driverloader' service is started.

If this is the source of the problem, you could adjust the starting 
order of your services to fix this issue.

Alternatively, under Fedora Core 3, you could add the following lines at 
the end of your '/etc/rc.local' file :

---
dldrstop
modprobe driverloader
ifup <iface>
---

You should replace '<iface>' with the name of your wireless interface, 
for example, eth1.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


Clifford Snow wrote:
> I'm running Fedora Core 3 on a Dell 600m laptop using Linuxant drivers.
> Recently I repartitioned my hard drive to add a /var partition.  I moved
> the data from the old partition to the new.  Except for loading the
> driverloader, everything works like it did before.  Now when I boot the
> system, my wireless network does not start.  I receive the following
> dmesg error:
> 
>         driverloader: /var/lib/driverloader/bcmwl5.sys: unable to open
>         (err=-2)
>         driverloader: unable to load "bcmwl5.sys" (-2)
>         driverloader: probe of 0000:02:03.0 failed with error -2
>         driverloader: /var/lib/driverloader/bcmwl5.sys: unable to open
>         (err=-2)
>         driverloader: unable to load "bcmwl5.sys" (-2)
>         driverloader: probe of 0000:02:03.0 failed with error -2
> 
> Running dldrconfig --dumpdiag solves the problem.  It goes ahead and
> loads the windows drivers.  Or I can load the drivers from
> http://127.0.0.1:8020 by clicking on reload.
> 
> I've removed driverloader using  "rpm -e driverloader" and have deleted
> and reinstalled the windows drivers with no success.  
> 
> Any suggestions?
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader


More information about the driverloader mailing list