RE: Kernel for linuxbios

[Sagiv Yefet]

Actually, I am using 2.4.24. 
Maybe I should upgrade to 2.6.*. 
but in the meanwhile what could be the problem?

The command is:

./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/bzImage	
    --command-line="rw console=ttyS0,115200 root=/dev/ram0"  
    --initrd=/home/sagivy/initrd --output=/home/sagivy/bzImage.elf

initrd created by thinstation: 2646kb.

Sagiv.

-----Original Message-----
From: Dave Aubin [mailto:[e-mail]] 
Sent: Wednesday, October 13, 2004 2:47 PM
To: Sagiv Yefet; Stefan Reinauer
Cc: [e-mail]
Subject: RE: Kernel for linuxbios

Sorry for the late response.  Are you using
Linux 2.6.*.  If so give initramfs a try.
Here is a link to aid you in how:

http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html

Dave

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Sagiv Yefet
Sent: Wednesday, October 13, 2004 8:10 AM
To: Stefan Reinauer
Cc: [e-mail]
Subject: RE: Kernel for linuxbios

I tried to use initrd - same problem.

Sagiv

-----Original Message-----
From: Stefan Reinauer [mailto:[e-mail]]
Sent: Monday, October 11, 2004 11:21 AM
To: Sagiv Yefet
Cc: [e-mail]
Subject: Re: Kernel for linuxbios

* Sagiv Yefet  [041011 11:06]:
> I add the console support and there is output. Thanks.
>
> My machine has no disks and I need initrd. So I took initrd from 
> Thinstation and build the elf file by the command :
>
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> Freeing initrd memory: 11922k freed
> Kernel panic: VFS: Unable to mount root fs on 01:00

use initrd, not ramdisk!

Stefan

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

Kernel for linuxbios

[Stefan Reinauer]

* Sagiv Yefet  [041013 16:11]:
> Actually, I am using 2.4.24. 
> Maybe I should upgrade to 2.6.*. 
> but in the meanwhile what could be the problem?
>
> The command is:
>
> ./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/bzImage	
>    --command-line="rw console=ttyS0,115200 root=/dev/ram0"  
>    --initrd=/home/sagivy/initrd --output=/home/sagivy/bzImage.elf

leave root=/dev/ram0 away in the parameters and say initrd=initrd
instead. IIRC there was some check in Linux that it only looks for an
initrd if there is a parameter saying that there is one.

Stefan

Kernel for linuxbios

Stefan Reinauer  writes:
> Sagiv Yefet  [041013 16:11]:
> > Actually, I am using 2.4.24. 
> > Maybe I should upgrade to 2.6.*. 
> > but in the meanwhile what could be the problem?
> >
> > The command is:
> >
> > ./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/bzImage
> > --command-line="rw console=ttyS0,115200 root=/dev/ram0"  
> >    --initrd=/home/sagivy/initrd --output=/home/sagivy/bzImage.elf
>
> leave root=/dev/ram0 away in the parameters and say initrd=initrd
> instead. IIRC there was some check in Linux that it only looks for an
> initrd if there is a parameter saying that there is one.

Not those arguments should be correct.  The initrd command line
is only parsed by bootloaders, especially by the HPA's bootloaders
syslinux, isolinux, and pxelinux.

Eric