[Hardy] Black screen - wrong monitor detection & refresh rate

[Peter Makowski]

Binary package hint: xorg

My Daytek DT-1530 monitor is detected as Generic Monitor with wrong refresh rates by Ubuntu 8.04. Correct refresh rates are:

H: 30-54
V: 50-120
Maximum resolution is 1024x768 with 60Hz.

[The Daytek 1536d model, listed in Ubuntu screen settings has the same parameters.]

My monitor isn't detected corectly and the screen is black when running live-cd and an installed system. Ubuntu 6.06 runs well in safe-graphics mode.

The only solution is to connect the machine to another monitor, change the monitor configuration in displayconfig-gtk to Daytek 1536d and connect the daytek back. After that there are no problems.

[Timo Aaltonen (tjaalton)]

We are not forcing refresh rates anymore, so please try hardy alpha2 livecd if it works ok.

[Peter Makowski (petermakowski)]

I started the Hardy Alpha-2 on my computer and the Ubuntu splash was displayed correctly. I don't know what about the desktop because the live-cd didnt' want to start because the computer has only 320mb of RAM. Probabily the problem does not occur in Hardy. But it's still actual with Gutsy.

[Timo Aaltonen (tjaalton)]

Gutsy will not receive fixes for problems like this. The splash-screen is not related to X. How were you able to run the livecd before, if you had only 320Mb memory? Did it actually complain about the RAM being too low?

[Peter Makowski (petermakowski)]

I had run the Xubuntu 7.10 live-cd without any problems... so I thik it may be a bug in Hardy. How much RAM does the Ubuntu live-cd exactly need? Should I make a report?

[Timo Aaltonen (tjaalton)]

I'm not sure how much it needs, but if you used Xubuntu before why not try that with Hardy too?

[Peter Makowski (petermakowski)]

So... I booted Xubuntu Hardy alpha3 and the usplash displayed correctly but when it has gone there appeared the "out of range" notification again. This bug prevents begginers from using Ubuntu (when installing ubuntu from alternate to a hard disk situation is the same).

[Timo Aaltonen (tjaalton)]

Piotr, if you add something to a bug, please subscribe to it. But if you happen to read this: your problem is not related to this bug, file a new one.

oponek: you should still try the Xubuntu hardy livecd.

[Peter Makowski (petermakowski)]

Sorry, I have merged my old account. Piotr Zaryk = oponek.

[Timo Aaltonen (tjaalton)]

Heh, ok. Is the "out of range" from your monitor, meaning that the driver is trying to use wrong settings for it? Sounds like it needs a quirk in the server.

Please try to get a Xorg.0.log from the failing session.. Should be possible by first changing to a virtual terminal.

[Peter Makowski (petermakowski)]

Ubuntu 6.06 runs on the same configuration even with 1024x768 mode (when setting safe graphical mode and 800x600 resolution on LiveCD, [strange])

[Peter Makowski (petermakowski)]

proper xorg.conf - monitor works!

[Daniel Hahler (blueyed)]

The autoconfiguration of the display fails with messages like this:
(II) NV(0): Not using default mode "1024x768" (hsync out of range)

It looks like no mode gets set by default?!

The relevant part from the log seems to be:
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1792x1344" (width too large for virtual size)
[...]
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "2048x1536" (width requires unsupported line pitch)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(--) NV(0): Virtual size is 1600x1200 (pitch 1600)
(**) NV(0): *Driver mode "1600x1200": 204.8 MHz, 94.1 kHz, 75.0 Hz
(II) NV(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync (94.1 kHz)
[.....]
(**) NV(0): *Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) NV(0): Modeline "320x175"x85.3 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync (37.9 kHz)
(**) NV(0): Display dimensions: (360, 270) mm
(**) NV(0): DPI set to (112, 112)

[Daniel Hahler (blueyed)]

Can you please try the proposed fix from bug 94671, which may be outdated:
  Edit /etc/X11/xorg.conf, add to the nvidia Devices section:
  Option "UseEDID" "False"

[Peter Makowski (petermakowski)]

The same bug occurs when using integrated graphic card (VIA). It is _not_ an nvidia bug. The problem is with the monitor detection.

[jotronic (jotronic)]

My Monitors also beeing wrong detected, always and no mater wich model i connect.

[Peter Makowski (petermakowski)]

The bug still exists in Interpid Alpha 5 (usplash is ok, but when the gnome desktop is loading the problem appears).

[nanog (sorenimpey)]

I can confirm this bug on multiple hardy and intrepid "nv" boxes with multiple monitors and projectors. Screen settings shows monitor not detected. Xrandr is similarly uninformative. When I use a manually configured xorg the monitor works properly. There needs to be an option to manually override randr settings when they are not working. Although I do not use windows I recall that windows 2000 had this option (with an appropriate warning).

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Piotr,

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 179472

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 179472 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/179472

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