| Summary: | KMS and X do not use monitor's native resolution | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Johannes Obermayr <johannesobermayr> | ||||||||||||||||
| Component: | General | Assignee: | Default DRI bug account <dri-devel> | ||||||||||||||||
| Status: | RESOLVED INVALID | QA Contact: | |||||||||||||||||
| Severity: | normal | ||||||||||||||||||
| Priority: | medium | ||||||||||||||||||
| Version: | DRI git | ||||||||||||||||||
| Hardware: | All | ||||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Johannes Obermayr
2009-11-24 06:16:03 UTC
Created attachment 31442 [details]
dmesg
Created attachment 31443 [details]
Xorg.0.log
In case you didn't notice, there are bigger problems as well (the gpu lockup message in dmesg). Also the scheduling while atomic error isn't a good thing. Created attachment 31699 [details] dmesg I updated to author Ben Skeggs <bskeggs@redhat.com> 2009-12-03 03:53:42 (GMT) committer Ben Skeggs <bskeggs@redhat.com> 2009-12-03 06:08:03 (GMT) commit 6169057b2992862565c513ca432b35c4df33288a and changed kernel flavor. I think it looks a bit better... Hmm, can you post your xorg.conf here too please. The GPU hang issues are known on NVAC, I haven't been able to get my hands on one to find out what's going wrong as of yet however. Created attachment 31704 [details]
xorg.conf
xorg.conf which was generated by SaX2 in relation to latest dmesg.
It's likely this that's screwing things up, can you get rid of the DisplaySize, HorizSync and VertRefresh lines from the monitor section of xorg.conf and retry. Created attachment 31707 [details] Xorg.0.log (In reply to comment #7) It does not change appearance on console/in X. Newly created Xorg.0.log after KDE's start is attached. You still have those lines somewhere: (II) NOUVEAU(0): Using hsync ranges from config file (II) NOUVEAU(0): Using vrefresh ranges from config file There is something really wrong: $ cat /etc/X11/xorg.conf | grep HorizSync $ cat /etc/X11/xorg.conf | grep VertRefresh $ cat /etc/X11/xorg.conf | grep DisplaySize As you can see there is no output... $ cat /var/log/Xorg.0.log | grep "config file" Markers: (--) probed, (**) from config file, (==) default setting, (==) Using config file: "/etc/X11/xorg.conf" (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) NOUVEAU(0): Using hsync ranges from config file (II) NOUVEAU(0): Using vrefresh ranges from config file (II) NOUVEAU(0): Using hsync ranges from config file (II) NOUVEAU(0): Using vrefresh ranges from config file And here is output... Created attachment 33820 [details]
Xorg.0.log with nv
ION is also working with nv driver now.
Attached is output with nv driver (for EDID) which is also 1280x720 but it fits to my monitor.
Nouveau's (invalid) EDID which "produces" output out of monitor's area:
00FFFFFFFFFFFF0020A337320100000026100103804627780A0DC9A05747982712484CBFCF0001010101010101010101010101010101011D007251D01A206E2855007E884200001A011D00BC52D01E20B8285540C48E21000018000000FC004C43443232333345550A202020000000FD0032500F440F000A202020202020015E
I hope it is useful.
Created attachment 47007 [details]
dmesg output on ASUS E35M1-I Deluxe
Same problem on ASUS E35M1-I Deluxe (radeon).
Assign to DRI / General since it seems to be a general problem. Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default). Sorry about the noise! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.