gpu-manager will sometimes erronously detect nvidia prime (and possibly fglrx) as unloaded even if not present

[atleta]

Hi,

I found that gpu-manager will detect an nvidia prime (and thus generate a bogus xorg.conf) sometimes. This happened to me when I moved my linux installation over from a machine with an nvidia card into one with an intel one (and no nvidia). I also saw a report from a guy who had a dual card setup and who has disabled the nvidia during boot.

The problem is that the has_unloaded_module greps the syslog for the "nvidia: module" string to find whether there is an nvidia card installed. However, this method is unreliable as the syslog can contain information from previous boot attempts. (E.g. in case of disabling/removing the nvidia card between two logrotations or logrotation failing, etc.) The comment for has_unloaded_module says that it searches dmesg and this is probably how it should be done. If switching to dmesg works then the fix is to be done at line 708.

See also my bug report here: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1485236

[tseliot]

Hi,

This is a known issue, tracked here for now: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1307069

I am going to fix it for Ubuntu 16.04, and possibly backport the fix.

[tseliot]

The fix (also linked to the bug report you filed) should be in Ubuntu 16.04 (Xenial) now. I plan to backport it to 14.04 too.