[driverloader] Strange loading problems

[Linuxant support (Jonathan)]

Hi,

it is possible that the DriverLoader module uses the 'eth0' interface 
instead of the 'eth1'. To fix this problem, please use the 'dldrconfig 
--netdevname=eth1' command in a root shell. With this command, 
DriverLoader will always use the 'eth1' device, even if the 'eth0' 
device is not loaded when the DriverLoader module is inserted into your 
kernel.

If it doesn't fix the problem, just after a reboot, please send at 
support at linuxant.com the output of 'dumpdiag'. Type the following in a
root shell:

---
dldrconfig --dumpdiag
---

Just send us the generated file located in /tmp 
('driverloaderdiag.txt'). It'll help us solve the problem.

Regards,


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


Brian D. McGrew wrote:
> I'm using RH9 on a Toshiba notebook with the builtin wireless.
> 
>  
> 
> The first time I loaded up driverloader life was good and I connected
> right away.
> 
>  
> 
> Upon subsequent reboots I get "driverloader device eth1 does not seem to
> be present, delaying initialization' if I try and bring it up from neat
> and I get the same thing if I do a /sbin/ifup eth1.
> 
>  
> 
> Modprobe -l shows /lib/modules/2.4.20-31.9/extra/driverloader.o
> 
>  
> 
> Any ideas?
> 
>  
> 
> -brian
> 
>  
> 
> Brian D. McGrew { brian at visionpro.com || brian at doubledimension.com }
> 
> ---
> 
> 
>>YOU!  Off my planet!
> 
> 
>  
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader