command line partition information

command line partition information

[Joaquin Luna]

[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]

Hello Linux powerpc community,

 

I am trying to move from 2.6.20 kernel to the new 2.6.27.4 kernel.  I am
not finding my root file system partition with the new kernel.  I am not
sure if I need to change my dts file, or if the problem is some where in
my kernel config.  In either case, it is evident from the boot log that
my partition table is not being used.  Where it says "[    0.917162]
List of all partitions:" it just lists the entire size of my flash, and
none of the partitions listed in the command line.

I do not list any partitions in my dts file, though I tried and not seen
any change in the behavior.  I have enabled the option in the kernel to
parse the partition information from the kernel command line, is there
something else I need to do to set up the mtdblockX devices?

 

Boot Command:

 

mtdparts=mtdparts=nand0:2m(u-boot),3M(kernel),128K(dtb),30M(jffs2),32M(m
ycust),90M(myfs),90M(myfs2)

mtd_args=setenv bootargs root=/dev/mtdblock3 rw rootfstype=jffs2
$mtdparts console=ttyS1,115200

 

Boot Log: 

 

[    0.825229] brd: module loaded

[    0.837681] loop: module loaded

[    0.841404] Driver 'sd' needs updating - please use bus_type methods

[    0.850005] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron
NAND 256MiB 3,3V 8-bit)

[    0.859783] Bad block table found at page 131008, version 0x01

[    0.867779] Bad block table found at page 130944, version 0x01

[    0.875443] RedBoot partition parsing not available

[    0.884431] eLBC NAND device at 0xff800000, bank 0

[    0.890643] i2c /dev entries driver

[    0.899633] Driver for 1-wire Dallas network protocol.

[    0.910115] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

[    0.917162] List of all partitions:

[    0.920856] 1f00     262144 mtdblock0 (driver?)

[    0.925466] No filesystem could mount root, tried:  jffs2

[    0.930952] Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(0,0)

[    0.939294] Rebooting in 180 seconds..

 

 

 

Thanks to all who can help,

Joaquin Luna


[-- Attachment #2: Type: text/html, Size: 7890 bytes --]

RE: command line partition information

[MingLiu]

[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]


Hello,
I had the same problem when I use 2.6.27-rc9 with Intel p33 NOR flash memory. My command line is "root=/dev/nfs ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,9600 mem=64M mtdparts=Intel:5M(kernel),2M(others),-(bitstream)". However the command line partition could not be parsed and there is still only one partition when I boot the kernel. 
 
Are there any persons who manage to use the command line partition option for flash memory? Please give us some hints. Thanks a lot. 
 
BR
Ming



Subject: command line partition informationDate: Sun, 16 Nov 2008 15:43:40 -0800From: Joaquin.Luna@jdsu.comTo: linuxppc-embedded@ozlabs.org





Hello Linux powerpc community,
 
I am trying to move from 2.6.20 kernel to the new 2.6.27.4 kernel.  I am not finding my root file system partition with the new kernel.  I am not sure if I need to change my dts file, or if the problem is some where in my kernel config.  In either case, it is evident from the boot log that my partition table is not being used.  Where it says “[    0.917162] List of all partitions:" it just lists the entire size of my flash, and none of the partitions listed in the command line.
I do not list any partitions in my dts file, though I tried and not seen any change in the behavior.  I have enabled the option in the kernel to parse the partition information from the kernel command line, is there something else I need to do to set up the mtdblockX devices?
 
Boot Command:
 
mtdparts=mtdparts=nand0:2m(u-boot),3M(kernel),128K(dtb),30M(jffs2),32M(mycust),90M(myfs),90M(myfs2)
mtd_args=setenv bootargs root=/dev/mtdblock3 rw rootfstype=jffs2 $mtdparts console=ttyS1,115200
 
Boot Log: 
 
[    0.825229] brd: module loaded
[    0.837681] loop: module loaded
[    0.841404] Driver 'sd' needs updating - please use bus_type methods
[    0.850005] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    0.859783] Bad block table found at page 131008, version 0x01
[    0.867779] Bad block table found at page 130944, version 0x01
[    0.875443] RedBoot partition parsing not available
[    0.884431] eLBC NAND device at 0xff800000, bank 0
[    0.890643] i2c /dev entries driver
[    0.899633] Driver for 1-wire Dallas network protocol.
[    0.910115] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    0.917162] List of all partitions:
[    0.920856] 1f00     262144 mtdblock0 (driver?)
[    0.925466] No filesystem could mount root, tried:  jffs2
[    0.930952] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.939294] Rebooting in 180 seconds..
 
 
 
Thanks to all who can help,
Joaquin Luna
_________________________________________________________________
MSN资讯快递，帮助你第一时间了解最新资讯！
http://im.live.cn/newsexpress

[-- Attachment #2: Type: text/html, Size: 7811 bytes --]

Re: command line partition information

[Scott Wood]

Joaquin Luna wrote:
> I do not list any partitions in my dts file, though I tried and not seen 
> any change in the behavior.  I have enabled the option in the kernel to 
> parse the partition information from the kernel command line, is there 
> something else I need to do to set up the mtdblockX devices?

Did you enable CONFIG_MTD_OF_PARTS for device-tree-based partitions?

> mtdparts=mtdparts=nand0:2m(u-boot),3M(kernel),128K(dtb),30M(jffs2),32M(mycust),90M(myfs),90M(myfs2)

Try replacing "nand0" with "ff800000.flash".

-Scott

RE: command line partition information

[Joaquin Luna]

Scott,

Thanks for your help, I was able to get it working with the open
firmware option you suggested.  I had tried this a few days back with no
luck, but I think my problem at that time was that my label "nand0" did
not match what was in the dts file.  I didn't give open firmware much
attention because I am using the command line for the partition
information in my working 2.6.20 kernel.  After spending this much time
on it though, I'll take what I can get.

Thanks,
Joaquin Luna

PS

U-boot did not accept "ff800000.flash" as the MTD ID and could not load
the kernel image with that in the command line.

-----Original Message-----
From: Scott Wood [mailto:scottwood@freescale.com]=20
Sent: Monday, November 17, 2008 11:59 AM
To: Joaquin Luna
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: command line partition information

Joaquin Luna wrote:
> I do not list any partitions in my dts file, though I tried and not
seen=20
> any change in the behavior.  I have enabled the option in the kernel
to=20
> parse the partition information from the kernel command line, is there

> something else I need to do to set up the mtdblockX devices?

Did you enable CONFIG_MTD_OF_PARTS for device-tree-based partitions?

>
mtdparts=3Dmtdparts=3Dnand0:2m(u-boot),3M(kernel),128K(dtb),30M(jffs2),32=
M(m
ycust),90M(myfs),90M(myfs2)

Try replacing "nand0" with "ff800000.flash".

-Scott

Re: command line partition information

[Scott Wood]

Joaquin Luna wrote:
> U-boot did not accept "ff800000.flash" as the MTD ID and could not load
> the kernel image with that in the command line.

Why would u-boot care what you pass to the Linux command line?

-Scott

AMCC 460EX SATA drive on Canyonlands

[Henry Bausley]

I can't seem to see a SATA drive on my 460EX Canyonlands board.  Did I
miss something in the kernel configuration.  The drive is a Seagate
Baracuda  750M - ST3750330AS


Below are the messages I get:

sata-dwc sata-dwc.0: id 0, controller version 1.82
sata-dwc sata-dwc.0: DMA initialized
sata-dwc sata-dwc.0: **** No negotiated speed (nothing attached?) ****
scsi0 : sata-dwc
ata1: SATA max UDMA/133 irq 21
4cc000000.nor_flash: Found 1 x16 devices at 0x0 in 16-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
4cc000000.nor_flash: CFI does not contain boot bank location. Assuming
top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Creating 7 MTD partitions on "4cc000000.nor_flash":
0x00000000-0x001e0000 : "kernel"
0x001e0000-0x00200000 : "dtb"
0x00200000-0x01600000 : "ramdisk"
0x01600000-0x01a00000 : "jffs2"
0x01a00000-0x03f60000 : "user"
0x03f60000-0x03fa0000 : "env"
0x03fa0000-0x04000000 : "u-boot"
ppc-of-ehci 4bffd0400.ehci: OF EHCI
ppc-of-ehci 4bffd0400.ehci: new USB bus registered, assigned bus number
1
ppc-of-ehci 4bffd0400.ehci: irq 33, io mem 0x4bffd0400
ppc-of-ehci 4bffd0400.ehci: USB 2.0 started, EHCI 1.00, driver 10 Dec
2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usb 1-1: new high speed USB device using ppc-of-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 2 ports detected
usb 1-1.1: new high speed USB device using ppc-of-ehci and address 3
usb 1-1.1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.

RE: AMCC 460EX SATA drive on Canyonlands

[Ayman El-Khashab]

=20

nlands
>=20
> I can't seem to see a SATA drive on my 460EX Canyonlands=20
> board.  Did I miss something in the kernel configuration. =20
> The drive is a Seagate Baracuda  750M - ST3750330AS
>=20

Maybe, but on that board the SATA and PCI-E 1L are shared and there is a
jumper to pick which one you want.