[driverloader] wpc54g working well; but a few questions

Linuxant Support (Jonathan) support at linuxant.com
Thu Jul 1 16:11:48 EDT 2004


Hi,

since you have a CardBUS (PCMCIA 32-bit) wireless adapter, please make sure 
that the 'pcmcia' service starts before the 'network' service. You should 
also make sure that the partition which is holding the 
'/var/lib/driverloader' directory must be mounted before the 'network' 
service is started.

For the suspend problem, please make sure that you are using a 3.40.x.x 
version of the Windows XP driver. You can obtain a 3.40.x.x version of this 
driver that will be compatible with your wireless card from the following 
URL :

http://ftp.us.dell.com/network/R74092us.EXE

Under Linux, you can use the 'unzip' command on the .EXE file to extract the 
Windows driver. The required .INF file will be named 'AR/bcmwl5a.inf' inside 
the .EXE file.

If you still experience problems with this Windows driver, 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').

You should also send at support at linuxant.com error or warning messages that 
might have been left in your '/var/log/messages' file just after a suspend.

Regards,


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


Le 1 Juillet 2004 12:32, Michael Perry a écrit :
> Hi all-
>
> I have a linksys wpc54g card which is working well on debian linux
> unstable on a dell inspiron 4100.  I have noticed a few things which I
> have not been able to figure out:
>
> 1) the card for some reason does not come up when the laptop boots.  I
> have to manually rmmod driverloader and then modprobe it to make it
> work.  After that I use some schemes in /etc/network/interfaces to do
> ifup statements for various locations.  All works then.  I should note
> that the driverloader module does get inserted into the running kernel
> at boot time and I have the card in the system when it boots.
>
> 2) suspend events seem problemmatic at times.  Oftentimes, by
> suspending the laptop using "apm -s", the laptop comes back great,
> sound modules work, X works, etc.  Oftentimes though driverloader
> requires re-inserting into the kernel and then restarting networking
> using the ifup scripts.
>
> BTW, this is running on a 2.6.7 kernel that is self-compiled from
> tarball off of kernel.org.


More information about the driverloader mailing list