From: Glen <mtd@empireenterprises.com>
To: linux-mtd@lists.infradead.org
Subject: [Fwd: Re: boot from diskonchip millenium]
Date: 06 Aug 2002 17:26:53 -0400 [thread overview]
Message-ID: <1028669214.1719.1.camel@glen> (raw)
Thank you for your help thus far.
> This always happens when the grub_firmware was compiled by
> running aclocal/autoconf/automake commands from README_DiskOnChip and
> specifying the --enable-diskonchip-mil option. [The latest patches are
> 0.92 and 2002-07-29].
This is what I did, with the 0.92 patch; are you saying I should have
done otherwise?
I started from scratch, and recompiled everything, reformatted, and the
like. Now I get the following message:
DoC Mil D000
E698
Jumping to Grub
Attempting to open /boot/grub/menu.lst on drive 0xe0, partition 0xff
Unknown ChipID a0 at c8000
DiskOnChip Millennium found at d0000
floor 0, chip 0; manufacturer: Toshiba
Chip: Toshiba TC58V64AFT/DC, total size: 8MiB
erase unit: 8192 bytes, page: 512 byes
unknown manufacturer code: 0x43
Total of 1 chips found - total capacity 8 MiB
Scanning for NFTL Media Header
NFTL Media Header found in flash sector 208
nftl_rawread(): error 16 in memcpy() or earlier, press any key
Interestingly enough, after I boot the machine to the HDD by entering
the commands in grub manually, I no longer have a nftl partition.
Does grub write to the DOC upon booting?
-g
On Tue, 2002-08-06 at 14:04, Ilguiz Latypov wrote:
>
> On 6 Aug 2002, Glen wrote:
>
> > Attempting to open /boot/grub/menu.lst 0x0 0x0
> > Attempting to open /boot/grub/menu.lst 0x0 0x1
>
> I believe there were attempts to open configuration file on disk 0xe0
> (DiskOnChip fake BIOS drive number just for the GRUB's internal BIOS disk
> access API). This always happens when the grub_firmware was compiled by
> running aclocal/autoconf/automake commands from README_DiskOnChip and
> specifying the --enable-diskonchip-mil option. [The latest patches are
> 0.92 and 2002-07-29].
>
> > Ideas??
>
> If you created a partition within NFTL layer, the "root (dc0,0)" command
> would be worth trying.
>
> Ilguiz
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next reply other threads:[~2002-08-06 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 21:26 Glen [this message]
2002-08-06 22:15 ` [Fwd: Re: boot from diskonchip millenium] Mark Meade
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=1028669214.1719.1.camel@glen \
--to=mtd@empireenterprises.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