apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1818879/+attachment/5244318/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818879

Title:
  pull cirrus.ko into main kernel package

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

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

  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
  value

  (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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+subscriptions

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