I am running FC3 on an IBM T42 laptop. Early this morning I was running system-config-network to change some network settings. The system- config-network app became very erratic in it behavior so I had to kill its process. I next rebooted my machine (normaly less that a 1 minute process) and it took 19 minutes to reboot. After many hours of searching I found that I had a corrupted /etc/modprobe.conf file. I was 185 MB in size and full of gibberish.
My question is how can I regenerate a correct modprobe.conf file for my machine? Can I simply reinstall the package that creates it? (rpm -q --whatprovides /etc/modprobe.conf does not return anything), Are there scripts in place that recreate the file? (I did try running /sbin/generate-modprobe.conf but all it seems to want to do is convert a modules.conf file to a modprobe.conf file).
Thanks in advance for any help that you can provide.
Charlie
On Wed, Aug 03, 2005 at 08:56:11PM -0400, cmcveigh@adelphia.net wrote:
I am running FC3 on an IBM T42 laptop. Early this morning I was running system-config-network to change some network settings. The system- config-network app became very erratic in it behavior so I had to kill its process. I next rebooted my machine (normaly less that a 1 minute process) and it took 19 minutes to reboot.
Where was it spending most of its time ?
After many hours of searching I found that I had a corrupted /etc/modprobe.conf file. I was 185 MB in size and full of gibberish.
*wow*. That's disturbing. If you can repeat this, please file a bug against system-config-network
My question is how can I regenerate a correct modprobe.conf file for my machine? Can I simply reinstall the package that creates it? (rpm -q --whatprovides /etc/modprobe.conf does not return anything), Are there scripts in place that recreate the file? (I did try running /sbin/generate-modprobe.conf but all it seems to want to do is convert a modules.conf file to a modprobe.conf file).
rm -f /etc/modprobe.conf rm -f /etc/sysconfig/hwconf kudzu
should get you a recreated modprobe.conf
Dave
On Wed, 2005-08-03 at 21:07 -0400, Dave Jones wrote:
After many hours of searching I found that I had a corrupted /etc/modprobe.conf file. I was 185 MB in size and full of gibberish.
*wow*. That's disturbing. If you can repeat this, please file a bug against system-config-network
I wasn't ever able to reproduce it (fortunately or unfortunately), but I've had the same thing happen to me once using one of the system-config tools (I *think* it was network). Each line in modprobe.conf was repeated over and over again. Every line in the file ended up like this:
alias eth0 8139tooalias eth0 8139tooalias eth0 8139tooalias eth0 8139[... and so on for about ten megabytes or so]
Symptom on boot was the same thing as the original poster mentioned - extremely long boot time. Opening up modprobe.conf in joe (emacs barfed on the file) and just deleting the repetitions fixed things.
Charles E. "Rick" Taylor, IV wrote:
On Wed, 2005-08-03 at 21:07 -0400, Dave Jones wrote:
After many hours of searching I found that I had a corrupted /etc/modprobe.conf file. I was 185 MB in size and full of gibberish.
*wow*. That's disturbing. If you can repeat this, please file a bug against system-config-network
I wasn't ever able to reproduce it (fortunately or unfortunately), but I've had the same thing happen to me once using one of the system-config tools (I *think* it was network). Each line in modprobe.conf was repeated over and over again. Every line in the file ended up like this:
alias eth0 8139tooalias eth0 8139tooalias eth0 8139tooalias eth0 8139[... and so on for about ten megabytes or so]
Symptom on boot was the same thing as the original poster mentioned - extremely long boot time. Opening up modprobe.conf in joe (emacs barfed on the file) and just deleting the repetitions fixed things.
Maybe an application needs to be setup to handle interfacing with /etc/modprobe.conf by other applications in a more safe way.
-
Arthur Pemberton -
Charles E. "Rick" Taylor, IV -
Charlie McVeigh -
Dave Jones