nvidia drivers fail to start in Maverick X11

Bug #623399 reported by Jeff Craig on 2010-08-24
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Undecided
Unassigned

Bug Description

When attempting to boot, I get loaded to a text login. The relevant error message is in the old Xorg log attached to this bug. The nvidia drivers seem to claim an ABI incompatibility.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nvidia-current 256.44-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 256.44 Thu Jul 29 01:22:44 PDT 2010
 GCC version: gcc version 4.4.5 20100816 (prerelease) (Ubuntu/Linaro 4.4.4-9ubuntu1)
Architecture: amd64
Date: Tue Aug 24 06:55:15 2010
DkmsStatus:
 nvidia-current, 256.44, 2.6.32-22-generic, x86_64: installed
 nvidia-current, 256.44, 2.6.35-17-generic, x86_64: installed
 virtualbox-ose, 3.2.8, 2.6.32-22-generic, x86_64: installed
 virtualbox-ose, 3.2.8, 2.6.35-17-generic, x86_64: installed
GdmLog: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 3: Error copying '/home/craig/.Xauthority' to '/tmp/libgksu-scIcu3': No such file or directory
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 3: Error copying '/home/craig/.Xauthority' to '/tmp/libgksu-YtjOEr': No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 3: Error copying '/home/craig/.Xauthority' to '/tmp/libgksu-tY7aMi': No such file or directory
Lsusb:
 Bus 002 Device 004: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
 Bus 002 Device 003: ID 045e:002b Microsoft Corp. Internet Keyboard Pro
 Bus 002 Device 002: ID 0451:1446 Texas Instruments, Inc. TUSB2040/2070 Hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: BIOSTAR Group TF560 A2+
ProcCmdLine: root=UUID=caa43afc-8122-4a32-8b18-35b5c0f84a34 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers
dmi.bios.date: 06/11/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: TF560 A2+
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: TF560 A2+
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/11/2007:svnBIOSTARGroup:pnTF560A2+:pvr1.0:rvnBIOSTARGroup:rnTF560A2+:rvr1.0:cvnBIOSTARGroup:ct3:cvrTF560A2+:
dmi.product.name: TF560 A2+
dmi.product.version: 1.0
dmi.sys.vendor: BIOSTAR Group
nvidia-settings:

system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-17-generic

Jeff Craig (foxxtrot) wrote :
Harry (harry33) wrote :

Hi Jeff Craig,

NVidia proprietary drivers (nvidia-current) do not accept the new ABI, which is required by the xserver 1.9 branch.
In order to avoid this you need to add the following lines to your xorg.conf.

Section "ServerFlags"
    Option "ignoreABI" "True"
EndSection

Nvidia-current_265.44 do work OK with xserver 1.9 after that.
You may, however, find that scrolling is not so fluent as it was with the xserver 1.8 branch.
We just have to wait for the new nvidia drivers to overcome that.

Jeff Craig (foxxtrot) wrote :

Are new nvidia drivers expected before October? Or should a workaround that automatically adds the ignoreABI option to the Xorg.conf be investigated?

I can apply this workaround easily, but there are a LOT of people with nvidia chipsets, and we can't have Maverick ship with the nvidia drivers failing in this fashion.

Harry (harry33) wrote :

Jeff,

Only Nvidia folks know that, like Aaron Plattner. Perhaps he could comment this.

However, by applying the IgnoreAbi option we can make maverick boot again.
But there are a lot of other issues with the recent nvidia-current_265.44 drivers, that need to be fixed.
So this is only a partial or superficial workaround for xserver 1.9 branch.

One example:
Open Synaptic and try to scroll (with mouse) the package list.
There is a huge difference compared to these drivers with xserver 1.8 branch.

It is true that Nvidia is a bit lagging now that xserver 1.9 has been publiced.

Aaron Plattner (aplattner) wrote :

A driver with support for the new ABI should be out relatively soon, though I can't make any actual promises as to a release date.

If scrolling using the same driver but a different X server shows different performance, it's highly likely that the regression is in the X server and not the driver.

Harry (harry33) wrote :

Aaron,

Thank You for the news.

About the driver compatibility.
I did mean the same issue we see when we compare the driver performance on xserver 1.8 branch:
with nvidia proprietary drivers any scrolling action is very fluent, but with open source ati drivers it certainly is not.
Now I see exactly the same sluggishness with nvidia drivers on xserver 1.9.0 and of course with open source ati drivers too.

Jeff Craig (foxxtrot) wrote :

Just as an additional note, this issue does seem to contribute to occasional crashes in mutter:

[12164.703625] mutter[1974]: segfault at 8 ip 00007f7fbf1d9e53 sp 00007fffb28b6600 error 4 in libnvidia-glcore.so.256.44[7f7fbe48a000+128e000]

Harry (harry33) wrote :

So NVidia has now publiced a new driver pre-release 256.52.
That one does support new video ABI xserver xorg 8, which is required by the xserver 1.9.
Now this will fix this bug. It is no more needed to put ignoreAbi text into the xorg.conf to bypass this issue.

So, please do build a nvidia-current_256.52 deb package into maverick repo (restricted).

John Vivirito (gnomefreak) wrote :

You can find the drivers in teh x-swap PPA as a work around

Harry (harry33) wrote :

The pre-release 256.52 can be found from PPA's xorg-edgers and x-updates (x-swatt).
But Nvidia has already published stable drivers too (256.53).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers