public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* Which major/minor for DOC2000?
@ 2001-12-29 22:29 Krist van Besien
  2002-01-01 11:47 ` David Woodhouse
  0 siblings, 1 reply; 2+ messages in thread
From: Krist van Besien @ 2001-12-29 22:29 UTC (permalink / raw)
  To: mtd

Hi all...

I have a problem...

The situation is as follows: I have an (three year old) system with a
8MB DOC2000 on it. No HD, no floppy. It has two ethernet cards, adn I
can connect a keyboard and monitor. I want to use it to build a
firewall.

Currently the system contains the "lrp" distribution, which was
installed on it for my the guys that sold me the system. The system
boots through syslinux , which loads a kernel and root image, and boots.
The kernel is an 2.0.7 kernel linked with the old (binary only) DOC2000
driver. (Which means that tohse guys that sold me the system in fact
violated the GPL. I do not plan on holding it against thme though...)

I want to replace the Os with a miny distro I built myself (based on
floppyfw). So I built a kernel, based on 2.4.17, with mtd, doc2000 and
ntfl support. Made my own initrd etc... By booting the original
kernel/root img. I was able to copy the new kernel and root image to the
DOC2000, and modify syslinux.cfg so I can choose between the old and the
new kernel when booting.

My problem is the following: Somehwere during startup I need to mount
the filesystem on the DOC2000. The filesystem is fat, and the original
lrp based distro mounted it from /dev/fla1, which the kernel considers
the first partition on /dev/fla   /dev/fla1 has major/minor 62/0 

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. 

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...

So can anybody help me with this? What is needed apart from built in
support in the kernel to be able to mount a fat filesystem on a DOC2000?

TIA

Krist

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Which major/minor for DOC2000?
  2001-12-29 22:29 Which major/minor for DOC2000? Krist van Besien
@ 2002-01-01 11:47 ` David Woodhouse
  0 siblings, 0 replies; 2+ messages in thread
From: David Woodhouse @ 2002-01-01 11:47 UTC (permalink / raw)
  To: Krist van Besien; +Cc: mtd

krist@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 raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-01-01 11:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-12-29 22:29 Which major/minor for DOC2000? Krist van Besien
2002-01-01 11:47 ` David Woodhouse

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox