filo booting cd problem

Hello,
I am trying to boot the GeeXboX installer cd from the filo grub prompt  
and I keep getting this
message:
hdc: ATAPI: SONY    DVD RW DRU-710A
8MB medium detected
Disc doesn't use boot disk emulation

What am I doing wrong?

Thanks - Joe

Quoting [e-mail]:
> Hello,
> I am trying to boot the GeeXboX installer cd from the filo grub prompt
> and I keep getting this
> message:
> hdc: ATAPI: SONY    DVD RW DRU-710A
> 8MB medium detected
> Disc doesn't use boot disk emulation
>
> What am I doing wrong?

Has anyone ever seen this before?

Thanks - Joe

Quoting [e-mail]:

Here is the command line I used as indicated in isolinux.cfg:
hdc1:/GEEXBOX/boot/vmlinuz initrd=hdc1:/GEEXBOX/boot/initrd.gz  
root=/dev/ram0 rw init=linuxrc boot=cdrom installator

does anyone know if maybe the CD-ROM isn't properly setup to emulate a  
floppy boot??
> > Hello,
> > I am trying to boot the GeeXboX installer cd from the filo grub prompt
> > and I keep getting this
> > message:
> > hdc: ATAPI: SONY    DVD RW DRU-710A
> > 8MB medium detected
> > Disc doesn't use boot disk emulation
> >
> > What am I doing wrong?
>
> Has anyone ever seen this before?

Thanks - Joe

[Peter Stuge]

On Mon, Mar 24, 2008 at 04:36:08PM -0400, [e-mail] wrote:
> does anyone know if maybe the CD-ROM isn't properly setup to
> emulate a floppy boot??

The floppy boot emulation is called ElTorito and is a BIOS extension.

Coreboot does not (and should not IMO) implement it.

Try using the real filename on the disc. I don't know how FILO deals
with ISO9660 extensions, filename casing and such. Best would be to
add lots of debugging prints to the 9660 decoding in FILO.

//Peter

> Try using the real filename on the disc. I don't know how FILO deals
> with ISO9660 extensions, filename casing and such.

I thought that is what I am doing?
hdc1:/GEEXBOX/boot/vmlinuz initrd=hdc1:/GEEXBOX/boot/initrd.gz  
root=/dev/ram0 rw init=linuxrc boot=cdrom installator
> Best would be to
> add lots of debugging prints to the 9660 decoding in FILO.

I will try that.

Thanks - Joe

[Peter Stuge]

On Mon, Mar 24, 2008 at 08:06:33PM -0400, [e-mail] wrote:
> > Try using the real filename on the disc. I don't know how FILO
> > deals with ISO9660 extensions, filename casing and such.
>
> I thought that is what I am doing?
> hdc1:/GEEXBOX/boot/vmlinuz initrd=hdc1:/GEEXBOX/boot/initrd.gz  
> root=/dev/ram0 rw init=linuxrc boot=cdrom installator

As you may know, ISO9660 does not support case sensitive filenames,
but I do not know if and how FILO will do case conversion.

//Peter

Quoting Peter Stuge :
> On Mon, Mar 24, 2008 at 08:06:33PM -0400, [e-mail] wrote:
> > > Try using the real filename on the disc. I don't know how FILO
> > > deals with ISO9660 extensions, filename casing and such.
> >
> > I thought that is what I am doing?
> > hdc1:/GEEXBOX/boot/vmlinuz initrd=hdc1:/GEEXBOX/boot/initrd.gz
> > root=/dev/ram0 rw init=linuxrc boot=cdrom installator
>
> As you may know, ISO9660 does not support case sensitive filenames,
> but I do not know if and how FILO will do case conversion.

Ok, I got it. I don't know why it matters but I just used hdc: instead  
of hdc1: to boot the cd-rom.

Also, the documentation is a little misleading. If your using filo  
with grub (USE_GRUB = 1), and want to boot to your linux install disk  
you have to do a mixture of grub and filo. Like grub you have to  
append a kernel (and parameters), then an initrd, and give a boot  
command. Like filo you have to give absolute paths.

Thanks - Joe

[Peter Stuge]

On Tue, Mar 25, 2008 at 09:08:16AM -0400, [e-mail] wrote:
> > > I thought that is what I am doing?
> > > hdc1:/GEEXBOX/boot/vmlinuz initrd=hdc1:/GEEXBOX/boot/initrd.gz
> > > root=/dev/ram0 rw init=linuxrc boot=cdrom installator
>
> Ok, I got it. I don't know why it matters but I just used hdc:
> instead of hdc1: to boot the cd-rom.

Oh yes! I am sorry I missed that in your previous post. It matters
because discs can not be partitioned like hard drives.
> Also, the documentation is a little misleading. If your using filo
> with grub (USE_GRUB = 1), and want to boot to your linux install disk  
> you have to do a mixture of grub and filo. Like grub you have to  
> append a kernel (and parameters), then an initrd, and give a boot  
> command. Like filo you have to give absolute paths.

Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
like GRUB and make sure I always disable USE_GRUB. :)

//Peter

Quoting Peter Stuge :
> On Tue, Mar 25, 2008 at 09:08:16AM -0400, [e-mail] wrote:
> > > > I thought that is what I am doing?
> > > > hdc1:/GEEXBOX/boot/vmlinuz initrd=hdc1:/GEEXBOX/boot/initrd.gz
> > > > root=/dev/ram0 rw init=linuxrc boot=cdrom installator
> >
> > Ok, I got it. I don't know why it matters but I just used hdc:
> > instead of hdc1: to boot the cd-rom.
>
> Oh yes! I am sorry I missed that in your previous post. It matters
> because discs can not be partitioned like hard drives.
> > Also, the documentation is a little misleading. If your using filo
> > with grub (USE_GRUB = 1), and want to boot to your linux install disk
> > you have to do a mixture of grub and filo. Like grub you have to
> > append a kernel (and parameters), then an initrd, and give a boot
> > command. Like filo you have to give absolute paths.
>
> Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
> like GRUB and make sure I always disable USE_GRUB. :)

How does everyone feel about adding something like this to the wiki?

Thanks - Joe

[Stefan Reinauer]

[e-mail] wrote:
> > > Also, the documentation is a little misleading. If your using filo
> > > with grub (USE_GRUB = 1), and want to boot to your linux install disk
> > > you have to do a mixture of grub and filo. Like grub you have to
> > > append a kernel (and parameters), then an initrd, and give a boot
> > > command. Like filo you have to give absolute paths.
> >
> > Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
> > like GRUB and make sure I always disable USE_GRUB. :)
>
> How does everyone feel about adding something like this to the wiki?

Please! http://www.coreboot.org/FILO is very old and does not reflect
all details and options of FILO these days.

Stefan

Quoting Stefan Reinauer :
> [e-mail] wrote:
> > > > Also, the documentation is a little misleading. If your using filo
> > > > with grub (USE_GRUB = 1), and want to boot to your linux install disk
> > > > you have to do a mixture of grub and filo. Like grub you have to
> > > > append a kernel (and parameters), then an initrd, and give a boot
> > > > command. Like filo you have to give absolute paths.
> > >
> > > Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
> > > like GRUB and make sure I always disable USE_GRUB. :)
> >
> > How does everyone feel about adding something like this to the wiki?
>
> Please! http://www.coreboot.org/FILO is very old and does not reflect
> all details and options of FILO these days.

Updated. How does it look?

Thanks - Joe

[Uwe Hermann]

On Tue, Mar 25, 2008 at 07:10:25PM -0400, [e-mail] wrote:
> Quoting Stefan Reinauer :
> > [e-mail] wrote:
> > > > > Also, the documentation is a little misleading. If your using filo
> > > > > with grub (USE_GRUB = 1), and want to boot to your linux install disk
> > > > > you have to do a mixture of grub and filo. Like grub you have to
> > > > > append a kernel (and parameters), then an initrd, and give a boot
> > > > > command. Like filo you have to give absolute paths.
> > > >
> > > > Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
> > > > like GRUB and make sure I always disable USE_GRUB. :)
> > >
> > > How does everyone feel about adding something like this to the wiki?
> >
> > Please! http://www.coreboot.org/FILO is very old and does not reflect
> > all details and options of FILO these days.
>
> Updated. How does it look?

Thanks! The CDROM part looks ok, but I'm not sure what you mean with the
FILO/GRUB example. What do you mean with "mixture of GRUB and FILO
commands"?

If you use "USE_GRUB=1" then shouldn't this stanza in your menu.lst work?

title           GEEXBOX/coreboot
  root            (hd0,1)
  kernel          /GEEXBOX/boot/vmlinuz root=/dev/ram0 rw init=linuxrc boot=cdrom installator
  initrd          /GEEXBOX/boot/initrd.gz

Replace "(hd0,1)" with the correct value, not sure which that is in
this case, maybe "(cd)"?

And if you use "USE_GRUB=0" shouldn't this line work in FILO's "Config" file?

AUTOBOOT_FILE = "hdc:/GEEXBOX/boot/vmlinuz initrd=/GEEXBOX/boot/initrd.gz root=/dev/ram0 rw init=linuxrc boot=cdrom installator"

Uwe.

Quoting Uwe Hermann :
> On Tue, Mar 25, 2008 at 07:10:25PM -0400, [e-mail] wrote:
> > Quoting Stefan Reinauer :
> > > [e-mail] wrote:
> > > > > > Also, the documentation is a little misleading. If your using filo
> > > > > > with grub (USE_GRUB = 1), and want to boot to your linux install disk
> > > > > > you have to do a mixture of grub and filo. Like grub you have to
> > > > > > append a kernel (and parameters), then an initrd, and give a boot
> > > > > > command. Like filo you have to give absolute paths.
> > > > >
> > > > > Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
> > > > > like GRUB and make sure I always disable USE_GRUB. :)
> > > >
> > > > How does everyone feel about adding something like this to the wiki?
> > >
> > > Please! http://www.coreboot.org/FILO is very old and does not reflect
> > > all details and options of FILO these days.
> >
> > Updated. How does it look?
>
> Thanks! The CDROM part looks ok, but I'm not sure what you mean with the
> FILO/GRUB example. What do you mean with "mixture of GRUB and FILO
> commands"?
>
> If you use "USE_GRUB=1" then shouldn't this stanza in your menu.lst work?

Yes, but you don't have a menu.lst until you install linux, right?  
Just an empty hard drive. The wiki part is just to get the Linux  
install up and working.
At this point filo has already been built, installed, and pointing to  
menu.lst. But it is not going to find it when it is not there, and the  
drive has not even been partitioned and formatted. Right?
> And if you use "USE_GRUB=0" shouldn't this line work in FILO's "Config" file?
>
> AUTOBOOT_FILE = "hdc:/GEEXBOX/boot/vmlinuz   
> initrd=/GEEXBOX/boot/initrd.gz root=/dev/ram0 rw init=linuxrc   
> boot=cdrom installator"

Yup, if you wanted to boot to the installation program and re-install  
Linux every time you turn on the computer "boot=cdrom installator" :-)

Just kidding...

Thanks - Joe

[Phani Babu Giddi]

Hello All,

Has anybody got a FILO to boot a SLES 10 SP1 DVD ? Even though I give the
path to vmlinuz and initrd it still complains of file not found. Just to be
sure I tried a RHEL CD and it works fine, I can actually see the
installation related tasks on the serial console.

Reagards,
Phani

On Tue, Mar 25, 2008 at 7:23 PM,  wrote:
> Quoting Uwe Hermann :
> > On Tue, Mar 25, 2008 at 07:10:25PM -0400, [e-mail]:
> > > Quoting Stefan Reinauer :
> > > > [e-mail] wrote:
> > > > > > > Also, the documentation is a little misleading. If your using filo
> > > > > > > with grub (USE_GRUB = 1), and want to boot to your linux install
>
> disk
> > > > > > > you have to do a mixture of grub and filo. Like grub you have to
> > > > > > > append a kernel (and parameters), then an initrd, and give a boot
> > > > > > > command. Like filo you have to give absolute paths.
> > > > > > >
> > > > > > Yes. FILO includes a bunch of GRUB code when USE_GRUB=1. I do not
> > > > > > like GRUB and make sure I always disable USE_GRUB. :)
> > > > >
> > > > > How does everyone feel about adding something like this to the wiki?
> > > >
> > > > Please! http://www.coreboot.org/FILO is very old and does not reflect
> > > > all details and options of FILO these days.
> > >
> > > Updated. How does it look?
> >
> > Thanks! The CDROM part looks ok, but I'm not sure what you mean with the
> > FILO/GRUB example. What do you mean with "mixture of GRUB and FILO
> > commands"?
> >
> > If you use "USE_GRUB=1" then shouldn't this stanza in your menu.lstwork?
>
> Yes, but you don't have a menu.lst until you install linux, right?
> Just an empty hard drive. The wiki part is just to get the Linux
> install up and working.
> At this point filo has already been built, installed, and pointing to
> menu.lst. But it is not going to find it when it is not there, and the
> drive has not even been partitioned and formatted. Right?
> > And if you use "USE_GRUB=0" shouldn't this line work in FILO's "Config"
>
> file?
> > AUTOBOOT_FILE = "hdc:/GEEXBOX/boot/vmlinuz
> > initrd=/GEEXBOX/boot/initrd.gz root=/dev/ram0 rw init=linuxrc
> > boot=cdrom installator"
>
> Yup, if you wanted to boot to the installation program and re-install
> Linux every time you turn on the computer "boot=cdrom installator" :-)
>
> Just kidding...
>
> Thanks - Joe

Quoting Phani Babu Giddi :
> Hello All,
>
> Has anybody got a FILO to boot a SLES 10 SP1 DVD ? Even though I give the
> path to vmlinuz and initrd it still complains of file not found. Just to be
> sure I tried a RHEL CD and it works fine, I can actually see the
> installation related tasks on the serial console.

What does the isolinux.cfg file say? Is it possible the install kernel  
is not setup for serial console? Does it work over vga?

Thanks - Joe

[Phani Babu Giddi]

I need to check that. I do specify the serial terminal parameters
"console=tty0 console=ttyS0,115200". The coreboog image doesot include the
VGA ROM so serial console is the only way for me to check it.

I am sure the Geode LX Frame Buffer driver is not part of the booting kernel
so the VGA will not litup.

-Phani

On Wed, Mar 26, 2008 at 8:39 AM,  wrote:
> Quoting Phani Babu Giddi :
> > Hello All,
> >
> > Has anybody got a FILO to boot a SLES 10 SP1 DVD ? Even though I give
>
> the
> > path to vmlinuz and initrd it still complains of file not found. Just to
>
> be
> > sure I tried a RHEL CD and it works fine, I can actually see the
> > installation related tasks on the serial console.
>
> What does the isolinux.cfg file say? Is it possible the install kernel
> is not setup for serial console? Does it work over vga?
>
> Thanks - Joe

[Phani Babu Giddi]

Hi Joe,

Looks like I was specifying the kernel and initrd file path in
correctly. This is what the .cfg file says.

default harddisk
# hard disk
label harddisk
  localboot 0x80
# install
label linux
  kernel linux
  append initrd=initrd splash=silent showopts
# noacpi
label noacpi
  kernel linux
  append initrd=initrd splash=silent showopts acpi=off
# nolapic
label nolapic
  kernel linux
  append initrd=initrd splash=silent showopts nolapic
# failsafe
label failsafe
  kernel linux
  append initrd=initrd splash=silent showopts apm=off acpi=off mce=off
barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll
pci=nommconf
# rescue
label rescue
  kernel linux
  append initrd=initrd splash=silent rescue=1 showopts
# memory test
label memtest
  kernel memtest
implicit 1
gfxboot  bootlogo
display  message
prompt  1
timeout  200

Regards,
Phani

On Wed, Mar 26, 2008 at 8:45 AM, Phani Babu Giddi  wrote:
> I need to check that. I do specify the serial terminal parameters
> "console=tty0 console=ttyS0,115200". The coreboog image doesot include the
> VGA ROM so serial console is the only way for me to check it.
>
> I am sure the Geode LX Frame Buffer driver is not part of the booting
> kernel so the VGA will not litup.
>
> -Phani
>
> On Wed, Mar 26, 2008 at 8:39 AM,  wrote:
> > Quoting Phani Babu Giddi :
> > > Hello All,
> > >
> > > Has anybody got a FILO to boot a SLES 10 SP1 DVD ? Even though I give
> >
> > the
> > > path to vmlinuz and initrd it still complains of file not found. Just
> >
> > to be
> > > sure I tried a RHEL CD and it works fine, I can actually see the
> > > installation related tasks on the serial console.
> >
> > What does the isolinux.cfg file say? Is it possible the install kernel
> > is not setup for serial console? Does it work over vga?
> >
> > Thanks - Joe

Quoting Phani Babu Giddi :
> # install
> label linux
>   kernel linux
>   append initrd=initrd splash=silent showopts

So you probibly want to use this one. I forgot to ask you this  
earlier, where is your DVD drive connected to? What is the absolute  
path on the DVD to "linux" and "initrd"? And, are you using filo with  
grub (USE_GRUB = 1)?

Thanks - Joe

[Phani Babu Giddi]

Yes I am using FILO with USE_GRUB=1 but while FILO is starting I press the
'Esc' key and later I key in the kernel and initrd parameters.

The absolute path is /boot/i386/loader/linux for the kernel image and
/boot/i386/loader/initrd for the initrd. Ofcourse I would have to add "hdb:"
to the path.

-Phani

On Wed, Mar 26, 2008 at 10:12 AM,  wrote:
> Quoting Phani Babu Giddi :
> > # install
> > label linux
> >   kernel linux
> >   append initrd=initrd splash=silent showopts
>
> So you probibly want to use this one. I forgot to ask you this
> earlier, where is your DVD drive connected to? What is the absolute
> path on the DVD to "linux" and "initrd"? And, are you using filo with
> grub (USE_GRUB = 1)?
>
> Thanks - Joe

[Russell Whitaker]

On Wed, 26 Mar 2008, Phani Babu Giddi wrote:
> Yes I am using FILO with USE_GRUB=1 but while FILO is starting I press the
> 'Esc' key and later I key in the kernel and initrd parameters.
>
> The absolute path is /boot/i386/loader/linux for the kernel image and
> /boot/i386/loader/initrd for the initrd. Ofcourse I would have to add "hdb:"
> to the path.
>
> -Phani
>
> On Wed, Mar 26, 2008 at 10:12 AM,  wrote:
> > Quoting Phani Babu Giddi :
> > > # install
> > > label linux
> > >   kernel linux
> > >   append initrd=initrd splash=silent showopts

On my main box I'm using factory bios + grub.
The kernel image is vmlinuz and is in the /boot directory.
Since I don't need to append any parameters, ny menu.lst looks like:

#grub configuration file

#by default, boot first entry
default 0
timeout 6

#first entry:
title slack.12
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1

#second entry:

[...]

#fifth entry
title memtest86
kernel (hd0,0)/boot/memtest.bin

Note the full path to the kernel.
Hope this helps,
   Russ

Quoting Phani Babu Giddi :
> Yes I am using FILO with USE_GRUB=1 but while FILO is starting I press the
> 'Esc' key and later I key in the kernel and initrd parameters.
>
> The absolute path is /boot/i386/loader/linux for the kernel image and
> /boot/i386/loader/initrd for the initrd. Ofcourse I would have to add "hdb:"
> to the path.
>
> -Phani
>
> On Wed, Mar 26, 2008 at 10:12 AM,  wrote:
> > Quoting Phani Babu Giddi :
> > > # install
> > > label linux
> > >   kernel linux
> > >   append initrd=initrd splash=silent showopts

Ok then. So if it brings you to the filo shell (boot:) you probibly want this:

boot: hdb:/boot/i386/loader/linux initrd=/boot/i386/loader/initrd  
splash=silent showopts console=ttyS0,115200n8

If it brings you to the grub/filo shell (grub>) then you would  
probibly want this:

grub>kernel hdb:/boot/i386/loader/linux splash=silent showopts  
console=ttyS0,115200n8

Press <Enter>

grub>initrd hdb:/boot/i386/loader/initrd

Press <Enter>

grub>boot

Press <Enter>

Your system will now boot right into the Linux install. Hope that helps:-)

Thanks - Joe

[Tiago Marques]

Any particular reason for that?

If it is indeed this widespread, it would be something necessary for a
bigger deployment of coreboot than what is possible today.

Best regards,

Tiago Marques

On 3/24/08, Peter Stuge  wrote:
> On Mon, Mar 24, 2008 at 04:36:08PM -0400, [e-mail]:
> > does anyone know if maybe the CD-ROM isn't properly setup to
> > emulate a floppy boot??
>
> The floppy boot emulation is called ElTorito and is a BIOS extension.
>
> Coreboot does not (and should not IMO) implement it.
>
> Try using the real filename on the disc. I don't know how FILO deals
> with ISO9660 extensions, filename casing and such. Best would be to
> add lots of debugging prints to the 9660 decoding in FILO.
>
> //Peter

[Peter Stuge]

On Tue, Mar 25, 2008 at 10:15:45AM +0000, Tiago Marques wrote:
> Any particular reason for that?

Coreboot is not the OS loader if the OS is on a CD. Coreboot is what
runs before that loader. An OS loader can be eliminated completely if
the OS fits into the boot flash, but so far this is not the typical
case. (LAB, Linux-as-Bootloader)
> If it is indeed this widespread, it would be something necessary
> for a bigger deployment of coreboot than what is possible today.

FILO (GRUB2?) are the OS loaders that can load from a CD. If support
for the ElTorito extension is needed it should be added there. Sorry
I wasn't more clear about this separation in the last post. I should
have been more clear since the subject says FILO but the discussion
started going toward coreboot.

But - ElTorito is needed only for floppy disk emulation. Possibly it
can be avoided completely and instead we'll have native support for
booting from the CDs that people want to use. (As FILO already does
for Linux, and hopefully will do for Windows too once booting Windows
in general works well enough.)

//Peter