Thanks for your response.
I tried what you said and it seemed to help, but when I ran mkinitrd I got this:
-------------------------------------------------------------------------------------------------------------------------------------------------
stephen@the-batman:/usr/local/src/linux-2.6.28$ sudo mkinitrd -o initrdsteo.img-2.6.28 2.6.28
/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
FATAL: Module sg not found.
FATAL: Module sd_mod not found.
WARNING: This failure MAY indicate that your kernel will not boot!
but it can also be triggered by needed modules being compiled into
the kernel.
stephen@the-batman:/usr/local/src/linux-2.6.28$
-------------------------------------------------------------------------------------------------------------------------------------------------
Then when I booted the kernel:
-------------------------------------------------------------------------------------------------------------------------------------------------
RAMDISK: Loading into RAM disk... done
List of all partitions:
0800 sda driver: sd
0801 <numbers> sda1
0802 <numbers> sda2
0803 <numbers> sda3
0804 <numbers> sda4
0b00 <numbers> sr0 driver: sr
No filesystem could mount root, tried: ext3 vfat msdos iso9660
Kernel Panic - not syncing: VFS: Unable to mount root fs on unkown block(0,0)
-------------------------------------------------------------------------------------------------------------------------------------------------
My entry in Grub /boot/menu.lst is:
title Steos Dev Kernel
root (sd0,1)
kernel /boot/vmlinuz-2.6.28 root=UUID=fa619a11-1e18-4044-aada-f953cb31d195 ro single
initrd /boot/initrdsteo.img-2.6.28
The root I've used works for my other kernel (the one's I didn't build :-) )
I haven't looked at the man pages for mkinitrd, but off the console:
stephen@the-batman:/usr/local/src/linux-2.6.28$ mkinitrd
$Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $
Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version]
Options:
-d confdir Specify an alternative configuration directory.
-k Keep temporary directory used to make the image.
-m command Set the command to make an initrd image.
-o outfile Write to outfile.
-r root Override ROOT setting in mkinitrd.conf.
See mkinitrd(8) for further details.
Thanks,
Ste
On Sat, Feb 28, 2009 at 6:05 PM, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote:
Hi...
hmm, i checked man page of mkinitrd and didn't find "-o" option. Are
On Sat, Feb 28, 2009 at 7:08 PM, Stephen Roberts
<sroberts82k@xxxxxxxxxxxxxx> wrote:
> (Reposting without attachment in case it got filtered out - apologies)
>
> 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
you sure you used that option?
to the best I know, devfs is no longer used. udev is used as device
> 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!
file name maintainer (don't know the exact official name, that's how I
name it).
Check your config file....better to do:
make mproper
make defconfig --> this one to generate default config suited for
current kernel version
i think it's gone, because syslogd doesn't have a chance to grab it
>
> 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?
and save it to disk. Probably netconsole could help here.
regards,
Mulyadi.
