headers
David Woodhouse | 1 Jan 2002 12:47
Favicon

Re: Which major/minor for DOC2000?

krist <at> vanbesien.org said:
>  I have been digging in the kernel Documentation and found some
> indication that I need a block device, with major 31 and minor 16. So
> I made one in the /dev/ directory on my initrd image. 

mknod /dev/nftla b 93 0
mknod /dev/nftla1 b 93 1
mknod /dev/nftla2 b 93 2

> But upon mounting I get a "device not initialised" error. I do get a
> lot of messages (repeatedly) like .... seems to be a DiskOnChip... or
> something. They scroll away to fast. And I do not get to the point
> that I can cal them back using dmesg... 

Use a serial console, or a video camera. Can you show me the config options 
you used to build the kernel?

--
dwmw2
Permalink | Reply | 0 comments |
headers
Agust Karlsson | 2 Jan 2002 11:50
Picon

Elan SC400 and Am29F016B

I am trying to build a Linux kernel on a AMD Elan SC400. It is an OEM built
device with 2 Am29F016B Flash memory.
Does anyone have any experience in how I can access theat device as a block
device (to build a file system on top of it).
Best regards.

--
Agust Karlsson            mailto:gusti <at> pallas.dk
Pallas Informatik A/S     http://www.pallas.dk
Allerød Stationsvej 2D    Tel.: +45 48 10 24 10
DK-3450 Allerød           Fax.: +45 48 10 24 01
Permalink | Reply | 0 comments |
headers
Sheela Kashyap | 3 Jan 2002 00:57
Picon
Favicon

Re: (no subject)

Thank you. I was the missing the root dev as you rightly guessed. I
am now successfully booting off mtd/jffs.

While creating the jffs image using mkfs.jffs, I noticed that it did
not create all the /dev entries for me. I had to use 'mknod' and
create it manually on the target. What is the easiest way for me to
create a target image with all the /dev files?

Thanks,
Sheela.

--- David Woodhouse <dwmw2 <at> infradead.org> wrote:
> 
> sheela_kashyap <at> yahoo.com said:
> > everything is fine till it comes time to mount the root FS.It
> still
> > seems to try and go out on the net. This is the trace I see. I
> have
> > cut out some parts to reduce the clutter.  
> 
> A kernel that old doesn't have 'mtdblock' in the root_dev_names
> array in 
> init/main.c. Add it.
> 
> --
> dwmw2
> 
> 

__________________________________________________
(Continue reading)

Permalink | Reply | 4 comments |
headers
David Woodhouse | 3 Jan 2002 01:06
Favicon

Re: (no subject)

sheela_kashyap <at> yahoo.com said:
>  While creating the jffs image using mkfs.jffs, I noticed that it did
> not create all the /dev entries for me. I had to use 'mknod' and
> create it manually on the target. What is the easiest way for me to
> create a target image with all the /dev files? 

Er, not sure - mkfs.jffs ought to work. Why are you using jffs not jffs2?

--
dwmw2
Permalink | Reply | 3 comments |
headers
Sheela Kashyap | 3 Jan 2002 01:27
Picon
Favicon

Re: (no subject)

Hmm... I will try mkfs.jffs again in that case. 

Well, by the time I was involved with the project, there had been
some work done on using jffs. But we'll be moving to Jffs2 in a short
while.

Thank you for your help.

Sheela.

--- David Woodhouse <dwmw2 <at> infradead.org> wrote:
> 
> sheela_kashyap <at> yahoo.com said:
> >  While creating the jffs image using mkfs.jffs, I noticed that it
> did
> > not create all the /dev entries for me. I had to use 'mknod' and
> > create it manually on the target. What is the easiest way for me
> to
> > create a target image with all the /dev files? 
> 
> Er, not sure - mkfs.jffs ought to work. Why are you using jffs not
> jffs2?
> 
> --
> dwmw2
> 
> 

__________________________________________________
Do You Yahoo!?
(Continue reading)

Permalink | Reply | 2 comments |
headers
David Woodhouse | 3 Jan 2002 10:26
Favicon

Re: (no subject)

sheela_kashyap <at> yahoo.com said:
> Hmm... I will try mkfs.jffs again in that case.  

If it fails, can you cut down the directory tree you're putting into the
JFFS image to the smallest testcase that shows the problem (like the /dev
directory and a single device node), then send me both a tarball and the
JFFS image of it?

Where did you get your mkfs.jffs from? 

--
dwmw2
Permalink | Reply | 1 comment |
headers
Felix Frey | 3 Jan 2002 16:51
Picon

Compatibility between m-system and mtd-driver

Hi folks,

I have a x86-board with a DOC-millenium. The DOC contains a single partition 
with a ext2-fs which is intented to be the rootfs. The partition was created 
and populated using the m-system driver v4.2.
When I use a kernel 2.4.9 with included mtd- and nftl-support, everything 
works fine. On boot up the kernel reports:

  M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
  $Id: nftlcore.c,v 1.73 2001/06/09 01:0943 dwmw2 Exp $
  Partition Check:
   nftla: nftla1
  VFS: Mounted root (ext2 Filesystem) readonly.
 ....
 init started: Busybox v0.51.....
--------

When I use the latest mtd-code from CVS and try to do the same, I get this:

  NFTL driver: nftlcore.c $Revision: 1.85 $, nftlmount.c $Revision: 1.25 $ 
  NFTL_notify_add for DiskOnChip Millennium 
  NFTL_setup
   nftla: nftla1
  VFS: Mounted root (ext2 filesystem) readonly.
  Freeing unused kernel memory: 48k freed
  Kernel panic: No init found.  Try passing init= option to kernel.
----
...and it's definitely not a problem with the init. The kernel seems to mount 
the filesystem but has problem to read it correctly. 
There is something which makes it confusing. When I use a harddrive to mount
(Continue reading)

Permalink | Reply | 0 comments |
headers
Allen Curtis | 3 Jan 2002 16:46

Re: (no subject)

We had the same problem where the /dev/ entries where not included in the
JFFS image. In our case I ran MAKEDEV to recreate the missing devices.

The version of JFFS we are using came with HHL Professional 2.0. Based on
the CVS versions, it looks like it is the original code release.
Permalink | Reply | 0 comments |
headers
Allen Curtis | 3 Jan 2002 16:49

JFFS and Hard Links

Are hard links supported in the latest JFFS? It appears that some of the
Linux administrative functions like "useradd" and "su" require hard links.
If they do not work, then it is not possible to have a system with only
JFFS.

Recommendations?
Permalink | Reply | 1 comment |
headers
David Woodhouse | 3 Jan 2002 16:58
Favicon

Re: JFFS and Hard Links

acurtis <at> onz.com said:
> Are hard links supported in the latest JFFS? It appears that some of
> the Linux administrative functions like "useradd" and "su" require
> hard links. If they do not work, then it is not possible to have a
> system with only JFFS.

> Recommendations? 

Switch to JFFS2?

--
dwmw2
Permalink | Reply | 0 comments |

Gmane