Journal Journal: Fixing Redhat eth0/pcmcia Bootup Problem
A few weeks ago I installed Redhat 8.0 on my trusty IBM T20 laptop. For the most part the installation has been problem-free.
One of the more annoying little quirks was that at bootup I could see that the network initialization of the eth0 device was failing. The network would be fine once it was booted. Not that it's a big deal, but you just hate to see that big red [FAILED] every time you boot your machine.
It all came to a head when I wanted to add a Samba share and have it auto-mount at bootup. This wouldn't work and I knew that it was because of this bootup problem.
After some digging on Google I found the fix. I'm still not clear if this is a Redhat thing or a general Linux problem.
Regardless, the problem is that the network devices are initialized before the PCMCIA devices, and if your network card is a PCMCIA card, then you'll have the same problem I have.
So to fix it you have to rename several startup scripts in several run level directories. Pretty annoying. In case I do some Redhat upgrade and it overwrites these new names, I wrote a little shell script to take care of it.
Here's the script to save yourself some time. I make no warranty, this is guaranteed to work on my laptop that I installed and nothing else. If you use this script, it will likely cause your entire network to erupt in flames. This script has been known to randomly beat up small children.
One of the more annoying little quirks was that at bootup I could see that the network initialization of the eth0 device was failing. The network would be fine once it was booted. Not that it's a big deal, but you just hate to see that big red [FAILED] every time you boot your machine.
It all came to a head when I wanted to add a Samba share and have it auto-mount at bootup. This wouldn't work and I knew that it was because of this bootup problem.
After some digging on Google I found the fix. I'm still not clear if this is a Redhat thing or a general Linux problem.
Regardless, the problem is that the network devices are initialized before the PCMCIA devices, and if your network card is a PCMCIA card, then you'll have the same problem I have.
So to fix it you have to rename several startup scripts in several run level directories. Pretty annoying. In case I do some Redhat upgrade and it overwrites these new names, I wrote a little shell script to take care of it.
Here's the script to save yourself some time. I make no warranty, this is guaranteed to work on my laptop that I installed and nothing else. If you use this script, it will likely cause your entire network to erupt in flames. This script has been known to randomly beat up small children.
#!/bin/sh
#rc0
mv/etc/rc.d/rc0.d/K96pcmcia /etc/rc.d/rc0.d/K89pcmcia
#rc1
mv/etc/rc.d/rc1.d/K96pcmcia /etc/rc.d/rc1.d/K89pcmcia
#rc2
mv/etc/rc.d/rc2.d/S10network /etc/rc.d/rc2.d/S11network
mv/etc/rc.d/rc2.d/S24pcmcia /etc/rc.d/rc2.d/S10pcmcia
#rc3
mv/etc/rc.d/rc3.d/S10network /etc/rc.d/rc3.d/S11network
mv/etc/rc.d/rc3.d/S24pcmcia /etc/rc.d/rc3.d/S10pcmcia
#rc4
mv/etc/rc.d/rc4.d/S10network /etc/rc.d/rc4.d/S11network
mv/etc/rc.d/rc4.d/S24pcmcia /etc/rc.d/rc4.d/S10pcmcia
#rc5
mv/etc/rc.d/rc5.d/S10network /etc/rc.d/rc5.d/S11network
mv/etc/rc.d/rc5.d/S24pcmcia /etc/rc.d/rc5.d/S10pcmcia
#rc6
mv/etc/rc.d/rc6.d/K96pcmcia /etc/rc.d/rc6.d/K89pcmcia
