public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Herman Theron" <HEtheron@csir.co.za>
To: <linux-mtd@lists.infradead.org>, <ilatypov@superbt.com>
Subject: Re: Error using GRUB patch (and LILO questions)
Date: Mon, 25 Feb 2002 11:22:51 +0200	[thread overview]
Message-ID: <sc7a1e95.021@CS-IMO.CSIR.CO.ZA> (raw)

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

             reply	other threads:[~2002-02-25  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25  9:22 Herman Theron [this message]
2002-02-25 20:00 ` Error using GRUB patch (and LILO questions) Ilguiz Latypov
  -- strict thread matches above, loose matches on Subject: below --
2002-02-22  7:22 Herman Theron
2002-02-22 16:57 ` Ilguiz Latypov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sc7a1e95.021@CS-IMO.CSIR.CO.ZA \
    --to=hetheron@csir.co.za \
    --cc=ilatypov@superbt.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox