Red Hat Bugzilla – Bug 122715
Airo_cs does not work after installation of Core 2 Test 3
Last modified: 2014-03-16 22:45:00 EDT
Description of problem:
Installed Core 2 test 3, using standard workstation option, on my IBM
Thinkpad T22, 40GB hard disk, 512MB Ram, Cisco 350 Wireless PCMCIA
card, not wired throught the built in network card. Installation was
successful, with no incidents.
After installation and reboot, network interfaces were eth0, eth1,
and wifi0. eth0 was the on board NIC, which is not plugged in. Lights
on the Cisco 350 card were not on. lsmod show the modules loaded. All
three show inactive.
Trying to activate the wifi0 and eth1 interfaces fails, and I cannot
activate the wireless.
Something is wrong with the configuration.
Version-Release number of selected component (if applicable):
Every time I install, I tried three times.
Steps to Reproduce:
1. Install Core 2 test 3
2. Look at network interfaces
3. Try to activate the wireless.
Wireless not working.
I was hoping that wireless would work. My Mandrake 9.2 installation
installs and works correctly, including the wireless.
What errors do you get?
Just installed Fedora Core 2 release. My Laptop has an internal nic
and a Cisco 350 wireless card. During installation the shown network
After installation, and the first reboot, the 350 lights the status
and activity lights never come on again.
Boot messages show, that eth0 failed because cable is not connected,
which is ok, and eth1 failed with message: "Bringing up eth1: airo_cs
device eth1 does not seem to be present, delaying initialization"
From System Settings->Network it shows all three as inactive, eth0,
eth1, and wifi0.
Trying to activate eth1 results in the same message as the boot
failed message for eth1 above.
Trying to activate wifi0 does nothing.
Sorry, I'm not very well versed in the configuration issues with
networking, so any pointers on what configuration files to change
would be helpful.
The alternative for me is to go back to Mandrake, which seems to
configure correctly for the Cisco card.
Additional information. As the lights to the 350 are not on, I might
suspect the pcmcia services. from init.d:
cardmgr is stopped
Starting PCMCIA services: cardmgr: no sockets found!
So for some reason I cannot start the pcmcia services.
I have cardmgr running now.
In /etc/rc5.d/ I moved "pcmcia" ahead of "network" in the numbering
scheme. We really do need pcmcia running for wireless cards and
pcmcia network cards.
Now the status and activity lights are going.
Re-configured my onboard ethernet, and the 350 wireless, and
everything seems to be working now. Sort of Trial and Error.
I am assuming just putting the pcmcia ahead of network in the init
scripts does the trick.
*** This bug has been marked as a duplicate of 121742 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.