failed to start x-server after gg_t-5 install "failed to load nvidia"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Invalid
|
Undecided
|
Brian Murray | ||
Bug Description
Installing gutsy 64 t-5 on hp dv2313cl amdx2 64 laptop.
Install works unless...you do these steps.
boot liveCD. after desktop is stable a notification icon appears taking me to the restricted drivers manager
I clicked on enable nvidia-glx-new just to see if it is working now.
package manager downloads and installs same. shows as enabled now in restricted manager dialog.
wants me to restart (which I know will blitz the download) so I just choose to do the "install ubuntu".
After install then reboot...fails at "failed to start x-server"
new user is trapped at this point. We let them play around with the liveCD but don't protect them from being bad.
xorg.conf (EE) failed to load module "nvidia" (module does not exist, 0) fatal server error "no screen found"
100% reproducible.
Installing or changing anything while using the liveCD should not affect a fresh install to hard disk. The user
should be able to change any settings / install-remove any packages while testing the liveCD without affecting the
installation process.
If system changes do affect the installers actions...then the installer should check to see if there have been any changes
and if so...immediately upon clicking to install, the installer should bring the system back to a "clean, fresh boot" state so
that the install is bit-for-bit identical to an install from a fresh liveCD boot.
OR...remove the installer from the desktop and only allow installs from the LiveCD boot screen:
1. Start Ubuntu.
2. Start Ubuntu in safe graphics mode.
3. Install Ubuntu.
4. Install Ubuntu with driver update CD.
5. Install Ubuntu (OEM for manufactures).
...
This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined. /wiki.ubuntu. com/StableRelea seUpdates . /wiki.ubuntu. com/Bugs/ HowToTriage .
According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https:/
The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https:/