Kubuntu hangs on initial boot when the monitor has a resolution greater than 1280x1024

[Kevin Slade]

I have installed several Kubuntu 9.04 AMD64 installs and whenever the screen resolution reported by the monitor(s) exceeds 1280 x 1024, the initial boot after installation & any subsequent boots until an Nvidia driver is loaded shows the Kubuntu initial load logo, then attempts to set the screen resolution to that reported by the monitor(s).

The version of the Kubuntu 9,04 installer is the AMD64 alternate boot CD.

At that time the system locks completely and the only thing that will recover access to the system is a full power down or a system reset.

When the monitor resolution reported is 1280 x 1024 or lower, the system boots normally and the Nvidia drivers can be loaded. Once these drivers are loaded, higher resolution monitors or dual monitors can then be used .

The real problem occurs when there is only one large high resolution monitor. The workaround may be to boot with the screen turned off and turn it on only after the system has come up to the logon prompt. I will try this in the next day or so when I have access to the system I have been rebuilding.

[Kevin Slade (kevin-kiwisoft)]

This moning I tried using a single High res mnitor that was turned OFF.

The system still hung at boot. The only way I could access the sytem was to use a low res (1280 x 1024) monitor.

[Kevin Slade (kevin-kiwisoft)]

lspci from one of the affected systems is

01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600XT]

[Kevin Slade (kevin-kiwisoft)]

The lspci entry from another system is:

01:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT] (rev a1)

[Fabio Marconi (fabiomarconi)]

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 PKGNAME.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

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 xorg.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

Hello Kevin Slade
Is this bug reproducible with the latest updated Lucid 's packages?
Thanks in advance.
:)Fabio

[Fabio Marconi (fabiomarconi)]

Hello Kevin Slade,
Sorry but something goes wrong during your report (i've received a blank mail and here don't appear nothing) so please can you repost here your comment.
Thanks
:)Fabio

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Kevin Slade (kevin-kiwisoft)]

This was able to be reproduced on several systems with NVIDIA video cards and high resolution LCD monitors. I have since used 10.04 on the same systems and it works flawlessly.

It appeared to be a fault with the default Nvidia driver, as it worked at 1280x1024 and at that resolultion I has able to install the optional Nvidia drivers and then use either a single monitor at 1920x1200 or with dual monitors at about 1600x1050.

I am happy to see this closed based on changes in 10.04

Regards Kevin

[Fabio Marconi (fabiomarconi)]

Hello Kevin
Thanks for the reply
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.