← Back to team overview

desktop-packages team mailing list archive

[Bug 1376966] Re: gpu-manager treats all files in /etc/modprobe.d as config files

 

The package in -proposed works fine here:

:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.2.91.8
  Candidate: 1:0.2.91.8
  Version table:
 *** 1:0.2.91.8 0
        400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.2.91.7 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
     1:0.2.91.4 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

This is the test case:

:~$ echo "blacklist nvidia" | sudo tee /etc/modprobe.d/blacklist.dpkg-old
blacklist nvidia

And here is the relevant part of the log (it clearly says "Is nvidia
blacklisted? no"):

:~$ sudo gpu-manager

last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
/etc/modprobe.d is not a file
grep dmesg status 256
dmesg status 256 == 0? No
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
Is nvidia loaded? yes
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is fglrx kernel module available? no
Is nvidia kernel module available? yes
Vendor/Device Id: 8086:166
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:de9
BusID "PCI:1@0:0:0"
Is boot vga? no
...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1376966

Title:
  gpu-manager treats all files in /etc/modprobe.d as config files

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Trusty:
  Fix Committed

Bug description:
  My media center computer have a single nvidia GPU connected to a TV,
  and have for many years been happily using the nvidia driver.
  Unfortunately the recent upgrade to version 1:0.2.91.7 broke X.
  Starting lightdm would fail, delete my xorg.conf and redirect libgl
  symlinks to mesa.

  After some debugging I fond that this was done by gpu-manager, because
  it incorrectly believes that my nvidia module is blacklisted. gpu-
  manager.log contained "Is nvidia blacklisted? yes".

  More debugging determined that this was happening because I have a several years old file named:
    /etc/modprobe.d/blacklist.dpkg-old
  which among other things contain the line "blacklist nvidia".

  However that is _not_ a modprobe config file. modprobe only uses files
  with a .conf extension. (See the man page modprobe.d(5)).
  Unfortunately gpu-manager does not have this restriction and looks in
  all files in /etc/modprobe.d by running:

    grep -G "blacklist.*nvidia[[:space:]]*$" /etc/modprobe.d/*

  
  I could work-around the bug by removing the .dpkg-old file. However this will likely break other machines as well. I found two bugs 1373968 and 1374871 about X not working after installing the latest update. However they does not contain enough information to determine if they are duplicates of this bug or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1376966/+subscriptions


References