modules.config QUESTION !!!
 

HI Guys,

I have made a silly mistake and I
do not know how to correct it.

I was configuring my sound card and
it did not work. I have copied some
modules.conf file from the internet
and modified it accordingly.

After that I am not able to boot.
The system boots ( after GRUB screen
and mounting disk...etc, loading modules
Loads the sound module and hangs.

I have to modify my moduels.config
file or remove it, for the system to
boot up clean.

I tried to enter in single user mope,
linux rescue, Interactive but still
the boot hangs and is still loading
the sound module.

How do i repair it......

thank you very much in advance,
- Srivamsi.

Did you create a rescue disk or has that already been tried? Only other risky thing you could try is getting a program like explore2fs or LTools. If you have windows that is, you can get into your linux partition and edit the file, MAYBE! The 'write' part of read-write access with these programs is warned against and that it could crap things out. That's why I say risky. So hopefully you have a boot disk. Sorry I can't think of anything else at the moment.

Try getting into single user mode again, but use this command linux single int=/bin/bash .

The problem you're having is that it tries to load a bad module on init, so the kernel has booted properly, its just ramming a module in there that you don't want it to. A good answer is: boot a different kernel. If your machine is formatted for the ext2 filesystem, i.e. a distro before RedHat 7.2 and before Mandrake 8.1, then try tomsrtbt , an entire distro that fits on a 3.5 and loads into RAM. After it loads you can mount the filesystem of your distro with:

mount /dev/hdx1 /mnt (where x is the drive letter, usually 'a')

then:

cd /mnt/etc (and either rm modules.conf, or edit it with vi, if you know vi, or just mv the file somewhere else so you can edit it when you boot back into your machine.

If you have ext3 or reiserfs as your file system, you could make a copy of the bare.i disk from Slackware8.0 with RAWRITE from a Windows box and just try the same trick. This is technically the first disk for installing Slackware, but it works great as a system rescue disk for the new filesystems. It won't try to forcefeed that bad sound module in there as even though init will run, it won't be able to find modules to go with the 2.4.5 kernel you are booting. I pulled this trick on a Caldera3.1 buggy install and it worked.

Hope that was close to what you needed,

Finegan

This is how it worked for me !!!
 

Hi folks,

This is how I did it and I would like
to share this with all of you.

I started the installation process
again and asked the installation
to upgrade my machine.

I have not actually said OK to
go ahead and upgrade but went
up to a stage when it asked me
what packages you want to upgrade.

At this time, my partitions should
have been mounted. When you click
Ctrl-Alt and F2, you will be given
a root shell in RH7.2.

I cded into the /mnt/systemImage .. under
which my partitions exists and the then
I cded into the etc/ and deleted the
modules.config file and after that
I was able to boot properly.

Still couldnot config my sound though.
I am into wine now.. and may the force
be with me.

thank you all very much for
the feedback.

- srivamsi.