Option for 2.6.7+ users - Re: wlan0 No such device
Nick Jones <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <[email protected]> |
You are trying this on 2.6.7 right? The at76c503 driver has issues with 2.6.7 and later kernels because of a number of changes in the usb subsystem in this version. It seems to have something to do with the ohci-hcd host controller driver and certain host hardware, like mine, which lspci tells me is a usb1.0 controller. Yes, I'm behind the times aren't I? The symptoms I was having was: driver seemed to load ok after reboot, I was able to set the wireless parameters using iwconfig, but when the first packet of network traffic (not wireless traffic mind you) tries to go through the device, the driver will unload. dmesg tried to convince me that it was EMR. Who knows? Anyway, I got around this problem by taking the ohci-hcd driver out of 2.6.6 and building it as a standalone module. I've attached it to this email for you and for anyone else who thinks they might have the problem I was having - but this may not be the same as your problem Robert. Give it a shot anyway. Before you build it, you will need to eliminate your current ohci controller driver. The best way to do this at first would be to compile it as a module then do "rmmod ohci-hcd" after you have booted up. It this fix really works for you, you can even eliminate the old (or newer I should say) driver from your kernel config. Also, it is probably best to unplug your wireless adapter before you go on. To build it, simply go to the unzipped directory as root, and type "make install". It will install a module called ohci2_hcd. Load it by typing "modprobe ohci2-hcd" and check dmesg to see that it loaded properly. After that, connect your wireless adapter card as you would normally. Joerg - if this can work for other users, how about we make it available on the project home page? I will write some short documentation and make a tarball available for you when 2.6.8 comes out. Which brings me to another thing. The 2.6.8 kernel will introduce more changes to the usb subsystem, one of these changes will affect this ohci2 driver in a minor way. I have tried to accomodate for this change in the current version, but I don't know if I have been successful. So if you upgrade to 2.6.8, please check with me, or maybe check the at76c503a home page. Ohci2 after the release of 2.6.8 may, but may not, be the same as the one attached to this email. Please tell us if it fixes your problem. Thanks Nick Robert Burns wrote: > I suspect the driver did not load the firmware correctly. I've found > that it's necessary to boot into Windows from a cold boot before I > reboot into Linux; otherwise, the driver will not load in Linux > (Linksys WUSB11 v.2.8). I suspect the reason is that the firmware is > not being loaded in Linux after a cold boot, but it is retained in the > device's memory after a system restart. > > Robert Burns > _______________________________________________ > at76c503a-user mailing list > [email protected] > http://lists.berlios.de/mailman/listinfo/at76c503a-user >
ohci2-hcd-0.1.tar.gz
(application/gzip, 38.2 KB) - not displayed