Anyone having difficulty with a custom built kernel after all these upgrades? More specifically, kernel 3.4.4 or 3.4.5?
Setup: /dev/sda1 = /boot partition (ext2), /dev/sda2 = luks encrypted LVM (groups root, swap, home, var, tmp, all are ext4)
Did a clean install of -current using a dvd created with all updates up through July 17 changelog. I then upgraded everything up to yesterday's packages which included mkinitrd-1.4.7-i486-4.txz.
Compiled and installed the new kernel and its modules, then created the initrd with the following command:
mkinitrd -c -k 3.4.5 -f ext4 -m mbcache:jbd:ext4:aes-generic:sha256-generic -C /dev/sda2 -r /dev/cvg0/root -h /dev/cvg0/swap -L -o /boot/initrd-3.4.5.gz
and edited lilo (or grub).
When I try to boot the new kernel, it fails when trying to decrypt the luks encrypted drive, then the 'init' script exits and I get dropped to a shell of some sort. I can see in the '/boot/initrd-tree/init' script where it is failing, I just can't figure out why. The strange part is that during installation, I created the initrd for the generic-smp kernel using the same command as above, and it boots fine.
To recap, since I feel like an incoherent twit: Clean install of -current which had mkinitrd-1.4.7-i486-3, using generic kernel 3.2.23-smp. Made initrd using that version. Then, upgraded to mkinitrd-1.4.7-i486-4, and used that to make initrd for custom kernel 3.4.5 and can't boot it. I see this in the ChangeLog from July 15:
According to rworkman, udev is indeed required now in early boot for any
system using an initrd, so we'll set UDEV=1 in mkinitrd (leaving -u as a
no-op). This should clear up the issues with the /init script that
expected udevadm to be present.
Use ldconfig -l to ensure all shared libraries have the correct symlinks.
Thanks to Olek on LQ.
So, I don't think I have to use any different options in the 'mkinitrd' script (i.e., '-u'). Also, the I built the custom kernel the same way I've been doing for years. No config changes there. I had a clean install of -current a couple of weeks ago (wiped it and tried CentOS for a few days because that's what we use at work) and 3.4.4 worked fine then, but it fails now. Any ideas? Thanks