plilo problems

plilo problems

[Rodrigo Moya]

Hi all!

I'm in the last step before successfully booting from the DiskOnChip. In
this step, as mentioned in the M-Systems docs, I run the patched lilo to
then update the firmware from DOS. But, when running:

/mnt/doc/sbin/plilo -C /mnt/doc/etc/lilo.conf -i /mnt/doc/boot/boot.b -m
/mnt/doc/boot/map

I get the following message:

First boot sector doesn't have a valid LILO signature

I'm using the plilo and boot.b files as shipped with the M-Systems drivers.

Thanks very much in advance



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

plilo problems

[Dvir Oren]

Rodrigo Moya writes ("plilo problems"):

> /mnt/doc/sbin/plilo -C /mnt/doc/etc/lilo.conf -i /mnt/doc/boot/boot.b -m
> /mnt/doc/boot/map
> I get the following message:
> First boot sector doesn't have a valid LILO signature

First try using the patched LILO (and boot.b file) provided either in
the MTD releases, or you might find it floating around somwhere in
this mailing list archive.  That should solve your problem.

There were a lot of discussions in this mailing list regarding this
problem.  Basically, there are two problems in the plilo binary
that M-Systems provide:  it's compiled against libc5 (unless they
changed that in the newer release) and it is patched against LILO
version 20, not 21.

-- 
Dvir Oren               <dviro@lucidvon.com>
Lucid VON Ltd.     <http://www.lucidvon.com>
9 Saloniki St.,        Tel-Aviv       Israel
Tel:  +972 3 644 3038  Fax:  +972 3 644 3039


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

plilo problems

[Dvir Oren]

Rodrigo Moya writes ("Re: Re: Re: Re: plilo problems"):

> Well, now my kernel is 436367 bytes, and the problem is still there. But I
> get a different LILO prompt:
> 
> > LILO
> > )boot:

Try an even smaller kernel.  Also check that LILO reads from the
correct places.  That is, make sure your /etc/lilo.conf tells it to
look for the kernel/boot loader/map in the flash, and not on a hard
disk that you might remove.

Also, you might want to use the same LILO and boot.b on a hard disk,
and see if it works there.  Other than that, I can't much help you
out.

Oh - one more thing you might want to check is to run the same LILO,
without the firmware (either install the .fff file, or press ctl+alt+b 
at boot when you see the M-Systems' messages to disable the firmware loading).

> Any time I run lilo, I then boot from DOS to put the firmware (with
> dupdate). Is that the correct way? Or it is needed only once?

You only need it once.  Note, though, that there are _two_ firmwares - 
one that is just 0's (the .fff file) and one which actually has the
firmware.  If you install the .fff file, you erase the firmware, so
you'll need to install it again, of course.  However, after you
installed the firmware, you don't need to re-install it every time.

-- 
Dvir Oren               <dviro@lucidvon.com>
Lucid VON Ltd.     <http://www.lucidvon.com>
9 Saloniki St.,        Tel-Aviv       Israel
Tel:  +972 3 644 3038  Fax:  +972 3 644 3039


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: plilo problems

[David Woodhouse]

Why doesn't someone just finish teaching Grub to read NFTL? I've done 
enough of it that it should be immediately obvious how to finish it off, 
but I just haven't had the time.



--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org