Karmic starts in low graphics mode

[Indian Art]

I updated my Laptop & Desktop PC to Karmic. Both these systems are using integrated Intel X3100 for graphics. However, my Desktop system is running Ubuntu in low-graphics mode. My Laptop (Acer 5920) works fine.
The message I get is “(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found”
I am writing this complaint on this Desktop PC which is running on a low resolution of 800 * 600. Even 'Systems > Preferences > Display only has 800 * 600 as the highest resolution. (The only other resolution is 640 * 480).
This problem was not there in Hardy Heron, although this problem would occasionally occur with Jaunty. I use a 15 foot VGA cable extension for my wall mounted Samsung SyncMaster 920 NW Monitor. (I have dual booted & XP graphics works fine, so I think it is unlikely to be a hardware issue)
I read somewhere in Launchpad the files required for reporting bugs like this, given by Mr. Bryce Harrington. I am attaching it herewith.
1) Release of Ubuntu = Ubuntu 9.10
2) The version of the package you are using, via 'apt-cache policy packagename'
p-desktop:~$ apt-cache policy packagename
W: Unable to locate package packagename
3) What you expected to happen
Expected to function on a higher resolution like before.
4) What happened instead
A low resolution of 800 * 600 on my 19 inch monitor.

ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sp 1851 F.... pulseaudio
 /dev/snd/controlC0: sp 1851 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x903a0000 irq 22'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,80860001,00100001'
   Controls : 38
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'Camera'/'V Micro. Corp. PC Camera at usb-0000:00:1a.0-2, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB0ac8:0302'
   Controls : 3
   Simple ctrls : 2
CheckboxSubmission: c4cd85dd135cab1f8dbc468c93307249
CheckboxSystem: fc73f07fcd9845bb95fa3ca6b8be7ef2
Date: Mon Dec 14 12:08:30 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=dbfc1592-1f8e-4085-87c4-5ca4956e7697
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Package: linux-image-2.6.31-16-generic 2.6.31-16.53
ProcCmdLine: root=UUID=e7683e24-bb69-4c5d-9bb4-9695cca5d6f2 ro quiet usernamelash
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-16-generic N/A
 linux-firmware 1.25
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-16-generic i686
WpaSupplicantLog:

dmi.bios.date: 05/02/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0216.2007.0502.1916
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33BU
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD79951-405
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0216.2007.0502.1916:bd05/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-405:cvn:ct2:cvr:

[Indian Art (goldfish-aol)]

I could not attach the logs in the last message, so here it is.

[Indian Art (goldfish-aol)]

Hi,

I now got a new message when I started my computer after a 'shut down'. The message was:

"Ubuntu is running in Low Graphics mode. The following error was encountered. You may need to update your configuration to solve this.
(EE) Failed to load module "i810" (module does not exist, 0)
(EE) open/dev/fb0 No such file or directory
(EE) intel (0): No modes
(EE) Screen(s) found, but none have a usable configuration."

I have the log file on my computer and can attach it to this bug report if required.

Incidentally, the 'Visual effects' can no longer function on 'Extra' and are on 'None'.

[Indian Art (goldfish-aol)]

Hi,

I checked my 15 feet extension cable by tightening the contact points like I did several times before. However, when I removed the cable I found that the VGA contact point was loose. Tightening it did not help. However, I do believe there could still be a loose contact.

However, following the following instructions solved my problem:

HOWTO: Wrong/Low Resolution and flicker
The Xorg server - the code that provides a graphic display - is very good about determining what an attached monitor can do. There are limitations.

This HOWTO explains one process for obtaining a rock-solid graphics screen within the constraints of your hardware's abilities. There are many other ways to do this.

Overview of the problem:
When Xorg starts, it tries to figure out what kind of monitor you have via DDC/CI and EDID protocols. If your monitor and cabling are first-rate, you will never need to care about any of this. (Yay!)

If not, Xorg will pick a "safe" VESA resolution and use that: probably not at all what you expected, and not likely to be satisfactory. (Grr.)

Lucky for us all, Xorg is highly configurable and it's very easy to get the exact resolution(s) that you want, deserve, and yes, paid-for with your invested time.
Warning: If you are terrified by a Linux command line, at least TRY to follow this procedure. It won't hurt you and it will help.

Still with me? Then let's proceed:

Step #1: What kind of monitor do you have? What are its capabilities? What is its maximum resolution?
Virtually every monitor vendor will publish the specifications for their products on the web. You can find them if you just look but first, you'll need the Vendor Name and Model of that monitor. It will be printed on a plate or tag, glued, screwed, or riveted to the back, top, bottom, or side of your monitor. Go look for it now. Write that information down and keep it handy.
Step #2: Fetch your specs.
Bring up a browser window and search for that model eg, 'dell 3007wfphc'.

Look for any site with details and specifications; the vendor's site is best, but most review sites will provide specifications too.

Ideally, you will find the "Horizontal Sync" range, expressed in kilohertz (KHz or khz), and the "Vertical Refresh" range, expressed in hertz (Hz).

If you found that, write it down like:
Code:
HorizSync 49.31 - 98.71
VertRefresh 60
and proceed to Step #4.

If not, then look for the "Maximum Resolution". This will be listed as something like "2560 x 1600 at 60Hz". Write that down.
Step #3: Calculate the frequencies from the specified resolution.
Open a terminal window (Applications -> Accessories -> Terminal) and enter
Code:
cvt 2560 1600 60
Hit Enter. This will output the following
Code:
# 2560x1600 59.99 Hz (CVT 4.10MA) hsync: 99.46 kHz; pclk: 348.50 MHz
Modeline "2560x1600_60.00" 348.50 2560 2760 3032 3504 1600 1603 1609 1658 -hsync +vsync
Aha! The vertical refresh will be exactly 59.99Hz and the horizontal sync will be 99.46KHz. Write it down as:

Code:
HorizSync 99.46
VertRefresh 59.99
Step #4: Create a basic xorg.conf
Write the following commands down on paper because we're going to turn off the GUI and run a few commands from the console.

Flip to the text ...

[Indian Art (goldfish-aol)]

Thanks everyone especially Giblet5 from Ubuntu Forums!

I have now closed the bug.

[Eliah Kagan (degeneracypressure)]

This problem was fixed on your computer, but not due to any change made to any software in Ubuntu. Therefore, this bug should be closed as Invalid rather than as Fix Released.

Thank you for your report, and please do not hesitate to continue reporting bugs as you find them! However, you might want to ask questions instead, if you are not sure something really is a bug (https://answers.launchpad.net/ubuntu).