[driverloader] Problems getting the driver to work on a new
Linuxant Support (Jonathan)
support at linuxant.com
Fri Jul 23 12:15:33 EDT 2004
as long as you will be unable to see an access point or another wireless
device in the output of the 'iwlist scanning' command, you will be unable to
associate (connect) to your access point or another wireless device.
Please make sure that your wireless card is activated. It is possible that you
might have to press a button or look in the BIOS for an option to activate
If you are trying to connect to an access point, make sure that your access
point broadcast it's ESSID and make sure that the ESSID string is not empty.
You should also disable all MAC address filtering and make sure that the
channel is set between 1 and 11. If your access point have a CTS protection
mode, please disable it. You should also make sure that you use the latest
firmware version for your access point.
If you require more assistance, please send at support at linuxant.com the output
of 'dumpdiag'. Type the following in a root shell:
Just send us the generated file located in /tmp ('driverloaderdiag.txt').
It'll help us solve the problem.
Technical specialist / Linuxant
support at linuxant.com
Le 23 Juillet 2004 05:10, Jesper Skov a écrit :
> I've installed driverloader with a trial license, and through it
> installed the Intel 2200BG Centrino driver. No problems that far.
> However, the led which should identify that the controller is active
> remains dark.
> iwconfig looks OK (I think):
> eth1 IEEE 802.11-DS ESSID:"casa" Nickname:"boystoy.zoftcorp.dk"
> Mode:Ad-Hoc Bit Rate=54Mb/s
> RTS thr=1600 B Fragment thr=2304 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> However, ifconfig shows only transmit errors:
> eth1 Link encap:Ethernet HWaddr 00:0E:35:39:66:DE
> inet addr:192.168.40.40 Bcast:192.168.40.255
> inet6 addr: fe80::20e:35ff:fe39:66de/64 Scope:Link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:9 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> iwlist scan results in this interesting message:
> # iwlist eth1 scan
> eth1 Failed to read scan data : No data available
> The only errors/warnings I see in the log are from my attempt to change
> Jul 23 11:05:11 boystoy kernel: driverloader: ndisQueryInformation:
> 802_11_CONFIGURATION st=FAILURE W=32 N=0
> Jul 23 11:05:11 boystoy kernel: eth1: Error -5 getting configuration to
> set frequency
> I have another laptop with a working wifi setup (under Windows 2000),
> which has the IP address 192.168.40.18. Pinging it from linux (route is
> set up correctly to use eth1) only results in counting up the TX error
> Has anyone seen anything like this before?
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader