On 3/15/16 4:01 PM, Safa Hamza wrote: > i solve the problem by degugging the linux kernel .. the problem was the > instruction omap_smc1 ..i'm not sure about what it did but when i delete > this instruction it works ... but i face another problem .. the execution > now stops in > [ 2.610379] VFS: Mounted root (ext4 filesystem) on device 179:2. > [ 2.623192] devtmpfs: mounted > [ 2.623584] Freeing unused kernel memory: 340K (c079e000 - c07f3000) > INIT: version 2.88 booting > Starting udev > [ 3.169771] udev[871]: starting version 164 > [ 5.205065] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some > data may be corrupt. Please run fsck. > [ 5.400187] EXT4-fs (mmcblk1p4): recovery complete > [ 5.400309] EXT4-fs (mmcblk1p4): mounted filesystem with ordered data > mode. Opts: (null) > [ 5.492162] random: nonblocking pool is initialized > ERROR: could not open directory > /lib/modules/3.15.0-rc2-00199-g0c0a3e5-dirty: No such file or directory > WARNING: -e needs -E or -F > ERROR: could not open directory > /lib/modules/3.15.0-rc2-00199-g0c0a3e5-dirty: No such file or directory > FATAL: could not search modules: No such file or directory > Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file > or directory > bootlogd. > [ 5.831227] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered > ALSA: Restoring mixer settings... > Configuring network interfaces... /usr/sbin/alsactl: load_state:1686: No > soundcards found... > ifconfig: SIOCGIFFLAGS: No such device > done. > hwclock: can't open '/dev/misc/rtc': No such file or directory > Mon Jul 1 15:13:00 UTC 2013 > hwclock: can't open '/dev/misc/rtc': No such file or directory > INIT: Entering runlevel: 5 > Starting telnet daemon. > hwclock: can't open '/dev/misc/rtc': No such file or directory > Starting syslogd/klogd: done > Starting thttpd. > Stopping Bootlog daemon: bootlogd. > > *************************************************************************************************************************************************** > no console appears .. i guess the problem in the file system ... but this > file works fine with the linux kernel in omap5 without the xen hypervisor > > should i make any changement in the rootfs so it can works with xen > hypervisor !! or any other solution !! > Regards > The issue is likely that you don't have a getty setup on /dev/hvc0. Edit your /etc/inittab and add one. Maybe something like: h0:2345:respawn:/sbin/agetty 38400 hvc0 linux But honestly there's other problems with the image you are using so you'll likely run into more but those look like Linux/distro related problems. Please make sure you reply to the list if you do reply to this. -- Doug Goldstein