[Trusty] Need additional udev rule to avoid efi framebuffer to be primary

Bug #1277006 reported by Stefan Bader on 2014-02-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
High
Stefan Bader

Bug Description

At least with the Trusty 3.13 kernel the driver name seems to have changed. So I had to add the following line to

--- /lib/udev/rules.d/78-graphics-card.rules ---
 DRIVERS=="nouveau", GOTO="graphics_end"
 DRIVERS=="efifb", GOTO="graphics_end"
+DRIVERS=="efi-framebuffer", GOTO="graphics_end"

 KERNEL=="fb[0-9]*", ENV{PRIMARY_DEVICE_FOR_DISPLAY}="1"
---

Without thiat, a virtual machine (again) gets stuck while ejecting the conflicting framebuffer.

Stefan Bader (smb) wrote :
Stefan Bader (smb) wrote :
Martin Pitt (pitti) wrote :

Thanks! Applied to my packaging git tree.

affects: udev (Ubuntu) → systemd (Ubuntu)
Changed in systemd (Ubuntu):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 204-5ubuntu11

---------------
systemd (204-5ubuntu11) trusty; urgency=medium

  [ Ben Howard ]
  * debian/extra/rules/75-persistent-net-generator.rules: Add new block of
    Windows Azure ethernet hardware address to ignore persistent naming
    (LP: #1274348).

  [ Stefan Bader ]
  * Modify debian/extra/rules/78-graphics-card.rules to match for
    "efi-framebuffer" in addition to "efifb" (LP: #1277006)

  [ Martin Pitt ]
  * debian/extra/rules/78-graphics-card.rules: Add vesa-framebuffer as well,
    thanks to Andy Whitcroft for pointing out.
 -- Martin Pitt <email address hidden> Thu, 06 Feb 2014 12:42:39 +0100

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers