<div dir="ltr"><div dir="ltr">On Fri, 30 Aug 2019 at 03:55, Mittal, Anuj <<a href="mailto:anuj.mittal@intel.com">anuj.mittal@intel.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> -QB_OPT_APPEND = "-show-cursor -device VGA,edid=on"<br>
> +QB_OPT_APPEND = "-show-cursor"<br>
<br>
Was this intentional? This is reverting an earlier fix:<br>
<br>
<a href="https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/conf/machine/qemuarm64.conf?h=master-next&id=b181bf92e2bc51a808478c12fe62177d966f2a85" rel="noreferrer" target="_blank">https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/conf/machine/qemuarm64.conf?h=master-next&id=b181bf92e2bc51a808478c12fe62177d966f2a85</a><br>
<br>
<a href="https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/conf/machine/qemuarm64.conf?h=master-next&id=ff35b6c57a380ca4dc158c5104a6137f8faea5cd" rel="noreferrer" target="_blank">https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/conf/machine/qemuarm64.conf?h=master-next&id=ff35b6c57a380ca4dc158c5104a6137f8faea5cd</a><br>
<br>
I'm not sure if this is the reason but master-next build is also<br>
showing problems when running X with qemuarm:<br>
<br>
<a href="https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/978/steps/8/logs/step1c" rel="noreferrer" target="_blank">https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/978/steps/8/logs/step1c</a><br></blockquote><div><br></div><div>Thanks, I wasn't aware that qemu's list of supported graphical hardware (and what the default selection is) differs between architectures and machines.</div><div>The documentation erroneously claims that '-vga std' is the default everywhere where in reality it is the default only on x86.</div><div><br></div><div>Patch will be reworked to not touch arm bits.<br></div></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
...<br>
<br>
> diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py<br>
> b/meta/lib/oeqa/runtime/cases/parselogs.py<br>
> index 19c9c52a0a9..0002730d46f 100644<br>
> --- a/meta/lib/oeqa/runtime/cases/parselogs.py<br>
> +++ b/meta/lib/oeqa/runtime/cases/parselogs.py<br>
> @@ -55,7 +55,11 @@ common_errors = [<br>
> "Failed to read /var/lib/nfs/statd/state: Success",<br>
> "error retry time-out =",<br>
> "logind: cannot setup systemd-logind helper (-61), using legacy<br>
> fallback",<br>
> - "Error changing net interface name 'eth0' to "<br>
> + "Error changing net interface name 'eth0' to ",<br>
> + "modeset(0): Failed to initialize the DRI2 extension",<br>
> + "uvesafb: cannot reserve video memory at",<br>
> + "uvesafb: probe of uvesafb.0 failed with error",<br>
> + "glamor initialization failed"<br>
> ]<br>
> <br>
<br>
parselogs test is used not only for qemu but for other MACHINES as well<br>
including genericx86 on actual hardware where glamor initialization<br>
error might need looking into. Perhaps this should be added to qemu<br>
specific parts of this test only?<br></blockquote><div><br></div><div> That's right as well. Let's add the messages to qemux86 parts, and see if other qemu targets need this as well.</div><div><br></div><div>Alex<br></div></div></div>