mx28,i use nand boot,and mount nfs is ok.But i use the same rootfs,make ubifs,can not mount rootfs,stop here:Freeing init memory: 160K

[HaohuaQIN]

hi,all

i use mx28 nfs boot.setenv:

setenv bootargs gpmi=g root=/dev/nfs rw console=ttyAM0,115200n8 nfsroot=192.168.1.51:/home/rootfs ip=192.168.1.110:192.168.1.51:192.168.1.1:255.255.255.0:epc.qust.edu.com:eth0:off

i can mount rootfs by nfs,it is work ok.

but i use the same rootfs,make rootfs.ubifs,like this:

root@qhh-ubuntu:/home# mkfs.ubifs -r rootfs   -m 2048 -e 126976 -c 1900 -o ubifs.img

root@qhh-ubuntu:/home# ubinize -o ubi.img -m 2048 -p 128KiB -s 512 ubinize.cfg

ubinize: volume alignment was not specified in section "rootfs", assume 1

root@qhh-ubuntu:/home# mv ubifs.img rootfs.ubifs

and then,burn to nandflash,and setenv to nand boot:

setenv bootargs gpmi=g console=ttyAM0,115200n8 console=tty0 ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs ip=192.168.1.110:192.168.1.51:192.68.1.1:255.255.255.0::eht0: fec_mac= ethact

kernel console print:

Creating 2 MTD partitions on "gpmi-nfc-main":

0x000000000000-0x000001400000 : "gpmi-nfc-0-boot"

0x000001400000-0x000008000000 : "gpmi-nfc-general-use"

UBI: attaching mtd1 to ubi0

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    126976 bytes

UBI: smallest flash I/O unit:    2048

UBI: VID header offset:          2048 (aligned 2048)

UBI: data offset:                4096

UBI: attached mtd1 to ubi0

UBI: MTD device name:            "gpmi-nfc-general-use"

UBI: MTD device size:            108 MiB

UBI: number of good PEBs:        860

UBI: number of bad PEBs:         4

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 860

UBI: number of PEBs reserved for bad PEB handling: 8

UBI: max/mean erase counter: 2/1

UBI: image sequence number: 0

UBI: background thread "ubi_bgt0d" started, PID 1010

ubiblka: unknown partition table

FEC Ethernet Driver

fec_enet_mii_bus: probed

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci: irq 93, io base 0x80080000

fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

can't find transceiver

fsl-ehci fsl-ehci: remove, state 1

usb usb1: USB disconnect, address 1

fsl-ehci fsl-ehci: USB bus 1 deregistered

fsl-ehci fsl-ehci: init fsl-ehci fail, -19

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 92, io base 0x80090000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

usbserial: USB Serial Driver core

USB Serial support registered for cp210x

usbcore: registered new interface driver cp210x

cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver

USB Serial support registered for FTDI USB Serial Device

usbcore: registered new interface driver ftdi_sio

ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver

USB Serial support registered for pl2303

usbcore: registered new interface driver pl2303

pl2303: Prolific PL2303 USB to serial adaptor driver

ARC USBOTG Device Controller driver (1 August 2005)

Can't find OTG driver!

mice: PS/2 mouse device common for all mice

input: MXS touchscreen as /devices/virtual/input/input0

rtc-pcf8563 0-0051: chip found, driver version 0.4.3

rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0

i2c /dev entries driver

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

Linux video capture interface: v2.00

mxs-pxp mxs-pxp.0: initialized

mxs watchdog: initialized, heartbeat 19 sec

mxs-mmc: MXS SSP Controller MMC Interface driver

mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96

usb 1-1: new full speed USB device using fsl-ehci and address 2

dcp dcp.0: DCP crypto enabled.!

usbcore: registered new interface driver hiddev

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

ALSA device list:

  No soundcards found.

TCP cubic registered

NET: Registered protocol family 17

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

rtc-pcf8563 0-0051: low voltage detected, date/time is not reliable.

rtc-pcf8563 0-0051: setting system clock to 2014-06-06 00:43:16 UTC (1402015396)

hub 1-1:1.0: USB hub found

hub 1-1:1.0: 4 ports detected

UBIFS: recovery needed

UBIFS: recovery completed

UBIFS: mounted UBI device 0, volume 0, name "rootfs"

UBIFS: file system size:   106278912 bytes (103788 KiB, 101 MiB, 837 LEBs)

UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)

UBIFS: media format:       w4/r0 (latest is w4/r0)

UBIFS: default compressor: lzo

UBIFS: reserved for root:  0 bytes (0 KiB)

VFS: Mounted root (ubifs filesystem) on device 0:14.

Freeing init memory: 160K

stop here!!

not to continue work.

i think nfs is work ok,and the rootfs is should be ok also.

i donot know the problem is where.

thanks!!

[HaohuaQIN]

hi,all

i find that the telnet is ok.

so,the system is work,and only console is not work.

thanks!!

[Rita_Wang]

Hi Haohua,

Which screen are you using to display? I see that in your u-boot  you set bootargs console=tty0, so the console will display on your screen. I wonder if you have set correct information for screen display.
Have a great day,
Dan

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[HaohuaQIN]

Thanks for your reply.

bootargs is right,no problem.

I think the problem is inittab in /rootfs/etc/.

My inittab is below,I set rootfs not need to login,and not need to "Plesae press enter to activate this console",and this inittab is work ok in my other platform.

old inittab:

::sysinit:/etc/init.d/rcS

::respawn:-/bin/sh

::/bin/sh

::restart:/sbin/init
::ctrlaltdel:/sbin/reboot
::shutdown:/bin/umount -a -r
::shutdown:/sbin/swapoff -a

I set the telnet is open in the rcS.

When power on,the telnet is work ok,so,this can be proved that the rcS is work and the system is work ok.

Only the console is not work.

Now i add "::respawn:/sbin/getty -L ttyAM0 115200 vt100" to enable login.

like this:

::sysinit:/etc/init.d/rcS

::respawn:-/bin/sh

::/bin/sh

::respawn:/sbin/getty -L ttyAM0 115200 vt100

::restart:/sbin/init
::ctrlaltdel:/sbin/reboot
::shutdown:/bin/umount -a -r
::shutdown:/sbin/swapoff -a

then,after power on,the console is work, let me to login.

But the start information of rcS is not printed.

Thanks!!