Ubuntu

Binary Nvidia drivers not loaded after upgrade to linux-image-2.6.15-26-686 2.6.15-26.***47*** (USN-346-1)

Reported by Eduardo Alvarenga on 2006-09-14
20
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
High
Ben Collins

Bug Description

Binary package hint: linux-image-2.6-686

After an upgrade to the latest 2.6.15 kernel (usn-346-1) the nvidia-glx 1.0.8762+2.6.15.11-3, nvidia-kernel-common 20051028+1 drivers are not loaded anymore giving and error, and consequently X is not started.

Sep 14 13:23:02 eduardo kernel: [17179596.644000] nvidia: disagrees about version of symbol boot_cpu_data
Sep 14 13:23:02 eduardo kernel: [17179596.644000] nvidia: Unknown symbol boot_cpu_data

The only way to make the card work is to downgrade to the the 2.6.15-26.***46*** linux-image.

description: updated
Chris McNabb (raizyr) wrote :

I'm having the same problem, nvidia drivers in linux-restricted-modules-2.6.15-26-686 and linux-image-2.6.15-26-686 don't have the same version symbols

2006/9/14, raizyr <email address hidden>:
> I'm having the same problem, nvidia drivers in linux-restricted-
> modules-2.6.15-26-686 and linux-image-2.6.15-26-686 don't have the same
> version symbols
>
> --
> Binary Nvidia drivers not loaded after upgrade to linux-image-2.6.15-26-686 2.6.15-26.***47*** (USN-346-1)
> https://launchpad.net/bugs/60433

Yeah, what I've done to solve this is:

dpkg -i /var/cache/apt/linux-image-2.6.15-26-686_2.6.15-26.46_i386.deb

and downgraded the kernel.

--
Eduardo Alvarenga

Rodney Gordon II (meff) wrote :

Same here.. This is a BIG problem.

I had to hand compile a 8762 module :/

P-D 830 3.0GHz Dual-core, nV 6600 256mb, 1536mb RAM.

Ben Collins (ben-collins) wrote :

Here's the quick and dirty: The last security update included on symbol change, boot_cpu_data, that should have caused an ABI bump. After inspection, it seemed that this symbol affected no modules. However, I failed to check the nvidia module.

The bad part is that the ABI check was disabled, since this one symbol only seems to affect i386 and amd64, and didn't seem to affect any modules.

This was a mistake, and I am rectifying this by uploading a new linux-restricted-modules-2.6.15 rebuild against the new kernel. Long term resolution will be in the next security update which will bump the ABI properly.

Regrets to anyone affected by this issue. Expect a new l-r-m package within 24 hours.

Changed in linux-meta:
assignee: nobody → ben-collins
importance: Untriaged → High
status: Unconfirmed → Fix Committed
Matt Zimmerman (mdz) wrote :

This issue is corrected in linux-restricted-modules-2.6.15 version 2.6.15.11-4

Changed in linux-source-2.6.15:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints