system freezes after using Screen Resolution to set to 1440 x 900 with DVI output (works from command line or with VGA)

I've been trying to help with this a bit so I'll take the liberty of summarizing:

7.10: 1440x900 with DVI works as it should

8.04: 1440x900 with DVI hardlocks the machine completely, networking and everything dies

8.04 with kernel from 7.10: same as for 8.04.

Using the latest git ati driver from the PPA does not change the situation either.

Tried my system on a Fedora 8 Live CD and setting my monitor to 1440 x 900 works.

Version of the X server:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora Core 7 Red Hat, Inc.
Current Operating System: Linux localhost.localdomain 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686
Build Date: 17 October 2007
Build ID: xorg-x11-server 1.3.0.0-33.fc8
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present

ATI driver version:

(II) ATI: ATI driver wrapper (version 6.7.195)

Does it also lock up if changing the resolution using the xrandr command line utility?
Also, please collect a backtrace from the crash - see http://wiki.ubuntu.com/X/Backtracing for directions.

"xrandr -s 1440x900" was successful at changing the resolution.

Unfortunately, I can't do a backtrace since networking dies as a result of the system locking up.

You'll probably need to connect wired ethernet.

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

The system running Hardy was connected using wired Ethernet (if that's the system you meant), however the system that was pinging (running Windows XP) was connected wirelessly. (but I don't think this would be a problem, would it?)

I discovered something interesting today, I can successfully change the resolution the graphical way (i.e.: System > Preferences > Screen Resolution) to 1440x900 IF I change the refresh rate to 75 Hz at the same time (i.e.: select 1440x900 from the resolution drop-down, then 75 Hz from the refresh rate drop-down, and then click apply). And after rebooting the resolution remains set properly (at 1440x900) whereas before if I used the xrandr command I would have to do it everytime I started up.

As for Intrepid, should I continue commenting here on this thread or start a new bug report? I'll just say what's happened so far: I tried Intrepid alpha 4 and I get as far as the Ubuntu loading screen (ubuntu icon and orange progress bar) but then the monitor goes blank for a second, then flashes "Input not supported" (it's an acer AL1916W 19", I'm using DVI hookup)

With regards to Intrepid what you are experiencing sounds like possibly a bug in usplash, which should be a separate bug report. However, it'd be helpful to know if your desktop eventually does come up. I've sometimes heard of usplash not being visible but people waiting long enough and the gdm login screen showing up.

Alright, I'll try waiting longer to see if the login screen eventually comes up.

Well this time I waited about half an hour for something to show up. I realized I probably should have explained a few things in more detail:

the usplash screen shows multiple (usually about 3) progress bars. One where it should be and properly drawn, the others moved around a bit and only partially drawn (e.g.: bottom half cut off), as well the extra bars don't update / indicate the actual progress of loading.

after the progress bar is full (loading is complete) the screen blanks and the message "No Signal" is displayed (although this happens with every ubuntu version I've used just before the gdm login screen appears), but then the message "Input Not Supported" comes up

then (and this is probably the most important point) I hear the login sound (heard after a successful login), since I'm running off of the LiveCD, I guess it logs me in as user ubuntu

I used ctrl-alt-backspace to restart the display manager, after which the process repeats (i.e.: "no signal" then "invalid input" then login sound)

Okay, the issue you are experiencing is xserver-xorg-video-ati bug then. However, the problems you are having with usplash, the image being corrupted, is also a valid bug and is worth submitting. Please include a photograph of what it looks like if you do submit a bug. Thanks!

Some more developments about the trouble with Intrepid (yes, I know this bug is about Hardy but I think the problems in Hardy and Intrepid are related, as I'll point out below)

I decided to try Intrepid using the VGA cable instead of DVI, and the display worked, except the resolution was set to 1600x1024, so I set it 1440x900, and everything was fine (so it seems both Hardy and Intrepid initialize at the wrong resolution).

* anyone who's had the same/similar problem, definitely read this paragraph *
Knowing that the resolution was initializing wrong, I switched back to the DVI cable to try alt+F2 to open the run box, then type "xrandr -s 1440x900" (blindly, since the monitor is blank, :) ), hit return, wait a few seconds, and success!

I guess if the monitor is using DVI input and the resolution is anything greater than 1440x900, it just flashes "Input Not Supported"

Hi TPepler,

You mentioned earlier that you had trouble pinging the machine even with it connected via ethernet - is that correct? If so then you may be having a kernel OOPS. I'll add the kernel component so the kernel QA team can take a look.

If that's the case, you may want to test this against alpha-5, which will have the new 2.6.27 kernel, to see if the issue is resolved there.

Meanwhile, could you attach Xorg.0.logs from both configurations (monitor on VGA and monitor on DVI)? Make sure to move aside your ~/.config/monitors.xml (if any) so it'll come up with the autodetected resolutions. If it is *not* a kernel bug, we'll need the logs from both those situations.

Anyway, as per comment #5, resolution switching from the command line seems to be working ok, so that suggests it's a bug in the Screen Resolution applet, but without a backtrace it's hard to begin troubleshooting on this one. The network failure makes me suspect a kernel issue, but more investigation would be needed on that angle to be sure.

could you try if that's still an issue in jaunty?

Tried 9.04 (Jaunty) and everything was great, initialized to the correct resolution (even from the liveCD) and that also includes the login screen (which was not setting to the correct resolution in Hardy or Intrepid). I even tried switching to some wrong resolutions (e.g.: 1024x768) and it was okay (i.e.: didn't crash).

thank you for the update, closing the bug since that works now

Closing kernel task. Thanks.