[Bug 1038055] Re: graphics fail to initialise correctly, in kvm with cirrus graphics (after LUKS install)

[Andy Whitcroft]

The cirrus driver is build out of the CONFIG_DRM_CIRRUS_QEMU
configuration option which is new in Quantal.  It may well be worth
bashing it off for the moment.  That said another bug on this issue
claims to have fixes for the X server for this: LP#1039648.  Perhaps
someone could test the packages implied there and confirm/deny this.

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

Title:
  graphics fail to initialise correctly, in kvm with cirrus graphics
  (after LUKS install)

Status in “cryptsetup” package in Ubuntu:
  Invalid
Status in “grub2” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Confirmed
Status in “plymouth” package in Ubuntu:
  Invalid
Status in “ubiquity” package in Ubuntu:
  Invalid

Bug description:
  reproducible with ubiquity or alternate installer in KVM virtual machine:
  1) select lvm + encrypted instalation

  
  it fails to boot, in a way that I get "no video mode activated" and I cannot type the password in to unlock the drive.

  As a workaround, I had to:
  1) force reboot machine
  2) then grub options come up
  3) select recovery mode
  4) then I can enter the password using text interface
  5) resume normal boot

  Disabling splash, brings up text interface to unlock the drive &
  allows to boot.

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