On Tue, 17 Nov 2009 02:57:23 John Davis wrote:
Hello
I am still failing to build my own version of suse kernel. Here is additional info.
System Info SuSE 11 x86 kernel 2.6.27.19-5-pae
1. Fresh Install 2. cd /usr/src/linux 2.a make mrproper 3. cp /boot/config-2.6.27.19-5-pae .config 4. make menuconfig 4.a change extraversion to be -5-pae-JFD 4.b exit saving changes. 5. make; make modules; make modules_install, make install This builds a kernel, modules and initrd and copies them to /boot. It also makes changes to grub so that the new kernel is an option for booting.
The initrd which is built has the modules: scsi__mod scsi_transport_spi mptbase mptschih mptspi hwmon thermal_sys processor thermal dock libata ata_piix ata_generic ide-core piix ide-pci-generic fan jbd mbcache ext3 edd crd-t10dif sd_mod usbcore ohci-hcd uhci-hcd ff-memless hid usbhid
Features enabled: block usb resume.userpace resume.kernel
The kernel and ramdisk are stored in /boot as: vmlinuz-2.6.27.19-5-pae-JFD initrd-2.6.27.19-5-pae-JFD
6. reboot
The new kernel is installed but grub seems to boot the earlier kernel by default. Simply select the new kernel above using arrow keys.
Result: Fails to mount root fs.
/etc/modprobe.d/unsupported-modules WARNING: module '/lib/modules/2.6.27.19-5-page-JFD/kernel/drivers/thermal/thermal_sys.ko' is unusable. Use --alow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules ... similar message with ext3 ... Waiting for device /dev/sda2 to appear:..... Could not find /dev/sda2 Want me to fall back to /dev/sda2 (Y/n)
and it fails. It appears that either the ramdisk is messed up or the kernel is missing module version info.
John
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
The result is that the system will boot, but the kernel can not read the filesystem.
FWIW, once this works, I will do a few more things with the system where I build a out of tree driver. I figure if my driver is failing, I should probably try to build the kernel as-is under non-modified setup.
Any response appreciated.
When you're doing your config (i.e. through make menuconfig or, more friendly, make xconfig), either disable thermal_sys or configure it to be included in the kernel rather than as a loadable module. Or...
Use --alow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules
Follow this instruction - it pretty clearly tells you where the problem is; thermal_sys.ko is an unsupported module and you have allow_unsupported_modules set to 0, so the kernel is configured not to allow it to load. (I'm pretty sure that this option is also settable at configure time). At that point, the kernel seems to stop loading any additional modules (including your filesystem drivers). -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org