From: Henrik Nordstrom <hno@marasystems.com>
To: Carlos Mateo <otepas@yahoo.es>,
Mark Meade <mark@lakeshoremicro.com>,
linux-mtd@lists.infradead.org
Subject: Re: Newbie with DOC2000
Date: Thu, 3 Oct 2002 18:28:09 +0200 [thread overview]
Message-ID: <200210031828.09766.hno@marasystems.com> (raw)
In-Reply-To: <20021003161000.41499.qmail@web13605.mail.yahoo.com>
You only need the MSYS firmware installed in the DOC if you want to boot from
the DOC or access it from DOS as a DOS drive..
For Linux use you should probably consider installing the GRUB based DOC
firmware...
The EBDA error is related to having a too old LILO version I think. Have never
used LILO in a DOC system, only GRUB. The current CVS versions of GRUB works
fine in systems having a MSYS DOC firmware installed.
Regards
Henrik
Carlos Mateo wrote:
> Mark,
> My system log says:
>
> M_Systems DiskOnChip driver. (C) 1999 Machine Vision
> Holdings, Inc.
> Using configured probe address 0xd000
> Possible DiskOnChip with unknown ChipID 63 found at
> 0xd000
> M-Systems NAND Flash Translation layer driver. (C)
> 1999 MVHI
> $Id:nftl.c, v 1.57 2000/12/01 17:51:54 dwww2 Exp $
>
> I have noticed that I can only boot when there is no
> firmware in the DOC. When I use the firmware (5.1.2)
> for linux, I cannot boot, because when lilo tries to
> take control, I get a "EBDA too big" error.
>
> --- Mark Meade <mark@lakeshoremicro.com> escribió: >
> Carlos,
>
> > What does your system log say? Run dmesg and see if
> > the DoC was detected
> > correctly, and if the nftl driver found any
> > partitions.
> >
> > Also check your /dev entries for nftla: nftla should
> > be 93,0; /dev/nftla1
> > should be 93,1.. etc.
> >
> > Mark
> >
> > Carlos Mateo wrote:
> > > I am trying to access a DOC2000, but I failed so
> >
> > far.
> >
> > > I am using kernel 2.4.4. I have recompiled it
> >
> > with
> >
> > > DOC support (M-Sys DOC200, Direct char device
> >
> > access
> >
> > > to MTD devices, FTL support, NTFL support and
> >
> > write
> >
> > > support for NTFL).
> > > The kernel boots fine, but I am not able to do
> > > anything with the DOC (fdisk, mke2fs...).
> > >
> > > Any hints on what I should do?
> > >
> > > Thank you
>
> _______________________________________________________________
> Yahoo! Messenger
> Nueva versión: Webcam, voz, y mucho más ¡Gratis!
> Descárgalo ya desde http://messenger.yahoo.es
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2002-10-03 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 8:48 Newbie with DOC2000 Carlos Mateo
2002-10-01 15:47 ` Mark Meade
2002-10-03 16:10 ` Carlos Mateo
2002-10-03 16:28 ` Henrik Nordstrom [this message]
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=200210031828.09766.hno@marasystems.com \
--to=hno@marasystems.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mark@lakeshoremicro.com \
--cc=otepas@yahoo.es \
/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