dracut information

Nic Alvaro nicalvaro at lavabit.com
Mon Jan 17 14:17:38 EST 2011

On Mon, 2011-01-17 at 17:58 +0000, Peter Robinson wrote:
> On Mon, Jan 17, 2011 at 5:53 PM, Nic Alvaro <nicalvaro at lavabit.com> wrote:
> > Detected XO-1
> > ...
> > subprocess.CalledProcessError: Command ['/bin/mount', '-t', 'vfat', ro', '/dev/sdal', '/mnt/usb'] returned non-zero exit status 32
> > Kernel panic - not syncing: Attempted to kill init!
> Looks like your not building your initrd. You can get all the
> information you need with 'man dracut' and 'dracut --help'

Last I checked that's what dracut was for. So I thought that the below
command should produce an initial ramdisk image that is sufficient to be
this thing called initrd.

$ sudo dracut image `uname -r`

I moved the image created to 
/version/pristine/860/boot/initrd-2.6..img.1 and modified olpc.fth to
take into account my new initrd and vmlinuz files and booted with "boot

lrwxrwxrwx 1 root root 12 2011-01-16 23:33 /boot/olpcrd-1.img -> initrd-1.img
lrwxrwxrwx 1 root root 60 2011-01-17 02:40 /boot/initrd-1.img -> initrd-2.6.31_xo1-20101216.1250.1.olpc.741a3e67d9e7bb8.img.1
lrwxrwxrwx 1 root root 55 2011-01-17 02:40 /boot/vmlinuz-1 -> vmlinuz-2.6.31_xo1-20101216.1250.1.olpc.741a3e67d9e7bb8

Below is the simple change I made to olpc.fth that I saved as
" ${DN}${PN}\vmlinuz-1"    expand$ to boot-device
" ${DN}${PN}\olpcrd-1.img" expand$ to ramdisk

More information about the Devel mailing list