Bug 419891

Summary: No signal with default mode.
Product: [Fedora] Fedora Reporter: Jan ONDREJ <ondrejj>
Component: xorg-x11-drv-atiAssignee: Dave Airlie <airlied>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8CC: lkundrak, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-10 05:38:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
xrandr --verbose
none
Xorg.log
none
xorg.conf
none
xorg.conf none

Description Jan ONDREJ 2007-12-11 15:39:40 UTC
Description of problem:


Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.3.0.0-36.fc8
xorg-x11-drv-ati-6.7.196-1.fc8
libXrandr-1.2.2-1.fc8

How reproducible: Always

Steps to Reproduce:
1. configure monitor automatically or set mode 1920x1280
2. start X server

  
Actual results:
Blank screen, after few seconds my monitor displays "No signal".

Expected results:
You know. :)

Additional info:
My monitor is not properly detected. I am unable to say to X server, that this mode:
Modeline "1920x1200"x59.9  193.25  1920 2056 2256 2592  1200
  1203 1209 1245 -hsync +vsync (74.6 kHz)
is wrong. Even if I have in configuration statically configured horizsync:
  HorizSync    31.5 - 74.5
this mode is selected. You can see, that this modeline is out of defined sync.
I am attaching my output from Xorg and xrand --verbose output.
I am able to set proper mode with this commend:
  xrandr --output DVI-0 --mode 0x51
Mode 0x51 at 74 kHz works well, but mode 0x50 (which is still autoselected) does
not work.
I don't know, how to tell to X server to ignore this bad mode.

An beginner user is unable to use this mode and it is hard to me too, because I
need to type this commend after logon and my monitor is off.

Comment 1 Jan ONDREJ 2007-12-11 15:39:40 UTC
Created attachment 284221 [details]
xrandr --verbose

Comment 2 Jan ONDREJ 2007-12-11 15:40:52 UTC
Created attachment 284231 [details]
Xorg.log

Comment 3 Jan ONDREJ 2007-12-11 15:43:28 UTC
Created attachment 284241 [details]
xorg.conf

Comment 4 Jan ONDREJ 2007-12-12 05:53:49 UTC
Created attachment 285091 [details]
xorg.conf

Previous xorg.conf has been my test, where the problematic mode has been
disabled.

Comment 5 Jan ONDREJ 2008-02-27 06:58:05 UTC
Still not working:
xorg-x11-drv-ati-6.8.0-1.fc8
xorg-x11-server-Xorg-1.3.0.0-42.fc8

Can I somehow help you?


Comment 6 Matěj Cepl 2008-02-27 07:08:37 UTC
Does vesa driver work? (so that at least you would have working computer :-))

Comment 7 Jan ONDREJ 2008-02-27 07:36:22 UTC
I can try VESA driver evening, if required, but:

- proprietary fglrx driver works well
- default driver from Fedora works too, but I have to set 60 Hz mode manually
after each login (which is not trivial, because my monitor is OFF)

I think my computer works perfectly. DDC does not send this 59.9 Hz mode to ATI
card. I don't know, where this bad mode rises.

Current solution is to use proprietary driver, but I don't like it and want to
go back to open source driver.


Comment 8 Matěj Cepl 2008-02-27 11:35:46 UTC
that xrandr command could be probably added to ~/.xinitrc (see xinit(1) for more).

Comment 9 Jan ONDREJ 2008-02-27 11:46:41 UTC
Probally. :-)

But it's a wrong solution for beginners, which have no signal after installation
of Fedora. May be it's a reason, why this bug has been marked as F9Target blocker.

Next proble is, tha I don't know, if it can't damage my monitor. Setting an
unsupported mode and then setting it back to an supported is not a good solution.

And last problem. GNOME's background is not properly set, when changing these
modes with xrandr. But it is another bug. Works well if this bug will be fixed.

Comment 10 Matěj Cepl 2008-02-27 22:46:43 UTC
Jan, I am not saying that this is the solution for this problem. Just as a
helpful bugmaster trying to make your life with broken Fedora slightly less painful.

Comment 11 Dave Airlie 2008-04-04 00:18:33 UTC
I've just checked a fix into the upstream server. it'll take a while to come
back downstream, but it definitely should be in F9 final.

maybe if we do another F8 server release I can fix it there.


Comment 12 Dave Airlie 2008-04-09 04:15:06 UTC
Should be fixed for F9 so removing blocker. it would be nice to have confirmation.

Comment 13 Jan ONDREJ 2008-04-09 05:01:17 UTC
I can't install F9 on my machine before it will be marked as stable.

Is it possible to install a package from F9 to F8 to test this?
Or can I test this new update elsewhere on F8?


Comment 14 Dave Airlie 2008-04-09 05:06:52 UTC
no its F9 only testable as it would require bringing in nearly all of F9, in
theory I could add the quirk to f8 but I haven't time at the moment.. you'll
just have to hope I fixed it correctly



Comment 16 Jan ONDREJ 2008-05-10 05:28:21 UTC
My old computer is completely down (requires to press F1 on broken PS/2 port :-).

On my new machine opensource graphics drivers are not working and with
proprietary driver this bug does not occur.

I can't check this anymore, so if you think, it is fixed in F9, you can close
this bug.


Comment 17 Dave Airlie 2008-05-10 05:38:50 UTC
I'll close it as I think its fixed.