WiFi works only with "generic" kernel(s) ?

[kalinik]

Hi there,
I have a strange problem with wireless: Ralink 2501 (it's a USB device) It works without troubles ONLY with "stock" kernels Here is a bit of info:

Code: Select all

inxi -v 1
System:    Host hss13 Kernel 2.6.35-25-generic x86_64 (64 bit) Distro Linux Mint 10 Julia
CPU:       Dual core AMD Athlon 64 X2 4800+ (-MCP-) clocked at 1000.00 MHz 
Graphics:  Card ATI RV620 LE [Radeon HD 3450] X.Org 1.9.0 Res: 2960x1050 
           GLX Renderer ATI Radeon HD 3450 GLX Version 3.3.10524 Compatibility Profile Context
Disks:     HDD Total Size: 1640.4GB (3.9% used)
Info:      Processes 179 Uptime 21:20 Memory 911.8/2008.8MB Client Shell inxi 1.4.23 

And here is the drivers it uses:

Code: Select all

lsmod | grep rt
rt2500usb              20266  0
rt73usb                24308  0
rt2x00usb              11316  1 rt73usb
rt2x00lib              31575  2 rt73usb,rt2x00usb
led_class               3393  1 rt2x00lib
mac80211              267163  2 rt2x00usb,rt2x00lib
cfg80211              170485  2 rt2x00lib,mac80211
...

By default Mint 10 comes with linux-2.6.32-22-generic - NO problems at all !
Lately, when I updated kernel to 2.6.35.-25-generic - NO problems at all too !
I have a DHCP wireless router network with WPA 1/2. It works perfectly.
But when i compile a new kernel (vanilla), although with the current 'config'-file - SYSTEM PERIODICALLY crashes and freezes!
Compiled 2.6.38.rt4 / rt5, then tried with 2.6.37 and 2.6.37.1 - no change and the system periodically crashes with the following logs:

kernel: [ 1751.540052] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:25 hss13 kernel: [ 1754.090035] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:27 hss13 kernel: [ 1756.640042] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:30 hss13 kernel: [ 1759.190041] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:30 hss13 kernel: [ 1759.190146] phy1 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x0000308c, value=0xffff8800
Feb 20 01:19:33 hss13 kernel: [ 1761.742244] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:35 hss13 kernel: [ 1764.290051] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:38 hss13 kernel: [ 1766.840047] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:40 hss13 kernel: [ 1769.390036] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:43 hss13 kernel: [ 1771.950053] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Feb 20 01:19:43 hss13 kernel: [ 1771.950159] phy1 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x0000308c, value=0xffff8800

... and so on until the system totally freezes !

Currently i use linux-2.6.37.1 but approx. every 5-6 minutes - the system hangs and freezes irrecoverably !
Same happens when I compiled linux-2.6.36 , -2.6.38.rt4/5 ...
I checked the logs for a solution and realized it loads 2 drivers at time: rt2500usb and rt73usb.
So i blacklisted rt2500usb
Now i have:

Code: Select all

lsmod | grep rt
rt73usb                24308  0 
rt2x00usb              11316  1 rt73usb
rt2x00lib              31575  2 rt73usb,rt2x00usb
led_class               3393  1 rt2x00lib
mac80211              267163  2 rt2x00usb,rt2x00lib
cfg80211              170485  2 rt2x00lib,mac80211

I have located rt73.bin and it seems OK:

locate rt73
/lib/firmware/rt73.bin
/lib/modules/2.6.35-25-generic/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
/lib/modules/2.6.37.1-hss/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
/usr/src/linux-2.6.37.1/.tmp_versions/rt73usb.mod
/usr/src/linux-headers-2.6.35-25-generic/include/config/rt73usb.h
/usr/src/linux-headers-2.6.37.1-hss/include/config/rt73usb.h

Now the system still freezes with error log :

hss13 NetworkManager[1080]: <info> (wlan0): supplicant connection state: completed -> disconnected
Feb 20 01:38:15 hss13 NetworkManager[1080]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/pci0000:00/0000:00:13.5/usb1/1-2/1-2:1.0/net/wlan0, iface: wlan0)
Feb 20 01:38:15 hss13 NetworkManager[1080]: <info> (wlan0): now unmanaged
Feb 20 01:38:15 hss13 NetworkManager[1080]: <info> (wlan0): device state change: 8 -> 1 (reason 36)
Feb 20 01:38:15 hss13 NetworkManager[1080]: <info> (wlan0): deactivating device (reason: 36).
Feb 20 01:38:15 hss13 avahi-daemon[1064]: Withdrawing address record for fe80::960c:6dff:fe8f:e168 on wlan0.
Feb 20 01:38:15 hss13 avahi-daemon[1064]: Withdrawing address record for 192.168.1.3 on wlan0.
Feb 20 01:38:15 hss13 avahi-daemon[1064]: Withdrawing workstation service for wlan0.
Feb 20 01:38:16 hss13 wpa_supplicant[1096]: Failed to initialize the driver after interface was added.
Feb 20 01:38:16 hss13 wpa_supplicant[1096]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Feb 20 01:38:16 hss13 dhclient: Internet Systems Consortium DHCP Client V3.1.3
Feb 20 01:38:16 hss13 dhclient: Copyright 2004-2009 Internet Systems Consortium.
Feb 20 01:38:16 hss13 dhclient: All rights reserved.
Feb 20 01:38:16 hss13 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Feb 20 01:38:16 hss13 dhclient:
Feb 20 01:38:16 hss13 NetworkManager[1080]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1279
Feb 20 01:38:16 hss13 NetworkManager[1080]: <info> (wlan0): cleaning up...
Feb 20 01:38:16 hss13 NetworkManager[1080]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Feb 20 01:38:16 hss13 NetworkManager[1080]: <info> radio killswitch /sys/devices/pci0000:00/0000:00:13.5/usb1/1-2/1-2:1.0/ieee80211/phy1/rfkill0 disappeared
Feb 20 01:38:16 hss13 wpa_supplicant[1096]: Failed to disable WPA in the driver.
Feb 20 01:38:16 hss13 dhclient: Listening on LPF/eth0/00:19:db:89:ba:8b
Feb 20 01:38:16 hss13 dhclient: Sending on LPF/eth0/00:19:db:89:ba:8b
Feb 20 01:38:16 hss13 dhclient: Sending on Socket/fallback
Feb 20 01:38:16 hss13 nm-dispatcher.action: Error in get_property: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist#012
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.0/ieee80211/phy3/rfkill1) (driver <unknown>)
Feb 20 01:40:01 hss13 NetworkManager[1080]: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.0/net/wlan0, iface: wlan0)
Feb 20 01:40:01 hss13 NetworkManager[1080]: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> (wlan0): new 802.11 WiFi device (driver: 'rt73usb' ifindex: 5)
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/2
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> (wlan0): now managed
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Feb 20 01:40:01 hss13 NetworkManager[1080]: <info> (wlan0): bringing up device.
Feb 20 01:40:02 hss13 NetworkManager[1080]: <info> (wlan0): preparing device.
Feb 20 01:40:02 hss13 NetworkManager[1080]: <info> (wlan0): deactivating device (reason: 2).

... and so on infinitely
The moment I unplug the device - the systems freeze !
With "stock" kernels I have no troubles (even when I plug/unplug 20 times per minute)
From FEB 22-2011 until now i'm using the stock kernel 2.6.35.-25-generic with no crashes or hangs... or anything wrong.

I have no idea what's wrong with 'non-stock' kernels and my WiFI so please someone give me a help

PS:Sorry for my bad english and the long post.

[bitmason]

I have had the same exact problem with Ralink driver with other distributions, with little success.

1. pick up the source code from Ralink's Website, and follow the instructions within the tarball. You'll get some functionality, but there is a good chance that teh source is broken. You can always get kernel patches from http://wireless.kernel.org and try those, bu support for modern ralink devices seems to be spotty at best.

BTW, what's wrong with the stock kernel?

[kalinik]

BTW, what's wrong with the stock kernel?

Nothing wrong with stock kernels - wireless works flawlessly !
But I want to know what's going wrong with non-stock kernels and why wireless doesn't work Even more... it breaks the whole system to a total freeze ! Unrecoverable...
I want to try the new kernels, primarily for video acceleration improvements . I'm still a newbie so I can't handle with kernel patches
Still no idea what causes the problem.

[AlbertP]

I guess that you need an update to the graphics driver and not the kernel for better acceleration. Nouveau and the proprietary drivers (don't know about opensource Radeon/Intel) can be updated independent from the kernel (though they may need a newer kernel sometimes).

[kalinik]

@AlbertP
You're wright about proprietary drivers. But I came from MS Windows and I want to know "how stuff works" That's why i'm trying to handle myself with the problems, but seems i have no idea what to do with my wifi problem

[bitmason]

Glad to see you figured out!

Also, keep making mistakes with building the kernel - I learned a lot from making mistakes with Linux in general!

[kalinik]

Some progress/testing these couple of days
1. I unplugged the usb adapter friday night (04/03/2011) and booted into my custom kernel 2.6.37-1 - the system worked PERFECT 2 days ! No hangs, no freeze... no Internet
2.I plugged the wifi this morning and ran "sudo iwconfig wlan0 power off" command - it seems to help a little! PC worked about 3-4 hours without problems... BUT i have to go out so when I come back - it was freezed again.
This situation makes me think there is a problem with power management
I rebooted again with stock kernel 2.6.35-25 and updated it throught 'update-manager' to 2.6.35-27 - everything works just fine (about 2 hours ago and counting..)
I'm really clueless what to do and how to figure out where is the problem

[TBABill]

I think this may be your problem:

rt73usb 24308 0
rt2x00usb 11316 1 rt73usb
rt2x00lib 31575 2 rt73usb,rt2x00usb
led_class 3393 1 rt2x00lib
mac80211 267163 2 rt2x00usb,rt2x00lib
cfg80211 170485 2 rt2x00lib,mac80211

Unless I'm mistaken, those are two different Ralink drivers. But you only have the one wireless device. An easy way to test my thinking would be to edit (as root) /etc/modprobe.d/blacklist.conf and add the following to the end of the file:

Code: Select all

blacklist rt2x00usb

and save the file, then exit.

Then edit (still as root) /etc/modules and just place # and a space in front of rt2x00usb so it reads

Code: Select all

 # rt2x00usb

then save and exit. Restart the machine and see if your results are different. If they are not, you can just reverse these actions and be back to the way it was.

I believe the two different USB drivers are causing a conflict on the machine, and this would happen in any kernel you setup this way. Even if you aren't experiencing problems, you could in the future.

[kalinik]

Woow
Thank you very much, TBABill !!!
Your post is very, very reasonable. I disabled/blacklisted the rt2500usb only.
I will try your logic as soon as I get home after work

[kalinik]

Hi again i'm at home ...
Unfortunately the previous idea by TBABill didn't get it
I blacklisted rt2x00usb but it seems to be used by rt73usb

Code: Select all

sudo rmmod rt2x00usb 
ERROR: Module rt2x00usb is in use by rt73usb

BUT... i found this : http://packages.debian.org/squeeze/firmware-ralink - some * Ralink RT2571W/RT2671 (RT2501USB/RT5201USB chipset) firmware, version 1.8 (rt73.bin)
Installed it, ran "sudo iwconfig wlan0 power off" and rebooted with kernel 2.6.37.1.custom - now it's about +1 hour uptime with no errors (fingers crossed ) @ heavy browsing , downloading , streaming , etc... It's OK right now
I will leave my PC idle for a while to see what will happen when power-management turns on ?!? (Last time my system was freezed when I leaved it idle for an hour time)

And if this didn't work - I will try again TBABill's logic, but to blacklist rt73usb and to enable rt2500usb.

[kalinik]

Bad news... again
It's still "mission impossible" to run the wifi with custom kernel !
I'm really pissed off !
I tried everything above with no real solution - the system freezes again... and again... and again.
Here is modinfo, just before the last freeze - everything seems to be fine

modinfo rt73usb
filename: /lib/modules/2.6.37.1-hss/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
license: GPL
firmware: rt73.bin
description: Ralink RT73 USB Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
srcversion: 7CBDD0E05C3D434F4F8B425
alias: usb:v148Fp2671d*dc*dsc*dp*ic*isc*ip*
alias: usb:v148Fp2573d*dc*dsc*dp*ic*isc*ip* <-- this is my device VendorID
alias: usb:v08DDp0120d*dc*dsc*dp*ic*isc*ip*
...
depends: rt2x00lib,rt2x00usb
vermagic: 2.6.37.1-hss SMP mod_unload modversions
parm: nohwcrypt:Disable hardware encryption. (bool)

and the last lines from dmesg | tail - n20:

[ 28.666417] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 31.103931] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro,commit=0
[ 31.639727] EXT4-fs (sdb6): re-mounted. Opts: commit=0
[ 31.738859] EXT4-fs (sdb5): re-mounted. Opts: commit=0
[ 39.420023] wlan0: no IPv6 routers present
[ 89.010029] Clocksource tsc unstable (delta = -283661423 ns)
[ 727.020070] usb 5-1: new low speed USB device using ohci_hcd and address 6
[ 727.170064] usb 5-1: device descriptor read/64, error -62
[ 727.430088] usb 5-1: device descriptor read/64, error -62
[ 727.710061] usb 5-1: new low speed USB device using ohci_hcd and address 7
[ 727.860079] usb 5-1: device descriptor read/64, error -62
[ 728.120066] usb 5-1: device descriptor read/64, error -62
[ 728.400066] usb 5-1: new low speed USB device using ohci_hcd and address 8
[ 728.820060] usb 5-1: device not accepting address 8, error -62
[ 728.990081] usb 5-1: new low speed USB device using ohci_hcd and address 9
[ 729.410034] usb 5-1: device not accepting address 9, error -62
[ 729.410067] hub 5-0:1.0: unable to enumerate USB device on port 1

BUMP!

[TBABill]

Ok, found that I didn't quite understand the rt2500usb/rt73usb actually work together. So in this instance you would actually want them both listed. I found

http://wiki.centos.org/HowTos/Laptops/Wireless

from the CENTOS wiki at http://wiki.centos.org/HowTos/Laptops/Wireless. Obviously don't follow any directions for CENTOS, just wanted a point of reference.

In your second list in the original post the rt2500usb is actually missing from your grep. What would happen if, instead of blacklisting anything, just add rt2500usb to /etc/modules? And remove anything related to rt2x00usb or rt73usb or rt2500usb from your /etc/modprobe.d/blacklist.conf.

[kalinik]

Ok, found that I didn't quite understand the rt2500usb/rt73usb actually work together. So in this instance you would actually want them both listed. I found

http://wiki.centos.org/HowTos/Laptops/Wireless

from the CENTOS wiki at http://wiki.centos.org/HowTos/Laptops/Wireless. Obviously don't follow any directions for CENTOS, just wanted a point of reference.

In your second list in the original post the rt2500usb is actually missing from your grep. What would happen if, instead of blacklisting anything, just add rt2500usb to /etc/modules? And remove anything related to rt2x00usb or rt73usb or rt2500usb from your /etc/modprobe.d/blacklist.conf.

OK. I'll try this right away.

Here we go :

Code: Select all

lsmod | grep rt
parport_pc             29976  0 
rt2500usb              19166  0 
rt73usb                23720  0 
rt2x00usb              11485  2 rt2500usb,rt73usb
rt2x00lib              35408  3 rt2500usb,rt73usb,rt2x00usb
mac80211              266921  2 rt2x00usb,rt2x00lib
cfg80211              161097  2 rt2x00lib,mac80211
gameport               10470  2 emu10k1_gp

Now we wait...

[TBABill]

Ok, found that I didn't quite understand the rt2500usb/rt73usb actually work together. So in this instance you would actually want them both listed. I found

http://wiki.centos.org/HowTos/Laptops/Wireless

from the CENTOS wiki at http://wiki.centos.org/HowTos/Laptops/Wireless. Obviously don't follow any directions for CENTOS, just wanted a point of reference.

In your second list in the original post the rt2500usb is actually missing from your grep. What would happen if, instead of blacklisting anything, just add rt2500usb to /etc/modules? And remove anything related to rt2x00usb or rt73usb or rt2500usb from your /etc/modprobe.d/blacklist.conf.

OK. I'll try this right away.

Here we go :

Code: Select all

lsmod | grep rt
parport_pc             29976  0 
rt2500usb              19166  0 
rt73usb                23720  0 
rt2x00usb              11485  2 [color=#FF0000]rt2500usb,rt73usb[/color]rt2x00lib              35408  3 [color=#FF0000]rt2500usb,rt73usb[/color],rt2x00usb
mac80211              266921  2 rt2x00usb,rt2x00lib
cfg80211              161097  2 rt2x00lib,mac80211
gameport               10470  2 emu10k1_gp

Now we wait...

Hoping those in red are the key to mirroring your success on standard kernels. EDIT: coloring didn't work too well, but you get my intent I hope

[kalinik]

Hoping those in red are the key to mirroring your success on standard kernels. EDIT: coloring didn't work too well, but you get my intent I hope

Yep ! I got it
Now i rebooted into 2.6.37.1-custom and "so far, so good" (for now).
Commented (#rt2500usb) in /etc/mmodprobe.d/blacklist.conf and added rt73usb (plus rt2500usb in new line) in /etc/modules
Now i have different errors from dmesg but no hangs for the moment:

usb 5-1: device descriptor read/64, error -62
[ 108.400066] usb 5-1: new low speed USB device using ohci_hcd and address 8
[ 108.820060] usb 5-1: device not accepting address 8, error -62
[ 108.990081] usb 5-1: new low speed USB device using ohci_hcd and address 9
[ 109.410034] usb 5-1: device not accepting address 9, error -62
[ 109.410067] hub 5-0:1.0: unable to enumerate USB device on port 1
[ 1090.576871] tcpdump uses obsolete (PF_INET,SOCK_PACKET)
[ 1145.300107] device wlan0 entered promiscuous mode
[ 1231.813540] device wlan0 left promiscuous mode
[ 1284.672777] UDP: bad checksum. From 113.14.136.210:16881 to 192.168.1.3:29118 ulen 106

[AlbertP]

I got this error when connecting a dead USB pendrive, but I don't think your USB WiFi is dead as it has worked fine with the stock kernel.

[kalinik]

No, the device is 100% fine and working. Runs fine with stock kernels on: Fedora 13 / Mint 10 & Debian Edition /Win7 / also tried it on Calculate Linux Live CD (gentoo based).
I have some good news here : Last night I configured this:

Post by kalinik on Mon Mar 07, 2011 10:28 pm
Now i rebooted into 2.6.37.1-custom and "so far, so good" (for now).
1) Commented (#rt2500usb) in /etc/mmodprobe.d/blacklist.conf and
2) added rt73usb (plus rt2500usb in new line) in /etc/modules
Now i have different errors from dmesg but no hangs for the moment...

This morning the PC was ALIVE !!! Maybe the change of rt73.bin in /lib/firmware from 'Debian squeeze' + iwconfig wlan0 power off + the 2 actions above = maybe solved the problem
I'll finish my work after 3 hours and will return home to continue testing.
No smiles before I'm 101% sure that it's fixed !

[kalinik]

So here is an update to the problem !

uptime && uname -a
19:56:00 up 23:19, 3 users, load average: 0.09, 0.15, 0.22
Linux hss13 2.6.37.1-hss #1 SMP Sat Feb 19 13:47:29 EET 2011 x86_64 GNU/Linux

It worked just perfect with custom kernel for a whole day !
But it freezed again 5 min. ago !

I found something very interesting that may help (I hope so)
Now:
i run modeinfo rt73usb with the 'stock' kernel 2.6.35-27-generic

modinfo rt73usb
filename: /lib/modules/2.6.35-27-generic/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
license: GPL
firmware: rt73.bin
description: Ralink RT73 USB Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
srcversion: 237B0124BEBB5CE00A44CEC
alias: usb:v0586p3415d*dc*dsc*dp*ic*isc*ip*
...
depends: rt2x00lib,rt2x00usb,crc-itu-t
vermagic: 2.6.35-27-generic SMP mod_unload modversions
parm: nohwcrypt:Disable hardware encryption. (bool)

That 'thing' crc-itu-t IS NOT loaded with NON-STOCK kernels !!!

Code: Select all

locate crc-itu-t.ko
/lib/modules/2.6.35-27-generic/kernel/lib/crc-itu-t.ko

As you can see - it's located ONLY on generic kernel tree


UPDATE: Here is the info about crc-itu-t.ko ... some 5 years ago: http://lkml.indiana.edu/hypermail/linux ... /2324.html

Now I have a question: How to load this crc-itu-t.ko with the custom kernel ??? I think that's the last problem...

[kalinik]

Hi... it's me again
After a month of trying and trying to resolve wireless issues I figured out what causes the real problem - it's due to these 2 modules crc_itu_t and led_class
I tried several non-stock kernels and found that they are not compiled at all, although i choose it from the 'menuconfig' ! Also I tried compiling vanilla kernels with "make oldconfig" and "make localmodconfig" based on Mint kernel 2.6.35-27-generic - these 2 modules didn't compile at all (and i don't know why !!!) - their sources are right in place but when the new vanilla kernel 2.6.38 is compiled:

>uname -r
2.6.38-lm1
> sudo updatedb
> locate led-class
/lib/modules/2.6.35-27-generic/kernel/drivers/leds/led-class.ko
/lib/modules/2.6.35-28-generic/kernel/drivers/leds/led-class.ko
>locate crc-itu
/lib/modules/2.6.35-27-generic/kernel/lib/crc-itu-t.ko
/lib/modules/2.6.35-28-generic/kernel/lib/crc-itu-t.ko

As you can see - the new kernel 2.6.38 is compiled and booted correc tly, but these modules are NOT
One thing I also noticed - there is /sys/class/leds/rt73usb and some files within that change dynamically only when booted into generic kernels !!!

Any help how to compile these modules with non-stock kernels would be the key to success... or some patching (but i don't know how to patch a kernel)

[AlbertP]

There has been some kind of 'reorganization' in the LED modules. LED's still work, those files aren't needed anymore with a 2.6.38 kernel.