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

Derek Jennings <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <[email protected]>
On Monday 02 Feb 2004 5:46 pm, Ryan Mueller wrote:
> Having some problems setting up a Linksys WUSB11 USB wireless adapter
> (version 2.8) in Mandrake 9.2. I have had the unit since October of last
> year, and a few weeks back finally found some pages detailing how the
> latest Berlios CVS tarball had support for the WUSB11 2.8 in it, and how
> to set it up. The method I'm trying now is at
> http://mandrake101.no-ip.org/.
>
> I installed the Mandrake kernel source rpm, and the wireless tools RPM
> from Mandrake's Package Manager. I did a make, and make install on the
> the at76c503a driver. I added the following lines to
> /etc/hotplug/blacklist:
>
> usbvnet_rfmd
> usbvnet_r503a
> usbvnet_r503_rfmd
>
> /etc/sysconfig/network-scripts/ifcfg-wlan0 consists of:
>
> DEVICE=wlan0
> BOOTPROTO=dhcp
> IPADDRESS=""
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> BROADCAST=192.168.1.255
> ONBOOT=yes
> KEY=no
> WIRELESS_RATE=11M
> WIRELESS_MODE=Managed
> WIRELESS_ESSID=linksys
>
> /etc/sysconfig/network is:
>
> NETWORKING=yes
> GATEWAY=192.168.1.1
> GATEWAYDEV=wlan0
>
> And finally, I changed ONBOOT=yes to ONBOOT=no for
> /etc/sysconfig/network-scripts/ifcfg-eth0. When I restarted the machine
> after doing all this, I still have no net access. When I ran dmesg, I
> found the following output:
>
> hub.c   connect-debounce failed, port 2 disabled
> hub.c   new USB device 00:1d.1-2, assigned address 2
> usb.c   USB device 2 (vend/prod 0x1915/0x2233) is not claimed by any
> active driver
> --- misc unrelated lines ---
> --- misc unrelated lines ---
> --- misc unrelated lines ---
> at76c503.c: Generic Atmel at76c503/at76c505 routines v0.11beta4
> at76c503-fw_skel.c: Atmel at76c505 (RFMD 2958) Wireless LAN Driver
> v0.12beta6 loading
> usb.c: registered new driver at at76c505-rfmd2958
> at76c503-fw_skel.c: using compiled-in firmware
> NTFS driver 2.1.4a [Flags: R/O MODULE].
> at76c503.c: Downloading external firmware failed: -22
> usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.11beta4
> usb.c: registered new driver usbdfu
> at76c503-fw_skel.c: using compiled-in firmware
> at76c503.c: Downloading external firmware failed: -22
>
> If I unplug the device and plug it back in, it registers a USB
> disconnect at address, it reconnects the device at address 3, and
> returns the same "Downloading external firmware failed: -22" message.
>
> I had been tinkering with this problem on Mandrake for about a week, and
> I gave up, and just for the hell of it blew away Mandrake and installed
> Fedora. After installing the wireless tools and Berlios driver in
> Fedora, and following approximately the same steps as listed above,
> everything worked fine and I was able to get on the net. The only
> problem with that is I would rather not use a "bleeding edge" distro
> like Fedora. I like Mandrake, and it seems to be a good system to learn
> the ins-and-outs of  Linux on. I have no Linux experience at all. I 've
> been using PC's since around 94, so I remember DOS, and have basic
> understanding of how things work with the command line. This problem has
> me stumped.
>
> I don't understand why it won't recognize the device, and I don't get
> the firmware downloading failure. I'm using the same driver as when I
> had it working in Fedora. I added what I assume are Mandrake's existing
> WLAN drivers to the blacklist file, so if they aren't loading then there
> shouldn't be a conflict. Confused, I am. If anyone has any ideas I would
> appreciate it. Thanks,
>
> Ryan Mueller
> [email protected]
>
> P.S.: Like I said, the device worked in Fedora, and works fine in WinXP,
> so it does work.
>

Did you try removing the old Mandrake supplied drivers completely?
They should be in /lib/modules/2.4.22-26mdk/kernel/3rdparty/at76c503

HTH

derek
-- 
veni, vidi, velcro
I came, I saw, I stuck around
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.