From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: Andre Puschmann <andre.puschmann@stud.tu-ilmenau.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting mtd block device raises "Block device required"
Date: Wed, 11 Jun 2008 10:55:01 +0200 [thread overview]
Message-ID: <484F92E5.2080207@cetrtapot.si> (raw)
In-Reply-To: <g2o39t$703$1@ger.gmane.org>
Andre Puschmann wrote:
> Hi list,
>
> I am successfully running kernel 2.6.21 on a custom AT91RM9200-based
> board. I now updated to kernel 2.6.25 for various reasons.
>
> Now, we use the _new_ atmel_spi driver and mtd_dataflash driver (but the
> problem also exist if I use the legacy one). If I try to mount a
> jffs2 or cramfs image on dataflash I get the following error:
> # mount /dev/mtdblock5 /mnt/flash
> mount: mounting /dev/mtdblock5 on /mnt/flash failed: Block device required
>
> Exactly the same line works with the 2.6.21 kernel. Also doing a cat
> on the normal /dev/mtd* nodes also works.
Char device seems to work..
>
> "cat /proc/devices" shows:
>
> Block devices:
> 7 loop
> 31 mtdblock
>
> So I have no idea here. Any hints?
What is the ls -l /dev/mtdblock5 output?
Also could you try:
mount -t jffs2 /dev/mtdblock5 /mnt/flash
HTH,
Hinko
--
ČETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar@cetrtapot.si
Http: www.cetrtapot.si
next prev parent reply other threads:[~2008-06-11 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 8:44 Mounting mtd block device raises "Block device required" Andre Puschmann
2008-06-11 8:55 ` Hinko Kocevar [this message]
2008-06-11 9:26 ` Andre Puschmann
2008-06-11 9:38 ` Nancy
2008-06-11 9:55 ` Hinko Kocevar
2008-06-11 10:33 ` Andre Puschmann
2008-06-12 13:08 ` Andre Puschmann
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 18:10 Fabiano Ferronato
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=484F92E5.2080207@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--cc=andre.puschmann@stud.tu-ilmenau.de \
--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