[Bug 825439] Re: Regression:Black screen/no video output is back in Oneiric as of August 10

Steve Langasek steve.langasek at canonical.com
Sun Oct 2 06:56:33 UTC 2011


Since yours is the only reported instance of this, and you say the
problem has gone away for you, I'm marking this issue as resolved.

** Changed in: plymouth (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/825439

Title:
  Regression:Black screen/no video output is back in Oneiric as of
  August 10

Status in “plymouth” package in Ubuntu:
  Fix Released

Bug description:
  I'm not sure exactly when this started as my /boot partition is only
  mounted when I bring in a new kernel or major changes that require a
  new initramfs (encrypted machine,special security needs), but the
  August 10 updates to Ubuntu Oneiric led to a black screen boot(no
  video output) with encryption passphrase input also ignored. Plymouth
  could not even accept the encryption password blindly, I had to either
  wait for Busybox to show up, boot with splash and vt-handoff removed
  from the kernel command line, or boot from an old kernel with a backup
  initramfs. Last time this happened, in July, there was no video
  display but the passphrase could be typed in blindly and was accepted.

   If thel vt-handoff is removed from the kernel commandline but splash
  kept, plymouth crashes, and the console shows an error saying plymouth
  unexpectedly disconnected from (forgot the exact text). At that point,
  Plymouth is again unresponsive and cannot enter the encryption
  password(my script calls plymouth --ask-for-password directly).

  If "splash" is removed from the kernel command line and the vt-handoff
  is kept, the black screen error still occurs, just as in a default
  boot. Only removing both splash and vt-handoff allows a responsive
  console or any text output after KMS initialiization and before a
  failed boot would bring up Busybox in the initramfs.

  I have tested this in both the Intel Atom netbook and the AMD 4
  core/ATI graphics machines I have. Plymouth version is
  0.8.2-2ubuntu25.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/825439/+subscriptions




More information about the foundations-bugs mailing list