Alexander Ziegler

Boot LTIB generated root file system with NFS

Discussion created by Alexander Ziegler on May 13, 2011
Latest reply on Jul 8, 2011 by Claude_Sylvain

First, i have compiled and installed the LTIB contained in the package L2.6.35_11.03.00_ER_source.tar.gz under Ubuntu 10.04 on a real machine (no VM) according to the steps described in the documents "i.MX53 START Linux" and ltib_build_host_setup.pdf.

Then i configured LTIB for the i.MX53 QSB as target. The compilation finished without errors

and the /rootfs folder was created successfully. I have flashed  and setup u-boot to the micro-sd.


When i start the board first the kernel is loaded successfully over ethernet from the host. The kernel

then mounts the /rootfs directory via NFS. But then after loading many modules

the startup aborts with the following error message in the serial terminal:


gtk: creating gdk-pixbuf.loaders

pango: creating module list
starting pid 2218, tty '': '/sbin/getty -L ttymxc0 115200 vt100'
(EE) XKB: Couldn't open rules file /usr/share/X11/xkb/rules/base
(EE) XKB: No components provided for device Virtual core keyboard

Backtrace (0 deep):

Fatal server error:
Segmentation fault caught

Can't deallocate console 2 Device or resource busy

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Wed, 11 May 2011 17:47:44 +0200
Freescale Semiconductor, Inc.

freescale login: matchbox-panel: failed to open displaymatchbox-desktop: unable to open display !
matchbox: can't open display! check your DISPLAY variable.
ts_open: No such file or directory


I have checked the folder /usr/share/X11 which contains only a text file. I have compared

the own generated rootfs with the rootfs contained in the demo image L2.6.35_11.03.00_ER_images_MX5X.tar.gz and it seams that many of files for X11 do not exist.

Is there a need to manually install packages with LTIB to the own build /rootfs ? I have checked

that all X11 packages are selected in LTIB before build the rootfs.

I have also tried the 11.01 packages but the behavior is the same.


What is wrong?


I have attached the complete output in the serial terminal and the u-boot configuration.