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

[Stefan Bader]

It really is the problem of remove_conflicting_framebuffers() returning
before the removed fb's driver has released its resources. As it is
visible below efifb seems to take quite a while (sometimes?).

[    0.189597] efifb: probing for efifb
[    0.189597] efifb: framebuffer region reserved
[    0.189597] efifb: framebuffer at 0xfc000000, mapped to 0xffffc90000900000, using 1408k, total 1408k
[    0.189597] efifb: mode is 800x600x24, linelength=2400, pages=1
[    0.189597] efifb: scrolling: redraw
[    0.189597] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[   10.823896] fb: conflicting fb hw usage cirrusdrmfb vs EFI VGA - removing generic driver
[   10.856476] cirrus: requestion framebuffer region
[   10.856481] cirrus: failed to get framebuffer region
[   11.361124] cirrus: failed to get framebuffer region
[   11.864322] cirrus: failed to get framebuffer region
[   12.368378] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM
[   12.368391] cirrus 0000:00:02.0: Fatal error during GPU init: -6
[   13.934174] efifb: frambuffer region released

-- 
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