Can't modify my DoC anymore (pb with GRUB)

Ilguiz Latypov ilatypov at
Thu Nov 22 12:48:29 EST 2001


On Sat, 1 Jan 2000, DAVID Guillaume wrote:

> But it seems that loading the kernel fails and grub runs a minimal
> bash.

I am curious if it is just the kernel or the menu and the kernel that
could not be loaded.  Could you try to stop the possible automatic menu
selection by pressing an arrow key during system startup?

If the menu could not be loaded, I'd suggest to see the partitions of DOC
by using the autocomplete feature of the GRUB command line.  Type in "root
(dc0," and press the Tab key.

As David Woodhouse said, it is possible to create a filesystem on the NFTL
space of the chip without partitioning it.

DW, I did set the boot drive to dc0 in the updated grub-0.90 patch, so no
floppy seek will be issued by GRUB.  The menu file will be sought in the
whole NFTL space first.  This should be appropriate when the whole NFTL
space is marked by the make file system utility.  If the menu file could
not be found, then the patched GRUB will assume the space is partitioned.
There will be an attempt to mount the first partition.

I never tested the whole space filesystem case.

> Moreover, I'm forced to let the disk-on-chip plugged if I want to
> correct it !

I heard and applied few times a common sense dangerous trick.  Remove DOC
from motherboard, and put it back into the cradle when the system has

This may cost not only the chip, but your life if there is a high voltage
around, as some HOWTO suggested,

[I suppose you have "DIP package" chip.  I myself find the cradle too
tight.  The legs can be damaged.  Inserting the chip in a wrong way can
toast it.]

The DiskOnChip debug information can be displayed by uncommenting "#define
DOC_DEBUG" in the GRUB's stage2/shared.h file, recompiling stage2 and
re-linking the DOC bootloader.  The screen will not be cleared in debug


More information about the linux-mtd mailing list