Hi,

I've made some sort of bone headed change to my 10.2 system this morning. I'm using the precompiled 2.6n kernel from disk 2. I was making some changes to the network modules in rc.module to comment out ndiswrapper and load 8139too. The goal was to just use the hard wire for a bit while upgrading to current.

Unfortunately, now when I boot, *none* of my modules are loading. lsmod shows just ext3 for the hard drive.

I'm guessing I've broken a link somewhere and I don't know what to "relink".

Any advice?

Kind regards,

desertViking

Some questions that come to mind,

Did you install the "kernel-modules" package alongside the kernel-generic" package? Did you break the rc.modules script by editing it? Did you disable hotplug by accident?

Eric

I suspect the answer is yes to question 2. When I run hotplug even by hand it seems to have no effect.

for example also says it can't find the module.

What could I have done to the rc.modules file?

Thx for the consideration.

Another question: did you run "lilo" after installing that new kernel?

Eric

Hi Eric,

I've been using the 2.6.13 kernel for awhile without any difficulty. This is just something that started this morning when I modified the rc files.

I confess to being a grub user, not lilo. Sorry ;->

I went to a backup of the rc.modules file I saved, but this also doesn't seem to work. I'm sure I've been hamfisted, but it's not obvious to me as I look at this.

I also rebooted to the 2.4 image just fine.

Check that the 'rc.modules' is good. Sometimes when module packages are installed 'rc.modules' is simply a 'symlink' to the 'real file' which might be something like 'rc.modules-2.6.xx'. The link might be broken.

Good suggestion. It is a symlink to 2.6.13. The file and link appears to be ok. The file exists and the same data is is displayed if I cat the link or the actual file.

Look if you have /lib/modules/kernel-version.

Greetings,

Yes, there's a link to the source from there. I'm going to try to re-install the source and modules from the 10.2 disk 2. Maybe that will repair my mistake.

Hi, Just a note to close this discussion.

I went back to the 10.2 disk and re-installed the kernel, modules and header files. This seemed to have fixed whatever it was that was broken, but for the life of me, I don't know what the issue was.

Working ok now.

Thx for considering my question.