From: Paul Hodson <starchart@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Unable to load DOC2000
Date: Mon, 12 Jul 2004 23:47:32 -0400 [thread overview]
Message-ID: <f88313bd04071220474c906cc5@mail.gmail.com> (raw)
Hello all,
I found a similar problem to mine in the archives, but unfortunately I
wasn't able to get my system working with its suggestions. I would
very much appreciate some guidance for what I think/hope is likely a
simple problem on my end.
Here's the story. I have a Tri-M TMZ104 with a 128MB DiskOnChip 2000.
I'm using their "Linux-MZ" distribution, but I need a kernel newer
than the 2.4.18 included with it. I set up and compiled 2.4.26 with
MTD according to all of the tips posted online. Actually booting is
my problem now. I should note that the existing kernel is built with
M-Systems' TrueFFS driver, whereas mine is not.
I set up LILO for both kernels, as shown in my lilo.conf:
==== begin lilo.conf
boot = /dev/doca
disk = /dev/doca
bios = 0x80
prompt
timeout = 10
vga = normal
serial = 0,9600n8
#append="console=tty0 console=ttyS0,19200 ide0=nodma"
#append="console=ttyS0,9600 console=tty1"
image = /boot/vmlinuz-2.4.18-doc514-allmod
#image = /boot/vmlinuz-2.4.18-ext3+allmod
initrd = /boot/initrd-2.4.18-ext3+allmodc.gz
root = /dev/doca1
label = Linux-2.4.18
read-only
image = /boot/bzImage-2.4.26
root = /dev/nftla1
label = Linux-2.4.26
read-only
==== end lilo.conf
I also ran "rdev bzImage-2.4.26 /dev/ntfla1" on the kernel since I
compiled it on a separate machine.
Upon booting, I get the following error message:
==== begin error
VFS: Cannot open root device "5a00" or 5a:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 5a:00
==== end error
I'm not sure if by this point the kernel has detected the DiskOnChip,
since I don't have a means of logging the kernel message output.
My guess is that the problem is related to the overall boot point of
/dev/doca, which perhaps doesn't exist upon loading the new kernel
because it doesn't use TrueFFS?
Would anyone be able to offer me any ideas?
Cheers,
Paul
reply other threads:[~2004-07-13 3:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f88313bd04071220474c906cc5@mail.gmail.com \
--to=starchart@gmail.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