* Building yocto for Odroid XU. No login after boot. @ 2014-08-06 16:13 Dr. Markus Eich 2014-08-06 16:26 ` Gary Thomas 0 siblings, 1 reply; 7+ messages in thread From: Dr. Markus Eich @ 2014-08-06 16:13 UTC (permalink / raw) To: yocto@yoctoproject.org 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. Cheers, Markus == [ 5.722795] CPUFREQ of CA7 L5 : 962500 uV [ 5.726871] CPUFREQ of CA7 L6 : 950000 uV [ 5.730947] CPUFREQ of CA7 L7 : 950000 uV [ 5.735025] CPUFREQ of CA7 L8 : 950000 uV [ 5.739095] CPUFREQ of CA7 L9 : 950000 uV [ 5.743146] CPUFREQ of CA7 L10 : 950000 uV [ 5.747336] CPUFREQ of CA7 L11 : 950000 uV [ 5.751583] CPUFREQ of CA15 L0 : 1362500 uV [ 5.755663] CPUFREQ of CA15 L1 : 1362500 uV [ 5.759826] CPUFREQ of CA15 L2 : 1225000 uV [ 5.764012] CPUFREQ of CA15 L3 : 1175000 uV [ 5.768129] CPUFREQ of CA15 L4 : 1137500 uV [ 5.772313] CPUFREQ of CA15 L5 : 1112500 uV [ 5.776474] CPUFREQ of CA15 L6 : 1075000 uV [ 5.780638] CPUFREQ of CA15 L7 : 1037500 uV [ 5.784800] CPUFREQ of CA15 L8 : 1000000 uV [ 5.788962] CPUFREQ of CA15 L9 : 975000 uV [ 5.793010] CPUFREQ of CA15 L10 : 937500 uV [ 5.797201] CPUFREQ of CA15 L11 : 912500 uV [ 5.801368] CPUFREQ of CA15 L12 : 900000 uV [ 5.805526] CPUFREQ of CA15 L13 : 900000 uV [ 5.809689] CPUFREQ of CA15 L14 : 900000 uV [ 5.813822] CPUFREQ of CA15 L15 : 900000 uV [ 5.818018] CPUFREQ of CA15 L16 : 900000 uV [ 5.822173] CPUFREQ of CA15 L17 : 900000 uV [ 5.826338] CPUFREQ of CA15 L18 : 900000 uV [ 5.830583] fout_apll[900000000] [ 5.836287] S divider change for DFS of MIF block [ 5.984276] init_volt[975000], freq[800000] [ 5.987809] ALSA device list: [ 5.989956] #0: Odroid-max98090 [ 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. == -- Dr.-Ing. Markus Eich Senior Researcher Marine Inspection Robotics Space Robotics Besuchsadresse der Nebengeschäftstelle: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 5 28359 Bremen, Germany Postadresse der Hauptgeschäftsstelle Standort Bremen: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 1 28359 Bremen, Germany Tel.: +49 421 178 45-4105 Zentrale: +49 421 178 45-0 Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen) E-Mail: markus.eich@dfki.de Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 ----------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Building yocto for Odroid XU. No login after boot. 2014-08-06 16:13 Building yocto for Odroid XU. No login after boot Dr. Markus Eich @ 2014-08-06 16:26 ` Gary Thomas 2014-08-07 6:24 ` Khem Raj 2014-08-07 12:51 ` Dr. Markus Eich 0 siblings, 2 replies; 7+ messages in thread From: Gary Thomas @ 2014-08-06 16:26 UTC (permalink / raw) To: yocto 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. > == > > [ 5.722795] CPUFREQ of CA7 L5 : 962500 uV > [ 5.726871] CPUFREQ of CA7 L6 : 950000 uV > [ 5.730947] CPUFREQ of CA7 L7 : 950000 uV > [ 5.735025] CPUFREQ of CA7 L8 : 950000 uV > [ 5.739095] CPUFREQ of CA7 L9 : 950000 uV > [ 5.743146] CPUFREQ of CA7 L10 : 950000 uV > [ 5.747336] CPUFREQ of CA7 L11 : 950000 uV > [ 5.751583] CPUFREQ of CA15 L0 : 1362500 uV > [ 5.755663] CPUFREQ of CA15 L1 : 1362500 uV > [ 5.759826] CPUFREQ of CA15 L2 : 1225000 uV > [ 5.764012] CPUFREQ of CA15 L3 : 1175000 uV > [ 5.768129] CPUFREQ of CA15 L4 : 1137500 uV > [ 5.772313] CPUFREQ of CA15 L5 : 1112500 uV > [ 5.776474] CPUFREQ of CA15 L6 : 1075000 uV > [ 5.780638] CPUFREQ of CA15 L7 : 1037500 uV > [ 5.784800] CPUFREQ of CA15 L8 : 1000000 uV > [ 5.788962] CPUFREQ of CA15 L9 : 975000 uV > [ 5.793010] CPUFREQ of CA15 L10 : 937500 uV > [ 5.797201] CPUFREQ of CA15 L11 : 912500 uV > [ 5.801368] CPUFREQ of CA15 L12 : 900000 uV > [ 5.805526] CPUFREQ of CA15 L13 : 900000 uV > [ 5.809689] CPUFREQ of CA15 L14 : 900000 uV > [ 5.813822] CPUFREQ of CA15 L15 : 900000 uV > [ 5.818018] CPUFREQ of CA15 L16 : 900000 uV > [ 5.822173] CPUFREQ of CA15 L17 : 900000 uV > [ 5.826338] CPUFREQ of CA15 L18 : 900000 uV > [ 5.830583] fout_apll[900000000] > [ 5.836287] S divider change for DFS of MIF block > [ 5.984276] init_volt[975000], freq[800000] > [ 5.987809] ALSA device list: > [ 5.989956] #0: Odroid-max98090 > [ 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. > > == > > > > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Building yocto for Odroid XU. No login after boot. 2014-08-06 16:26 ` Gary Thomas @ 2014-08-07 6:24 ` Khem Raj 2014-08-07 12:51 ` Dr. Markus Eich 1 sibling, 0 replies; 7+ messages in thread From: Khem Raj @ 2014-08-07 6:24 UTC (permalink / raw) To: Gary Thomas; +Cc: yocto 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" ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Building yocto for Odroid XU. No login after boot. 2014-08-06 16:26 ` Gary Thomas 2014-08-07 6:24 ` Khem Raj @ 2014-08-07 12:51 ` Dr. Markus Eich 2014-08-07 13:05 ` Gary Thomas 1 sibling, 1 reply; 7+ messages in thread From: Dr. Markus Eich @ 2014-08-07 12:51 UTC (permalink / raw) To: yocto Hi Gary, unfortunately, this didn't help much. I have compiled the kernel with the CONFIG_FHANDLE=y. I have also set all configs given in http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system To pinpoint the error down, I have tried the kernel build from Yocto on a LINARO distro image. I have just replaced the kernel and the modules build with yocto. And voila: I have a login promt. If the complete distro is build with Yocto (the whole rootfs), I cannot log in. Has setting the SERIAL_CONSOLE = "115200 ttymxc0" the same effect as giving the console param for the u-boot? i.e. I have something like #setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait rw" ? Cheers, Markus On 06.08.2014 18:26, 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. > >> == >> >> [ 5.722795] CPUFREQ of CA7 L5 : 962500 uV >> [ 5.726871] CPUFREQ of CA7 L6 : 950000 uV >> [ 5.730947] CPUFREQ of CA7 L7 : 950000 uV >> [ 5.735025] CPUFREQ of CA7 L8 : 950000 uV >> [ 5.739095] CPUFREQ of CA7 L9 : 950000 uV >> [ 5.743146] CPUFREQ of CA7 L10 : 950000 uV >> [ 5.747336] CPUFREQ of CA7 L11 : 950000 uV >> [ 5.751583] CPUFREQ of CA15 L0 : 1362500 uV >> [ 5.755663] CPUFREQ of CA15 L1 : 1362500 uV >> [ 5.759826] CPUFREQ of CA15 L2 : 1225000 uV >> [ 5.764012] CPUFREQ of CA15 L3 : 1175000 uV >> [ 5.768129] CPUFREQ of CA15 L4 : 1137500 uV >> [ 5.772313] CPUFREQ of CA15 L5 : 1112500 uV >> [ 5.776474] CPUFREQ of CA15 L6 : 1075000 uV >> [ 5.780638] CPUFREQ of CA15 L7 : 1037500 uV >> [ 5.784800] CPUFREQ of CA15 L8 : 1000000 uV >> [ 5.788962] CPUFREQ of CA15 L9 : 975000 uV >> [ 5.793010] CPUFREQ of CA15 L10 : 937500 uV >> [ 5.797201] CPUFREQ of CA15 L11 : 912500 uV >> [ 5.801368] CPUFREQ of CA15 L12 : 900000 uV >> [ 5.805526] CPUFREQ of CA15 L13 : 900000 uV >> [ 5.809689] CPUFREQ of CA15 L14 : 900000 uV >> [ 5.813822] CPUFREQ of CA15 L15 : 900000 uV >> [ 5.818018] CPUFREQ of CA15 L16 : 900000 uV >> [ 5.822173] CPUFREQ of CA15 L17 : 900000 uV >> [ 5.826338] CPUFREQ of CA15 L18 : 900000 uV >> [ 5.830583] fout_apll[900000000] >> [ 5.836287] S divider change for DFS of MIF block >> [ 5.984276] init_volt[975000], freq[800000] >> [ 5.987809] ALSA device list: >> [ 5.989956] #0: Odroid-max98090 >> [ 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. >> >> == >> >> >> >> > -- Dr.-Ing. Markus Eich Senior Researcher Marine Inspection Robotics Space Robotics Besuchsadresse der Nebengeschäftstelle: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 5 28359 Bremen, Germany Postadresse der Hauptgeschäftsstelle Standort Bremen: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 1 28359 Bremen, Germany Tel.: +49 421 178 45-4105 Zentrale: +49 421 178 45-0 Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen) E-Mail: markus.eich@dfki.de Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 ----------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Building yocto for Odroid XU. No login after boot. 2014-08-07 12:51 ` Dr. Markus Eich @ 2014-08-07 13:05 ` Gary Thomas 2014-08-08 11:41 ` Dr. Markus Eich 0 siblings, 1 reply; 7+ messages in thread From: Gary Thomas @ 2014-08-07 13:05 UTC (permalink / raw) To: yocto On 2014-08-07 06:51, Dr. Markus Eich wrote: > Hi Gary, > > unfortunately, this didn't help much. I have compiled the kernel with the CONFIG_FHANDLE=y. > I have also set all configs given in > > http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system > > To pinpoint the error down, I have tried the kernel build from Yocto on a LINARO distro image. I have just replaced the kernel and the modules build with yocto. > > And voila: I have a login promt. If the complete distro is build with Yocto (the whole rootfs), I cannot log in. > > Has setting the SERIAL_CONSOLE = "115200 ttymxc0" the same effect as giving the console param for the u-boot? > > i.e. I have something like > > #setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait rw" ? Setting SERIAL_CONSOLE tells the build system (Yocto) what device to use as the main console. A login prompt will appear on this device after bootup. The 'console=XXX' settings to the kernel (from U-Boot) tell the kernel where to send messages, especially the bootstrap messages. These are subtly different uses but they should match. In your case, I think you should have SERIAL_CONSOLE = "115200 ttySAC2" > On 06.08.2014 18:26, 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. >> >>> == >>> >>> [ 5.722795] CPUFREQ of CA7 L5 : 962500 uV >>> [ 5.726871] CPUFREQ of CA7 L6 : 950000 uV >>> [ 5.730947] CPUFREQ of CA7 L7 : 950000 uV >>> [ 5.735025] CPUFREQ of CA7 L8 : 950000 uV >>> [ 5.739095] CPUFREQ of CA7 L9 : 950000 uV >>> [ 5.743146] CPUFREQ of CA7 L10 : 950000 uV >>> [ 5.747336] CPUFREQ of CA7 L11 : 950000 uV >>> [ 5.751583] CPUFREQ of CA15 L0 : 1362500 uV >>> [ 5.755663] CPUFREQ of CA15 L1 : 1362500 uV >>> [ 5.759826] CPUFREQ of CA15 L2 : 1225000 uV >>> [ 5.764012] CPUFREQ of CA15 L3 : 1175000 uV >>> [ 5.768129] CPUFREQ of CA15 L4 : 1137500 uV >>> [ 5.772313] CPUFREQ of CA15 L5 : 1112500 uV >>> [ 5.776474] CPUFREQ of CA15 L6 : 1075000 uV >>> [ 5.780638] CPUFREQ of CA15 L7 : 1037500 uV >>> [ 5.784800] CPUFREQ of CA15 L8 : 1000000 uV >>> [ 5.788962] CPUFREQ of CA15 L9 : 975000 uV >>> [ 5.793010] CPUFREQ of CA15 L10 : 937500 uV >>> [ 5.797201] CPUFREQ of CA15 L11 : 912500 uV >>> [ 5.801368] CPUFREQ of CA15 L12 : 900000 uV >>> [ 5.805526] CPUFREQ of CA15 L13 : 900000 uV >>> [ 5.809689] CPUFREQ of CA15 L14 : 900000 uV >>> [ 5.813822] CPUFREQ of CA15 L15 : 900000 uV >>> [ 5.818018] CPUFREQ of CA15 L16 : 900000 uV >>> [ 5.822173] CPUFREQ of CA15 L17 : 900000 uV >>> [ 5.826338] CPUFREQ of CA15 L18 : 900000 uV >>> [ 5.830583] fout_apll[900000000] >>> [ 5.836287] S divider change for DFS of MIF block >>> [ 5.984276] init_volt[975000], freq[800000] >>> [ 5.987809] ALSA device list: >>> [ 5.989956] #0: Odroid-max98090 >>> [ 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. >>> >>> == >>> >>> >>> >>> >> > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Building yocto for Odroid XU. No login after boot. 2014-08-07 13:05 ` Gary Thomas @ 2014-08-08 11:41 ` Dr. Markus Eich 2014-09-16 6:24 ` Ravikant 0 siblings, 1 reply; 7+ messages in thread From: Dr. Markus Eich @ 2014-08-08 11:41 UTC (permalink / raw) To: yocto Problem solved. It was an error in the boot.ini (u-boot). Changing the SERIAL_CONSOLE or kernel config params (like CONFIG_FHANDLE=y) did not change much. Problem was hidden in the boot params. In the boot.ini I used "setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x42000000 uInitrd; bootz 0x40008000 0x42000000"" which caused the problem (although uInitrd was present). I changed this line to "fatload mmc 0:1 0x40008000 zImage; bootz 0x40008000" and now I can log in (using systinitv or systemd, doesn't matter). Dunno why, but maybe the solution helps somebody. Cheers, Markus On 07.08.2014 15:05, Gary Thomas wrote: > On 2014-08-07 06:51, Dr. Markus Eich wrote: >> Hi Gary, >> >> unfortunately, this didn't help much. I have compiled the kernel with >> the CONFIG_FHANDLE=y. >> I have also set all configs given in >> >> http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system >> >> >> To pinpoint the error down, I have tried the kernel build from Yocto >> on a LINARO distro image. I have just replaced the kernel and the >> modules build with yocto. >> >> And voila: I have a login promt. If the complete distro is build with >> Yocto (the whole rootfs), I cannot log in. >> >> Has setting the SERIAL_CONSOLE = "115200 ttymxc0" the same effect as >> giving the console param for the u-boot? >> >> i.e. I have something like >> >> #setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 >> root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait rw" ? > > Setting SERIAL_CONSOLE tells the build system (Yocto) what device to > use as the main console. A login prompt will appear on this device > after bootup. The 'console=XXX' settings to the kernel (from U-Boot) > tell the kernel where to send messages, especially the bootstrap > messages. > These are subtly different uses but they should match. > > In your case, I think you should have > SERIAL_CONSOLE = "115200 ttySAC2" > >> On 06.08.2014 18:26, 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. >>> >>>> == >>>> >>>> [ 5.722795] CPUFREQ of CA7 L5 : 962500 uV >>>> [ 5.726871] CPUFREQ of CA7 L6 : 950000 uV >>>> [ 5.730947] CPUFREQ of CA7 L7 : 950000 uV >>>> [ 5.735025] CPUFREQ of CA7 L8 : 950000 uV >>>> [ 5.739095] CPUFREQ of CA7 L9 : 950000 uV >>>> [ 5.743146] CPUFREQ of CA7 L10 : 950000 uV >>>> [ 5.747336] CPUFREQ of CA7 L11 : 950000 uV >>>> [ 5.751583] CPUFREQ of CA15 L0 : 1362500 uV >>>> [ 5.755663] CPUFREQ of CA15 L1 : 1362500 uV >>>> [ 5.759826] CPUFREQ of CA15 L2 : 1225000 uV >>>> [ 5.764012] CPUFREQ of CA15 L3 : 1175000 uV >>>> [ 5.768129] CPUFREQ of CA15 L4 : 1137500 uV >>>> [ 5.772313] CPUFREQ of CA15 L5 : 1112500 uV >>>> [ 5.776474] CPUFREQ of CA15 L6 : 1075000 uV >>>> [ 5.780638] CPUFREQ of CA15 L7 : 1037500 uV >>>> [ 5.784800] CPUFREQ of CA15 L8 : 1000000 uV >>>> [ 5.788962] CPUFREQ of CA15 L9 : 975000 uV >>>> [ 5.793010] CPUFREQ of CA15 L10 : 937500 uV >>>> [ 5.797201] CPUFREQ of CA15 L11 : 912500 uV >>>> [ 5.801368] CPUFREQ of CA15 L12 : 900000 uV >>>> [ 5.805526] CPUFREQ of CA15 L13 : 900000 uV >>>> [ 5.809689] CPUFREQ of CA15 L14 : 900000 uV >>>> [ 5.813822] CPUFREQ of CA15 L15 : 900000 uV >>>> [ 5.818018] CPUFREQ of CA15 L16 : 900000 uV >>>> [ 5.822173] CPUFREQ of CA15 L17 : 900000 uV >>>> [ 5.826338] CPUFREQ of CA15 L18 : 900000 uV >>>> [ 5.830583] fout_apll[900000000] >>>> [ 5.836287] S divider change for DFS of MIF block >>>> [ 5.984276] init_volt[975000], freq[800000] >>>> [ 5.987809] ALSA device list: >>>> [ 5.989956] #0: Odroid-max98090 >>>> [ 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. >>>> >>>> == >>>> >>>> >>>> >>>> >>> >> > -- Dr.-Ing. Markus Eich Senior Researcher Marine Inspection Robotics Space Robotics Besuchsadresse der Nebengeschäftstelle: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 5 28359 Bremen, Germany Postadresse der Hauptgeschäftsstelle Standort Bremen: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 1 28359 Bremen, Germany Tel.: +49 421 178 45-4105 Zentrale: +49 421 178 45-0 Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen) E-Mail: markus.eich@dfki.de Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 ----------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Building yocto for Odroid XU. No login after boot. 2014-08-08 11:41 ` Dr. Markus Eich @ 2014-09-16 6:24 ` Ravikant 0 siblings, 0 replies; 7+ messages in thread From: Ravikant @ 2014-09-16 6:24 UTC (permalink / raw) To: yocto Hello Markus, I was going through the .bb files for odroid-3.8.y at the link given by you. It uses tools/hardkernel/genBscr.sh but somehow i am not able to find this file with the kernel code. Can you please guide me on where to get this file and what it does? Just for trying i commented it out and in this case i get an error form do_deploy while executing copy for .scr files it does not find any .scr files. I am not sure if this problem is because of missing genBscr.sh. Thanks a lot Ravikant ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-09-16 6:30 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-08-06 16:13 Building yocto for Odroid XU. No login after boot Dr. Markus Eich 2014-08-06 16:26 ` Gary Thomas 2014-08-07 6:24 ` Khem Raj 2014-08-07 12:51 ` Dr. Markus Eich 2014-08-07 13:05 ` Gary Thomas 2014-08-08 11:41 ` Dr. Markus Eich 2014-09-16 6:24 ` Ravikant
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.