public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Mateo Anderson <mateo@posta.star.si>
To: jay.s@sohu.com
Cc: linux-mtd@lists.infradead.org
Subject: DOC 2000 and GRUB (WORKING!!)
Date: Mon, 9 Sep 2002 01:04:49 -0700 (PDT)	[thread overview]
Message-ID: <20020909080449.49A693968@sitemail.everyone.net> (raw)

Jay

>well, I've met the same problem as you before. I have choosed not to
>include the --enable-diskonchip-biosnetboot since there's no option
>for me to use in my bios.

Exactly.

>later I redo the firmware with this option enabled, and I still have
>the problem, but I plug out the doc and boot the system from hd, when
>I saw the lilo option I plug in the doc and fdisk/format the doc, cp
>the software needed into doc. 

Well, this step I did a little different.
I put the DoC into the separate socket. On this socket I removed the
pin for the CS (chip select) and connected it to a switch. The other
end of the switch I put into the socket on the board.
Then I booted the system, and when the LILO appeared I turned the 
switch on, so the Linux found the DoC.

Here I would like to thank all the good people who helped me
and probably I could not do it without their help.
Thank you all!!!

One note.
They recommended me, that id use a DOS 5.x utility DFORMAT to
transfer the GRUB firmware to DoC. 
I must say, that DFORMAT could not transfer this to DoC, it
reported some errors.
But I could use the Linux, doc_loadbios to load the firmware
and then nftl_format to format the DoC.

Then the standard fdisk, mkfs, cp, ...

>now I can boot the doc alone without problem, but I can't get it work
>along with hd, when they met, usually the grub take the first to boot
>and hangs.
>
>I don't know why the problem exists, because I have another doc
>(someone else made it for me) which can work properly with the hd. 
>so there's no concern about the bios, it must be concerned with 
>the grub firmware I built. but what's wrong. yet it can work well
>alone.

I have the same problem.
If you find the solution, please post it to the mtd mailing list.
If I find it, I'll post it here.

Thank you once again and best regards,
Mateo

_____________________________________________________________
Brezplacen E-mail - http://email.star.si
Brezplacen prostor 100 MB,lastna domena - http://www.slohosting.com

_____________________________________________________________
Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag

             reply	other threads:[~2002-09-09  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09  8:04 Mateo Anderson [this message]
2002-09-09  8:24 ` DOC 2000 and GRUB (WORKING!!) Henrik Nordstrom

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=20020909080449.49A693968@sitemail.everyone.net \
    --to=mateo@posta.star.si \
    --cc=jay.s@sohu.com \
    --cc=linux-mtd@lists.infradead.org \
    /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