public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kevin Moore <kevin@moore-and-moore.com>
To: mtd@infradead.org
Subject: Re: Grub support in DiskOnChip.
Date: Mon, 16 Oct 2000 08:34:26 -0700	[thread overview]
Message-ID: <20001016083426.A29185@flapjack> (raw)
In-Reply-To: <31553.971082474@redhat.com>; from dwmw2@infradead.org on Mon, Oct 09, 2000 at 02:07:54 -0700

On Mon, 09 Oct 2000 02:07:54 David Woodhouse wrote:
> 
> Grub doesn't yet support the DiskOnChip Millennium. It shouldn't be 
> difficult to fix that, it's just that I did my development on DiskOnChip 
> 2000.
> 
> First you need to add Millennium support to Grub itself - you can boot Grub
> from a floppy to test this. Once Grub can detect and read the DiskOnChip,
> you also need to add Millennium support to the Grub loader found in the 
> grub/ directory of my CVS tree. 
> 

I now have grub successfully detecting the DoC Millennium and (almost)
booting the kernel.  Everything goes great until the kernel looks
for a filesystem, at which point it says:

Kernel panic: I have no root and I want to scream

This is with the same kernel that works fine for access to the DoC
when booted off the hard drive (all built-ins, no modules).  The mtd
files are from a cvs checkout I made on 7 October.  The grub commands
I use are:

root (dc0,0)
kernel /boot/vmlinuz-2.4.0-test9 root=/dev/nftla1
boot

The flash chips are detected fine during boot-up and 4 lines above
the kernel panic I see:

 nftla: nftla1

Also, the /dev directory on the DoC is populated.  If I specify the
root as "root=/dev/hda1", then I can boot using the kernel on the
DoC and the root filesystem on the hard drive.  It seems like I'm
close.

Three questions:
- Does anybody have suggestions on what the problem is or how to
  debug this?  Could I be leaving the DoC in a bad state exiting
  grub even though the kernel seems to detect it okay?
- Thinking past this, does anybody have suggestions on what needs
  to be changed in the grub loader to support DoC Millennium?  I've
  not done much x86 assembly, but I'm willing to give it a shot.
- I've gotten this far by looking at doc2000.c, doc2001.c, and nftl.c
  from the kernel driver.  I saw many comments starting with "see
  software requirement..."  I've searched the M-systems website,
  and haven't found any docs that look like this.  Can somebody
  point me to the proper documentation?

thanks,

Kevin



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-10-16 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-09  1:13 Grub support in DiskOnChip Kevin Moore
2000-10-09  9:07 ` David Woodhouse
2000-10-16 15:34   ` Kevin Moore [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-18 22:33 Volker Sonn
2000-10-09  9:07 ` David Woodhouse
2000-09-05 12:53 David Woodhouse
2000-09-06 18:40 ` Dvir Oren
2000-09-07  7:09   ` David Woodhouse

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=20001016083426.A29185@flapjack \
    --to=kevin@moore-and-moore.com \
    --cc=mtd@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