* jffs2 root filesystem
@ 2004-11-09 16:30 sam
2004-11-09 18:00 ` Michael
2004-11-09 18:05 ` Jeff Angielski
0 siblings, 2 replies; 4+ messages in thread
From: sam @ 2004-11-09 16:30 UTC (permalink / raw)
To: linux-mtd
hi
I try to port linux-2.4.19-rmk1 to a pxa255 board
i am success to use MTD partition and can mount it
But when i try to use MTD as root filesystem (root=/dev/mtdblock/3
console=ttyS0,38400)
kernel boot message show:
.......
physmap flash device: 2000000 at 0
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
mtd: Giving out device 0 to Physically mapped flash
MTD partition setup...
partition num: 4
Using physmap partition definition
Creating 4 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "U-boot"
mtd: Giving out device 1 to U-boot
0x00040000-0x00340000 : "zImage"
mtd: Giving out device 2 to zImage
0x00340000-0x00a00000 : "ramdisk"
mtd: Giving out device 3 to ramdisk
0x00a00000-0x02000000 : "User system"
mtd: Giving out device 4 to User system
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double precision)
mtdblock_open
ok
mtdblock: read on "Physically mapped flash" at 0x400, size 0x400
mtdblock_release
ok
mtdblock_open
ok
mtdblock: read on "Physically mapped flash" at 0x0, size 0x200
FAT: bogus logical sector size 5349
mtdblock_release
ok
mtdblock_open
ok
mtdblock: read on "Physically mapped flash" at 0x0, size 0x200
FAT: bogus logical sector size 5349
mtdblock_release
ok
mtdblock_open
ok
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
0x0016 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
0x0160 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
0x01c0 instead
Further such events for this erase block will not be printed
JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing init memory: 64K
Warning: unable to open an initial console.
Kernel panic: No init found. Try passing init= option to kernel.
..................
why can't i use mtd as my root disk
Sam
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: jffs2 root filesystem
2004-11-09 16:30 sam
@ 2004-11-09 18:00 ` Michael
2004-11-09 18:05 ` Jeff Angielski
1 sibling, 0 replies; 4+ messages in thread
From: Michael @ 2004-11-09 18:00 UTC (permalink / raw)
To: sam; +Cc: linux-mtd
> FAT: bogus logical sector size 5349
This is wierd. I wonder if it's trying to mount it as a FAT
filesystem first. Most people usually include 'rootfstype=jffs2'
in the command line.
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
> 0x00000000:
> 0x0016 instead
I think there's mention of this in the mailing list. Can you try
searching the archives and see what this indicates?
> Freeing init memory: 64K
> Warning: unable to open an initial console.
> Kernel panic: No init found. Try passing init= option to kernel.
> ..................
> why can't i use mtd as my root disk
It looks like you ARE using MTD for your root disk. I usually get
this "unable to open an initial console" warning / error when the
device file /dev/console doesn't exist. Perhaps the above error is
messing up the root filesystem.
BTW, have you tried booting off a ramdisk and manually mounting
that partition? That should clear up most of the issues that you'd
run into, but it's much easier to debug.
I hope this makes sense and that it helps.
Mike
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: jffs2 root filesystem
2004-11-09 16:30 sam
2004-11-09 18:00 ` Michael
@ 2004-11-09 18:05 ` Jeff Angielski
1 sibling, 0 replies; 4+ messages in thread
From: Jeff Angielski @ 2004-11-09 18:05 UTC (permalink / raw)
To: sam; +Cc: linux-mtd
On Tue, 2004-11-09 at 11:30, sam wrote:
> hi
>
> I try to port linux-2.4.19-rmk1 to a pxa255 board
> i am success to use MTD partition and can mount it
> But when i try to use MTD as root filesystem (root=/dev/mtdblock/3
> console=ttyS0,38400)
> kernel boot message show:
Try using /dev/mtdblock3.
And is the flash really mapped at 0x00000000?
Jeff Angielski
The PTR Group
^ permalink raw reply [flat|nested] 4+ messages in thread
* jffs2 root filesystem
@ 2005-08-11 13:32 Alex Karev
0 siblings, 0 replies; 4+ messages in thread
From: Alex Karev @ 2005-08-11 13:32 UTC (permalink / raw)
To: linux-mtd
It seems that problem gone with upgrading to 2.6. kernel.
Thanks to all, and my apologize for distraction. 2.4. kernel was wish of
our customer, but now we have strong arguments to debate about 2.6 :-)
Now we are trying to make root file system on nand, and here come some
mysterious debug output while booting which we can't interpreter.
The operation order was:
1. flash_eraseall -j /dev/mtdN
2. mount -t jffs2 /dev/mtblockN /mnt
3. ... copy root fs files to /mnt
4. umount /mnt
5. verification and mount umount test -> all ok.
we also was playing with mkfs.jffs2 and nandwrite, but failed even to
mount files ytem.
mkfs.jffs2 -e 0x4000 -l -r ... -o ...
nandwrite -j /dev/mtdN img
where N = [0,1];
While booting we have:
Loading kernel..............................Ready.
Linux version 2.6.12.4 (alex@slack-srv) (gcc version 3.3.4) #1 Thu Aug 11 14:57:31 MSD 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009d800 (usable)
BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000008000000 (usable)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
128MB LOWMEM available.
DMI not present.
Allocating PCI resources starting at 08000000 (gap: 08000000:f7f00000)
Built 1 zonelists
Kernel command line: BOOT_IMAGE=kernel root=/dev/mtdblock0 rootfs=jffs2 vag=0x315 console=ttyS0,115200n8 console=tty1
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Detected 199.618 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 125704k/131072k available (2217k kernel code, 4912k reserved, 945k data, 168k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512
CPU: Rise iDragon
CPU: Rise iDragon stepping 01
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xff6cc, last bus=0
PCI: Using configuration type 1
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0d.0
audit: initializing netlink socket (disabled)
audit(1123793271.425:0): initialized
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
JFFS2: default compression mode: priority
vga16fb: mapped to 0xc00a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device
Non-volatile memory driver v1.2
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ÿttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002
originally by Donald Becker <becker@scyld.com>
http://www.scyld.com/network/natsemi.html
2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
natsemi eth0: NatSemi DP8381[56] at 0xfa000000 (0000:00:17.0), 00:08:b3:00:00:1e, IRQ 10, port TP.
natsemi eth1: NatSemi DP8381[56] at 0xfa001000 (0000:00:18.0), 00:08:b3:00:00:1f, IRQ 10, port TP.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hdc: SAMSUNG CF/ATA, CFA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: max request size: 128KiB
hdc: 254208 sectors (130 MB) w/0KiB Cache, CHS=993/8/32
hdc: cache flushes not supported
hdc: hdc1 hdc2
Flash driver build on Aug 11 2005 at 14:42:17
Reseting flash control register
NAND device: Manufacturer ID: 0xec, Chip ID: 0x73 (Samsung NAND 16MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 339 at 0x0054c000
Bad eraseblock 683 at 0x00aac000
Bad eraseblock 999 at 0x00f9c000
Using static partition definition
Creating 2 MTD partitions on "NAND 16MiB 3,3V 8-bit":
0x00000000-0x00800000 : "Nand Flash MAIN"
mtd: Giving out device 0 to Nand Flash MAIN
0x00800000-0x01000000 : "Nand Flash JFFS"
mtd: Giving out device 1 to Nand Flash JFFS
Return happy
usbmon: debugs is not available
USB Universal Host Controller Interface driver v2.2
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
ip_conntrack version 2.1 (1024 buckets, 8192 max) - 212 bytes per conntrack
input: AT Translated Set 2 keyboard on isa0060/serio0
ip_tables: (C) 2000-2002 Netfilter core team
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 1
NET: Registered protocol family 17
mtdblock_open
ok
mtdblock_release
ok
mtdblock_open
ok
mtdblock_release
ok
mtdblock_open
ok
mtdblock_release
ok
mtdblock_open
ok
mtdblock_release
ok
mtdblock_open
ok
mtdblock_release
ok
mtdblock_open
ok
input: GenPS/2 Genius Wheel Mouse on isa0060/serio1
mtdblock_release
ok
mtdblock_open
ok
mtdblock_release
ok
mtdblock_open
ok
nand_read_ecc: Failed ECC read, page 0x00002a60
nand_read_ecc: Failed ECC read, page 0x00002a60
end_request: I/O error, dev mtdblock0, sector 10848
UDF-fs: No VRS found
mtdblock_release
ok
Kernel panic - not syncing: VFS: U
UDF filesytem not compiled into the kernel.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-08-11 13:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-11 13:32 jffs2 root filesystem Alex Karev
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 16:30 sam
2004-11-09 18:00 ` Michael
2004-11-09 18:05 ` Jeff Angielski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox