Dear list, Bruce and Armin,
Bruce wrote:
[...]
> You are going a little too fast. Get the kernel working without initramfs
> first. Set the kernel command line to init=/bin/bash root=/dev/sda1 and see
> if
> you can get something. If sda doesn't work, try sdb. Also see if you can
> see what the kernel finds in the startup messages -- try using the scroll
> lock
> or pause keys to stop the messages (I'm not sure that will work though).
[..]
> As I said, change back to sda1 to see what is going on. After you know what
> the
> kernel thinks, transition to initramfs.
I was not able to find out the startup message (to fast and both keys does not
work). Setting root=/dev/sdb1 results in "error: file `/boot/vmlinuz...´ not
found".
Setting "linux /boot/vmlinuz... root=/dev/sda1 ro init=/bin/bash " ('e' key at
grub menu) lets the kernel boot but also panicing and "init=/bin/bash not
found".
Trying
--------------8<----------
grub > root=hd0,1
grub > linux /boot/vmlinuz...
grub > init=/bin/bash
grub > boot
--------------8<----------
also results in kernel panic and init=/bin/bash not found.
################
Armin wrote:
> Since you are using USB with initramfs, you should use UUID on the kernel
> command line and fstab. Node names can change, especially since
> usb is in question.
Using UUID on kernel command line (grub > root=UUID=***) and fstab resulted in
something like "Device UUID=*** not found" and no loading of the kernel.
Interestingly, "grub > ls (hd0,1)" resulted in an UUID one number less than
blkid command at host system for /dev/sdb1 - I tried both obtained UUIDs...
##################
If it might be helpful I could attach some (really) low quality pictures of the
screen after kernel panic... And of course, any further help is appreciated. ^^
Thanks,
Seba
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
