Hi,
since you are able to see the MAC address of your wireless card in the output
of the 'dldrconfig --info' command, it means that DriverLoader is correctly
installed. The licensing information is also correctly entered. However, we
don't see any access points in the output of the 'iwlist scanning' command.
As long as you are unable to see an access point in the output of the
previous command, you will not be able to associate (connect) with your
access point.
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
the card.
Please verify the version of the Windows driver you have installed. You can
obtain this information on the front page of the http://127.0.0.1:18020 'web
site'. If you are not using version 3.40.x.x, please try to upgrade. You can
obtain a 3.40.x.x version of the Windows 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.
Please 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:
---
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
Le 24 Juin 2004 14:30, Norris Dan - IL a écrit :
> I have a relatively new Dell Latitude D600 with the TrueMobile 1450 PCI
> wireless card. It worked fine under Windows, so I know that the hardware
> isn't faulty, but now that I'm running Linux, I can't make it hook up.
>
>
>
> Has anyone gotten this card to work with the driverloader?
>
>
>
> Here's what I know (or think I know):
>
> --driverloader 1.72 loaded okay into my RHEL ES 3.0 2.4.21-15.EL kernel
>
> --device drivers loaded and the driverloader config page appears to be
> happy
>
> [root at dnorris-lap dann]# dldrconfig --info
>
> Linuxant DriverLoader for Wireless LAN devices, version 1.72
>
>
>
> Web configurator: listening on 127.0.0.1:18020
>
>
>
> Current parameters: ("dldrconfig --info")
>
>
>
> Wireless interface name: eth1
>
> MAC address : 00:90:96:A6:15:64
>
> Device instance: PCI-0000:02:03.0-14e4:4324-1028:0003
>
> Device driver : bcm43xxa
>
> License owner : norrisd at tusc.com
>
> License key : 06-D3-8D-70-37-E5
>
> License status : OK (Expires 2004-07-01)
>
>
>
> [root at dnorris-lap dann]# iwlist eth1 scan
>
> eth1 Failed to read scan data : No data available
>
>
>
> [root at dnorris-lap dann]# iwconfig eth1
>
> eth1 IEEE 802.11g ESSID:"" Nickname:"unknown"
>
> Mode:Managed Bit Rate=54Mb/s Tx-Power=25 dBm
>
> RTS thr:off Fragment thr:off
>
> 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
>
>
>
> I did monkey around once with the settings, but it was several weeks ago
> and I'm afraid I may have left something partially configured. Is there a
> good way to set everything back to the defaults. Particularly, I'm
> thinking I had tried to set up the WEP encryption or something along those
> lines, but I can't find the config files I modified any more (forgot where
> they are).
>
>
>
> Any pointers would be appreciated. I tried to follow the documentation and
> the FAQ, but those steps didn't seem to make any difference for me.
>
>
>
> Thanks,
>
> Dan