mkinitrd is giving me a headache
I'm making the switch to Linux from Windows, but have hit some errors when booting...
I'm new to suse 9.3. Just installed it on a dell inspiron 6000 notebook. I have been trying to compile the 2.6.12.2 kernel and get it running. So i did the following
1) untarred the source inusr-src 2) cd into the new directory 3) make config 4) make bzImage 5) make modules 6) make modulesinstall 7) copy the new kernal and System map intoboot ( with appropriate names)
and now the problematic part,
That's true, but my case is different. I do not want to handle foreign systems, but I want to optimize my own for my special tasks. Yet you think more about it...
8) mkinitrd
well, this is supposed to create an initrd file inboot and it does. However, I get this output from mkinitrd:
My only direct experience of the IBM System-360 architecture was mediated through the Michigan Terminal System operating system. This ran on an...
Kernel image:boot-vmlinuz-2.6.12.2-default Initrd image:boot-initrd-2.6.12.2-default Shared libs: lib-ld-2.3.4.so lib-libblkid.so.1.0 lib-libc.so.6 lib-libselinux.so.1 lib-libuuid.so.1.2
Driver modules: lib-modules-2.6.11.4-21.7-default-kernel-drivers-scsi-scsimod.ko lib-modules-2.6.11.4-21.7-default-kernel-drivers-scsi-sdmod.ko lib-modules-2.6.11.4-21.7-default-ker .ko lib-modules-2.6.11.4-21.7-default-kernel-drivers-scsi-ahci.ko lib-modules-2.6.11.4-21.7-default-kernel-drivers-scsi-atapiix.ko lib-modules-2.6.11.4-21.7-default-kernel-drivers-id es-2.6.11.4-21.7-default-kernel-drivers-ide-ide-disk.ko lib-modules-2.6.11.4-21.7-default-kernel-drivers-cdrom-cdrom.ko lib-modules-2.6.11.4-21.7-default-kernel-drivers-ide-ide-cd.ko .7-xen-kernel-drivers-scsi-scsimod.ko lib-modules-2.6.11.4-21.7-xen-kernel-drivers-scsi-sdmod.ko lib-modules-2.6.11.4-21.7-xen-kernel-drivers-scsi-libata.ko lib-modules-2.6.11.4-21. si-ahci.ko lib-modules-2.6.11.4-21.7-xen-kernel-drivers-scsi-atapiix.ko lib-modules-2.6.11.4-21.7-xen-kernel-drivers-ide-ide-core.ko lib-modules-2.6.11.4-21.7-xen-kernel-drivers-ide-2.6.11.4-21.7-xen-kernel-drivers-cdrom-cdrom.ko lib-modules-2.6.11.4-21.7-xen-kernel-drivers-ide-ide-cd.ko kernel-drivers-scsi-scsimod.ko kernel-drivers-scsi-sdmod.ko kernel-driverdrivers-scsi-ahci.ko kernel-drivers-scsi-atapiix.ko kernel-drivers-ide-ide-core.ko kernel-drivers-ide-ide-disk.ko kernel-drivers-cdrom-cdrom.ko kernel-drivers-ide-ide-cd.ko kernel-d kernel-drivers-scsi-sdmod.ko kernel-drivers-scsi-libata.ko kernel-drivers-scsi-ahci.ko kernel-drivers-scsi-atapiix.ko kernel-drivers-ide-ide-core.ko kernel-drivers-ide-ide-disk.ko rom.ko kernel-drivers-ide-ide-cd.ko Filesystem modules: lib-modules-2.6.11.4-21.7-default-kernel-fs-reiserfs-reiserfs.ko lib-modules-2.6.11.4-21.7-xen-kernel-fs-reiserfs-reiserfs.ko kernel-fs-reiserfs-reiserfs.ko ke fs.ko Including: klibc initramfs udev fsck.reiserfs Bootsplash: SuSE (1024x768) 9981 blocks
The thing to point out is that initrd is telling the 2.6.12.2 kernel to use the old modules located inlib-modules-2.6.11.4-21.7-defaultinstead oflib-modules-2.6.12.2-default-. Both directories do indeed exist, but why is initrd-2.6.12.2-default directing the kernel to the wrong modules.
Booting this new kernel confirms the problem with error messages related to incompatible module versions and quickly ending in a stall.
Thanks for the help,
dan
07-06-2005 ITYM 470V-6. No, you're mixing apples and oranges. The ISAM format made it possible for the editor to insert records without having to rewrite the...
Linux groups from Newsgroups