Live CD unusable with HP Pavillion desktop due to screen resolution

[Tony Pursell]

The spec of the PC is

HP Pavillion t3510-uk desktop
Processor Intel Pentium D, memory 1GB
Graphics ATI Radeon Express 200 (integrated)
Monitor HP vs17s flat screen

Live i386 CD for 6.06 LTS used

With option Start/Install the result is a Gnome desktop at 640x480 resolution and this is the only option in System > Preferences > Screen Resolution. Both Install and Gparted options are unusable at this resolution because the dialogs do not fit the screen and cannot be resized.

With the option Safe Graphics Start/ Install the monitor displays a message asking for 1280x1024 @ 60Hz and cannot display the desktop.

Work around was to use the Gparted live CD which allows for screen resolution and video driver selection followed by an install from the Alternate Install CD. Even then manual X configuration was required to get a range of usable values in System > Preferences > Screen Resolution.

[towsonu2003 (towsonu2003)]

assigning to xorg as per
> With option Start/Install the result is a Gnome desktop at 640x480 resolution

[towsonu2003 (towsonu2003)]

also assigned to ubiquity as per
> Both Install and Gparted options are unusable at this resolution because the dialogs do not
> fit the screen and cannot be resized.

[Brian Murray (brian-murray)]

There is already a ubiquity bug regarding 640x480 not being usable. It is bug 38442.

[Brian Murray (brian-murray)]

Thanks for your bug report. Could you please add the full output of 'lspci -vv', 'lspci -vvn' and 'sudo xresprobe radeon' where radeon is the video driver you use to your bug report as attachments? Thanks in advance.

[Tony Pursell (ajpursell)]

I have attached the information you asked for.

[Bryce Harrington (bryce)]

Sounds like this is another example of a mis-detected monitor, so marking as a dupe of 3731.

A work around for this is to doublecheck the horizontal sync and vertical refresh rates in your xorg.conf file, to make sure they are appropriate for your monitor (check your monitor's documentation).

The ideal solution to the root problem is to ensure monitors like yours are detected properly; 3731 will be where we track this activity.

Thank you for reporting this issue in any case!
Bryce