lilo and mtd ans doc

lilo and mtd ans doc

[Patrick Allaire]

Hi,

I have finaly accepted that this driver is working with linux 2.4 !!! Wow
its more easy that way ... I can now compile without any problems the kernel
with DOC2000 support and Nftl !!! Now I can see the DOC, I can write to it,
I can read from it ... the only thing left is :

I cant boot from my DOC2000 ! There is a lilo.conf (listed below) on the
chip. I have run the lilo-mtd with the good boot.b-mtd {lilo-mtd -C
/etc/lilo.conf -r /mnt}. Every thing look fine, I see the "Patched LILO for
M-Systems DiskOnChip 2000   added s*" that is my label. When I boot with
only the DOC, the kernel get loaded, I see the DOC partition : "Partition
check : nftla1" ... but then it does not find the root fs :

Kernel Panic : VFS: unable to mount root fs on 03:05


is it the fault of :

lilo-mtd ?
boot.b-mtd ?
map ?

if so where do I get them ? I have taken those on the mtd CVS ! execpt from
map wich i didnt find anywhere.


************************************
lilo.conf
************************************
boot=/dev/nftla
map=/boot/map
install=/boot/boot.b-mtd
vga=extended
image=/boot/bzImage
label=s
root=/dev/nftla1
read-write

************************************
/dev/nftla* on the DOC
************************************
brw-r--r--    1 root     root     93,   0 Aug 28  2001 nftla
brw-r--r--    1 root     root     93,   1 Aug 28  2001 nftla1
brw-r--r--    1 root     root     93,   2 Jul  8 09:29 nftla2
brw-r--r--    1 root     root     93,   3 Jul  8 09:29 nftla3
brw-r--r--    1 root     root     93,   4 Jul  8 09:29 nftla4
brw-r--r--    1 root     root     93,   5 Jul  8 09:29 nftla5
brw-r--r--    1 root     root     93,   6 Jul  8 09:29 nftla6


thank you all !!


Patrick Allaire
mailto:pallaire@gameloft.com
If you can see it, but it's not there, it's virtual. 
If you can't see it, but it is there, it's hidden. 
It you can't see it and it isn't there, it's gone.

Re: lilo and mtd ans doc

[David Woodhouse]

pallaire@gameloft.com said:
> Kernel Panic : VFS: unable to mount root fs on 03:05 

Er, that's /dev/hda5. It's not trying to mount the DiskOnChip at all.
Try append="root=/dev/nftla1" instead of just root=/dev/nftla1

LILO sucks like that.

BTW, how many partitions do you have on the DiskOnChip? If only one, why 
are you wasting space on partitions rather than just using a filesystem on 
/dev/nftla ?

--
dwmw2

RE: lilo and mtd ans doc

[Patrick Allaire]

I have tried what you have told me but it does not seem to change a thing
!!! The systems is still hanging on "Kernel panic : VFS: Unable to mount
root fs on 03:05" !!!!!!!!!

Where does it find the information to search 03:05 to boot ? I did compile
the kernel on /dev/hda5 !!! Is there a place in the kernel config where I
could specify the boot device ? Is this information stored in boot.b-mtd (I
dont think so) ? In the /boot/map ??? the last one is generated by lilo ? no
? so it should not contain /dev/hda5 information since I run lilo-mtd from a
floppy the HD was removed !

I have added those two lines to my lilo.conf :

prompt
timeout=50

Then I have tried what you told me. When I boot ... I write :

lilo: s append="root=/dev/nftla1"


For your question about why I am using /dev/nftla1 instead of /dev/nftla ...
its because on our final product we will have multiple partitions.

Thank you !


Patrick Allaire
mailto:pallaire@gameloft.com
If you can see it, but it's not there, it's virtual. 
If you can't see it, but it is there, it's hidden. 
It you can't see it and it isn't there, it's gone.



> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: August 31, 2001 5:37 PM
> To: Patrick Allaire
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: lilo and mtd ans doc 
> 
> 
> 
> 
> pallaire@gameloft.com said:
> > Kernel Panic : VFS: unable to mount root fs on 03:05 
> 
> Er, that's /dev/hda5. It's not trying to mount the DiskOnChip at all.
> Try append="root=/dev/nftla1" instead of just root=/dev/nftla1
> 
> LILO sucks like that.
> 
> BTW, how many partitions do you have on the DiskOnChip? If 
> only one, why 
> are you wasting space on partitions rather than just using a 
> filesystem on 
> /dev/nftla ?
> 
> --
> dwmw2
> 
> 

Re: lilo and mtd ans doc

[David Woodhouse]

Use rdev to change the default. No clue why LILO isn't managing to pass 
arguments correctly.

--
dwmw2

Re: lilo and mtd ans doc

[Vipin Malik]

Patrick Allaire wrote:

> I have tried what you have told me but it does not seem to change a thing
> !!! The systems is still hanging on "Kernel panic : VFS: Unable to mount
> root fs on 03:05" !!!!!!!!!
>
> Where does it find the information to search 03:05 to boot ? I did compile
> the kernel on /dev/hda5 !!! Is there a place in the kernel config where I
> could specify the boot device ? Is this information stored in boot.b-mtd (I
> dont think so) ? In the /boot/map ??? the last one is generated by lilo ? no
> ? so it should not contain /dev/hda5 information since I run lilo-mtd from a
> floppy the HD was removed !
>
> I have added those two lines to my lilo.conf :
>
> prompt
> timeout=50
>
> Then I have tried what you told me. When I boot ... I write :
>
> lilo: s append="root=/dev/nftla1"

This may be a valid way to specify lilo cmd's too, but I would do just:

LILO: s root=/dev/nftla1

and try that.

You need the append="...." only when you specify the cmd line args in the
lilo.conf file, not if you are specifing them during boot time.

Vipin



>
>

RE: lilo and mtd ans doc

[Karl Hammar]

  $ man rdev
  ...
	 In a bootable image for the Linux kernel, there  are  sev­
	 eral  pairs  of  bytes  which specify the root device, the
	 video mode, the size of the RAM disk, and the swap device.
	 These  pairs  of  bytes,  by  default, begin at offset 504
	 (decimal) in the kernel image:

		 498 Root flags
		(500 and 502 Reserved)
		 504 RAM Disk Size
		 506 VGA Mode
		 508 Root Device
		(510 Boot Signature)

	 rdev will change these values.
  ...

I think that the default root device is the current root device.
To change:

  $ rdev vmlinux /dev/hda2

or similar.

Regards,
/Karl

-----------------------------------------------------------------------
Karl Hammar                    Aspö Data           karl@kalle.csb.ki.se
Lilla Aspö 2340             +46  173 140 57                    Networks
S-742 94 Östhammar         +46  10 270 26 67                  Computers
Sweden                                                       Consulting
-----------------------------------------------------------------------

From: Patrick Allaire <pallaire@gameloft.com>
Subject: RE: lilo and mtd ans doc 
Date: Tue, 4 Sep 2001 09:43:57 -0400

> I have tried what you have told me but it does not seem to change a thing
> !!! The systems is still hanging on "Kernel panic : VFS: Unable to mount
> root fs on 03:05" !!!!!!!!!
> 
> Where does it find the information to search 03:05 to boot ? I did compile
> the kernel on /dev/hda5 !!! Is there a place in the kernel config where I
> could specify the boot device ? Is this information stored in boot.b-mtd (I
> dont think so) ? In the /boot/map ??? the last one is generated by lilo ? no
> ? so it should not contain /dev/hda5 information since I run lilo-mtd from a
> floppy the HD was removed !
> 
> I have added those two lines to my lilo.conf :
> 
> prompt
> timeout=50
> 
> Then I have tried what you told me. When I boot ... I write :
> 
> lilo: s append="root=/dev/nftla1"
> 
> 
> For your question about why I am using /dev/nftla1 instead of /dev/nftla ...
> its because on our final product we will have multiple partitions.
> 
> Thank you !
> 
> 
> Patrick Allaire
> mailto:pallaire@gameloft.com
> If you can see it, but it's not there, it's virtual. 
> If you can't see it, but it is there, it's hidden. 
> It you can't see it and it isn't there, it's gone.
> 
> 
> 
> > -----Original Message-----
> > From: David Woodhouse [mailto:dwmw2@infradead.org]
> > Sent: August 31, 2001 5:37 PM
> > To: Patrick Allaire
> > Cc: linux-mtd@lists.infradead.org
> > Subject: Re: lilo and mtd ans doc 
> > 
> > 
> > 
> > 
> > pallaire@gameloft.com said:
> > > Kernel Panic : VFS: unable to mount root fs on 03:05 
> > 
> > Er, that's /dev/hda5. It's not trying to mount the DiskOnChip at all.
> > Try append="root=/dev/nftla1" instead of just root=/dev/nftla1
> > 
> > LILO sucks like that.
> > 
> > BTW, how many partitions do you have on the DiskOnChip? If 
> > only one, why 
> > are you wasting space on partitions rather than just using a 
> > filesystem on 
> > /dev/nftla ?
> > 
> > --
> > dwmw2
> > 
> > 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

RE: lilo and mtd ans doc

[Patrick Allaire]

in the mtd cvs download --> /mtd/patches there is a lilo-mtd.tar.gz ! inside
this file there is a lilo-mtd allready compiled and a lilo21-mtd-patch ...
should I recompile lilo our I should use the one that is there ? ... I am
currently using the precompiled one.

Patrick Allaire
mailto:pallaire@gameloft.com
If you can see it, but it's not there, it's virtual. 
If you can't see it, but it is there, it's hidden. 
It you can't see it and it isn't there, it's gone.



> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: August 31, 2001 5:37 PM
> To: Patrick Allaire
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: lilo and mtd ans doc 
> 
> 
> 
> 
> pallaire@gameloft.com said:
> > Kernel Panic : VFS: unable to mount root fs on 03:05 
> 
> Er, that's /dev/hda5. It's not trying to mount the DiskOnChip at all.
> Try append="root=/dev/nftla1" instead of just root=/dev/nftla1
> 
> LILO sucks like that.
> 
> BTW, how many partitions do you have on the DiskOnChip? If 
> only one, why 
> are you wasting space on partitions rather than just using a 
> filesystem on 
> /dev/nftla ?
> 
> --
> dwmw2
> 
>