startx from CD boot fails on nvidia card
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-nv (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I have just tried booting my laptop with the live CD from the Ubuntu 9.04 beta release.
The boot fails to start the desktop, putting the computer into a command line prompt. A quick check shows that xwindows failed to start.
When I run
sudo startx
It reports that
no screens found
I get the same behavior with the safe graphics mode option.
I also get the same behavior with 8.1, which also had the MP-BIOS bug:8254 Timer not connected problem. This confuses the problem with 8.10, but with 9.04 the bios problem has gone, but the xwindows problem remains. So it is fair to assume they are not related.
In the case of 8.04 the entire system works perfectly (with the exception of the webcam)
The laptop is a Clevo D901c with
# Intel Core 2 QUAD
# SLI ENABLED DUAL nVidia 9800M GTX Video Cards
The configuration is obviously that which is shipped with the CD. An isolated partition obtains the same behavior. But as I know nothing about xwindows, I don't know how to change the config files.
Changed in xserver-xorg-video-nv (Ubuntu): | |
status: | Incomplete → New |
tags: | added: karmic |
tags: | removed: needs-xorglog |
tags: | removed: needs-lspci-vvnn |
Changed in xserver-xorg-video-nv (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in xserver-xorg-video-nv (Ubuntu): | |
status: | Confirmed → Won't Fix |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. I have classified this bug as a bug in xserver- xorg-video- nv.
When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.
Sorry for not being able to answer you in a timely manner, are you still able to reproduce this? Does this happen in a newer Ubuntu release?