Your lspci shows you are using the onboard Intel GPU not your ATI one you told, so I get suspicious right there that your drivers for ATI are having problems.
I am getting crazier after each day LoL
Xorg showing it is using Intel
Code:
[ 25.560] (--) intel(0): Integrated Graphics Chipset: Intel(R) 965Q
Xorg showing it did not get an EDID from any ATI but from an Intel GPU, the next line where it says "Printing probed modes" is what makes me think that the there was something wrong with the EDID the Intel GPU found or parsed and that Xorg is trying to guess what the modelines are.
Code:
[ 25.567] (II) intel(0): Output VGA1 has no monitor section
[ 25.583] (II) intel(0): EDID for output VGA1
[ 25.583] (II) intel(0): Printing probed modes for output VGA1
[ 25.583] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 134
4 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 25.583] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 6
00 601 605 628 +hsync +vsync (37.9 kHz e)
[ 25.583] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 6
00 601 603 625 +hsync +vsync (35.2 kHz e)
[ 25.583] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 4
80 486 494 517 +hsync +vsync (31.0 kHz e)
[ 25.583] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 48
0 489 492 525 -hsync -vsync (31.5 kHz e)
[ 25.583] (II) intel(0): Output VGA1 connected
[ 25.583] (II) intel(0): Using exact sizes for initial modes
[ 25.583] (II) intel(0): Output VGA1 using initial mode 1024x768 +0+0
On other notes:
Honestly what is needed is a database of hardware and their ideal configurations, that unfortunately doesn't exist, the closest thing I saw was the archlinux wiki that has sections that users add with their own hardware optimal settings.
MythTV modeline database
http://www.mythtv.org/wiki/Modeline_Database
Designing your own EDID.
https://ubuntuforums.org/showthread.php?t=316985
Caveats:
The new way of doing it is to create a file in /usr/share/X11/xorg.conf.d/ to configure that you could call it.
10 - ACERMONITORMODEL.conf and optionally if possible create a Fedora wiki entry with tne name the monitor-edid gives you, which makes it easy for others to search and direct others to search for:
example:
Code:
$ monitor-edid | egrep -i name
Name: Acer X223W
That would be the name for the data to post.
Code:
su -
copy paste this whole block, hit enter and be amazed:
echo; \
echo "Date:"; \
echo; \
date; \
echo; \
echo "Linux kernel version"; \
echo; \
uname -r; \
echo; \
echo "GPU manufacturer, model and specs"; \
echo; \
lspci -v | awk '/VGA/,/^$/'; \
echo; \
echo "Monitor manufacturer, model and specs"; \
echo; \
monitor-edid
Then do a cat on the configuration file you created so others can see what you did.
e.g.:
Code:
In this example since the name of the monitor is Acer X223W and I would have created a file named 10-Acer-X223W.conf I would get the inside of that file with:
$ cat /usr/share/X11/xorg.conf.d/10-Acer-X223W.conf
ps: Your custom config file could help others that use the same chipset(GPU) you are using eventhough this should be in a database that could be searched by gpu, monitor model etc and not a wiki that have limited searchebility.
ps 2: you can also inclued the manufacture and product name using
Code:
# dmidecode -t system
or
# dmidecode -t system | egrep -i 'manufacturer|product'
ps: Maybe dmidecode is a better way to find a name for a wiki post, it would get the whole computer and not just parts, those parts could be included in subsections of the main article.
Hint:
For other that help in this forum, wouldn't be nice if we all got in the same page and asked the same information in a standard manner that everyone would be up to speed eventually?
Instead of asking "what computer do you have" you could say "copy paste this" and all necessary information will be available.
I got the idea watching how the people on the h-node did things.
http://h-node.org/hardware/catalogue/en
You can use xrandr --verbose to see what EDID if any it got and what the modelines are.
[/code]$ xrandr --verbose[/code]
ps: It is easier using grep on it to filter the data
Hint: Find Blocks of Text
Code:
lspci -v | awk '/VGA/,/^$/'
Explanation of how it does it:
The caret, ^, is a regular expression anchor that matches the start of a string, and $ matches the end, so in this example /^$/ looks for the line breaks at the beginning and end of the text block.
Source:
https://www.linux.com/learn/tutorial...thout-sorting/
dmidecode can give you the names and codes that everybody else uses to search for those things and a perfil of your own hardware.
Why that is important?
Is a question of communication, when searching for things is good to look for it in the format others use to transmit that information else it becomes harder to find anything.
monitor-edid I think it will try to probe the video card and ask for the EDID it may do it like Xorg or not I don't really know, but it could show you what the computer can see.
Code:
$ su -
# monitor-edid
mmap /dev/mem: Permission denied
Name: Acer X223W
EISA ID: ACR0009
EDID version: 1.3
EDID extension blocks: 0
Screen size: 47.3 cm x 29.6 cm (21.97 inches, aspect ratio 16/10 = 1.60)
Gamma: 2.2
Analog signal
Max video bandwidth: 170 MHz
HorizSync 30-83
VertRefresh 56-76
# Monitor preferred modeline (60.0 Hz vsync, 65.3 kHz hsync, ratio 16/10, 90 dpi)
ModeLine "1680x1050" 146.25 1680 1960 2136 2240 1050 1053 1059 1089 +hsync -vsync
You have to confirm that the data you see is what the manual of the monitor says it is.
On the issue of regressions, I good suspect is the /usr/share/X11/xorg.conf.d/10-quirks.conf
But it would be better to find where the commits history is locate for the repositories used for the GPU drivers. RPMFusion I have no clue where that could be, and in the standard Fedora repositories I know they have some kind of commit history I just don't know where it is.
Still one can use yum history to find out what was installed
Code:
# # yum history info 161
Where 161 is the code ID of the operation you want to look into and which you can get using:
Is on the ID column.
cvt now comes in the xorg-x11-server-Xorg yay!
Maybe useful:
Find the kernel driver it is using:
Code:
$ lspci -v | awk '/VGA/,/^$/'
And look into the parameters(aka options aka parm) that it has:
e.g.:
And then use the manual(aka man) to find out what those parameters mean.
e.g.:
ps: For those that don't speak english fluently "e.g." (aka exempli gratia) means "for example".
source: http://www.grammar-monster.com/easil...used/eg_ie.htm
And "aka" means "also known as"
source: http://www.urbandictionary.com/define.php?term=aka
Resources:
http://askubuntu.com/questions/81370...from-a-monitor
https://stackoverflow.com/questions/...id-from-eeprom
http://www.x.org/wiki/FAQVideoModes/
http://www.mythtv.org/wiki/Modeline_Database
https://wiki.archlinux.org/index.php/xrandr
UPDATE:
More places to look:
Showing the binary EDID in the terminal, meaning it will appear as a bunch of crazy symbols
Code:
# monitor-get-edid -v
This one will try to probe the GPU for the EDID from what I understood, and if you get permission denied or something like that, then you have a SeLinux problem somewhere.
Code:
# grep . /sys/class/drm/card*-*/*
The most important one is the EDID for example:
/sys/class/drm/card0-VGA-1/edid
It should have a copy of your EDID in there, if it is empty then there is something very wrong somewhere.
source: https://bugs.freedesktop.org/show_bug.cgi?id=74164