Hi,

On Thu, 2005-12-15 at 17:01 -0400, D Teed wrote:

Hi,

You didn't say how you booted (floppy, cdrom, network), and this is important for anyone to be able to give specific instructions to you.

sorry. I boot with PXE.

If you are booting over PXE network boot, then this sounds like a problem in your defaults file. Make sure you have included the append line which references the new init

e.g.:

default 1 label 1 kernel vmlinuz-2.4.20-12.i586 append load_ramdisk=1 ramdisk_size=16384 initrd=initrd root=/dev/ram0

That's the same like in my config.

This initrd should be in the same location as the Linux kernel file.

I know and they are both in the same folder.

Was my way of creating the files the correct way? I am confused about compiling an own kernel with initrd. With the web-creator it's just an easy way, but when i am missing modules wich i need, it's really hard to get it running. :-(

I just think that my initrd is broken, becaus i created it wrong.

--Donald Teed

On Thu, 15 Dec 2005, Thomas Kuehling wrote:

...

Dear all,

with the standard initrd i build with the webcreator, it was not possible to get this scsi-controller running. In the Dell Power Edge 1855s blades i've got this controller:

Perc4/IM | LSI Logic MPT SCSI

I tried to build my own initrd and kernel. I compiled the kernel with the initial .config of udpcast. I added the modules i thaught wich would be correct.

[root@knecht linux-2.6.14.3]# diff udpc-config.txt .config 4c4

< # Sun Dec 4 09:43:24 2005

...

# Thu Dec 15 20:05:22 2005

27d26 < CONFIG_KERNEL_BZIP2=y 346,347d344 < CONFIG_RD_BZIP2=y < CONFIG_RD_GZIP=y 488,489c485,487 < # CONFIG_MEGARAID_NEWGEN is not set

< # CONFIG_MEGARAID_LEGACY is not set

...

CONFIG_MEGARAID_NEWGEN=y CONFIG_MEGARAID_MM=m CONFIG_MEGARAID_MAILBOX=m

495,501c493,499 < CONFIG_SCSI_SATA_MV=m < CONFIG_SCSI_SATA_NV=m < CONFIG_SCSI_SATA_PROMISE=m < CONFIG_SCSI_SATA_QSTOR=m < CONFIG_SCSI_SATA_SX4=m < CONFIG_SCSI_SATA_SIL=m

< CONFIG_SCSI_SATA_SIS=m

...

# CONFIG_SCSI_SATA_MV is not set # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_PROMISE is not set # CONFIG_SCSI_SATA_QSTOR is not set # CONFIG_SCSI_SATA_SX4 is not set # CONFIG_SCSI_SATA_SIL is not set # CONFIG_SCSI_SATA_SIS is not set

Now i copied the bzImage to /tftpboot/udpcast/linux and created the initrd like this:

[root@knecht ~]# makeImage -k /usr/src/linux-2.6.14.3/arch/i386/boot/bzImage --initrd /tftpboot/udpcast/initrd --fullbox

In the next step i booted the blade, after the kernel was stared i got a kernel panic with this message:

Warning: unable to open an initial console. Kernel panic - not synching: No init found. Try passing init= option to kernel.

I searched with google for a soloution but found nothing helpfull. What am i doing wrong? Could you help me please?

King regards Thomas Kuehling -- Mapsolute Gmbh - Techn. Administration - TK2325-RIPE Düsseldorfer Straße 40a - 65760 Eschborn/Frankfurt a.M. - Germany Phone: +49 6196 777 56 413 - Fax: +49 6196 777 56 100 E-Mail: thomas.kuehling@mapsolute.com - web: http://www.mapsolute.com

---

Udpcast mailing list Udpcast@udpcast.linux.lu https://lll.lgl.lu/mailman/listinfo/udpcast

Am Donnerstag, den 15.12.2005, 17:42 -0400 schrieb D Teed:

On Thu, 15 Dec 2005, Thomas Kuehling wrote:

...

That's the same like in my config.

...

This initrd should be in the same location as the Linux kernel file.

I know and they are both in the same folder.

I should have also added - these files are in the same place as the pxelinux.0 file, and the default file is under a directory called pxelinux.cfg None of this goes inside the initrd file, in case that was part of the confusion.

The error said specifically that no init was found.

When you do a 'file' on the initrd file, what does it come back with? You may have compressed it with a format it can't handle. Alternately, there may be a kernel option which means it can't mount the initrd, but the error really looked like a simple problem with getting the name and location correct so I'd start with that end.

My own preference for building new init files, was to use castomatic on the web, which is pretty nice, and then mount the initrd so I can use the contents as a starting point. Then after I've added my own stuff, I used genromfs to recreate a new initrd. I don't think I bothered recompressing it but I may be wrong - it has been awhile.

That sounds good, but how do you mount the bunzip2ed initrd? When i do mount initrd.out /mnt -o loop, mount asked my after the filesystem.

Check that all of the normal stuff is OK. Is the initrd file and so on readable to all?

I hope that helps...

--Donald Teed

Mit freundlichen Grüßen Thomas Kühling

Am Freitag, den 16.12.2005, 12:56 -0400 schrieb D Teed:

Was writ:

...

That sounds good, but how do you mount the bunzip2ed initrd? When i do mount initrd.out /mnt -o loop, mount asked my after the filesystem.

mv initrd.out initrd.bz2 bunzip initrd.bz2

Then mount it as you tried to.

You might also need support for the file system and initrd in your kernel used by whatever machine you do this development work on.

I got it on another way running. I extracted the default initrd for pxe. Then i build an own kernel with initramfs and this directory. Now i am able to add my own stuff, build the kernel and could easily boot this kernel via pxe.

Thanks all a lot for help and creating this nice tool! ;-)

Mit freundlichen Grüßen Thomas Kühling