[driverloader] Driver loaded, now what?
Linuxant support (Jonathan)
support at linuxant.com
Mon Apr 11 12:50:16 EDT 2005
for the 'Set Mode' error, please make sure that you have set the mode to
'Managed' with the network configuration tool if you want to connect to
an access point.
For the 'Set Encode' error, you have entered a WEP key in a wrong
format. If you do not want to use WEP, please make sure that the WEP key
text box is completely empty, it is possible that there a spaces in the
text box which need to be deleted.
As long as you are unable to seen an access point in the output of the
'iwlist scanning' command in a root shell, you will be unable to connect
to an 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. It is also possible that you will have to press
the button in Windows XP and then reboot in Linux as some wireless
button requires a driver to make it work. Such Linux drivers and
information on how to use them might be available at :
Please also try with different versions of the Windows XP driver.
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
Finally, according to the output of the 'dldrconfig --info' command you
have posted, your wireless card is based on the RT2500 chipset which is
not officially supported by DriverLoader and there are known issues with
this chipset and DriverLoader. It is possible that this is the source of
the problem that you are unable to see an access point in the output of
the 'iwlist scanning' command in a root shell. However, the problem with
this chipset and DriverLoader is generally that you are unable to send
and/or receive packets with the wireless interface.
Technical specialist / Linuxant
support at linuxant.com
Jason Kaskel wrote:
> Warning, my knowledge of most SysAdmin tasks on Linux sucks. I'm
> trying to get better.
> So I got my driverloader business working, and I uploaded and licensed
> the driver for my Belkin wirleess card. Everything looks good from the
> driverloader end, and it's mapped to device eth0.
> My question is, now what? I tried using the redhat network
> configuration tool but I wasn't able to get it working. It kept
> spitting back an error:
> Error for wireless request "Set Mode" (8B06):
> SET failed on device eth0: Invalid argument
> Error for wireless request "Set Encode" (8B2A):
> Invalid argument "s".
> The network itself works fine for my other computers on the network so
> it's got to be my setup. Does anyone have an idiot's guide (ie: step
> by step) on how to set up this part of it?
> Here's my configuration info if it helps:
> dldrconfig --info
> Wireless interface name: eth0
> MAC address : 00:11:50:14:DD:95
> Device instance : PCI-0000:02:09.0-1814:0201-1799:700A
> Device driver : rt2500
> Description : IEEE 802.11g Wireless Card
> License owner : jason at terrapinjay.com
> License key : 89-E5-01-AB-6F-SS
> License status : OK (Expires 2005-05-09)
> iwlist scan returns:
> eth0 Failed to read scan data : No data available
> (it's set to use channel 6, which is what the AP is configured for)
> Any help would be greatly appreciated.
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader