Latest kernel from Current, no wireless even though modules loaded

vdemuth · 05-09-2009, 09:47 AM

Just upgraded my kernel to the one in Slackware current using slackpkg. Kernel ref 2.6.29.2.
Now I have no wireless using my laptops ralink wireless link. Normally uses the rt2500pci driver, which lsmod shows is installed. But an iwlist scan gives no results.

The problem of course with doing a kernel upgrade using this method, is that the original working kernel gets deleted, along with all of the sources and support libraries.

Fortunately, I also have a PCMCIA wireless adapter that uses the bc43 drivers, so at least I can get on using that.

So, how do I get the ralink drivers to work again, or is this a case of having to go back to the previous kernel?

For information, ifconfig shows wlan0 interface. iwconfig shows wlan0 interface, but scanning gives no scan results.

C-Sniper · 05-10-2009, 09:54 AM

try hitting the wirless button on your laptop. Mine has a problem to where it will bring up the interfaces even though the button is presses. The worse part is that my LED still lights up so I can never tell.

run iwlist -scanning
If there are no results, try hitting the button and running the command again.

vdemuth · 05-11-2009, 02:08 AM

Tried that, same result. So I downloaded the kernel source from kernel.org, and compiled my own. Still the same result. Fortunately, rolling back to the stock Slackware 12.2 kernel gets it working again.
It seems then that kernel 2.6.29.2 under Slackware doesn't support Ralink wireless devices. So, do I submit a bug report to PV, or the the kernel maintainers?

onebuck · 05-11-2009, 06:31 AM

Hi,

You are running '-current' as your install?

rworkman · 05-11-2009, 08:15 AM

No, don't report a bug. You installed the kernel from -current onto a 12.2 system, so while it *may* be a bug, it's not in a configuration that is *expected* to work, so it's not supported at all. In other words, your report will be ignored, because *nobody* is expected to be running that combination.

vdemuth · 05-11-2009, 09:13 AM

My apologies,

For information, I am running current, including the latest KDE4. So with the stock 12.2 Kernel, wireless is fine, but with the 'current' kernel, no wireless.

rworkman · 05-11-2009, 09:46 AM

Okay, in that case, perhaps there is a problem :-)
It's possible that the device is supported by a different driver in the 2.6.29.x series; I don't have any of that hardware, so I don't know one way or the other. Maybe someone who does will jump in, or perhaps some web searches for your hardware with "2.6.29" as a query will result in something useful...

vdemuth · 05-12-2009, 02:36 AM

Solved this.

It turns out that the new kernel didn't like the order the modules were loaded in. Moved the rt2500pci module load position to be the very last module loaded prior to starting the X server (by placing in rc.local), and it now works again.
Don't understand why this should be, but hey, it did the trick.

rworkman · 05-12-2009, 08:16 AM

Quote:

Originally Posted by vdemuth

It turns out that the new kernel didn't like the order the modules were loaded in. Moved the rt2500pci module load position to be the very last module loaded prior to starting the X server (by placing in rc.local), and it now works again.
Don't understand why this should be, but hey, it did the trick.

Okay, that's interesting news. Can you paste the output of "lsmod" into this thread? I'd like to investigate that...

vdemuth · 05-12-2009, 08:45 AM

Certainly I can do that. Here goes:

Quote:

Module Size Used by
rt2500pci 14844 0
rt2x00pci 7804 1 rt2500pci
rt2x00lib 28892 2 rt2500pci,rt2x00pci
rfkill 10416 2 rt2x00lib
mac80211 166176 2 rt2x00pci,rt2x00lib
cfg80211 37236 2 rt2x00lib,mac80211
eeprom_93cx6 1948 1 rt2500pci
vboxnetflt 84808 0
vboxdrv 112200 1 vboxnetflt
tifm_sd 9604 0
ipaq 31856 0
usbserial 31272 1 ipaq
snd_seq_midi 5888 0
snd_rawmidi 21280 1 snd_seq_midi
ppp_generic 23228 0
slhc 6364 1 ppp_generic
snd_seq_dummy 2496 0
snd_seq_oss 29216 0
snd_seq_midi_event 6972 2 snd_seq_midi,snd_seq_oss
snd_seq 47536 6 snd_seq_midi,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6728 5 snd_seq_midi,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37632 0
snd_mixer_oss 14268 1 snd_pcm_oss
ipv6 250868 23
fuse 54488 3
snd_hda_codec_si3054 4476 1
snd_hda_codec_realtek 189760 1
snd_hda_intel 23336 3
snd_hda_codec 61532 3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6880 1 snd_hda_codec
snd_pcm 74340 4 snd_pcm_oss,snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec
ohci_hcd 25196 0
sdhci_pci 6844 0
snd_timer 20608 2 snd_seq,snd_pcm
sdhci 15872 1 sdhci_pci
snd 56900 19 snd_rawmidi,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_si3054,snd_hd a_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ehci_hcd 35336 0
rtc_cmos 10476 0
yenta_socket 23848 1
mmc_core 49520 2 tifm_sd,sdhci
thermal 15192 0
processor 35116 2 thermal
ssb 40992 1 ohci_hcd
uli526x 15756 0
tifm_7xx1 5628 0
pcmcia 34304 1 ssb
ohci1394 30380 0
rsrc_nonstatic 10780 1 yenta_socket
k8temp 4188 0
thermal_sys 11516 2 thermal,processor
rtc_core 17492 1 rtc_cmos
led_class 3872 2 rt2x00lib,sdhci
rtc_lib 2844 1 rtc_core
psmouse 41196 0
i2c_ali1535 5664 0
i2c_ali15x3 6208 0
soundcore 7072 1 snd
snd_page_alloc 8644 2 snd_hda_intel,snd_pcm
tifm_core 7568 2 tifm_sd,tifm_7xx1
ieee1394 85916 1 ohci1394
serio_raw 5056 0
pcmcia_core 35244 4 yenta_socket,ssb,pcmcia,rsrc_nonstatic
hwmon 2384 2 k8temp,thermal_sys
button 5804 0
battery 10016 0
ac 3936 0
evdev 9216 5
i2c_core 23500 2 i2c_ali1535,i2c_ali15x3
ati_agp 6664 0
agpgart 33580 1 ati_agp

rworkman · 05-12-2009, 09:11 AM

Okay, here's the important part:

Code:

Module         Size      Used by
rt2500pci      14844     0
rt2x00pci      7804      1 rt2500pci
rt2x00lib      28892     2 rt2500pci,rt2x00pci
rfkill         10416     2 rt2x00lib
mac80211       166176    2 rt2x00pci,rt2x00lib
cfg80211       37236     2 rt2x00lib,mac80211
eeprom_93cx6   1948      1 rt2500pci

Now what I'd like to see is how that's different when you <b>don't</b> load the rt2500pci module in rc.local -- in other words, let the system do everything on its own.

Looking at the module dependencies, I don't see how it could be any different -- the deps look like they should handle everything correctly -- but we'll see.

vdemuth · 05-12-2009, 10:20 AM

If I comment out the rt2500pci module, I get no wireless anyway, as it is blacklisted in /etc/modprobe.d/blacklist. This means there are no wireless modules loaded at all.

With the default kernel that comes with Slackware 12.2, I could modprobe rt2500pci anywhere in my rc.local, set the speed and away it just work. Now I have to modprobe it after everything else, or it seems not to work. To the point that I have to also run the following tiny script when using the wicd network manager

Code:

#!/bin/bash
# Shell wrapper that calls iwconfig using sudo
sudo /sbin/rmmod rt2500pci
sudo /sbin/modprobe rt2500pci
sudo /sbin/iwconfig wlan0 rate 54M

FYI, I am currently having to use my external Linksys cardbus adapter as the rt2500pci isn't loaded, as the snippet below would confirm.

Code:

Module                  Size  Used by
rfkill_input            5532  0      
b43                   127512  0      
rfkill                 10416  3 rfkill_input,b43
mac80211              166176  1 b43             
cfg80211               37236  2 b43,mac80211    
input_polldev           3620  1 b43

I could of course modprobe the rt2500pci module manually, but that sort of defeats the object

Thanks for the input on this, will be good to find out what's going on.

rworkman · 05-12-2009, 10:39 AM

Ah... that module shouldn't be blacklisted any more. I'm not sure when it was last done in Slackware, but it wasn't in the stock 12.2 configs, and it isnt' in the -current ones either.

Try removing it from the blacklist see what happens.

vdemuth · 05-12-2009, 01:26 PM

OK, done that, and the modules now get loaded on bootup as expected, but in the middle of the list when running lsmod thus:

Code:

Module                  Size  Used by            
vboxnetflt             84808  0                  
vboxdrv               112200  1 vboxnetflt       
snd_seq_midi            5888  0                  
snd_rawmidi            21280  1 snd_seq_midi     
ppp_generic            23228  0                  
slhc                    6364  1 ppp_generic      
snd_seq_dummy           2496  0                  
snd_seq_oss            29216  0                  
snd_seq_midi_event      6972  2 snd_seq_midi,snd_seq_oss
snd_seq                47536  6 snd_seq_midi,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event                                                                       
snd_seq_device          6728  5 snd_seq_midi,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq                                                                      
snd_pcm_oss            37632  0                                                 
snd_mixer_oss          14268  1 snd_pcm_oss                                     
ipv6                  250868  23                                                
fuse                   54488  3                                                 
snd_hda_codec_si3054     4476  1                                                
snd_hda_codec_realtek   189760  1                                               
snd_hda_intel          23336  3                                                 
ohci_hcd               25196  0                                                 
snd_hda_codec          61532  3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel                                                                        
snd_hwdep               6880  1 snd_hda_codec                                   
ssb                    40992  1 ohci_hcd                                        
snd_pcm                74340  4 snd_pcm_oss,snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec                                                                    
snd_timer              20608  2 snd_seq,snd_pcm                                 
thermal                15192  0                                                 
rt2500pci              14844  0                                                 
rt2x00pci               7804  1 rt2500pci                                       
rt2x00lib              28892  2 rt2500pci,rt2x00pci                             
rfkill                 10416  2 rt2x00lib                                       
mac80211              166176  2 rt2x00pci,rt2x00lib                             
sdhci_pci               6844  0                                                 
tifm_7xx1               5628  0                                                 
ohci1394               30380  0                                                 
sdhci                  15872  1 sdhci_pci                                       
i2c_ali1535             5664  0
yenta_socket           23848  1
rsrc_nonstatic         10780  1 yenta_socket
pcmcia                 34304  1 ssb
snd                    56900  19 snd_rawmidi,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
processor              35116  2 thermal
cfg80211               37236  2 rt2x00lib,mac80211
eeprom_93cx6            1948  1 rt2500pci
uli526x                15756  0
i2c_ali15x3             6208  0
pcmcia_core            35244  4 ssb,yenta_socket,rsrc_nonstatic,pcmcia
k8temp                  4188  0
soundcore               7072  1 snd
snd_page_alloc          8644  2 snd_hda_intel,snd_pcm
mmc_core               49520  1 sdhci
rtc_cmos               10476  0
rtc_core               17492  1 rtc_cmos
rtc_lib                 2844  1 rtc_core
thermal_sys            11516  2 thermal,processor
hwmon                   2384  2 k8temp,thermal_sys
ati_agp                 6664  0
i2c_core               23500  2 i2c_ali1535,i2c_ali15x3
battery                10016  0
ac                      3936  0
ieee1394               85916  1 ohci1394
button                  5804  0
tifm_core               7568  1 tifm_7xx1
ehci_hcd               35336  0
psmouse                41196  0
agpgart                33580  1 ati_agp
led_class               3872  2 rt2x00lib,sdhci
serio_raw               5056  0
evdev                   9216  5
vic@captainpugwash:/usr/src/linux-2.6.25.9$

And now there is no response I get is:

Code:

bash-3.1# iwlist scan                         
lo        Interface doesn't support scanning. 

eth0      Interface doesn't support scanning.

vboxnet0  Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     No scan results

So, I do an rmmod rt2500pci and a modprobe rt2500pci, then scanning works once and gives results as expected. Any subsequent scan gives no result, so I have to do the rmmod/modprobe again. Hence the reason for the short script when using wicd.

Blacklisting and loading manually via rc.local works, but still needs the short script shown above.

I have found out though, that if I modprobe it in rc.M just prior to the wicd daemon loading, then I can remove my short script from the wicd gui and scanning works consistantly

rworkman · 05-12-2009, 02:22 PM

Quote:

Originally Posted by vdemuth

OK, done that, and the modules now get loaded on bootup as expected, but in the middle of the list when running lsmod thus:

Code:

Module                  Size  Used by                                            

rt2500pci              14844  0                                                 
rt2x00pci               7804  1 rt2500pci                                       
rt2x00lib              28892  2 rt2500pci,rt2x00pci                             
rfkill                 10416  2 rt2x00lib                                       
mac80211              166176  2 rt2x00pci,rt2x00lib


cfg80211               37236  2 rt2x00lib,mac80211
eeprom_93cx6            1948  1 rt2500pci

And now the response I get is:

Code:

wlan0     No scan results

So, I do an rmmod rt2500pci and a modprobe rt2500pci, then scanning works once and gives results as expected. Any subsequent scan gives no result, so I have to do the rmmod/modprobe again. Hence the reason for the short script when using wicd.

Blacklisting and loading manually via rc.local works, but still needs the short script shown above. I have found out though, that if I modprobe it in rc.M just prior to the wicd daemon loading, then I can remove my short script from the wicd gui and scanning works consistently

Wow. I have no idea what's going on here. It appears as if something isn't "ready" yet when the rt2500pci module is loaded by udev (as evidenced by the point you make about loading it in rc.M). Ultimately, I think you need to mail the rt2500 guys about this (link this thread to them, and CC me on the email); maybe they'll have some insight...