My archlinux seems not to be able to extract kernel26.img since kernel 2.6.19. This goes for upgraded 0.7.2 as well as for 0.8 alpha clean install.
Booting freezes after Grub starting. This is what happens before:
Booting Command List root (hd0,0) Filesystem type is extfs, partition type 0x83 kernel /vmlinuz26 root=/dev/sda3 ro [Linux-bzImage, setup=0x1e00, size=0x1a1a60] initrd / kernel26.img [Linux-initrd @ 0x1ff7c000, 0x73ce 6 bytes] _
What I tried so far:
-- rebuild mkinitcpio, reduced step by step until "MODUELS=aic7xxx" and "hook=base autodetect scsi"
-- reinstalled 0.7.2 and updated step by step, finding out that the kernel update brakes the stuff. Kernel 2.6.16 with mkinitcpio worked fine.
-- booted into the broken archlinux installation to see if something can be fixed - found nothing.
-- booted 0.8 to see it behaves just the same way.
Hardware available Adaptec SCSI, Promise Sata, SIL Sata
Used for Archlinux: Adaptec as / and /boot, Sata disks as raid0 for /home
System was running
/dev/sda1, sda2, sda3 == scsi
/dev/sdb1, sdc1, sdd1, sde1 == sata
As mkinitcpio only needs to detect my scsi disk to boot, I can't see any miracles at all. Reducing mkinitcpio to scsi detection should work, or even addressing the modules by hand. It did until kernel 2.6.19.
Am I blind - it must be really simple imho, but I can't see it. Any help and hint is welcome.
Frumpus ♥ addict
If you have an Intel chipset, it could be the earlymodules=piix issue.
Or maybe there is a naughty little space before the kernel26.img?
If you have a separate boot partition, which seems to be the case, with the /dev/hda3 and hd0,0, make sure you write the whole path to the kernel (as in /boot/vmlinuz26 in place of /vmlinuz26). It does seems counterintuitive. My philosophy is, if your computer likes it that way, so be it.
I own no Intel Chipset, but an extra boot partition. As the error is the same when booting 0.8 installer cd, the partition could not be the point. Furthermore, grub does well with the config with older kernels.
Frumpus ♥ addict