@Daniel - on one hand it is also a change in xorg that makes the driver missing 
now - so an FYI for that.
But in an IRC discussion there were two potential paths to resolve this issue 
- make the cirrus.ko available in the non -extra package so that it works out 
of the box using this driver
- tjaaltonen identified the message around fbbpp (24) which could be a fix in X 
source to get base VESA working even without cirrus.ko being in place

We don't mind which path is chosen to fix it, the kernel change seems
the more straight forward one to me, but OTOH if a fix for the 24bit
Vesa is found that would eliminate the new dependency on the kernel
module which would be even nicer.

** Tags added: apport-collected disco uec-images

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  pull cirrus.ko into main kernel package

Status in linux package in Ubuntu:
Status in xorg-server package in Ubuntu:

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra-<version>-generic package, which is not installed by default in

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [    25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to