[driverloader] Misc. problems with the driverloader module
support at linuxant.com
Tue Jan 6 11:41:31 EST 2004
the INF file still says "184.108.40.206", but if you run "strings -el
/var/lib/driverloader/w70n51.sys", you will see "220.127.116.11".
Did you have this version of the binary file already?
Maybe Alexandre can tell us where he got his "18.104.22.168" from.
Also, please let us know if you have the same results (using a daemon to
autoconfigure or not).
Technical specialist / Linuxant
support at linuxant.com
----- Original Message -----
From: "Peter Theunis" <peter at drunkcoders.com>
To: "Linuxant support" <support at linuxant.com>
Cc: "Peter Theunis" <peter at drunkcoders.com>;
<driverloader at lists.linuxant.com>
Sent: Monday, January 05, 2004 5:56 PM
Subject: Re: [driverloader] Misc. problems with the driverloader module
Thanks for the swift answer.
The driver at that location is still the 07/31/2003,22.214.171.124 version.
I'd love to give the new driver a swing, any other locations for that driver
Linuxant support [support at linuxant.com] wrote:
> please try with the latest Centrino driver (126.96.36.199) to see if it helps.
> can get it from the following link.
> Jean-Simon Durand
> Technical specialist / Linuxant
> support at linuxant.com
> ----- Original Message -----
> From: "Peter Theunis" <peter at drunkcoders.com>
> To: <driverloader at lists.linuxant.com>
> Sent: Wednesday, December 31, 2003 3:19 PM
> Subject: [driverloader] Misc. problems with the driverloader module
> Distribution: Gentoo
> kernel: 2.4.23-pac1
> version: driverloader-1.54 (built from tarball)
> Win drivers: 07/31/2003,188.8.131.52
> Hardware: IBM Thinkpad T40, with Intel Centrino 802.11b mini-PCI card
> The wrapper works ok to the exceptions of a few (show stopper) issues (see
> #1: After a couple hours of use:
> Wifi stops working and i get "netndis_xmitcomplete_handler: err -5" syslog
> messages, I have to unload and reload the driverloader module to have it
> work again.
> This has been happening since the first time I tried the driver, almost a
> month ago. Since then I've upgraded it quite a few time, without any
> #2: I just got the following syslog error, it recovered though:
> Any chances on getting this fixed ? I plan to buy the wrapper, but only if
> it's more stable; otherwise i'll just replace the mini-PCI card with one
> that has native drivers.
More information about the driverloader