On 14-08-06 10:26:23, Gary Thomas wrote: > On 2014-08-06 10:13, Dr. Markus Eich wrote: > >Dear all, > > > >I am trying to build an image for the Odroid XU, featuring the Samsung Octa > >5 CPU > > > >I managed to build everything needed (modules, kernel, u-boot, etc.) > > > >The recipes can be found at: https://github.com/MarkusEich/meta-odroid. > > > >The last problem (hopefully last :-) I have is that I cannot log in after > >the kernel is loaded via UART console > > > >Maybe init.d or systemd is not setup properly? > > > >I am using the console-image-minimal.bb from meta. > > > >Here is the last console output. It seems that the kernel is loaded > >(including modules) and the rootfs is properly mounted. There is no error, > >there is simply no login or shell. > > > >Any ideas why I cannot login? Its a bit poking in the dark ATM. > > If you are using systemd, make sure your kernel is built with CONFIG_FHANDLE=y > Without this, systemd won't start a session on a serial port. > > If you're using the old sysvinit, make sure your console settings > are correct. These normally live in your ${MACHINE}.conf and look > something like this: > SERIAL_CONSOLE = "115200 ttymxc0" > > You might also want to remove 'quiet' from your kernel bootargs, > at least until you get things settled a bit more.
see the needed kernel config options here http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system > >[ 5.993533] Freeing init memory: 256K > >[ 5.996898] Write protecting the kernel text section c0008000 - c09e2000 > >[ 6.003931] rodata_test: attempting to write to read-only section: > >[ 6.009728] write to read-only section trapped, success > >[ 6.055010] systemd-udevd[1299]: starting version 204 > >[ 6.350360] EXT4-fs (mmcblk0p2): recovery complete > >[ 6.356827] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data > >mode. Opts: (null) > >INIT: version 2.88 booting > >Starting udev > >[ 6.880415] udevd[1376]: starting version 182 > >[ 7.075108] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered > >Starting Bootlog daemon: bootlogd. > >[ 7.369381] max77802_rtc_read_time: 114/7/6 16:10:3(3) > >INIT: Entering runlevel: 5 > >Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device > >[ 7.431705] max77802_rtc_read_time: 114/7/6 16:10:4(3) > >Starting syslogd/klogd: done > >Stopping Bootlog daemon: bootlogd. it seems you have a mix of systemd and sysvinit scripts stepping over each other so may be just go for systemd only init system in local.conf set DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
