Slackware64-13.0 multilib can not build valid initrd for kernels 2.6.30
Hello all,
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-2.6.29.6 with an initrd set up using mkinitrd.conf Everything is fine except that I cannot build a right initrd for kernels 2.6.30, both the /testing one or a custom build: if I try, it will panic at boot with the "couldn't find a valid RAM disk image" error. On the same hardware, without multilib support, I was able to correctly build and boot 2.6.30 initrds. Can anyone confirm this strange behaviour? In case, got any workaround or suggestions? Thanks in advance for any help, Marco |
The multilib capability doesn't affect the initrd setup process. The problem should be either in the links in /boot (System.map and so on) or in your lilo.conf. Did you try to get a suggestion of the mkinitrd command you need using '/usr/share/mkinitrd/mkinitrd_command_generator.sh -r'?
|
Quote:
Quote:
|
I can confirm that you can build and boot an initrd.gz for kernel 2.6.32.7 and the ext4 filesystem using Slackware64-current with the multi-lib packages installed.
samac |
Quote:
|
How large is your initrd?
Did you try the option large-memory in your lilo.conf file? |
Hi, I also have this issue, but I think, that it is combined rather with kernel, than glibc version. I had no problem with mkinitrd with some older kernels. This problem starts with 2.6.30 kernels.
Maybe some upgrade of mkinitrd tool is needed? |
Slackware-current has the 2.6.32.7 kernel and I can create initrd's without any problem (32-bit, 64-bit and multilib systems). Likewise, I don't see why Slackware-13.0 should not be able to create a wrorking initrd for newer kernel versions.
You can try upgrading to the mkinitrd package that is part of Slackware64-current, but if you do that, make sure you have a "rescue" entry in your /etc/lilo.conf that allows you to boot your computer in case the new mkinitrd does not work for Slackware 13.0. Eric |
Quote:
I'll test it tonight or tomorrow and report back. Thanks to anyone who chimed in for help. ciao |
Quote:
|
I confirm it was the missing "large-memory" option. thanks!
|
Awesome!
|
All times are GMT -5. The time now is 03:23 AM. |