Hello Zoran Yes, i have set INIT_MANAGER ?= "systemd"
it does not related to console but init Failure logs : - sh-5.1# ls -l /sbin/init ls: cannot access '/sbin/init': No such file or directory sh-5.1# ls -l /lib/systemd/ total 8 drwxr-xr-x 2 root root 4096 Mar 9 2018 system drwxr-xr-x 2 root root 4096 Mar 9 2018 system-preset Working Logs (after adding IMAGE_INSTALL = " systemd") :- root@qemuriscv64:/# ls -l /sbin/init lrwxrwxrwx 1 root root 22 Mar 9 2018 /sbin/init -> ../lib/systemd/systemd root@qemuriscv64:/# ls /lib/systemd/ journald.conf.d system-shutdown systemd-growfs systemd-network-generator systemd-shutdown systemd-update-done libsystemd-shared-250.so system-sleep systemd-hibernate-resume systemd-networkd systemd-sleep systemd-update-helper logind.conf.d system.conf.d systemd-hostnamed systemd-networkd-wait-online systemd-socket-proxyd systemd-update-utmp network systemd systemd-initctl systemd-pstore systemd-sulogin-shell systemd-user-runtime-dir ntp-units.d systemd-ac-power systemd-journald systemd-quotacheck systemd-sysctl systemd-user-sessions resolv.conf systemd-backlight systemd-localed systemd-random-seed systemd-time-wait-sync systemd-userdbd system systemd-boot-check-no-failures systemd-logind systemd-remount-fs systemd-timedated systemd-userwork system-generators systemd-cgroups-agent systemd-makefs systemd-reply-password systemd-timesyncd systemd-vconsole-setup system-preset systemd-fsck systemd-modules-load systemd-resolved systemd-udevd systemd-volatile-root root@qemuriscv64:/# Thank you Regards Vaibhav Vivek Deshpande On Fri, Oct 21, 2022 at 5:18 AM Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > I have added systemd in rootfs by adding > > MAGE_INSTALL = " systemd" in local.conf > > and the issue solved is this required for the > > latest yocto version (kirkstone)? > > You did set the INIT_MANAGER ?= "systemd", didn't you? > > And how (in which manner) systemd influences the console, or consoles > setup? > > Consoles' setup should be done much earlier then systemd!? > > Zee > _______ > > On Thu, Oct 20, 2022 at 7:07 PM Vaibhav Deshpande > <vdeshpa...@ventanamicro.com> wrote: > > > > Helo > > > > I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in > local.conf and the issue solved > > is this required for the latest yocto version (kirkstone)? > > > > > > Thank you. > > > > Regards > > Vaibhav Vivek Deshpande > > > > > > On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic < > zoran.stojsavlje...@gmail.com> wrote: > >> > >> Interesting... Looking into the log massage itself! > >> > >> > [ 0.000000] Kernel command line: root=/dev/vda2 rootwait > console=ttyS0 earlycon=uart8250,mmio,0x10000000 > >> > >> Command line does not specify baud rate... Usually by default it is > >> 115200. Just a kludge. > >> > >> Then: > >> > >> > [ 0.000000] earlycon: uart8250 at MMIO 0x0000000010000000 (options > '') > >> > [ 0.000000] printk: bootconsole [uart8250] enabled > >> > >> bootconsole enabled, seems correct. > >> > >> Then: > >> > >> > [ 1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing > disabled > >> > [ 1.648238] printk: console [ttyS0] disabled > >> > [ 1.652252] 10000000.uart: ttyS0 at MMIO 0x10000000 (irq = 166, > base_baud = 230400) is a 16550A > >> > [ 1.656816] printk: console [ttyS0] enabled > >> > [ 1.656816] printk: console [ttyS0] enabled > >> > [ 1.657728] printk: bootconsole [uart8250] disabled > >> > [ 1.657728] printk: bootconsole [uart8250] disabled > >> > >> From what we see that the base baud rate is 230400 (?), everything > >> else is, seems, correct. > >> > >> So, three things, which came adhoc to my mind: > >> [1] Please, check the baud rate; > >> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)? > >> [3] The terminal should be interactive, but no way to check this (from > >> the logs)??? > >> > >> My two cent worth answer, > >> Zee > >> _______ > >> > >> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande > >> <vdeshpa...@ventanamicro.com> wrote: > >> > > >> > Hello > >> > > >> > I am trying to build a yocto image from the kirkstone branch ( > https://github.com/openembedded/openembedded-core/tree/kirkstone) build > gets successful but at the time of linux booting I am getting below error. > >> > >> ...[snap]... >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58388): https://lists.yoctoproject.org/g/yocto/message/58388 Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
