[RV530] Black screen on a Daewoo DLT-22W4T monitor

[Fabio Bossi]

Binary package hint: xorg

Screen goes black after booting an Ubuntu LiveCD on a system with a Radeon X1650 card and a Daewoo DLT-22W4T TV/Monitor, though splash screen is displayed correctly and I can still acces ttys. I have no problems if I replace the monitor with a different one.

I have tried both Intrepid and Jaunty, and also reverted to VESA with no effect.

In Lucid I don't get the black screen, but the monitor is still not properly detected and I can't set it to a decent resolution without running xrandr manually.

[lspci]
00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host Bridge [1106:0336]
     Subsystem: VIA Technologies, Inc. K8M890CE Host Bridge [1106:0336]
02:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon X1650 Pro [1002:71c1] (rev 9e)
     Subsystem: PC Partner Limited Device [174b:0840]

[Bryce Harrington (bryce)]

Hi fabio-bossi,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

I should have access to that machine later today. Expect those files to be uploaded in the next 12 hours.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

Here are the files. This time I took them using Linux Mint 7 Gloria, but it should make no difference. The ones with the .safe prefix were taken in safe mode.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

I got. Here's the problem:

(II) RADEON(0): Using fuzzy aspect match for initial modes
(II) RADEON(0): Output DVI-1 using initial mode 1152x864

I have tried that resolution under Windows an it also results in a black screen. So the problem is that the autodetected resolution is wrong.

Should I try the workaround described in https://wiki.ubuntu.com/X/Troubleshooting/Resolution ?

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

The (correct) resolution used by default in Windows, and suggested in the monitor's manual, is 1440*900.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

I have tried tweaking xorg.conf to the best of my capabilities, but it had no effect.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

This persists in Karmic. Removed the jaunty tag since I have reproduced this on three different versions of Ubuntu.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

In Lucid I don't get the black screen, but the monitor is still not properly detected and I can't set it to a decent resolution without running xrandr manually.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Fabio,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 444789

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 444789 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/444789

[Bryce Harrington (bryce)]

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.