Rhythmdvl - as an aside, how do you have that monitor hooked up to the machine? Is it through a KVM switch or is it connected directly to the PC? It is weird that a newer Dell monitor like that is not passing back it’s EDID info. Some older KVM switches and cables do not have have all the pins needed for 2-way communication between monitor and PC.
My setup is very confusing. The back of the monitor has a bajillion ports. At first I thought I’d have no use for them. Ha!
I actually have four machines connected to my desk at the moment. My primary work machine is an XP box running to the DVI. I also have a Mac mini (useful for manipulating Quark or InDesign files in their native layout format) going to the second DVI. I’m in the middle of two builds, rebuilding my main machine (the new one that’s taking over is on the HDMI port) and then there’s the Linux machine, connecting directly to the VGA port. It’s been our long-used file and Web-test server, but I’m migrating us to a Synology NAS that does the same thing but with (ostensibly) less input/learning curve from me. The Linbox is going through a fresh rebuild with new drives.
Anyway, everything is run directly to the monitor and I use its input selector to switch between displays. This is all made possible by this awesome little USB 4-port switch box that lets me use the same USB keyboard and mouse for all machines.
I’ve booted with the switch connected to the Linux machine, so I don’t think the lack of permanent monitor-to-computer USB connection could be the root of this, but am far from sure.
So close Part Deux
So I changed the file to:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Dell"
ModelName "2408 WFP"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "intel"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
EndSection
I got the same “out of synch” blank screen, hit the manual reset switch, flashed again, saw the warning for a moment and eventually up popped the desktop again – without the native resolution showing up.
Couple side notes:
Sorry, didn’t mean that my setup was confusing to describe/follow, I meant that it was confusion in a “what the hell computer am I working on at the moment” sort of way.
Another side note for others with no clue: the right alt+print screen+K combination works by holding down the right alt key and the print screen key then hitting k. It took a couple tries a while ago to figure out that it wasn’t a workssometimes combo.
ETA a question: Could the 10’ length of VGA cable make a difference in information reporting?
You say “without the native resolution showing up”, so do you now have 1920x1080 as an option?
Oops, no. The closest I have is the 1680 x 1050 wide screen option. There are a couple options with slightly higher resolutions but in 4:3 proportion.
OK, can you post your Xorg.0.log again and we can check why it won’t go higher.
Another idea is if you could temporarily hook it up via DVI and see if it gets EDID. You could then use that info (which will be in Xorg.0.log) and put it in xorg.conf.
Since it’s onboard graphics, the only out I have is for VGA. I’m not even sure I have a VGA-DVI adaptor (I know I have several DVI-VGA adaptors) around to test with.
What part of the Xorg.0.log file is relevant? I believe I’d have to post it in four or five chunks given the Board’s limits. Here is some of what seems relevant:
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server x86_64 Ubuntu
Current Operating System: Linux GotBack 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-server root=UUID=e3ee6afd-35e4-4886-9fa1-50e636f3aea3 ro quiet splash
Build Date: 26 October 2009 05:19:56PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 8 16:15:15 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0xb40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0:0:2:0) 8086:29c2:1043:82b0 Intel Corporation 82G33/G31 Express Integrated Graphics Controller rev 16, Mem @ 0xfe980000/524288, 0xe0000000/268435456, 0xfe800000/1048576, I/O @ 0x0000cc00/8
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX**
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX**
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX**
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX**
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX**
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX**
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 2.9.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX**
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX**
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX**
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX**
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX**
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX**
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) intel(0): Creating default Display subsection in Screen section
"Screen0" for depth/fbbpp 24/32
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) G33
(--) intel(0): Chipset: "G33"
(II) intel(0): Output VGA1 using monitor section Monitor0
(II) intel(0): EDID for output VGA1
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1360x768" (monitor doesn't support reduced blanking)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1680x1050" (monitor doesn't support reduced blanking)
(II) intel(0): Not using default mode "1680x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1080" (monitor doesn't support reduced blanking)
(II) intel(0): Not using default mode "1920x1200" (monitor doesn't support reduced blanking)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Printing probed modes for output VGA1
(II) intel(0): Modeline "1792x1344"x60.0 204.80 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.7 kHz)
(II) intel(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz)
(II) intel(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) intel(0): Modeline "1680x1050"x74.9 187.00 1680 1800 1976 2272 1050 1053 1059 1099 -hsync +vsync (82.3 kHz)
(II) intel(0): Modeline "1680x1050"x69.9 174.00 1680 1800 1976 2272 1050 1053 1059 1096 -hsync +vsync (76.6 kHz)
(II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
(II) intel(0): Modeline "1600x1024"x60.2 103.12 1600 1600 1656 1664 1024 1024 1029 1030 +hsync +vsync (62.0 kHz)
(II) intel(0): Modeline "1400x1050"x74.8 155.80 1400 1464 1784 1912 1050 1052 1064 1090 +hsync +vsync (81.5 kHz)
(II) intel(0): Modeline "1400x1050"x70.0 145.06 1400 1496 1648 1896 1050 1051 1054 1093 -hsync +vsync (76.5 kHz)
(II) intel(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz)
(II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
(II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
(II) intel(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz)
(II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) intel(0): Modeline "1152x864"x75.0 104.99 1152 1224 1352 1552 864 865 868 902 -hsync +vsync (67.6 kHz)
(II) intel(0): Modeline "1152x864"x70.0 96.77 1152 1224 1344 1536 864 865 868 900 -hsync +vsync (63.0 kHz)
(II) intel(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 -hsync +vsync (53.7 kHz)
(II) intel(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
(II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Output VGA1 connected
(II) intel(0): Using fuzzy aspect match for initial modes
(II) intel(0): Output VGA1 using initial mode 1792x1344
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (96, 96)
Monitor doesn’t support reduced blanking? Full blank ahead!
ETA: it looks like reduced blanking is only relevant to CRTs…
Add this line to your xorg.conf monitor section:
Option “ReducedBlanking”
Even if you get this working, it is a good idea to file an Ubuntu bug report with relevant information about your problem and your current solutions, and hopefully it will be fixed for everybody in a future update.
Blanking is the “dead time” between horizontal rows being displayed that gave the old CRT monitors time to reset the electron beam from the right side of the screen back to the left to start displaying the next row. Since X has no EDID from your monitor it doesn’t know you have an LCD rather than CRT so it uses the safe “normal” blanking that is CRT compatible. Option “reduced blanking” tells X that it’s OK to shorten the time between rows and that’s the only way to get high resolutions within the horizontal refresh rate we specified.
Awwww…
No such luck. Still getting the monitor warning during reboot (I tried restarting again to see if it was an artifact of alt-prntscr-k), and still not getting the right/native resolution. I tried it with Option “ReducedBlanking” and Option “Reduced Blanking” (with/without the space) in Section “monitor.” Could it be as simple as needing a tab between Option and Reduced…?
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Dell"
ModelName "2408 WFP"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
Option "Reduced Blanking"
EndSection
Section "Device"
Identifier "Device0"
Driver "intel"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
EndSection
The crazy thing is that these should both be mainstream products. Dell monitors are prevelant, and I typically build with Asus boards because of their widespread use. For this project I’d even focused on finding a board with high numbers of reviews at NewEgg. Of course, the integrated Intel chipset is common as well – which is why I’m baffled that I’m only halfway there, and getting more and more convinced that it’s some bit of stupidity on my part (installation, cable, etc.).
I think I’m going to try putting in direct values for synch/refresh.
It should be one word “ReducedBlanking”. What does Xorg.0.log say? Do a grep for it (grep ReducedBlanking /var/log/Xorg.0.log). That will tell us if the graphics driver accepts the option or not.
Nope. Taking values from the chart on Dell’s page that Henrichek linked to got me locked into just one mode: 1600 x 1200 4:3. This is both with and without a space in “Reduced Blanking,” It’s as if it rounded the 74.5 up to 75 per the chart. There was the benefit that I no longer get the monitor warning/blank screen.
Section "Monitor"
Identifier "Monitor0"
VendorName "Dell"
ModelName "2408WFP"
HorizSync 74.5
VertRefresh 60.0
Option "DPMS"
Option "Reduced Blanking"
EndSection
What about BIOS settings … could I have left a stone unturned there?
I will say that this resolution, while not optimal, is MUCH better than the earlier 800 x 600.
It might perhaps be possible to force the right timings with a modeline. Try adding for example:
ModeLine "1920x1200_60hz" 154.0 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync
to your monitor section. Maybe zwede is more skilled with modelines.
Y’know…I’m pretty sure I maintain an Ubuntu 8.04 box with two Dell 2408 monitors (dual display) at work. (That is, I’m pretty sure they’re 2408 monitors.) No problems with the resolution (1900x1200 on each), although I’m using the proprietary nVidia driver.
I’m at home…I just tried sshing in, but the machine is already turned off for the weekend. And unfortunately, I won’t be there again until Monday to look at the configuration files. If you still need it and I remember to do so, I’ll post the conf settings then.
Feel free to PM me with a reminder…
Yeah, I find that very odd myself. I’ve used analog VGA cables in the past and EDID came in just fine. Do you have another cable to try? Maybe this one is not connecting all the pins?
Even my Samsung DLP TV (not monitor) which I have connected to a HTPC via VGA reported proper EDID and “just worked” in Linux.
!!!wooooohooooo!!!
ETA: again, in case anyone finds this thread because of a similar problem, here’s the wiki article on modelines. The numbers make much more sense after reading it.
Unless there’s something off in the the background, Display Preferences is showing 1920x1200 (16:10) and a 60 Hz refresh rate – just what it’s supposed to do!
I’m not quite sure what my next step should be.
I should probably put the synch/refresh rates back to the ranges earlier suggested, but then again, if it’s not broke…
Over the weekend or so I’ll try and dig out another VGA cable and see if EDID is read. Is enough user error accounted for to file a bug report? I do think I’m going to track down the previous attempts at fixing this on other boards and post there too, just to help out someone else looking for a solution.
In the meantime, it seems as if this is the end of the video saga (unless there si somewhere else to check besides visually and in Display Preferences). Thanks an awful lot for all the help and patience in this thread! This is so much better on my eyes and quite the relief!
THANKS!!!
Great news!
I do wonder if there’s really much of a point in filing a bug report. What can the X-server do when the monitor does not respond to the EDID request? I think the only reasonable thing to do is to use safe defaults which is exactly what it did.
Excellent!
zwede:
Well, the xserver-xorg package used to let you do some manual configuration (by dpkg-reconfigure), including choosing resolutions and sync frequencies. That could be combined with some UI to handle situations such as this. I think they had something like it before (displayconfig-gtk), but I don’t know what happened with it. Oddly enough my monitor doesn’t respond to manual EDID requests, though everything gets set up correctly anyway. Though that could have something to do with the proprietary nvidia driver I use, since it seems to manage to get the information it needs, but gives get-edid nothing.
I guess it’s the software developer in me, I just get defensive when I hear the words “bug report” for something I’d consider a feature request. What you’re saying makes sense, it would be nice to offer some kind of recovery in case EDID is unavailable. Maybe a Gnome/KDE app that automatically gets launched in case the Xorg.0.log contains info that EDID was not available and offers to force higher resolutions.