public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: tommy <jiujin.hong@mid-fun.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: about ubiformat mtdblock
Date: Wed, 01 Jul 2009 19:13:28 +0800	[thread overview]
Message-ID: <1246446808.11095.2.camel@tommy-desktop> (raw)
In-Reply-To: <1246446371.20721.22.camel@localhost.localdomain>

THANKS!~
Kernel command line: console=ttySAC0,115200 ubi.mtd=2 root=ubi0_0
rootfstype=ubifs

mount: mounting proc on /proc failed: Device or resource busy      
WARNING: Couldn't open directory /lib/modules/2.6.24.2: No such file or
directory
FATAL: Could not open /lib/modules/2.6.24.2/modules.dep.temp for
writing: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.24.2/modules.dep: No
such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.24.2/modules.dep: No
such file or directory

open_ubi name rootfs<3>UBIFS error (pid 576): ubifs_get_sb: cannot open
"rootfs", error -22 

root@localhost:/etc/rcS.d# vi S35mountall.sh
#
# Mount local filesystems in /etc/fstab. For some reason, people
# might want to mount "proc" several times, and mount -v complains
# about this. So we mount "proc" filesystems without -v.
#
test "$VERBOSE" != no && echo "Mounting local filesystems..."
mount -at nonfs,nosmbfs,noncpfs 2>/dev/null

root@localhost:/etc/rcS.d# cat ../fstab
# stock fstab - you probably want to override this with a machine
specific one

rootfs               /                    auto       defaults
1  1
proc                 /proc                proc       defaults
0  0
devpts               /dev/pts             devpts     mode=0620,gid=5
0  0
#usbdevfs             /proc/bus/usb        usbdevfs   noauto
0  0
tmpfs                /var                 tmpfs      defaults
0  0
tmpfs                /mnt/ram           tmpfs      defaults
0  0

# uncomment this if your device has a SD/MMC/Transflash slot
#/dev/mmcblk0p1       /media/card          auto
defaults,sync,noauto  0  0



On 三, 2009-07-01 at 14:06 +0300, Artem Bityutskiy wrote:
> On Wed, 2009-07-01 at 18:58 +0800, tommy wrote:
> > ps:
> > 
> > if my board nfs boot ,not ubifs boot,following is ok!
> > nfs@root:ubiattach /dev/ubi_ctrl -m 2
> > nfs@root:mount -t ubifs ubi0_0 /mnt /
> > it it ok!
> 
> Try adding:
> 
> ubi.mtd=0 root=ubi0_0 rootfstype=ubifs
> 
> to the kernel boot line.
> 

  reply	other threads:[~2009-07-01 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 10:03 about ubiformat mtdblock tommy
2009-06-26 10:46 ` Artem Bityutskiy
2009-06-27  3:49   ` tommy
2009-06-27 11:32     ` Artem Bityutskiy
2009-06-29  2:14       ` tommy
2009-06-30 14:51         ` Artem Bityutskiy
2009-07-01  0:54           ` tommy
2009-07-01  9:50             ` Artem Bityutskiy
2009-07-01 10:43               ` tommy
2009-07-01 10:45                 ` Artem Bityutskiy
2009-07-01 10:58                   ` tommy
2009-07-01 11:06                     ` Artem Bityutskiy
2009-07-01 11:13                       ` tommy [this message]
2009-07-02  9:39           ` tommy
     [not found]             ` <d16af8a00907020255r60112844qbb7f020afd9a1ac0@mail.gmail.com>
2009-07-02 10:13               ` tommy

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=1246446808.11095.2.camel@tommy-desktop \
    --to=jiujin.hong@mid-fun.com \
    --cc=dedekind@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