Re: probs with a Linksys WUSB11 ver2.8 in Mandrake...

Ryan Mueller wrote:

> Derek Jennings wrote:
>
>> On Monday 02 Feb 2004 8:42 pm, Ryan Mueller wrote:
>>  
>>
>>> Derek Jennings wrote:
>>>   
>>>
>>>> On Monday 02 Feb 2004 7:49 pm, Ryan Mueller wrote:
>>>>     
>>>>
>>>>>> Did you try removing the old Mandrake supplied drivers completely?
>>>>>> They should be in /lib/modules/2.4.22-26mdk/kernel/3rdparty/at76c503
>>>>>>         
>>>>>
>>>>> I tried removing the drivers located in
>>>>> /lib/modules/2.4.22-10mdk/kernel/3rdparty/at76c503/, per 
>>>>> suggestion, but
>>>>> the only thing that does is get an insmod at76c505_rfmd2958 error 
>>>>> during
>>>>> startup, if I remember correctly. Wouldn't the drivers contained 
>>>>> in the
>>>>> at76c503 directory be the Berlios drivers I installed? As far as I 
>>>>> can
>>>>> guess the Mandrake drivers would be in
>>>>> /lib/modules/2.4.22-10mdk/kernel/3rdparty/atmelwlandriver, but 
>>>>> those are
>>>>> blacklisted. Didn't seem to have helped. Thanks for the suggestion,
>>>>> though.
>>>>>
>>>>> Ryan
>>>>> [email protected]
>>>>>       
>>>>
>>>> Mandrake 9.2 contains both the atmelwlan driver and the at76c503a 
>>>> driver
>>>> When you compile the at76c503a driver 'make install' will put it 
>>>> into a
>>>> different location to where Mandrake has them. They will go in
>>>> /lib/modules/2.4.22-26mdk/kernel/drivers/usb
>>>> If you remove any driver then do depmod -a afterwards
>>>>     
>>>
>>> There's my lack o' knowledge kicking in. Did not know about the depmod
>>> command, or that I had to run it. It helped. Now when I dmesg it shows
>>> that it's DL'ing the firmware for the device, and it recognizes it and
>>> registers it as wlan0. It still doesn't show up in the USB Devices
>>> windows thats in the Configuration/KDE/Information menu (I think that's
>>> where it's located).
>>>
>>> On the reboot following the depmod-ing, it gave me an error message
>>> along the lines of a problem with the key argument being set to no in
>>> /etc/sysconfig/network-scripts/ifcfg-wlan0. I changed it from KEY=no to
>>> KEY="" and that fixed that problem. No, when starting up, shortly after
>>> it starts checking module dependencies it prints an error message 
>>> saying
>>> "Determining IP information for wlan0........failed......no link
>>> present, check cable". I will repost the contents of my network files
>>> for reference:
>>>
>>> /etc/sysconfig/network-scripts/ifcfg-wlan0 consists of:
>>> DEVICE=wlan0
>>> BOOTPROTO=dhcp
>>> NETMASK=255.255.255.0
>>> NETWORK=192.168.1.0
>>> BROADCAST=192.168.1.255
>>> ONBOOT=yes
>>> KEY=""
>>> WIRELESS_RATE=11M
>>> WIRELESS_MODE=Managed
>>> WIRELESS_ESSID=linksys
>>>
>>> /etc/sysconfig/network is:
>>> NETWORKING=yes
>>> GATEWAY=192.168.1.1
>>> GATEWAYDEV=wlan0
>>>
>>> There is nothing wrong with the physical connection. I didn't touch it,
>>> and I'm using it to mail this through XP right now. Making some
>>> progress.......
>>>
>>> Ryan
>>>   
>>
>> The driver is working. Its now just a matter of getting your 
>> configuration right. The KEY parameter is your encryption key. It 
>> must be given in the form
>> KEY=4567-89ab-cd      if it is Hex, or
>> KEY=s:mykey             if it is ASCII
>> If you are not using encryption then leave  out the KEY parameter 
>> altogether.
>> The WIRELESS_ESSID parameter is case sensitive. Make sure it matches 
>> your wireless access point.
>>
>> Any time you edit the config file you can test it out with
>> 'service network restart'
>> 'iwconfig'  will tell you how it is currently configured.
>> If you can see a MAC address for the Access point in iwconfig, then 
>> the wireless link is OK, although the encryption key may still be wrong.
>>
>> I have seen reports from other users of Linksys routers that they had 
>> to power cycle the router before it would give them an IP address. I 
>> have no idea why.
>>
>> derek
>>  
>>
> I removed the KEY="" entry from ifcfg-wlan0, but it did not change 
> anything. When I run iwconfig it prints the following output:
>
> wlan0:   IEEE 802.11-DS   ESSID:"linksys"   Nickname:"localhost"
> Mode: Managed   Channel:10   Access Point: 00:00:00:00:00:00
> Bit Rate: 11mb/s
> RTS thr=1536B   Fragmentation thr = 1536B
> Encryption key=off
> Power Mgmt=off
>
> All signal quality and data transmission values are 0, as it's not 
> connected. Might I need to specify the DHCP server? Windows lists it 
> as the same address as the gateway IP. I don't know what the access 
> point address is supposed to be. From what I saw in the iwconfig man 
> it should determine it automatically. I tried running "iwconfig wlan0 
> ap any" which would force it to set determination to auto, but it said 
> command not supported. The only thing that comes up in windows 
> resembling an address is "Physical Address" under Network Connection 
> Details. Listed as 00-0C-41-56-67-89. Do I need to specify that? 
> Thanks for the help,
>
> Ryan
>
> _______________________________________________
> at76c503a-user mailing list
> [email protected]
> http://lists.berlios.de/mailman/listinfo/at76c503a-user
>
Slight addendum......the 00-0C-41-56-67-89 is the address for my access 
point, and it shows it in the dmesg output when it loads the drivers and 
recognizes the device.

Ryan