Hi guys,
I have tried to compile the source for 2.6.28 and not changed any code. I took just the defaults for the config (I suspect the config is the issue...) and did:
make
make modules
make modules_install
mkinitrd -o initrdsteo.img-2.6.28 2.6.28
and then added it to grub like so:
title Steos Dev Kernel
root (hd0,1)
kernel /boot/vmlinuz-2.6.28 root=UUID=fa619a11-1e18-4044-
aada-f953cb31d195 ro single
initrd /boot/initrdsteo.img-2.6.28
When I boot up, I am getting a panic:
--------------------------------------------------------------------------------------------------------------------------------
SCSI Subsystem initialized
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
umount: devfs: not mounted
/scripts/ext-3-add-journal.sh: 27: arithmetic _expression_: Expecting EOF: "0x"
mount: unknown filesystem type 'devfs'
/sbin/init: 426: arithmetic _expression_: Expecting EOF: "0x"
Kernel Panic - not syncing: Attempting to kill init!
--------------------------------------------------------------------------------------------------------------------------------
Aside: Is it possible to get this output on dmesg after subsequently booting up a working kernel? Or is it gone by this stage? Or, as it seems it has no access to a filesystem, it wouldn't even be able to save them anywhere anyway?
Thanks,
Ste
initrd /boot/initrdsteo.img-2.6.28
When I boot up, I am getting a panic:
--------------------------------------------------------------------------------------------------------------------------------
SCSI Subsystem initialized
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
umount: devfs: not mounted
/scripts/ext-3-add-journal.sh: 27: arithmetic _expression_: Expecting EOF: "0x"
mount: unknown filesystem type 'devfs'
/sbin/init: 426: arithmetic _expression_: Expecting EOF: "0x"
Kernel Panic - not syncing: Attempting to kill init!
--------------------------------------------------------------------------------------------------------------------------------
Aside: Is it possible to get this output on dmesg after subsequently booting up a working kernel? Or is it gone by this stage? Or, as it seems it has no access to a filesystem, it wouldn't even be able to save them anywhere anyway?
Thanks,
Ste
