public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jim Zeus <zeusj@firstlinux.net>
To: David Woodhouse <dwmw2@infradead.org>,
	"David  Woodhouse" <dwmw2@infradead.org>
Cc: all in MTD mailinglist <linux-mtd@lists.infradead.org>
Subject: Whats wrong with my jffs2?
Date: Wed, 27 Mar 2002 21:46:04 -0800 (PST)	[thread overview]
Message-ID: <20020328054604.BFC5D2755@sitemail.everyone.net> (raw)


--- David Woodhouse <dwmw2@infradead.org> wrote:
>
>zeusj@firstlinux.net said:
>>     Can you tell me why only my mtd char device with even minor deivce
>> number works? and there is no such thing happened on my mtd block
>> device. 
>
>Did you run the MAKEDEV script or try to make your devices by hand? If you 
>did them by hand, did you do so without referring to Documentation/devices.txt?
>
>grep -A6 " 90 char" /usr/src/linux/Documentation/devices.txt 

Thanks, I have checked the devices.txt, so I got why the odd mtd "permission denied". But if the device nodes with major 31 ,mi 0-7 are ROM card (as the device.txt said),why my flash can works without nothing wrong? I think the minor number should be 8-15 , isnt it?

one more question
when I use jffs as the root filesystem, everything is ok, but when I use jffs2 (I remeber that you said its more stable than jffs:), I got a problem some message appears on my screen and the root filesystem is readonly (this never happened on jffs), the following is the message:

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0014: 0x552f in
stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0018: 0x175e in
stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e001c: 0xcdf6 in
stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0020: 0xb7fb in
stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0024: 0x7615 in
stead

Further such events for this erase block will not be printed

VFS: Mounted root (jffs2 filesystem) readonly.

Freeing init memory: 40K

serial console detected.  Disabling virtual terminals.

init started:  BusyBox v0.60.2 (2002.02.24-07:14+0000) multi-call
mount: Mounting /dev/ram0 on / failed: No such device or address

mount: Mounting devpts on /dev/pts failed: Nh




BusyBox v0.60.2 (2002.02.24-07:25+0000) Built-in shell (msh)

Ee o-a


Processing /etc/profile... Done
#

Thank you very much!


Jim Zeus 


_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net

_____________________________________________________________
Run a small business? Then you need professional email like you@yourbiz.com from Everyone.net  http://www.everyone.net?tag

             reply	other threads:[~2002-03-28  5:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28  5:46 Jim Zeus [this message]
2002-03-28  7:23 ` Whats wrong with my jffs2? David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2002-03-29  1:25 Jim Zeus

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=20020328054604.BFC5D2755@sitemail.everyone.net \
    --to=zeusj@firstlinux.net \
    --cc=dwmw2@infradead.org \
    --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