Description of problem: Inserting my cisco aironet 350 pcmcia card into my sony vaio pcg-fx702 laptop causes the laptop to lock up immediately. The last entries in syslog are Apr 29 06:59:29 tux cardmgr[1154]: socket 0: 350 Series Wireless LAN Adapter Apr 29 06:59:29 tux kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Apr 29 06:59:29 tux kernel: airo: Probing for PCI adapters Version-Release number of selected component (if applicable): kernel-2.6.5-1.327 pcmcia-cs-3.2.7-1.5 How reproducible: 100% Additional info: I don't have any other pcmcia cards, so I don't know if this a pcmcia or airo problem. But pcmcia looks normal without any cards inserted. The same hardware works fine with FC1.
Seems to work now.
I just tried with kernel-2.6.6-1.427 and the problem persists. I noted that it will print "airo: cmd= 111" on the console as the last thing before it locks up.
I have the exact same problem with FC2 Final and kernel-2.6.6-1.435. If the card is inserted at boot time it will freeze at the pcmcia startup, if inserted later it will lockup instantly with the "airo: cmd= 111" message. This is also on Sony Vaio FX series hardware with a Cisco Aironet 350 PCMCIA card. Was working fine on FC1.
It might be futile to get any response on this, but since I keep trying new kernels I might as well report my findings in the hope that someone with better knowledge takes an interrest. Using kernel-2.6.7-1.494.2.2 the Aironet card appears to be working. But then the next test kernel, 2.6.8-1.520, results in a system freeze when loading the airo_cs module.
any improvement with the 2.6.9 based update ?
Not in my case at least. I don't know if I have a different problem though. It will power up, lock on to the signal and enable when inserted, but after an indeterminate period of time, it will lock hard and usually requires a reboot. It appears to be bandwidth related. I can run the card for days at a time with light traffic. Email and web type traffic doesn't seem to trigger the failure. If however I try and run a movie using X across the card or do a long sustained file transfer using any protocol, it will last a matter of minutes before locking up hard. I can sometimes get away with variations on: service pcmcia stop killall -9 cardmgr service pcmcia stop service network stop modprobe -r eth0 service network stop service pcmcia start service network start There may have to be a number of goes at some of the commands, and quite often they will lock, unkillable. Removing the card, once it's lights go off (not before) also seems to help get the module out of memory. Once the airo_cs module has been removed, the pcmcia and network services can be kicked back off again. The same hardware and OS, but with a 3Com wired 10/100 card in place of the wireless, can be pushed hard with no ill effects. - Dell Latitude CSx - 256M RAM Non of these kernels will drive this card safely on the above hardware. kernel-2.6.5-1.358 kernel-2.6.6-1.435.2.3 kernel-2.6.7-1.494.2.2 kernel-2.6.8-1.521 kernel-2.6.9-1.640 kernel-2.6.9-1.643 kernel-2.6.9-1.667 kernel-2.6.9-1.681_FC3
Similar here. The card kind of works with recent kernels, but it is unstable.
Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you.