[SOLVED-ish] Wifi conx not retained over reboot - in periods...

[Hootiegibbon]

Cj

Can you post the results of the frolowing in a terminal

lspci
ifconfig (may need to su to root on this if its not in your $PATH)
iwconfig (as above)
 
Jase

[CJ]

** All, please note that a few things need to be made clear as things have changed slightly since my last post here some weeks ago:
1. Due to this and other issues, I did a re-install (retaining my /home partition, though). Things did not improve, save for:
2. All I have to do now, in order to get the card working on KDE start-up, is simply to, as root, issue the command 'modprobe -r rt61pci', and the card connects.
Beware, though, before you come to the conclusion that it is the rt61pci driver that stands in the way, that it seems to reload that same driver (according to PCC->Hardware) automatically and then connect.
**

apparently there are two driver available for your card (ralink rt61 chipset): rt61pci (also called Legacy), and a new rt2x00pci
http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page

the rt2x00pci is available with PCLinuxOS kernel 2.6.33.7 and with kernel 2.6.38.8 (I have this two installed on my system), so I think is available with any kernel from 2.6.33.7 up the the current.

Worth to try if the new driver may work better, then may be you need to blacklist the rt61pci and manually load the rt2x00pci.
If something is not clear please ask.

AS, I wasn't even remotely aware that this was the case! I have searched on the card and all references I have found have always been to the rt61pci. As I am far from the only one that have had issues with this driver, this is indeed good news! I shall try to follow your advice and post back. I might indeed need some help along the way, but I shall give it a shot. Thank you so much for this info!

Regarding the 3 previous cards, did you ever remove the config for those cards from PCC?

Jase, I did indeed, thank you. As per my note above, it has become a moot point in the meantime, though...

This sounds like a driver conflict. You might want to try blacklisting all wireless modules and then enabling only one for installation at boot.

If AS' advice above does not work, I shall try this approach. I might need to ask a little help to locate all the drivers I need to blacklist. I shall ask if and when it becomes necessary. Thanks.


Jase, as per your request (all as root):

Code: [Select]

lspci
00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d4)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 04)
00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce GTS 250] (rev a2)
02:00.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 61)
02:02.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
02:03.0 Multimedia audio controller: Creative Labs CA0106 Soundblaster

Code: [Select]

ifconfig
    [...]
          wlan0     Link encap:Ethernet  HWaddr 48:5B:39:BE:09:7D
          inet addr:192.168.1.104  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::4a5b:39ff:febe:97d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1872 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2073 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:694195 (677.9 KiB)  TX bytes:401081 (391.6 KiB)

Code: [Select]

iwconfig
    [...]
          wlan0     IEEE 802.11bg  ESSID:"doghouse"
          Mode:Managed  Frequency:2.467 GHz  Access Point: 00:1A:4D:21:82:8C
          Bit Rate=54 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=56/70  Signal level=-54 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:259   Missed beacon:0
Again, thank you all for taking the time and making your knowledge available to me! Much appreciated!
CJ

[mikkl]

If you do decide to try blacklisting, be certain to review /etc/modprobe.preload as modules listed here are loaded before the blacklist(s) are used, based on some other threads I have been reading recently.

mikkl

[CJ]

Ok, I am making a dog's meal out of this and need some help.

I am trying to follow AS' advice and use the newer driver for my card.
I have blacklisted rt61pci, and the machine starts up without connecting (but that is hardly a difference since that is how it has behaved so far).
When I check the card in PCC->Hardware, it still says module rt61pci.

I then do a 'modprobe rt2x00pci', and nothing happens.

Something slightly weird that I have also noticed:
If I do a 'rmmod rt61pci', fine and the connection stays inactive.
If, on the other hand, I do a 'modprobe -r rt61pci', the connection activates and come on (this is not new).
Maybe I just don't understand the difference between the two, but I thought they did the same thing?

Anyway, here is what the modules look like after the 'blacklist rt61pci' and 'modprobe rt2x00pci':

Code: [Select]

lsmod | grep rt
rt61pci                18270  0
rt2x00pci               4034  1 rt61pci
rt2x00lib              27180  2 rt61pci,rt2x00pci
mac80211              189461  2 rt2x00pci,rt2x00lib
cfg80211              126787  2 rt2x00lib,mac80211
eeprom_93cx6            1052  1 rt61pci
iTCO_vendor_support     1585  1 iTCO_wdt
crc_itu_t               1103  2 rt61pci,firewire_core
parport_pc             28023  0
parport                25179  2 ppdev,parport_pc

Code: [Select]

rmmod rt2x00pci
ERROR: Module rt2x00pci is in use by rt61pci
Seems that one is tagging onto the other...?

Cheers!
CJ

[AS]

Hi CJ,

try to blacklist the module: add the following line to /etc/modprobe.d/blacklist:
blacklist rt61pci

additionally, check in file /etc/modprobe.conf and /etc/modprobe.preload about reference to rt61pci, if you will find references, delete them from both files.

then reboot and retry to config your connection.

AS

[mikkl]

Hi CJ,

try to blacklist the module: add the following line to /etc/modprobe.d/blacklist:
blacklist rt61pci

additionally, check in file /etc/modprobe.conf and /etc/modprobe.preload about reference to rt61pci, if you will find references, delete them from both files.

then reboot and retry to config your connection.

AS

Can you comment out the lines of interest instead of deleting?  Yes, this adds bloat to the files, but it also makes it easier to go back.

mikkl

[CJ]

Hi CJ,

try to blacklist the module: add the following line to /etc/modprobe.d/blacklist:
blacklist rt61pci

additionally, check in file /etc/modprobe.conf and /etc/modprobe.preload about reference to rt61pci, if you will find references, delete them from both files.

then reboot and retry to config your connection.

AS, that was exactly what I was doing, but I did it a few times again - no improvement.

Can you comment out the lines of interest instead of deleting?  Yes, this adds bloat to the files, but it also makes it easier to go back.

Fair point, but not to worry, there is nothing to remove.


Ok, here is what happens with the module blacklisted:
As before, the connection does not come on by itself.

1. When setting up the connection in PCC, I get as far as choosing the card and clicking next. That seems to load the module (I can only assume rt61pci) and the connection starts up (before I actually finish the wizard).
I have tried finishing it, and I have tried leaving it, and rebooting - it still won't stick.

2. Refreshing the station list in Network Manager, again, seemingly loads the module and the connection comes up without me having to manually selecting a station to connect to.

In other words, it knows what connection I want, but needs the module to load at a much later stage, for some reason.
I know it sounds weird - this whole issue is getting weird! - but... it seems like the first instance of loading rt61pci (which, of course, does not happen when it is blacklisted) it not good enough. Only by loading it a second time will make it happy...

I am sorry, I don't know what further information I can provide... sigh....

Cheers!
CJ

[AS]

1. When setting up the connection in PCC, I get as far as choosing the card and clicking next. That seems to load the module (I can only assume rt61pci) and the connection starts up (before I actually finish the wizard).
I have tried finishing it, and I have tried leaving it, and rebooting - it still won't stick.

did you manually loaded the rt61pci module ?
when the connection is established, can you check (and post) the output of lsmod | grep rt ?
other than not sticking at reboot, once the connection is up is it stable ?

AS

[CJ]

did you manually loaded the rt61pci module ?

No. As per above, all I have to do is start the PCC Network wizard, choose the card - at that point the connection becomes active and connects. I guess the module is loaded then.

when the connection is established, can you check (and post) the output of lsmod | grep rt ?

Code: [Select]

rt61pci                18270  0
rt2x00pci               4034  1 rt61pci
rt2x00lib              27180  2 rt61pci,rt2x00pci
mac80211              189461  2 rt2x00pci,rt2x00lib
cfg80211              126787  2 rt2x00lib,mac80211
eeprom_93cx6            1052  1 rt61pci
iTCO_vendor_support     1585  1 iTCO_wdt
crc_itu_t               1103  2 rt61pci,firewire_core
parport_pc             28023  0
parport                25179  2 ppdev,parport_pc

other than not sticking at reboot, once the connection is up is it stable ?

Yes, it is working just fine!

CJ

[CJ]

Just for the shell of it, I tried combining the blacklisting of rt61pci with sticking a 'modprobe rt61pci' in rc.local - and so far, it seems to take it!
I know it's a kludge, and doesn't really tell us what is the root of the issue, but apart from working (I have to reboot a few more times to see if it lasts), it might tell us something about the cause...?

Cheers!
CJ

[AS]

the dependencies of the rt61pci modules are as follows:

# modprobe --show-depends rt61pci
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/drivers/misc/eeprom/eeprom_93cx6.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/net/rfkill/rfkill.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/net/wireless/cfg80211.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/net/mac80211/mac80211.ko.gz ieee80211_default_rc_algo=pid
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/drivers/net/wireless/rt2x00/rt2x00pci.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/lib/crc-itu-t.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/drivers/net/wireless/rt2x00/rt61pci.ko.gz

as far as I can see this configuration match your lsmod output .... (but this is my system)

try the following command on your system:

modprobe --show-depends rt61pci

[CJ]

* EDIT: The below is when the conx is working. I shall get you a non-working for comparison a little later. *

Here you go, AS:

Code: [Select]

modprobe --show-depends rt61pci
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/drivers/misc/eeprom/eeprom_93cx6.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/net/rfkill/rfkill.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/net/wireless/cfg80211.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/net/mac80211/mac80211.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/drivers/net/wireless/rt2x00/rt2x00pci.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/lib/crc-itu-t.ko.gz
insmod /lib/modules/2.6.38.8-pclos1.bfs/kernel/drivers/net/wireless/rt2x00/rt61pci.ko.gz
The only difference I see:
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/net/mac80211/mac80211.ko.gz ieee80211_default_rc_algo=pid

CJ

[AS]

The only difference I see:
insmod /lib/modules/2.6.38.8-pclos1.pae.bfs/kernel/net/mac80211/mac80211.ko.gz ieee80211_default_rc_algo=pid

Sorry, forget about and ignore ieee80211_default_rc_algo option, I have changed it at some point because of a specific issue related to my wireless iwl3945.
Also, don't need you repeat the command when connection is not working, it's output will not change, instead post the output of lsmod | grep rt at time of non working connection. (already there, in previous post.)

[CJ]

Sorry, forget about and ignore ieee80211_default_rc_algo option, I have changed it at some point because of a specific issue related to my wireless iwl3945.
Also, don't need you repeat the command when connection is not working, it's output will not change, instead post the output of lsmod | grep rt at time of non working connection. (already there, in previous post.)

Ok, thanks for that.

So... at present I have rt61pci blacklisted, only to be modprobed later in rc.local - and it works (a tiny bit slow, insofar as it starts up with the desktop only, i.e. take about 10 secs after full desktop).
Do we consider that a solution or do we dig deaper? Myself, I am not sure... thoughts?

CJ

[muungwana]

There are solutions and there are work arounds . This is a work around and it is up to you if you live with it.

can you live with that tiny bit of slowness? If it works consistently and the delay is tolerable then i think you should stick with it.

If you have time and want to play around and learn a little bit more then you can look into it later. How much time you want to spend on this is really on you.