Can't make a clean install of Ubuntu 9.10 on this computer

[Keith Hayward]

Binary package hint: yelp

I started with a new blank Hard Disk WD 500GB. All was ok until I get to the end. I rebooted the new system ok, but the graphics were poor because the Nvidia driver needed installing (my motherboard has built-in Nvidia graphics). I installed the Nvidia driver (recommended version) from System>Admin. The screen then went blank. A small window appeared in the blank screen which stated OUT OF RANGE. 81.1 KHz / 65 Hz. I was then in a catch 22 position: I couldn't get into the system to change the settings to be suitable for the limitations of my display. I tried the whole installation again, with the same result. My solution was to start again and install Ubuntu 9.04. So at present I do not have Ubuntu 9.10 on this computer, though presumably I could now upgrade to Ubuntu 9.10. My display is LG Flatron W2242S.

On my other computer, which also has on-board Nvidia graphics, but has a Fujitsu display, I did an upgrade rather than a clean install, and that worked ok.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: nvidia
Package: yelp 2.25.1-0ubuntu5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux 2.6.28-16-generic i686

[Brian Murray (brian-murray)]

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/FindRightPackage. I have classified this bug as a bug in nvidia-graphics-drivers-180.

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/ReportingBugs.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.