Error using GRUB patch (and LILO questions)

Error using GRUB patch (and LILO questions)

[Herman Theron]

Hi everybody,

I downloaded the latest GRUB patch for the DOC2000 and also the latest
GRUB cvs. The patch installed perfectly. When I run 
"aclocal && automake && autoconf, I get the following errors:

stage1/Makefile.am:55: invalid variable
`nodist_pkgdata_DATA'stage2/Makefile.am: nbloader_exec_OBJECTS should
not be definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: pxeloader_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: diskless_exec_OBJECTS should not be
definedstage2/Makefile.am: pre_stage2_exec_OBJECTS should not be
definedstage2/Makefile.am: start_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: e2fs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: fat_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: ffs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: jfs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: minix_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: reiserfs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: vstafs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: xfs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not defineddocs/Makefile.am:
kernel_OBJECTS should not be defineddocs/Makefile.am: variable `LDADD'
not definednetboot/Makefile.am:34: bad macro name
`3c509_drivers'netboot/Makefile.am:35: bad macro name
`3c595_drivers'netboot/Makefile.am:36: bad macro name
`3c90x_drivers'netboot/Makefile.am:187: bad macro name
`3c509_o_CFLAGS'netboot/Makefile.am:188: bad macro name
`3c529_o_CFLAGS'netboot/Makefile.am:189: bad macro name
`3c595_o_CFLAGS'netboot/Makefile.am:190: bad macro name
`3c90x_o_CFLAGS'netboot/Makefile.am:198: bad macro name
`3c507_o_CFLAGS'netboot/Makefile.am:206: bad macro name
`3c503_o_CFLAGS'

(This errors are generated by automake)> Am I doing something wrong? 

Other question:

Is somebody using the latest LILO which ?supports? DOC devices? If so,
what options must I add in lilo.conf, since I get the 
following at bootup:

L 01 01 01 01 01 01

I've been using lilo-mtd for a while and it boots the DOC with linux
ok. Only thing  is, it doen't look as if the commandline is
passed to the kernel. "cat /proc/cmdline" is empty. Does the newer LILO
versions correct this?


Thanks in advance for any help/info
Herman

****************************************
Herman Theron
Hermanus Magnetic Observatory
CSIR
PO Box 32
Hermanus
7200
South Africa
E-mail: hetheron@csir.co.za
Phone: +27 28 3121196
Fax: +27 28 3122039
Cel: +27 833 206 311

Re: Error using GRUB patch (and LILO questions)

[Ilguiz Latypov]

Herman,

Can you try the updated automake and autoconf packages from
  ftp://ftp.redhat.com/pub/redhat/linux/rawhide/i386/RedHat/RPMS

Mine are
  automake-1.5-8
  autoconf-2.52-6
I get only a couple of warnings with autoconf.  Sorry for the 
configuration nuisance.

Ilguiz

P.S.  Have you checked the LILO HOWTO at
http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/LILO ? After the quick
search on the web I have a suspicion that your M-Sys BIOS firmware was
configured to pretend as a second hard drive.

On Fri, 22 Feb 2002, Herman Theron wrote:

> stage1/Makefile.am:55: invalid variable `nodist_pkgdata_DATA'

Re: Error using GRUB patch (and LILO questions)

[Herman Theron]

Hi Ilguiz

Yes, I upgraded to automake 1.5, and that solved the problem with grub.
I successfully installed Grub and got the system booting. Being used to
LILO, I must say that is was a bit difficult for me. The
README_DiskOnChip can give more information on how to setup the DOC
(going through nftl_format,etc, etc). Grub unfortunately doesn't abide
to the BIOS boot order. Sometimes I want to boot using a stiffy (rescue
disk), but Grub will always start first. I know that you should be able
to boot from fd0 from Grub, but it is not easy (especially not for
somebody that does not know grub well enough).

So, I still prefer LILO. And yes, I actually got version Lilo 22.2 to
boot my DOC. Thanks Ilguiz. Here follows my lilo.conf:

boot=/dev/nftl/disc0/disc
disk=/dev/nftl/disc0/disc
bios=0x80
lba32
install=/boot/boot-text.b
map=/boot/map
backup=/dev/null
prompt
timeout=50
default=Linux
image=/boot/bzImage-2.4.17-rthal5g
        label=Linux
        root=/dev/nftl/disc0/disc
        vga=normal
	read-only
image=/boot/bzImage-2.4.17-rthal5g
        label=Linux-fb
        root=/dev/nftl/disc0/disc
        vga=0x314
	read-only

I had to tell LILO to use the DOC as the first drive (bios=0x80);

Thanks all
Herman
>>> Ilguiz Latypov <ilatypov@superbt.com> 02/22/02 06:57PM >>>

Herman,

Can you try the updated automake and autoconf packages from
  ftp://ftp.redhat.com/pub/redhat/linux/rawhide/i386/RedHat/RPMS 

Mine are
  automake-1.5-8
  autoconf-2.52-6
I get only a couple of warnings with autoconf.  Sorry for the 
configuration nuisance.

Ilguiz

P.S.  Have you checked the LILO HOWTO at
http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/LILO ? After the
quick
search on the web I have a suspicion that your M-Sys BIOS firmware was
configured to pretend as a second hard drive.

On Fri, 22 Feb 2002, Herman Theron wrote:

> stage1/Makefile.am:55: invalid variable `nodist_pkgdata_DATA'




______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/ 


****************************************
Herman Theron
Hermanus Magnetic Observatory
CSIR
PO Box 32
Hermanus
7200
South Africa
E-mail: hetheron@csir.co.za
Phone: +27 28 3121196
Fax: +27 28 3122039
Cel: +27 833 206 311

Re: Error using GRUB patch (and LILO questions)

[Ilguiz Latypov]

Herman,

Yes, when starting from a floppy, it is BIOS who hands the control over to
the boot sector content of the floppy disk.  LILO doesn't interfere with
the BIOS boot order.

The DoC patch to GRUB will affect the BIOS boot order, since the code in
the flash memory will gain control earlier.

It is still possible to boot off the floppy drive by using the GRUB 
loader (see below an untested sample of /boot/grub/menu.lst).

Ilguiz

================================================================
default=0
timeout=2
serial --speed=115200
terminal --timeout=2 serial console

title=Linux with serial console
root (dc0,0)
kernel /boot/vmlinuz root=/dev/nftla2 ro console=ttyS0,115200

title=Rescue floppy disk
root (fd0)
kernel /vmlinuz root=/dev/fd0 ro console=ttyS0,115200

title=Windows
rootnoverify (hd0,0)
makeactive
chainloader +1
================================================================


On Mon, 25 Feb 2002, Herman Theron wrote:

> Sometimes I want to boot using a stiffy (rescue disk), but Grub will
> always start first.