Kernel update broke xorg configuration

Bug #519080 reported by babygenius55
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I'm using Ubuntu 9.10 kernel 2.6.31-19 (for about 1 hour now)
I apologize for the formatting, you guys seem to hate this.

1. After update I expected to use my system as normal
2. After updating from 2.6.31-17 to 2.6.31-19 I received notifications that the xserver would not start. "Failed to initialize the nvidia kernel module. Screens found but none have usable configuration".
3. I'm not sure how to make this happen again, as I don't know how to downgrade the kernel, and have since fixed the issue.
  for your information I was using nvidia driver NVIDIA-Linux-x86-190.4#-pkg# (Not exactly sure, but it wasn't too long ago, and worked until todays update to .31-19) After installing NVIDIA-Linux-x86-190.53-pkg1 and restarting X everything seems to be kosher.

This very well may be my fault, as I had some display issues concerning OpenGL and Gnome theme persistance throughout the desktop environment and made some changes, but not any to the xorg config file. I just wanted you guys to know that it happened.

Revision history for this message
Monkey (monkey-libre) wrote :

I´ve assigned this bug to the xorg package. Thank You for making Ubuntu better.

affects: ubuntu → xorg (Ubuntu)
Revision history for this message
babygenius55 (babygenius55a) wrote :

I just installed VMware workstation and it happened again. I was running Ubuntu's driver 195 this time. Since I only had 190 downloaded I shut down X, then reinstalled 190. working fine now, but had there been anyone else with this problem? Something freaky is happening here. I didn't make too many changes to this install, and none since the kernel update. Is there somewhere I can go to peek at references to nvidia Xorg driver? maybe there is a reputable forum I can visit?

Revision history for this message
babygenius55 (babygenius55a) wrote :

--Note. Nvidia doesn't have a 195 version of their driver up that is accessible via their downloads page.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi babygenius55a,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for reporting this bug to help make Ubuntu better. I gather you had installed the driver from nvidia.com? If so, we don't support that configuration since that installation code is outside our control and who knows what havok it can cause.

The good news is that for Lucid we've vastly improved the installation procedure for -nvidia and I strongly suspect what you experienced can no longer happen (at least not so easily).

Changed in xorg (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
babygenius55 (babygenius55a) wrote :

Thanks for the heads up. Since the status is won't fix I gather you wont be needing to see the output of lspci, dmesg, etc. I'll include it anyway, maybe it'll help someday.blspci

Revision history for this message
babygenius55 (babygenius55a) wrote :

It's still happening. with the update a few days ago. :( It's a shame when "I" know how to reinstall drivers by heart. I've been using Linux for about a year now, this is by far the most disconcerting problem that is still there for me. I'm going to do a fresh install when Lynx comes out. Maybe I'll be able to stop bugging you.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.