[Expired for plymouth (Ubuntu) because there has been no activity for 60
days.]
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Expired
--
System fails to boot with plymouth installed (radeon driver with only 1
display, using KMS)
https://bugs.launchpad.net/bugs/541521
You
If you boot with both 'splash' and 'nomodeset', what happens?
** Summary changed:
- System fails to boot with plymouth installed (radeon driver with only 1
display)
+ System fails to boot with plymouth installed (radeon driver with only 1
display, using KMS)
--
System fails to boot with
Scott, no I can't, unless there's someway to boot with xforcevesa or someway to
boot without plymouth.
Otherwise I'm stuck.
--
System fails to boot with plymouth installed (radeon driver with only 1 display)
https://bugs.launchpad.net/bugs/541521
You received this bug notification because you
With the vesa driver, the screen goes alive when gdm starts.
Doesn't that imply you already have a way to boot with vesa?
If it's a framebuffer issue, booting without 'splash' on the kernel
commandline should be enough to bypass the problem. If you have the
same behavior when booting without
Steve, with the vesa driver, which was default after installation, even though
the screen was dead during the boot process, it got alive when gdm started. So
in a way the bug description is wrong since the dead screen issue also happens
with the vesa driver.
But since I can't get a command
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: plymouth
After selecting the kernel on grub, the screen dies.
With the vesa driver, the screen goes alive when gdm starts.
The recovery mode renders the same results.
.ubuntu lucid
I was able to boot without 'splash' and with 'nomodeset'.
With these settings, the screen goes alive when gdm starts, even with the
radeon driver. So I guess this bug description is obsolete.
Apport points this to #537262.
--
System fails to boot with plymouth installed (radeon driver with
** Description changed:
Binary package hint: plymouth
After selecting the kernel on grub, the screen dies.
With the vesa driver, the screen goes alive when gdm starts.
The recovery mode renders the same results.
- .ubuntu lucid / radeon 4670, the display is connected through
Could you please run apport-collect 541521
** Changed in: plymouth (Ubuntu)
Status: New = Incomplete
** Changed in: plymouth (Ubuntu)
Importance: Undecided = Medium
--
System fails to boot with plymouth installed (radeon driver with only 1 display)
