[Bug 1172028] New: Wrong patch4 in Plymouth.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 Bug ID: 1172028 Summary: Wrong patch4 in Plymouth. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: olivier.lahaye1@free.fr QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Please remove patch4 in Plymouth package as it seems counter productive on emu. I'm using emu-5.0.0 on MacOS-X with HVF acceleration, and my Plymouth theme with script module fails to go to graphic mode in my specially crafter initrd. (SystemImager-NG) If I rebuild the Plymouth package without the patch 4 (plymouth-only_use_fb_for_cirrus_bochs.patch), and if I re-generate my initrd, my theme works fine. (everything is displayed as expected) I'm using tianocore UEFI bios on emu-5.0.0 on MacOS with HVF acceleration. kernel: vmlinuz-5.3.18-lp152.14-default plymouth: plymouth-0.9.4+git20190304.ed9f201-lp152.4.4.x86_64 See more infos and log here: https://lists.freedesktop.org/archives/plymouth/2020-May/000890.html -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 http://bugzilla.opensuse.org/show_bug.cgi?id=1172028#c1 --- Comment #1 from Olivier LAHAYE <olivier.lahaye1@free.fr> --- using QEMU-5.0.0 on MacOS-X 10.14.6 (not emu; syntax auto corrector is wrong) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 Olivier LAHAYE <olivier.lahaye1@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Wrong patch4 in Plymouth. |Wrong patch4 in Plymouth: | |need to remove it in order | |to have qemu working. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 http://bugzilla.opensuse.org/show_bug.cgi?id=1172028#c3 --- Comment #3 from Olivier LAHAYE <olivier.lahaye1@free.fr> --- My ignited is generated like this: lsinitrd /usr/share/systemimager/boot/x86_64/standard/initrd.img |more Image: /usr/share/systemimager/boot/x86_64/standard/initrd.img: 65M ======================================================================== Version: dracut-049.1+suse.138.g9068a629-lp152.1.12 Arguments: --force --add 'systemimager' --omit 'dash' --no-hostonly --no-hostonly-cmdline --no-hostonly-i18n --add-drivers 'pcspkr' --local dracut modules: bash systemd systemd-initrd i18n network-legacy network drm plymouth systemimager btrfs crypt dm kernel-modules kernel-modules-extra kernel-network-modules lvm mdraid nvdimm qemu qemu-net lunmask resume rootfs-block suse-btrfs suse-xfs terminfo udev-rules dracut-systemd usrmount base fs-lib shutdown suse suse-initrd ======================================================================== The fact is: with the patch, the display fails while without patch, it works. This means that the patch is wrong in the way it fails to handle this situation that would normally function. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 http://bugzilla.opensuse.org/show_bug.cgi?id=1172028#c4 --- Comment #4 from Fabian Vogt <fvogt@suse.com> --- (In reply to Olivier LAHAYE from comment #3)
My ignited is generated like this:
That doesn't show the list of available modules. What's the emulated video adapter?
The fact is: with the patch, the display fails while without patch, it works. This means that the patch is wrong in the way it fails to handle this situation that would normally function.
It's exactly this situation which the patch was made for, to not block loading of the actual driver outside of the initrd. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 http://bugzilla.opensuse.org/show_bug.cgi?id=1172028#c24 --- Comment #24 from Cliff Zhao <qzhao@suse.com> --- (In reply to Cliff Zhao from comment #23)
(In reply to Michal Suchanek from comment #19)
What driver is the VM using?
Hi Oliver: May I bother you to take a little time on Michal's question? He is an important people in the team, and we very respect on his suggestions. Thank you!
Hi Oliver: Ping? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 http://bugzilla.opensuse.org/show_bug.cgi?id=1172028#c25 --- Comment #25 from Cliff Zhao <qzhao@suse.com> --- (In reply to Cliff Zhao from comment #24)
(In reply to Cliff Zhao from comment #23)
(In reply to Michal Suchanek from comment #19)
What driver is the VM using?
Hi Oliver: May I bother you to take a little time on Michal's question? He is an important people in the team, and we very respect on his suggestions. Thank you!
Hi Oliver: Ping?
Hi Oliver: Are you there? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 http://bugzilla.opensuse.org/show_bug.cgi?id=1172028#c39 Cliff Zhao <qzhao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #39 from Cliff Zhao <qzhao@suse.com> --- Currently, discussion result is this bug could not fix, Plymouth should take plymouth-only_use_fb_for_cirrus_bochs.patch to avoid system hanging, which means there's no boot animation in the Framebuffer device except the cirrus driver. We can't have it both ways. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com