Pyrosophy
01-22-2001, 04:30 AM
This might be a bit technical, but here goes... I'm now a happy owner of a debian woody installation with the 2.4.0 kernel installed mainly for the USB support. The post-install has got me a bit stumped. I compiled many useful devices as modules, which means I have to load those modules into the kernel upon boot up.
Now I could just stuff all of them into my /etc/modules file. I could also use modprobe, which scares me. But I'm using debian, and this modconf script is really nice. The only thing is that it doesn't bloody work with 2.4.0. Unlike my previous kernels, I start it up and nothing's there to be installed.
According to a bug report on the modconf package, it's simply looking in the wrong place. The old kernels put their modules in /lib/modules/2.2.x/moddirs and the new one puts them in /lib/modules/2.4.0/kernel/moddirs. I tried pointing the script to the right place... no dice. So I tried making symlinks to the new directories so the script would accidentally look in the right place... no dice. Finally I tried copying all of the files to identical directories just like in the old kernel... still nothing shows up when i run modconf.
Is there anyone out there who has modconf running with the 2.4.0 kernel? If so, I'd love to hear how you did it. If not, what's your solution? Just piling modules in /etc/modules?
This shouldn't be that hard to fix, right?
Pyro
Now I could just stuff all of them into my /etc/modules file. I could also use modprobe, which scares me. But I'm using debian, and this modconf script is really nice. The only thing is that it doesn't bloody work with 2.4.0. Unlike my previous kernels, I start it up and nothing's there to be installed.
According to a bug report on the modconf package, it's simply looking in the wrong place. The old kernels put their modules in /lib/modules/2.2.x/moddirs and the new one puts them in /lib/modules/2.4.0/kernel/moddirs. I tried pointing the script to the right place... no dice. So I tried making symlinks to the new directories so the script would accidentally look in the right place... no dice. Finally I tried copying all of the files to identical directories just like in the old kernel... still nothing shows up when i run modconf.
Is there anyone out there who has modconf running with the 2.4.0 kernel? If so, I'd love to hear how you did it. If not, what's your solution? Just piling modules in /etc/modules?
This shouldn't be that hard to fix, right?
Pyro