PCMCIA Fedora Core 2 problem fixed!

(this article has moved here)

Yesterday I upgraded the Fedora on the notebook (Acer TM 202). The new linux kernel was 2.6.6. Surpsingly, after the reboot PCMCIA networking stopped. There was an error about eth0 not being present (because PCMCIA was loaded after the networking), and that’s it – it was not getting online after loadig of the PCMCIA.

Before (in Core 1) the behavior was the same, but after PCMCIA loading it was somehow working – it seems it was detecting/raising the eth0! Now it was refusing to do so. And I had to look for another solution.

I checked the Google – nothing special :(. Similar problems, lots of results (more than 5000), but no straight solution for my problem (logically: Fedora Core 2 was only 5 days old).

I started to solve the problem manually, and after:

rmmod 3c509_cs
rmmod ds
/etc/init.d/pcmcia restart

it went fine! HELL! It seemed that the eth0 failure (when PCMCIA driver was not yet present) was locking something, which ruined the success of any future network driver loading.

I decided to ask LUG-Bulgaria. After one hour maximum I received a valuable answer from Peter Georgiev, who told me to switch the PCMCIA loading priority from 24 (current) to 9 (higher than the networking). His precise instructions were:

  1. Open /etc/init.d/pcmcia
  2. Change the line
    # chkconfig: 2345 24 96


    # chkconfig: 2345 09 96

    Yes, it’s in a comment, but it seems it has meaning to the chkconfig command (see below).

  3. Execute
    chkconfig --level 2345 pcmcia reset

After these changes, PCMCIA executes before my network, and all works.

I am still wondering if that solution is correct. Maybe we just killed the resulting symptom, not the real problem, but it works for now. I do not hear the standart “beep beep” when my PCMCIA gets up, and I do not hear it when I remove/insert a card. But I can live with that.

Please, if someone reads this, and if this someone has another explanation of my problem – I will be really curious to hear it. It seems that the problem is somewhere in the newer kernel modules, but… I am yet too lame to find and resolve it. I miss the old way, but the newer kernel is more important than it.

14 thoughts on “PCMCIA Fedora Core 2 problem fixed!

  1. I installed the standard fedora 2 core and also don’t get any beep beep for pcmcia card insert/remove. The problem however is not with that but terminal beeps in general, echo ctr-G characters to a terminal window also does not sound the bell. Nor do I get any sound from modem initializtion as I should.

    On the other hand normal ASLA sound works fine!

    Have you discovered any more?

  2. Nope. Anyway – this seems not to be so big problem for me.
    However, if you have some success, I will be very glad to update this aticle.

  3. You just solved the problem that has been slowly breaking my sanity.
    …and such a simple fix.
    Thank you, you are the man.

  4. i just had the same problem. first of all the pcmcia service didn’t even seem to be running, and it needed the command:

    /sbin/modprobe yenta-socket; service pcmcia restart

    to get it going and the lights on the cards flashing. i eventually got it to work by changing the order for starting the services, but i did it by moving the ‘network’ service forward from 10 to 27 – moving a service backwards in the list might cause it not to see services it’s dependent on b/c they haven’t started yet, and i think this is a reported problem for some people. i was then able to go into system-control-network as root user and configure, add my modem, etc. it all works fine now.

    i don’t get beeps related to inserting pcmcia cards but i didn’t under rh9 either.

  5. Thank you for documenting your PCMCIA FC2 solution. It worked perfectly.

    I’m really surprised FC2 made it out with this problem. I guess nobody tested on a laptop?

  6. Thanks very much….just installed core 2 and had the same problem….your fix worked great.
    thanks again…

  7. Thanks! I struggled with this all day yesterday until I found this link. Rebooted and worked fine.

  8. Thank you! Thank you! It was so frustrating to see the problem happening (during boot-up) and not know how to fix it. I had tried several “fixes” mentioned on several different forums, none of them worked in my case. The fix mentioned above worked perfectly for me. And just for anyone caring on my particular setup: I have a Panasonic Toughbook CF-37, Fedora Core 2, and a Lucent Orinoco wireless PCMCIA card. – Nice work, donangel, thanks for sharing!

  9. It’s not necessary to change the loading priority. The fix is to remove the “alias eth0” line from your modprobe.conf file. See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id121742

    For console beeps you have to have the pcspkr module loaded – it’s as simple as that (when you know how) but I’m not sure how you are meant to find out about it unless you are recompiling your kernel.

  10. I did a modeprobe yenta_socket; pcmcia restart. It worked..but not after rebooting. This solution was all that it needed. Well done guys.

Leave a Reply

Theme: Overlay by Kaira Extra Text
%d bloggers like this: