gpu-manager treats all files in /etc/modprobe.d as config files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-drivers-common (Ubuntu) |
Fix Released
|
High
|
Alberto Milone | ||
Trusty |
Fix Released
|
High
|
Alberto Milone |
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/
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.
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.
Related branches
tags: | added: regression-update |
Changed in ubuntu-drivers-common (Ubuntu): | |
status: | New → Triaged |
Changed in ubuntu-drivers-common (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in ubuntu-drivers-common (Ubuntu): | |
importance: | Undecided → High |
Changed in ubuntu-drivers-common (Ubuntu Trusty): | |
importance: | Undecided → High |
Changed in ubuntu-drivers-common (Ubuntu): | |
assignee: | nobody → Alberto Milone (albertomilone) |
Changed in ubuntu-drivers-common (Ubuntu Trusty): | |
milestone: | none → trusty-updates |
Changed in ubuntu-drivers-common (Ubuntu): | |
status: | Triaged → In Progress |
Changed in ubuntu-drivers-common (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in ubuntu-drivers-common (Ubuntu Trusty): | |
status: | Triaged → In Progress |
tags: |
added: verification-done removed: verification-needed |
With the last update I ended up having no nvidia modules loaded. It was exactly because of this bug.
Even something like:
#blacklist nvidia
in a config file "blacklist.conf~" (emacs backup file)
makes nvidia module not loaded...