From: Nikhil Goel <nikhil@smartbridges.com>
To: John Sutton <john@scl.co.uk>
Cc: linux-mtd@lists.infradead.org, Russ.Dill@asu.edu
Subject: Re: Booting from DOC2000 with GRUB loader
Date: Thu, 02 May 2002 03:49:14 +0800 [thread overview]
Message-ID: <3CD046BA.4010906@smartbridges.com> (raw)
In-Reply-To: 02050120383503.07252@diva.localdomain
From the commands pondered upon -
nftl_format /dev/mtd0 98304
works fine for me in a similar setup. The same was given as a reference,
the first time the grub and DOC2000 patch showed up.
John Sutton wrote:
> Hi all (and Russ in particular)
>
> I've got the same problem as previous post on this subject:
>
> ---------------------------------------
> On Thu, 2002-04-25 at 19:19, Zhiwei Yu wrote:
>
>>Hi,
>>
>>I am working on booting from DOC2000, LILO works on my
>>box but GRUB doesn't. After I patched the latest
>>patch for GRUB, I got grub-fireware and sucessfully
>>load the fireware in DOC.
>>
>>For now, everytime I boot up, I got grub prompt, but I
>>failed to load kernel, the command I using is
>>kernel (dc0,0)/boot/bzImage.
>>
>>This problem is not new to the list, I found several
>>similar mails, All of them didn't have the answer. DI
>>u have any idea? Thanks in advance.
>
>
> probably because you overwrote some nftl stuff with grub. Erase the
> whole thing (eraseall /dev/mtd0), put grub on it, find the next free
> block directly past grub and nftl_format at that offset. fdisk your
> nftla, mkfs the partition, add the kernel, and maybe a menu.lst.
> ----------------------------------------------
>
> My question is: *how* do I "find the next free block directly past grub"?
>
> When I put grub on there (not at that stage realising I was going to trash my
> existing nftl partitions and so I omitted to record the output), I *seem to*
> recall that doc_loadbios reported needing 6 x 16k "blocks" to store the grub
> firmware - which fits, because the grub_firmware file is 87k.
>
> So, in what units is the <start offset> argument to nftl_format? i.e. do I do :
>
> nftl_format /dev/mtd0 6 (16k blocks)
>
> or nftl_format /dev/mtd0 96 (1k blocks)
>
> or nftl_format /dev/mtd0 98304 (bytes)
>
> etc...?
>
> I'm nervous about messing this up because since I put grub on the DoC, the
> machine only ever boots from the DoC - completely ignores floppy, scsi disks
> and cdrom. So if I screw up this nftl_format and trash grub, I'm going to end
> up with an unbootable system ;-( (OK, I'll just have to pull the DoC chip out
> of the board *again*, but even this gives me the eebies, so tight is the damn
> thing stuck in its socket! And anyway, if the system is unbootable with the
> DoC chip in there, how am I ever going to reprogram it?)
>
> Help much appreciated!
>
> TIA
> John
>
> ***************************************************
> John Sutton
> SCL Internet
> URL http://www.scl.co.uk/
> Tel. +44 (0) 1239 711 888
> ***************************************************
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
next prev parent reply other threads:[~2002-05-01 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 19:17 Booting from DOC2000 with GRUB loader John Sutton
2002-05-01 19:49 ` Ilguiz Latypov
2002-05-01 19:49 ` Nikhil Goel [this message]
2002-05-01 20:15 ` Russ Dill
2002-05-02 7:47 ` John Sutton
2002-05-02 9:32 ` Russ Dill
2002-05-02 10:56 ` John Sutton
2002-05-02 16:09 ` Ilguiz Latypov
2002-05-02 17:33 ` Jasmine Strong
2002-05-02 17:39 ` Jasmine Strong
2002-05-02 18:17 ` Frederick Lefebvre
2002-05-02 18:45 ` Ilguiz Latypov
2002-05-03 13:40 ` John Sutton
2002-05-03 16:19 ` Jasmine Strong
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 2:19 Zhiwei Yu
2002-04-26 2:35 ` Russ Dill
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=3CD046BA.4010906@smartbridges.com \
--to=nikhil@smartbridges.com \
--cc=Russ.Dill@asu.edu \
--cc=john@scl.co.uk \
--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