[regression] Trusty kernel doesn't recognize GeForce 8600m GT nor with nouveau or nvidia drivers

[Marco Trevisan (Treviño)]

When loading trusty (also from a brand new live-USB) in an Acer Aspire 5920G, that has a Nvidia 8600m GT card, the nouveau driver fails to load and the UI falls back to llvmpipe.
Using noacpi kernel cmdline doesn't help.

The highlights from dmesg are:

[ 20.051842] nouveau 0000:01:00.0: enabling device (0004 -> 0007)
[ 20.052191] [drm] hdmi device not found 1 0 1
[ 20.052340] nouveau E[ DEVICE][0000:01:00.0] unknown chipset, 0xffffffff
[ 20.052346] nouveau E[ DRM] failed to create 0x80000080, -22
[ 20.052540] nouveau: probe of 0000:01:00.0 failed with error -22

Installing the Nvidia drivers 331 or current (304) gives out a similar error when loading the nvidia kernel module:

[ 18.405583] nvidia: module license 'NVIDIA' taints kernel.
[ 18.405588] Disabling lock debugging due to kernel taint
[ 18.418853] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 18.426016] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[ 18.426115] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 18.426161] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0407)
[ 18.426161] NVRM: installed in this system is not supported by the 331.38
[ 18.426161] NVRM: NVIDIA Linux driver release. Please see 'Appendix
[ 18.426161] NVRM: A - Supported NVIDIA GPU Products' in this release's
[ 18.426161] NVRM: README, available on the Linux driver download page
[ 18.426161] NVRM: at www.nvidia.com.
[ 18.426215] nvidia: probe of 0000:01:00.0 failed with error -1
[ 18.426869] NVRM: The NVIDIA probe routine failed for 1 device(s).
[ 18.426872] NVRM: None of the NVIDIA graphics adapters were initialized!
[ 18.426874] [drm] Module unloaded
[ 18.426982] NVRM: NVIDIA init module failed!

/var/log/gpu-manager.log: http://paste.ubuntu.com/7286246/
nvidia-bug-report.sh (contains full dmesg and Xorg.log): http://paste.ubuntu.com/7287180/

Fun fact is that the card is supported by the latest nvidia drivers as reported by their appendix [1].
Also they used to work in 12.04.

So, I've manually installed the saucy kernel, and with it both nouveau and nvidia modules are loaded properly, making X to load the proper driver and GLX to work.
Everything works also using the daily mainline kernel linux-image-3.15.0-999-generic_3.15.0-999.201404190220_amd64.deb.
Thus this seems to indicate pretty clearly that the bug is inside the trusty linux kernel itself.

[1] ftp://download.nvidia.com/XFree86/Linux-x86_64/331.38/README/supportedchips.html

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: luca 1967 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 21 00:20:42 2014
HibernationDevice: RESUME=UUID=375bbd5e-c25c-4d6e-bfa4-66bed5e80cb0
InstallationDate: Installed on 2011-12-28 (844 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Acer, inc. Aspire 5920G
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=d9d0e5ab-b408-439e-ae8b-c2bf704713bf ro quiet splash vt.handoff=7 noacpi
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-19 (1 days ago)
dmi.bios.date: 08/15/2007
dmi.bios.vendor: Acer
dmi.bios.version: v1.3708
dmi.board.name: Chapala
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv1.3708:bd08/15/2007:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 5920G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

[Marco Trevisan (Treviño) (3v1n0)]

FYI I can experience the same issue also with mainline kernels:
 - linux-image-3.13.0-031300-generic
 - linux-image-3.13.10-031310-generic

[Brad Figg (brad-figg)]

This change was made by a bot.

[Marco Trevisan (Treviño) (3v1n0)]

Same happens using the mainline kernel
 - linux-image-3.14.0-031400-generic

So, it seems something that got broken in between 3.11 and 3.15...

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/

[Marco Trevisan (Treviño) (3v1n0)]

Yes, as said linux-headers-3.15.0-031500rc2-generic_3.15.0-031500rc2.201404201435 or daily works.

[Marco Trevisan (Treviño) (3v1n0)]

Also, i've been running trusty in a very similar laptop to the one I used for this report (same CPU/Chipset) but using a slightly different video card, instead: G86M [GeForce 8600M GS].

And that works.

I've noticed they have a different bios version, though:
 - Not working: v1.3804
 - Working: v1.3804

So, I've upgrade this laptop bios to version v1.3818, and magically things work now.

Then, while I think we're still somewhat regressing in handling that old-configured-hw, Acer 5920G users should know that they need to upgrade their bios to have trusty properly running.

[Marco Trevisan (Treviño) (3v1n0)]

Err, not working bios revision was v1.3708

[Jakub Liška (liska-jakub)]

For me ubuntu is not usable right now.

Using nouveau driver I get this :

https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1097178 which freezes the system 10 times a day.

And using nvidia proprietary driver installed via Additional Drivers (tried 331 and 331 update) I'm getting this one, which freezes the system a few seconds after x starts.

So either I have to try different kernels or install cutting edge nvidia drivers manually...

[Jakub Liška (liska-jakub)]

I tried 3.15.0-031500rc2_3.15.0-031500rc2.201404201435 and this issue is gone, but there are these errors that freeze X :

May 2 11:04:23 lisak nvidia-persistenced: Started (2206)
May 2 11:05:21 lisak kernel: [ 71.350777] apt-check[2392]: segfault at 17bf6 ip 0000000000017bf6 sp 00007fff02f32fe8 error 14 in python3.4[400000+354000]
May 2 11:05:21 lisak kernel: [ 71.492139] apport[2393]: segfault at 17bf6 ip 0000000000017bf6 sp 00007fffea07f428 error 14 in python3.4[400000+354000]
May 2 11:05:21 lisak kernel: [ 71.492162] Process 2393(apport) has RLIMIT_CORE set to 1
May 2 11:05:21 lisak kernel: [ 71.492164] Aborting core
May 2 11:05:23 lisak kernel: [ 73.351741] apport-checkrep[2396]: segfault at 17bf6 ip 0000000000017bf6 sp 00007fff28a26378 error 14 in python3.4[400000+354000]
May 2 11:05:23 lisak kernel: [ 73.493450] apport[2397]: segfault at 17bf6 ip 0000000000017bf6 sp 00007fffc1208e38 error 14 in python3.4[400000+354000]
May 2 11:05:23 lisak kernel: [ 73.493473] Process 2397(apport) has RLIMIT_CORE set to 1
May 2 11:05:23 lisak kernel: [ 73.493475] Aborting core
May 2 11:05:23 lisak kernel: [ 73.623298] apport-checkrep[2398]: segfault at 17bf6 ip 0000000000017bf6 sp 00007fffb3c755c8 error 14 in python3.4[400000+354000]
May 2 11:05:24 lisak kernel: [ 73.764436] apport[2399]: segfault at 17bf6 ip 0000000000017bf6 sp 00007fff1a649818 error 14 in python3.4[400000+354000]
May 2 11:05:24 lisak kernel: [ 73.764459] Process 2399(apport) has RLIMIT_CORE set to 1
May 2 11:05:24 lisak kernel: [ 73.764461] Aborting core

That might relate to issue https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1299390

[Gianluca Bertaina (bertaina)]

I also have a 5920g with Nvidia 8600m GT. My video card has not been working since kernel 2.6.32, I had to use the pci=bios directive in grub (see bug 661248). Even so it seldomly hangs at boot time.

@Marco Trevisan : how did you manage to update the bios? The bios installer on the ACER website works only in Windows.

[Marco Trevisan (Treviño) (3v1n0)]

@Gianluca:

You can grab the latest bios version from http://is.gd/XqTq1B, but unfortunately I did this in one of my friend's PC, and he still had a Win partition, then I used that not to spend too time to figure out another solution.

Although this laptop has a WinPhlash bios, then I think you can also use safely a FreeDOS disk (or usb dongle) with the phlash16.exe utility and the bios file (the ZD13813.wph, probalby renamed as BIOS.wph).

Looking around I've seen that there are multiple ways to obtain the phlash16.exe utility, check this one mentioned on the Ubuntu wiki:
 - https://wiki.ubuntu.com/DellBIOS#Obtaining_and_using_an_image_from_the_WinPhlash_utility

[Gianluca Bertaina (bertaina)]

@Marco

Thanks to your suggestions I was able to update the bios to version 1.3813. However, without the pci=bios option I still have an unstable system.

[NW (ubuntu327)]

I encountered similar issues on a geForce FX 5200 (at least with regard to the 'llvmpipe' fallback behavior.) However, according to Nvidia that 8600M GPU should be using the 340 series driver and Ubuntu should not offer to install 304 or 331 on the OP's platform (unless I misread something here.) Is it possible that he installed the wrong driver manually instead of accepting what Ubuntu offers through Software & Updates "Additional Drivers" ?

http://www.nvidia.com/object/IO_32667.html
_____

The default behavior is to install Nouveau (though it may silently fail), but 'Software & Updates' did offer the correct Nvidia proprietary driver for my 5200, and it does initialize as shown here:

[ 23.731531] nvidia: module license 'NVIDIA' taints kernel.
[ 23.731548] Disabling lock debugging due to kernel taint
[ 23.983464] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
[ 24.018659] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 24.449665] ACPI: PCI Interrupt Link [APCE] enabled at IRQ 16
[ 24.449706] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 24.483764] NVRM: loading NVIDIA UNIX x86 Kernel Module 173.14.39

https://devtalk.nvidia.com/default/topic/655258/unix-graphics-announcements-and-news/linux-solaris-and-freebsd-driver-173-14-39-legacy-for-geforce-fx-series-/
_____

But now there is another problem: I get a kernel panic with spontaneous reboot when the Unity desktop begins to load. I suspect others may be encountering the same issue with other proprietary legacy Nvidia drivers. In this case, you cannot revert the driver directly from the GRUB recovery menu: you would have to uninstall Nvidia's driver from terminal or install LXDE from terminal if you want to regain access to a GUI desktop environment. This would really aggravate the ordinary user because there is no obvious way to extract logs from the affected machine and request help in the forums. Furthermore, it appears that a crash report on this issue would not be sent automatically if you are running Unity, so the developers are probably not receiving any feedback from most of the users affected by this bug. You may encounter these display faults on any geForce, Quadro or Tesla GPU using a proprietary legacy Nvidia driver, including the frozen 173.14.39, 71.86, 96.43, 304.xx (supported through 2017) and 340.xx (supported through 2019), for example:
_____

96.43.23: file date 2012-09-04; incompatible with X.Org included in Slackware 14.1. Usable with Slackware 14.0, but needs patching for kernel compatibility. 96.43 is needed by cards in the GeForce2 MX to GeForce4 range.

71.86.15: Incompatible with recent X.Org. The file date of 2011-07-20 is misleading: apparently Nvidia maintained kernel compatibility for quite some time after they let the X server ABI breakage go to hell. I had to go all the way back to Slackware 12.2 (2008-12) before the driver would work, which means that the last compatible X server version is either 1.4 or 1.5. The last kernel for which the 71.86.15 module will build and load without patching is 3.2.x (a longterm branch), and then only w...

[Anton Veretenenko (anton.veretenenko)]

also have this issue with Acer Aspire V5-572G which has GeForce GT 750M, nvidia module loads ok with 3.16 kernel, does not load with 3.15 or lower.

[Anton Veretenenko (anton.veretenenko)]

also want to note that everything works with clean install, something broke while upgrading from previous version.

[NW (ubuntu327)]

I also want to add that I have now seen this issue in LXDE. It only happened a couple of times--once while I was on YouTube and once while I was using the Ubuntu Software Center. But LXDE is still the only desktop that I can successfully launch and use when Nvidia's driver is enabled.

[Jeroen Ruigrok van der Werven (asmodai)]

Running 3.13.0-40-generic triggering this as well:

kernel: [ 11.095358] nvidia: module license 'NVIDIA' taints kernel.
kernel: [ 11.095361] Disabling lock debugging due to kernel taint
kernel: [ 11.100122] nvidia: module verification failed: signature and/or required key missing - tainting kernel

[Bryan Quigley (bryanquigley)]

Has this been fixed in 15.10?

[Alberto Quattrini Li (alberto-quattrinili)]

Also 3.16.0-60-generic triggers that in dmesg:

[ 8.106834] nvidia: module license 'NVIDIA' taints kernel.
[ 8.106843] Disabling lock debugging due to kernel taint
[ 8.115743] nvidia: module verification failed: signature and/or required key missing - tainting kernel

Note that I am using Ubuntu 14.04.4, with nvidia 352.79.

[Alberto Milone (albertomilone)]

@Alberto: the "tainting kernel" message is expected.