** No longer affects: linux
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in Plymouth:
New
** Changed in: systemd
Status: Unknown => New
** Changed in: linux
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #32509
https://github.com/systemd/systemd/issues/32509
** Also affects: systemd via
https://github.com/systemd/systemd/issues/32509
Importance: Unknown
** Changed in: sddm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in Linux:
New
Status
Plymouth not displaying anything is covered by bug 1869655 already so
please try kernel parameter:
plymouth.use-simpledrm
which should solve that.
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
here is i915 failed to boot in the same way. you can see the i915 kernel
driver does not finish until much after sddm starts
** Attachment added: "i915-fail-boot.txt"
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770118/+files/i915-fail-boot.txt
--
You received this bug
here is i915 with a successfull boot. the i915 driver finishes starting
before sddm starts.
** Attachment added: "i915-successfull-boot.txt"
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770119/+files/i915-successfull-boot.txt
--
You received this bug notification because you
I am hitting this on i915 as well with the same 50-75% frequency.
I think this need to be upgraded to critical status (at least for non
GDM login managers where no mitigation exists) and potentially release
blocker depending on how widespread this issue is.
Devices I have confirmed affected by
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
** Changed in: sddm
Status: Unknown => New
** Changed in: plymouth
Status: Unknown => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to
** Bug watch added: github.com/sddm/sddm/issues #1917
https://github.com/sddm/sddm/issues/1917
** Also affects: sddm via
https://github.com/sddm/sddm/issues/1917
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
AMD kernel developer wants to classify this is as both SDDM bug and
plymouth bug https://gitlab.freedesktop.org/drm/amd/-/issues/3341.
amdgpu kernel driver is not ready by the time that sddm and plymouth are
started in some cases (race condition). Marking this as a sddm and
plymouth bug (in
** Changed in: linux
Status: Unknown => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in Linux:
New
Status in linux
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3341
https://gitlab.freedesktop.org/drm/amd/-/issues/3341
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/3341
Importance: Unknown
Status: Unknown
--
You received this bug notification
this issue has appeared before on other AMD hardware but was closed due
to lack of activity and driver changes. my issue shows that it has re-
appeared on new hardware and drivers
https://gitlab.freedesktop.org/drm/amd/-/issues/1256
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues
Going to change this back to linux as the plymouth failing to display
indicates an issues with KMS (plymouth uses KMS to display graphics on
earlyboot which is what is happening here). The bootlogo from plymouth
always shows (even for a very brief time) when SDDM starts and when it
boots to a
Plymouth seems to be running, but also terminating within a couple of
seconds. Since it's designed to not display anything if it thinks it
won't run for very long then I think failing to see a Plymouth boot logo
is OK in this case. You might like to try the workaround for bug 1869655
which is to
Here is my current boot journalctl (where booting to a desktop
succeeded) for comparison incase it helps.
I will also note that on the boot to black screen I never see any
plymouth bootlogos or messages. The screen remains black after grub
(with only backlight level changing). When I get a
Attached is the journalctl as instructed. I tried to power it off by
short pressing the power button a few times (as you can see in the log
at the end) while black screened but wasn't able to do that so hard to
force power off.
There are no logs in /var/crash/
** Attachment added: "preboot.txt"
Next time you have a failed boot followed by a successful boot, please
run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: amdgpu
Also, are there any files in /var/crash ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in linux package in Ubuntu:
Incomplete
** Changed in: linux-meta (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent
22 matches
Mail list logo
