On Thu, Mar 12, 2020 at 9:44 AM Andre McCurdy <[email protected]> wrote: > > On Thu, Mar 12, 2020 at 9:13 AM Khem Raj <[email protected]> wrote: > > On 3/12/20 8:21 AM, Marko, Peter wrote: > > > Hi, > > > > > > I'm trying to boot my own qemu image on zeus branch with "runqemu > > > nographic /path/to/extracted/rootfs" but I have problem that console is > > > flooded with > > > process '/sbin/getty 115200 hvc0' (pid 383) exited. Scheduling for > > > restart. > > > starting pid 385, tty '': '/sbin/getty 115200 hvc0' > > > I'm using yocto qemuarm kernel and qemuarm machine (but it's the same > > > with qemuarm64). > > > > > > Basically qemuarm machine has > > > SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0" > > > which is transferred to /etc/inittab, however hvc0 device does not exist > > > after booting in nographic mode. > > > > > > What kind of configuration am I missing in my image? > > > I think that might be the graphic console which does not exist in > > > nographic mode? > > > > that is correct > > > > > Is there a way to get rid of this problem without breaking graphic mode > > > console? > > > > I did not find one, it particularly happens with busybox init. > > I don't know what the proper fix is, but changing SERIAL_CONSOLES to > "115200;ttyAMA0" avoids the issue. > > I've changed the machine config directly but you could probably also > use the _qemuarm over-ride to set SERIAL_CONSOLES from local.conf, > etc, e.g.: > > SERIAL_CONSOLES_qemuarm = "115200;ttyAMA0"
that made -ctestimage fail last time when I tried it but havent tried it lately maybe things are better -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
