In a new Fedora-18/64 bit install in a new computer I am unable to set the resolution above 1024x768 at 60HZ and would like to set it higher.
I found the following:.
[root@box10 ~]# ll /etc/X11/xorg.conf.d total 4 -rw-rw-r--. 1 root root 161 Feb 28 04:42 00-anaconda-keyboard.conf
To which I attempted to add configuration data for this ViewSonic VX2035WM monitor, trying to increase the resolution to the manufacturer's spec.
The following does not work. I got a black screen and had to bring up another terminal and remove the file in order to reboot. The truth is I don't really know what I'm doing, perhaps someone who understand this can point out what needs to be done?
/etc/X11/xorg.conf.d/10-monitor-conf
Section "Monitor" Identifier "Monitor0" EndSection
Section "Device" Identifier "Device0" Driver "vesa" #Choose the driver used for this monitor EndSection
Section "Screen" Identifier "Screen0" #Collapse Monitor and Device section to Screen section Device "Device0" Monitor "Monitor0" DefaultDepth 16 #Choose the depth (16||24) SubSection "Display" Depth 16 Modes "1680x1050_60.00" #Choose the resolution EndSubSection EndSection
Any suggestion appreciated.
Bob
On 03/01/2013 06:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set the resolution above 1024x768 at 60HZ and would like to set it higher.
I found the following:.
[root@box10 ~]# ll /etc/X11/xorg.conf.d total 4 -rw-rw-r--. 1 root root 161 Feb 28 04:42 00-anaconda-keyboard.conf
To which I attempted to add configuration data for this ViewSonic VX2035WM monitor, trying to increase the resolution to the manufacturer's spec.
The following does not work. I got a black screen and had to bring up another terminal and remove the file in order to reboot. The truth is I don't really know what I'm doing, perhaps someone who understand this can point out what needs to be done?
/etc/X11/xorg.conf.d/10-monitor-conf
Section "Monitor" Identifier "Monitor0" EndSection Section "Device" Identifier "Device0" Driver "vesa" #Choose the driver used for this monitor EndSection Section "Screen" Identifier "Screen0" #Collapse Monitor and Device section to Screen section Device "Device0" Monitor "Monitor0" DefaultDepth 16 #Choose the depth (16||24) SubSection "Display" Depth 16 Modes "1680x1050_60.00" #Choose the resolution EndSubSection EndSectionAny suggestion appreciated.
hey bob,
give this a try:
Section "Monitor" Identifier "Monitor0" EndSection
Section "Device" Identifier "Videocard0" Driver "ati" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 Modes "1680x1050_60.00" EndSubSection EndSection
hth.
On 03/01/2013 02:42 PM, g wrote:
give this a try:
Section "Monitor" Identifier "Monitor0" EndSection Section "Device" Identifier "Videocard0" Driver "ati" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 Modes "1680x1050_60.00" EndSubSection EndSectionhth. -- g
Well that's an improvement in that it works however I still don't have an option of selecting higher than 1024x768.
Section "Device" Identifier "Videocard0" Driver "ati"
I wonder if the ati driver is appropriate. The processor is an AMD A8 3850 and the GPU is apparently integral to it. The only thing I've found so far:
Integrated Graphics
* Type AMD Radeon HD 6550D * Base Frequency 600 MHz
Bob
On 03/02/13 05:49, Bob Goodwin - Zuni, Virginia, USA wrote:
ell that's an improvement in that it works however I still don't have an option of selecting higher than 1024x768.
Section "Device" Identifier "Videocard0" Driver "ati"
I wonder if the ati driver is appropriate. The processor is an AMD A8 3850 and the GPU is apparently integral to it. The only thing I've found so far:
Integrated Graphics
- Type AMD Radeon HD 6550D
- Base Frequency 600 MHz
Time for the usual questions.....
What is the output of "xrandr"? And, is your monitor attached to your system via a KVM switch?
On 03/01/2013 06:29 PM, Ed Greshko wrote:
Time for the usual questions.....
What is the output of "xrandr"? And, is your monitor attached to your system via a KVM switch?
--
[bobg@box10 ~]$ xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 HDMI-0 disconnected (normal left inverted right x axis y axis)
And no, I don't have a KVM switch.
On 03/02/13 00:55, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/01/2013 06:29 PM, Ed Greshko wrote:
Time for the usual questions.....
What is the output of "xrandr"? And, is your monitor attached to your system via a KVM switch?
--
[bobg@box10 ~]$ xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 HDMI-0 disconnected (normal left inverted right x axis y axis)
And no, I don't have a KVM switch.
ls -l /sys/class/drm/
poma
On 03/02/2013 12:36 AM, poma wrote:
ls -l /sys/class/drm/
poma
[bobg@box10 ~]$ ls -l /sys/class/drm/ total 0 lrwxrwxrwx. 1 root root 0 Mar 2 2013 card0 -> ../../devices/pci0000:00/0000:00:01.0/drm/card0 lrwxrwxrwx. 1 root root 0 Mar 2 2013 card0-HDMI-A-1 -> ../../devices/pci0000:00/0000:00:01.0/drm/card0/card0-HDMI-A-1 lrwxrwxrwx. 1 root root 0 Mar 2 2013 card0-VGA-1 -> ../../devices/pci0000:00/0000:00:01.0/drm/card0/card0-VGA-1 lrwxrwxrwx. 1 root root 0 Mar 2 2013 controlD64 -> ../../devices/pci0000:00/0000:00:01.0/drm/controlD64 lrwxrwxrwx. 1 root root 0 Mar 2 2013 ttm -> ../../devices/virtual/drm/ttm -r--r--r--. 1 root root 4096 Mar 2 2013 version
A new command to me, interesting but what do I do with it?
Bob
On 03/02/13 13:32, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/02/2013 12:36 AM, poma wrote:
ls -l /sys/class/drm/
poma
[bobg@box10 ~]$ ls -l /sys/class/drm/ total 0 lrwxrwxrwx. 1 root root 0 Mar 2 2013 card0 -> ../../devices/pci0000:00/0000:00:01.0/drm/card0 lrwxrwxrwx. 1 root root 0 Mar 2 2013 card0-HDMI-A-1 -> ../../devices/pci0000:00/0000:00:01.0/drm/card0/card0-HDMI-A-1 lrwxrwxrwx. 1 root root 0 Mar 2 2013 card0-VGA-1 -> ../../devices/pci0000:00/0000:00:01.0/drm/card0/card0-VGA-1 lrwxrwxrwx. 1 root root 0 Mar 2 2013 controlD64 -> ../../devices/pci0000:00/0000:00:01.0/drm/controlD64 lrwxrwxrwx. 1 root root 0 Mar 2 2013 ttm -> ../../devices/virtual/drm/ttm -r--r--r--. 1 root root 4096 Mar 2 2013 version
A new command to me, interesting but what do I do with it?
If VGA-0 is connected(xrandr), monitor-parse-edid /sys/class/drm/card0-VGA-1/edid should show information about a monitor and its capabilities i.e. edid. Note that there is a discrepancy in naming scheme between kernel(VGA-1) and display server(VGA-0). I assume it's the monitor from "Display rates" thread[1].
poma
[1] http://lists.fedoraproject.org/pipermail/users/2013-January/429876.html
On 03/01/2013 09:49 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/01/2013 02:42 PM, g wrote:
give this a try:
<> cutting that out. sending full layout.
Well that's an improvement in that it works however I still don't have an option of selecting higher than 1024x768.
Section "Device" Identifier "Videocard0" Driver "ati"
I wonder if the ati driver is appropriate. The processor is an AMD A8 3850 and the GPU is apparently integral to it.
good question. i have no idea, but you can find out with command;
]$ lspci
which will list all of your pci hardware, among which will/should/may be your graphics chip.
]$ lshw|less
will give you a complete hardware listing. "less" is because it is a long listing and it will finish before you see what you want to. :)
The only thing I've found so far:
Integrated Graphics
- Type AMD Radeon HD 6550D
- Base Frequency 600 MHz
i was not familiar with the amd a8-3850 cpu/gpu. a quick search via ixquick.com [i am thru with gobble and their tracking] to find out a little more about the cpu/gpu chip. nothing to say how it appears.
amd now owns ati, so your driver ?should? be correct. or so i would imagine, because i see no reason for things to be different.
here is the full listing of what i have in my /etc/X11/xorg.conf file;
=+=+= # Xorg configuration created by system-config-display
Section "ServerLayout" Identifier "single head configuration" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us+inet" EndSection
Section "Monitor" Identifier "Monitor0" ModelName "Monitor 1280x1024" HorizSync 31.5 - 81.0 VertRefresh 50.0 - 75.0 Option "dpms" Gamma 1.00 1.00 1.00 # created by KGamma EndSection
Section "Device" Identifier "Videocard0" Driver "ati" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1280x768" \ "1280x720" "1152x864" "1152x768" "1024x768" \ "832x624" "800x600" "640x480" "640x400" EndSubSection EndSection =+=+=
*note* my monitor is not maxed at 1280x1024, but i set it that way because if i go higher, text/type gets too small to read.
i do not know if 'horzSynic' and 'vertRefresh' are necessary, but i put them anyway.
what you may want/need to do is look up your monitor to see for sure what it can do.
as for the "Screen" section, "Modes" are what my graphics card can do. i tend to believe that you will need to have capabilities listed. if not listed, you may not get what you want.
something you might try is changing "1680x1050_60.00" to just "1680x1050" to see what happens.
a few years/releases back, there was an "x" command that would read your hardware and set up the xorg.conf file. i do not recall the name of it, but i believe it has been pulled for reasons of determining setup with another way. i do not recall 'new way', perhaps someone else reading your thread may help on that.
later.
On 03/01/2013 06:40 PM, g wrote:
i was not familiar with the amd a8-3850 cpu/gpu. a quick search via ixquick.com [i am thru with gobble and their tracking] to find out a little more about the cpu/gpu chip. nothing to say how it appears.
amd now owns ati, so your driver ?should? be correct. or so i would imagine, because i see no reason for things to be different.
here is the full listing of what i have in my /etc/X11/xorg.conf file;
Ok, it's about the end of the day for me but I will experiment with this tomorrow.
The low res. is easier to read but it tends to go off the edges.
Thanks.
Bob
On Fri, 01 Mar 2013 16:49:56 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
Section "Device" Identifier "Videocard0" Driver "ati"
I wonder if the ati driver is appropriate. The processor is an AMD A8 3850 and the GPU is apparently integral to it. The only thing I've found so far:
Integrated Graphics
- Type AMD Radeon HD 6550D
- Base Frequency 600 MHz
Well, first of all, you probably want to put "radeon" driver up there instead of "ati".
Second, the data about your PCI hardware, including the graphics card, is displayed by "lspci -v", which should confirm that you have an ATI Radeon graphics card.
Third, you want to remove any extra hardware (like a KVM switch) from between the monitor and the computer, and connect the two directly. This will ensure that the EDID data from the monitor is being read properly, if possible.
Fourth, you should tell us whether this was a clean install or an upgrade. If it was a clean install, you should send us the content of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin or something). This file can tell all the details about what is going wrong with automatic resolution detection and EDID readout.
Fifth, if you did an upgrade from a previous Fedora version, there may be a lot of cruft left from a previous X (mis)configuration. In that case, you want to remove all custom drivers that you may have added before, rename /etc/xorg.conf.d/ to something else, and reboot the system to let it start with default automatic configuration. The automatic configuration usually Just Works, and is by far the best method for configuring X.
Finally, please don't just copy-paste other people's xorg.conf files. This is just ignorant and wrong --- every hardware combination has a different configuration, and it is most likely that someone else's xorg.conf file will *not* work on your system. Or if it does, it may work suboptimally and create a lot of minor glitches all over the system.
HTH, :-) Marko
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
Well, first of all, you probably want to put "radeon" driver up there instead of "ati".
Did that ...
Second, the data about your PCI hardware, including the graphics card, is displayed by "lspci -v", which should confirm that you have an ATI Radeon graphics card.
[bobg@box10 ~]$ lspci -v 00:00.0 Host bridge: Advanced Micro Devices [AMD] Family 12h Processor Root Complex Subsystem: Advanced Micro Devices [AMD] Family 12h Processor Root Complex Flags: bus master, 66MHz, medium devsel, latency 0
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6550D] (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device 1707 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at e0000000 (32-bit, prefetchable) [size=256M] I/O ports at f000 [size=256] Memory at fef00000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: radeon
00:01.1 Audio device: Advanced Micro Devices [AMD] nee ATI BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series] Subsystem: Advanced Micro Devices [AMD] nee ATI BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series] Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at fef44000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel ............snip...........
Third, you want to remove any extra hardware (like a KVM switch) from between the monitor and the computer, and connect the two directly. This will ensure that the EDID data from the monitor is being read properly, if possible.
There is no KVM, etc.
Fourth, you should tell us whether this was a clean install or an upgrade.
New install via Fedora LiveUsb Creator on external hard drive. I've found that often works when flash drives wont even though they are recognized?
If it was a clean install, you should send us the content of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin or something). This file can tell all the details about what is going wrong with automatic resolution detection and EDID readout.
I have been screwing with "Dropbox" for more than an hour and still don't know how to provide a link to the Xorg.0.log file I put there?
Fifth, if you did an upgrade from a previous Fedora version, there may be a lot of cruft left from a previous X (mis)configuration. In that case, you want to remove all custom drivers that you may have added before, rename /etc/xorg.conf.d/ to something else, and reboot the system to let it start with default automatic configuration. The automatic configuration usually Just Works, and is by far the best method for configuring X.
Only "cruft" might be from various attempts to create a working file.
Finally, please don't just copy-paste other people's xorg.conf files. This is just ignorant and wrong
Sorry, I must plead ignorance ...
--- every hardware combination has a different configuration, and it is most likely that someone else's xorg.conf file will *not* work on your system. Or if it does, it may work suboptimally and create a lot of minor glitches all over the system.
HTH,:-)
Thanks,
Bob
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
If it was a clean install, you should send us the content of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin or something). This file can tell all the details about what is going wrong with automatic resolution detection and EDID readout.
/home/bobg/Dropbox/Link to Xorg.0.log
Ok, I can pnly hope this link works!
Bob
On 03/02/2013 01:40 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
If it was a clean install, you should send us the content of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin or something). This file can tell all the details about what is going wrong with automatic resolution detection and EDID readout.
/home/bobg/Dropbox/Link to Xorg.0.log
Ok, I can pnly hope this link works!
Bob
Another try, one of these should be a link, I find their user instructions less than clear!
https://www.dropbox.com/s/wlz2dm4fh2kizlp/Xorg.0.log?m https://dl-web.dropbox.com/get/Link%20to%20Xorg.0.log?w=AADYgwU3gh3ti2lRRfNI...
On Sat, 02 Mar 2013 14:24:57 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
On 03/02/2013 01:40 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
If it was a clean install, you should send us the content of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin or something). This file can tell all the details about what is going wrong with automatic resolution detection and EDID readout.
https://www.dropbox.com/s/wlz2dm4fh2kizlp/Xorg.0.log?m https://dl-web.dropbox.com/get/Link%20to%20Xorg.0.log?w=AADYgwU3gh3ti2lRRfNI...
Ok, this is the relevant portion of the file:
[ 31.968] (II) RADEON(0): EDID for output VGA-0 [ 31.968] (II) RADEON(0): Printing probed modes for output VGA-0 [ 31.968] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 31.968] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 31.968] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 31.968] (II) RADEON(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e) [ 31.968] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
So the EDID is being read.
This readout can mean two things: either your monitor is reporting only these resolutions as supported (and X chooses the highest one available, 1024x768), or the radeon driver is probing only for these resolutions (probably as a consequence of a config file).
So we need two more pieces of information: (1) the exact make and model of your monitor, and possibly a link to its instruction manual or technical specifications or similar (google is your friend), and (2) the contents of /etc/X11/xorg.conf.d/ directory (the files should be small, copy-paste them directly into the e-mail).
If your monitor is too old or has a broken EDID information, we'll probably set up manual modelines for your desired resolution in the config files. But first we should see the current configuration.
HTH, :-) Marko
On 03/03/2013 04:57 AM, Marko Vojinovic wrote:
Ok, this is the relevant portion of the file:
[ 31.968] (II) RADEON(0): EDID for output VGA-0 [ 31.968] (II) RADEON(0): Printing probed modes for output VGA-0 [ 31.968] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 31.968] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 31.968] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 31.968] (II) RADEON(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e) [ 31.968] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
So the EDID is being read.
This readout can mean two things: either your monitor is reporting only these resolutions as supported (and X chooses the highest one available, 1024x768), or the radeon driver is probing only for these resolutions (probably as a consequence of a config file).
So we need two more pieces of information: (1) the exact make and model of your monitor, and possibly a link to its instruction manual or technical specifications or similar (google is your friend),
ViewSonic VX2035WM
Specifications LCD Type Color Filter Glass Surface 20.1” (full 20.1" viewable diagonal area), TFT (Thin Film Transistor), Active Matrix WSXGA+ LCD, 0.258 mm pixel pitch RGB vertical stripe Anti-Glare Input Signal Video RGB analog (0.7/1.0 Vp-p, 75 ohms) / TMDS Digital (100ohms) Sync Separate Sync, fh:30-82 kHz, fv:50-85 Hz Compatibility PC Up to 1680 x 1050 Non-interlaced Power Macintosh up to 1680 x 1050 Macintosh1 Resolution Recommended 1680 x 1050 @ 60 Hz and supported 1600 x 1200 @ 60 Hz 1400 x 1050 @ 60, 75 Hz 1280 x 1024 @ 60, 70, 72 Hz 1024 x 768 @ 60, 70, 72, 75, 85 Hz 800 x 600 @ 56, 60, 72, 75, 85 Hz 640 x 480 @ 60, 75, 85 Hz 720 x 400 @ 70 Hz Power Voltage 100-240 VAC, 50-60 Hz (auto switch)
Source: http://www.viewsonic.com/us/support/downloads/search_user_guides/?prod_name=...
and (2) the contents of /etc/X11/xorg.conf.d/ directory (the files should be small, copy-paste them directly into the e-mail).
[bobg@box10 ~]$ ll /etc/X11/xorg.conf.d/ total 16 -rw-rw-r--. 1 root root 161 Feb 28 04:42 00-anaconda-keyboard.conf -rw-rw-r--. 1 root root 551 Mar 2 10:16 10-monitor-conf -rw-rw-r--. 1 root root 543 Mar 1 19:23 10-monitor-conf~ -rw-r--r--. 1 root root 549 Mar 1 19:22 10-monitor-conf.test
Presently as created by my attempts, works good but at 1024x768:
[bobg@box10 ~]$ cat /etc/X11/xorg.conf.d/10-monitor-conf # /etc/X11/xorg.conf.d/10-monitor-conf #
Section "Monitor" Identifier "Monitor0" EndSection
Section "Device" Identifier "Videocard0" Driver "radeon" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 Modes "1680x1050_75.0" EndSubSection EndSection
If your monitor is too old or has a broken EDID information, we'll probably set up manual modelines for your desired resolution in the config files. But first we should see the current configuration.
The monitor is old, perhaps 4 years, but little used, an artifact of the last Windows computer in the house, replaced by an iPad, etc. Still too good to toss overboard ...
Thanks,
Bob
HTH,:-)
On 03/03/13 05:57, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/03/2013 04:57 AM, Marko Vojinovic wrote:
Ok, this is the relevant portion of the file:
[ 31.968] (II) RADEON(0): EDID for output VGA-0 [ 31.968] (II) RADEON(0): Printing probed modes for output VGA-0 [ 31.968] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 31.968] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 31.968] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 31.968] (II) RADEON(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e) [ 31.968] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
So the EDID is being read.
This readout can mean two things: either your monitor is reporting only these resolutions as supported (and X chooses the highest one available, 1024x768), or the radeon driver is probing only for these resolutions (probably as a consequence of a config file).
So we need two more pieces of information: (1) the exact make and model of your monitor, and possibly a link to its instruction manual or technical specifications or similar (google is your friend),
ViewSonic VX2035WM
Specifications LCD Type Color Filter Glass Surface 20.1” (full 20.1" viewable diagonal area), TFT (Thin Film Transistor), Active Matrix WSXGA+ LCD, 0.258 mm pixel pitch RGB vertical stripe Anti-Glare Input Signal Video RGB analog (0.7/1.0 Vp-p, 75 ohms) / TMDS Digital (100ohms) Sync Separate Sync, fh:30-82 kHz, fv:50-85 Hz Compatibility PC Up to 1680 x 1050 Non-interlaced
Ok, after messing with this for several days I finally have an /etc/X11/xorg.conf.d/10-monitor.conf file that allows allows use of the recommended display set up.
[bobg@box10 ~]$ cat /etc/X11/xorg.conf.d/10-monitor.conf # /etc/X11/xorg.conf.d/10-monitor.conf #
Section "Monitor" Identifier "Monitor0" Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync Modeline "1024x768_60.00" 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync EndSection
Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Modes "1680x1050_60" "1280x1024_60.00" "1024x768_60.00" EndSubSection EndSection
Section "Device" Identifier "Card0" Driver "radeon" EndSection
However despite selecting 1680x1050 in the Display GUI menu nothing changes until I do xrandr -s 1680x1050.
I can probably live with that by adding it to my routine set up procedure it would be nice if I could make it come up that way after I do "startx."
More help needed there, suggestions and criticism invited.
Bob
On 3/1/2013 1:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set the resolution above 1024x768 at 60HZ and would like to set it higher.
I found the following:.
[root@box10 ~]# ll /etc/X11/xorg.conf.d total 4 -rw-rw-r--. 1 root root 161 Feb 28 04:42 00-anaconda-keyboard.conf
To which I attempted to add configuration data for this ViewSonic VX2035WM monitor, trying to increase the resolution to the manufacturer's spec.
The following does not work. I got a black screen and had to bring up another terminal and remove the file in order to reboot. The truth is I don't really know what I'm doing, perhaps someone who understand this can point out what needs to be done?
/etc/X11/xorg.conf.d/10-monitor-conf
Section "Monitor" Identifier "Monitor0" EndSection Section "Device" Identifier "Device0" Driver "vesa" #Choose the driver used for this monitor EndSection Section "Screen" Identifier "Screen0" #Collapse Monitor and Device section to Screen section Device "Device0" Monitor "Monitor0" DefaultDepth 16 #Choose the depth (16||24) SubSection "Display" Depth 16 Modes "1680x1050_60.00" #Choose theresolution EndSubSection EndSection
Any suggestion appreciated.
Bob
You could use "system-config-display" to do this. But Fedora dropped it several releases ago.
And now is when you will get message after message chock full of helpful 'try this' suggestions that won't work and many 'what does some cryptic CLI command say? Followed by more 'try this' suggestions that won't work either.
Or? You could use "system-config-display" to do this. But as I said Fedora dropped it several releases ago.
Or? You could try Mageia which will find a generic monitor that will offer the correct resolution for you. And you can actually use their configuration suite so that you might actually find the *exact* monitor, by the name and the model and then find a series of *exact* resolution settings for your exact monitor.
Or? You can stay here and deal with 'something that almost works'.
On 03/01/2013 06:41 PM, David wrote:
You could use "system-config-display" to do this. But Fedora dropped it several releases ago.
And now is when you will get message after message chock full of helpful 'try this' suggestions that won't work and many 'what does some cryptic CLI command say? Followed by more 'try this' suggestions that won't work either.
Or? You could use "system-config-display" to do this. But as I said Fedora dropped it several releases ago.
Or? You could try Mageia which will find a generic monitor that will offer the correct resolution for you. And you can actually use their configuration suite so that you might actually find the *exact* monitor, by the name and the model and then find a series of *exact* resolution settings for your exact monitor.
Or? You can stay here and deal with 'something that almost works'. -- David
Yes, I understand your point but I have nothing better to do and it's an interesting problem, I may learn something messing with it too.
If I can't make it work acceptably I can switch monitors around or perhaps even buy another one. Problem there is that this ViewSonic monitor has been laying around here unused for a couple of years and it needs to do some work.
Thanks for responding.
Bob
On 3/1/2013 7:11 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/01/2013 06:41 PM, David wrote:
You could use "system-config-display" to do this. But Fedora dropped it several releases ago.
And now is when you will get message after message chock full of helpful 'try this' suggestions that won't work and many 'what does some cryptic CLI command say? Followed by more 'try this' suggestions that won't work either.
Or? You could use "system-config-display" to do this. But as I said Fedora dropped it several releases ago.
Or? You could try Mageia which will find a generic monitor that will offer the correct resolution for you. And you can actually use their configuration suite so that you might actually find the *exact* monitor, by the name and the model and then find a series of *exact* resolution settings for your exact monitor.
Or? You can stay here and deal with 'something that almost works'. -- David
Yes, I understand your point but I have nothing better to do and it's an interesting problem, I may learn something messing with it too.
If I can't make it work acceptably I can switch monitors around or perhaps even buy another one. Problem there is that this ViewSonic monitor has been laying around here unused for a couple of years and it needs to do some work.
Thanks for responding.
Bob
Sure.
But before *I* bought (read *pay my money for here*) another monitor to replace one that I already own (read already paid for but does not work here), which might (read maybe) configure, or might not (read creditable chance to fail), I would try a different Linux distro (free and similar), that costs nothing to download and try with my already paid for hardware. Which 'some guy' (me) told me might, probably would, work without me spending money to replace still working hardware.
Your choice of course.
Me? I would try thr 'free' path first.
Good luck.
On Fri, 01 Mar 2013 18:41:41 -0500 David dgboles@gmail.com wrote:
You could use "system-config-display" to do this. But Fedora dropped it several releases ago.
Did you ever get well informed about *why* it was dropped? There was a reason for that.
And now is when you will get message after message chock full of helpful 'try this' suggestions that won't work and many 'what does some cryptic CLI command say? Followed by more 'try this' suggestions that won't work either.
This is just FUD. There is always a well-defined way to troubleshoot X-related problems --- read and understand the /var/log/Xorg.0.log file. Or if you don't know how to read and understand it, send it to the mailing list so that someone can tell you what's wrong and how to fix it.
There are typically three types of causes for X problems:
(1) Driver misconfiguration. You want to use lspci to determine your graphics hardware, and use yum to install an appropriate driver. Also, reconfigure xorg.conf (if it is present on the system) to use the new driver. While at it, rethink if you really need an xorg.conf file at all (typically, you're better off without it).
(2) EDID data not being read correctly. This may happen on some very very old (or broken) monitors which do not provide EDID data, or with a faulty VGA cable, or with a lousy KVM switch which interferes with EDID readout. Depending on the cause, either remove the KVM, or change the cable, or manually set modelines in the xorg.conf (as a last resort only).
(3) PEBCAK. Two Fedora versions ago, your graphics didn't work, and someone gave you their xorg.conf, compiled their custom drivers from source on your machine, and it started working. After two Fedora upgrade cycles, the configuration is broken again. What could possibly be wrong this time??!
Best, :-) Marko
Allegedly, on or about 02 March 2013, Marko Vojinovic sent:
or with a faulty VGA cable
Or, just so nobody is left in the lurch, an apparently not faulty brand new cable, that simply hasn't got any wiring between the two pins that carry the EDID signals. Some cheap cables only bother wire up the video, sync, and ground pins.
And there are some monitors that don't bother to provide EDID, at all. Though, I only expect that slackness on very old, or cheap, monitors, or television sets with VGA inputs.
I do wonder how well EDID circuitry handles hot plugging, and whether it gets blown by people un/plugging while all the gear is running (monitors and computers).
On Sat, 02 Mar 2013 21:18:21 +1030 Tim ignored_mailbox@yahoo.com.au wrote:
Allegedly, on or about 02 March 2013, Marko Vojinovic sent:
or with a faulty VGA cable
Or, just so nobody is left in the lurch, an apparently not faulty brand new cable, that simply hasn't got any wiring between the two pins that carry the EDID signals. Some cheap cables only bother wire up the video, sync, and ground pins.
Yeah, that could be called "broken by design". :-)
And there are some monitors that don't bother to provide EDID, at all. Though, I only expect that slackness on very old, or cheap, monitors, or television sets with VGA inputs.
I do wonder how well EDID circuitry handles hot plugging, and whether it gets blown by people un/plugging while all the gear is running (monitors and computers).
I never ever ever (un)plug a VGA cable on a live system. Not even on laptops, where this is supposed to be safe. I had some very bad experiences with doing that --- burnt graphics cards, burnt monitors, burnt motherboards, etc. Since then I typically disconnect everything from the power outlet before mangling video cables.
Best, :-) Marko
On 03/01/2013 12:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set the resolution above 1024x768 at 60HZ and would like to set it higher.
Just for grins, have you tried without any conf file at all? I don't have one, and X auto-detects everything correctly and I get the right resolution.
On 03/02/2013 03:49 PM, Thomas Cameron wrote:
On 03/01/2013 12:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set the resolution above 1024x768 at 60HZ and would like to set it higher.
Just for grins, have you tried without any conf file at all? I don't have one, and X auto-detects everything correctly and I get the right resolution.
Yes, the resolution I get without adding anything to the original installation is 1024x768 while the manufacturer's spec is 1680x1050. As it stands the browser is easy to read but scrolls off the screen. If it was user selectable I would set it a little bit higher.
I have three monitors connected to three F-18 computers all of which work well except this monitor [ViewSonic VX2035WM] is not recognized and gets a generic driver, hence the reason for this exercise.
Bob
-
Bob Goodwin -
David -
Ed Greshko -
g -
Marko Vojinovic -
poma -
thomas cameron -
Tim