Hi all,

Anyone knows a quick way to get rid of a module? No! rmmod won't do because I don't even get a prompt.
I upgraded all my system (debian sarge) tonight and upon reboot (kernel 2.6.11) I had a horrible kernel panic error saying it cannot mount my root partition.
Obviously, from the error message (sorry I didn't post it), the module software suspend is responsible for that. I am certain that if the module isn't invoked, there would be no more problems; The proof is that when using an old kernel without software suspend support, ithe partition is mounted flawlessly.
I patched my kernel to accepr support for the software suspend http://www.suspend2.net/ module. Now how do I get rid of it without recompiling the kernel.

Any suggestion is very welcome.

Boot the machine with a knoppix-like cd. Mount the debian root partition. Go to /lib/modules/ and try to find the offending module file. Rename it from module.ko to module.ko.bak. This way, debian will fail to load it even if it tries. There will be a warning msg at dmesg, that's all.

Thanks for your advice. The point was that I already looked in /lib/modules before posting but couldn't find anything. I was hoping there was some file from which the modules were called and that I could edit manually.
Anyway, that was not feasible because it turned out the software suspend was built into the kernel (I did it myself but then assumed it could only be a module since I had to patch the kernel).
What caused the problem BTW was an update of everything thru Synaptic. As soon as I rebooted, the kernel panic showed up with something like:
I compiled a fresh kernel but it didn't help. Confirming that was no Software Suspend problem.
After two days of being stuck with bloody M$, and trying a fresh install (BTW, using the latest debian testing with kernel 2.6 couldn't detect my internet connection ) I had to stick to stable with kernel 2.4. But then I had to reconfigure my video chip, my wlan card, install all the apps, configure them... and that was costly for a very busy student. I had to find a solution to recover my old system.
Then, I tried something out of the blue: Add the initrd line in /boot/grub/menu.lst with the appropriate image as parameter (i.e: the one that I built for the old 2.6 kernel in question. Guess what? It worked!
I never came across anything that strange and unexplainable with any Linux distro. From my experience, it is safe to say that kernel 2.6 is not the best choice for production machines.