...

trying to build a kernel with suse, i've used this technique on other distros and I don't know why it does work here. I am wondering if I have an incomplete setup or I am simply missing a step.

1. Fresh Install 2. cd /usr/src/linux 3. make oldconfig 4. make 5. make init 6. make modules 7. make modules_install 8. make install 9. reboot

Rodney you rock. The quick fix is to do as you suggested. I was reluctant to test this since it was editing the /etc/modprobe.d/unsupported-modules file. I thought it was odd to edit this file since it resides on the hard disk - especially since reading the hard disk was the error. Anyway, it looks like you need to make this change before you do make install (it calls mkinitrd). The mkinitrd must copy this modified modprobe config file to its ramdisk. When I think of it, it makes sense. The first ramdisk uses the modprobe config files when it loads its modules. Later when the harddisk is mounted, the modprobe config files on it are used. So, you could have two different unsupported-modules files. The one in the ramdisk which is permissive and the one used at runtime which is not. I am guessing that is what suse did when it shipped the kernel and ramdisk. I've heard that you can use cpio to disassemble the ramdisk. I could do that, but I don't know off hand. I would rather spend my time trying to figure out how to sign the modules so I don't need to tweak the unsupported flag. Anyway, Rodney thanks for the pointer. -- John F. Davis 独树一帜 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org