See screenshot: http://www.more-solutions.co.uk/files/12032010325.JPG
I have tried two identical PCs in case the problem is system or video memory.
Initially I had the monitor through a KVM, which gave me a lower resolution but usable screen, although with square blocks on the screen where it wasn't updating properly. (I tried to open a terminal window and just got a white box which I could move around but could see nothing in the box.) It was when I bypassed the KVM and rebooted that it identified the screen and gave me a decent resolution login screen followed by the linked screenshot after login.
Chipset is Intel 82810E DC-133 (CGC) according to /var/log/messages
Suggestions? I'm hoping the screenshot will tell someone exactly what is wrong, but I can't google a screenshot and can't work out how to describe it in words!
Tbh that looks like a dogdy video driver, wrong res
Regards Ian Porter
www : www.codingfriends.com
On 12 Mar 2010, at 11:31, Mark Rogers mark@quarella.co.uk wrote:
See screenshot: http://www.more-solutions.co.uk/files/12032010325.JPG
I have tried two identical PCs in case the problem is system or video memory.
Initially I had the monitor through a KVM, which gave me a lower resolution but usable screen, although with square blocks on the screen where it wasn't updating properly. (I tried to open a terminal window and just got a white box which I could move around but could see nothing in the box.) It was when I bypassed the KVM and rebooted that it identified the screen and gave me a decent resolution login screen followed by the linked screenshot after login.
Chipset is Intel 82810E DC-133 (CGC) according to /var/log/messages
Suggestions? I'm hoping the screenshot will tell someone exactly what is wrong, but I can't google a screenshot and can't work out how to describe it in words!
-- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Fri, 12 Mar 2010 11:31:07 +0000 Mark Rogers mark@quarella.co.uk wrote:
See screenshot: http://www.more-solutions.co.uk/files/12032010325.JPG
I have tried two identical PCs in case the problem is system or video memory.
I had a similar issue with the Ubuntu installation CD - it would give an unusable display very similar to that. The work-around that enabled me to run the installer was to connect the same PC to the same monitor with a BNC cable (rather than HD15) thus preventing reading EDID data from the monitor and forcing "safe" settings.
Unfortunately I cannot remember which PC had the problem but I don't think I have any PCs with the Intel chipset you mention so the problem may be wider than that - for example choosing a video mode based on the monitor saying it supports it (or even prefers it) but the X driver for the chipset does not know how to program the various timers correctly.
If enabled X can cycle through possible video modes with, IIRC, Ctrl-Alt KP+ and KP- so it may be worth trying that to see if you get a stable display.
Alternatively if you can force the "safe" mode as I did (sounds like the KVM does not connect the data lines for EDID) you could experiment with forcing X to use a different mode by editing xorg.conf and I think there is something in the archive on this list for doing that with Ubuntu.
HTH, Steve.
On 12/03/10 14:29, Steve Fosdick wrote:
Alternatively if you can force the "safe" mode as I did (sounds like the KVM does not connect the data lines for EDID) you could experiment with forcing X to use a different mode by editing xorg.conf and I think there is something in the archive on this list for doing that with Ubuntu.
Note that the screenshot was when bypassing the KVM, but I agree that getting bad EDID sounds like the cause.
Where is xorg.cong in Ubuntu 9.10? There doesn't seem to be one in /etc/X11
On 12/03/10 17:13, Mark Rogers wrote:
Where is xorg.cong in Ubuntu 9.10? There doesn't seem to be one in /etc/X11
OK, Google answered that one; it's not there unless it's needed. I need to use xrandr, I believe, but I'm stuck at that point!
On 12 March 2010 17:18, Mark Rogers mark@quarella.co.uk wrote:
On 12/03/10 17:13, Mark Rogers wrote:
Where is xorg.cong in Ubuntu 9.10? There doesn't seem to be one in /etc/X11
OK, Google answered that one; it's not there unless it's needed. I need to use xrandr, I believe, but I'm stuck at that point!
Mark.
I haven't had this problem as I neither use Ubuntu 9.10 nor a KVM, however a similar one was asked as a Star Question in this month's Linux Format magazine, LXF130 April 2010. I've repeated the advice for you below, as it may be of use.
HTH,
Peter.
Screen Resolution
Q. I use three computers attached to a KVM switch (not the hypervisor), which works fine with Windows XP, and with Ubuntu 9.04 and earlier. However, I'm having a problem with Ubuntu 9.10 and Fedora 12. I tried Fedora 12 hoping the problem would be different. It seems that neither of these current distros can read the EDID block, so I'm not able to set the display resolution above 800x600. There is no xorg.conf file, so I had one generated with:
Xorg -configure :1
This was recommended in LXF117. I also tried using the Modeline instructions as described in that issue, but the X server wouldn't start until I removed Modeline. I have tried adding this to Section "Screen":
Subsection "Display" Modes "1280x800" EndSubSection
But this seems to be ignored. How can I get the X server to set display modes higher when it can't read EDID (through a KVM switch) and it seems to be ignoring settings in xorg.conf? Rob Solomon
A. X is ignoring your specified mode settings because it thinks that your monitor can't handle a resolution of more than 800x600. There's a quick and dirty solution to this, though: connect the monitor directly to the computer and see it reads the EDID information and sets up the display correctly. Then run:
sudo X -configure
This will write the existing configuration, working, configuration to /root/xorg.conf. Check that this works by logging out of X, logging in to a virtual console and running:
sudo X -config /root/xorg.conf
If this works, copy /root/xorg.conf to /etc/X11, and you have a working configuration that has all the information it needs in xorg.conf with no need to read the EDID information from the monitor itself.
Repeat this process for each of the computers, then reconnect them through the KVM.
-
Ian Porter -
Mark Rogers -
samwise -
Steve Fosdick