I suspect the alpha code has not handled the situation correctly. I have
reproduced the upgrade scenario with 9.04 Beta March 26 and everything
works rock solid.
Scenario:
Upgrading from Intrepid to jaunty when using a restricted driver (177) with a
card having a missing device id in nv.ids.
What happened is exactly what you wished for: jaunty is running with the
restricted driver at level 180 (not 177) which is the recommended level
for jaunty. I removed the restricted driver and it works as expected: no
device id, so the nv driver does not load and reverts back to vesa
driver. I always have a working desktop.
Scenario:
Running jaunty without restricted driver, add Driver = "nvidia" in the Device
section of xorg.conf.
This simulates situations where either user edited the conf file or some script
messed it up or a user reinstated a bad backup file. The files for the
restricted driver and kernel module are physically not installed, but X org
will try to load it anyway.
You will be prompted by a dialog asking you what to do, as it can't load the
desktop. Looking it the log file, you will see:
(II) LoadModule: "nvidia"
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: "nvidia"
(EE) Failed to load module "nvidia" (module does not exist, 0)
(EE) No drivers available.
You can chose to run the desktop in low graphic mode.
Now, from a bug report triage point of view, I'll confirm the bug. I am not
sure how development handle alpha code bugs, perhaps FixReleased if they feel
comfortable it has been fixed.
BugSquad
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Incomplete => Confirmed
--
-nv reports it does not support GeForce 9100M G
https://bugs.launchpad.net/bugs/333040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
