From: Wolfgang Denk <wd@denx.de>
To: Marco Schramel <Schramel.Linux@go.bartec.de>
Cc: PPC_LINUX <linuxppc-embedded@ozlabs.org>
Subject: Re: mtd mount problem
Date: Thu, 21 Apr 2005 12:32:29 +0200 [thread overview]
Message-ID: <20050421103234.ED367C1510@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 21 Apr 2005 11:17:25 +0200." <200504211117.25584.Schramel.Linux@go.bartec.de>
In message <200504211117.25584.Schramel.Linux@go.bartec.de> you wrote:
>
> /dev # date > /dev/mtd1
> MTD_open
> MTD_ioctl
> MTD_write
> MTD do_write_buffer(): software timeout
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR ERROR ERROR ERROR ERROR ERROR ERROR
> MTD_close
> /dev #
>
> It all seems to be fine, but...
I disagree. There was a pretty clear error message above. Don't
ignore this, it will bite you later.
> dev # mount -t jffs2 /dev/mtdblock1 /mnt/Flash1
> mount: Mounting /dev/mtdblock1 on /mnt/Flash1 failed: No such device
Assuming that this is a mount builtin to the busybox, this message
means that there is no such file as "/dev/mtdblock1" in your root
file system - exactly as the error message says.
> I checked out the Majors of my ramdisk, they are ok.
What has a ramdisk to do with this?
What does "cat /proc/mtd" show? What are the kernel boot messages
look like?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"It was the Law of the Sea, they said. Civilization ends at the wa-
terline. Beyond that, we all enter the food chain, and not always
right at the top." - Hunter S. Thompson
next prev parent reply other threads:[~2005-04-21 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 9:17 mtd mount problem Marco Schramel
2005-04-21 8:50 ` Eugene Surovegin
2005-04-21 9:44 ` Marco Schramel
2005-04-21 15:47 ` Eugene Surovegin
2005-04-21 9:54 ` Daniel Ann
2005-04-21 10:32 ` Wolfgang Denk [this message]
2005-04-21 13:02 ` Marco Schramel
2005-04-22 1:31 ` Jörn Engel
2005-04-22 1:53 ` Eugene Surovegin
2005-04-22 1:55 ` Eugene Surovegin
2005-04-22 2:11 ` Jörn Engel
2005-04-21 14:44 ` Kylo Ginsberg
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=20050421103234.ED367C1510@atlas.denx.de \
--to=wd@denx.de \
--cc=Schramel.Linux@go.bartec.de \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).