Low graphics mode

[canadianwriterman]

I'm having an issue with a clean install of 12.10 Ubuntu 64-bit. It's similar to other posts I've seen to do with GRUB and nvidia, but in my case it's happening with Intel HD4000 graphics. I get a window on bootup with "Low graphics mode." It happens about 90% of the time I boot. I have to keep rebooting until my graphics card is finally recognized. Any suggestions, folks?

[pesho21]

I have the same problem. My processor is i3 2125 with embedded intel hd3000 graphics.

[canadianwriterman]

Seems there are only the two of us, pesho21. There are many posts about xorg and the display manager having issues related to the nvidia video driver, but none about the Intel video driver in 12.10.

[pesho21]

This sounds badly for us. I tried to understand when the problem is occurred, but it seems that the problem is reproducing randomly. In my case it happens in 60-70% of boot times.

[pesho21]

I have reinstalled my 64 bit Ubuntu 12.10, but this doesn't help. Ubuntu 12.10 is the best Ubuntu I've ever seen, but this issue makes me crazy. If someone can help - I'll be very grateful.

[ronzo]

Same problem here. Intel HD4000 Graphics. Here's a snippet of the Xorg.log:

[     1.967] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 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, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
	Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
	Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
	Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
	Haswell Server (GT2+), Haswell SDV Desktop (GT1),
	Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
	Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
	Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
	Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
	Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
	Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
	Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
	Haswell ULT Server (GT1), Haswell ULT Server (GT2),
	Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
	Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
	Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
	Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
	Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
	ValleyView PO board
[     1.968] (II) VESA: driver for VESA chipsets: vesa
[     1.968] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     1.968] (II) FBDEV: driver for framebuffer: fbdev
[     1.968] (++) using VT number 7

[     1.968] (II) intel(0): using device path '/dev/dri/card0'
[     1.968] (WW) Falling back to old probe method for vesa
[     1.968] (WW) Falling back to old probe method for modesetting
[     2.031] (WW) Falling back to old probe method for fbdev
[     2.031] (II) Loading sub module "fbdevhw"
[     2.031] (II) LoadModule: "fbdevhw"
[     2.031] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     2.031] (II) Module fbdevhw: vendor="X.Org Foundation"
[     2.031] 	compiled for 1.13.0, module version = 0.0.2
[     2.031] 	ABI class: X.Org Video Driver, version 13.0
[     2.086] (EE) intel(0): [drm] Failed to open DRM device for pci:0000:00:02.0: No such file or directory
[     2.086] (EE) intel(0): Failed to become DRM master.
[     2.086] (II) UnloadModule: "intel"
[     2.086] (EE) Screen(s) found, but none have a usable configuration.
[     2.086] 
Fatal server error:
[     2.086] no screens found
[     2.086] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[     2.086] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     2.086] (EE) 
[     2.150] Server terminated with error (1). Closing log file.

[pesho21]

Here is the snippet from the Xorg.0.log.old. I found only this error:

[    14.072] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 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, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
	Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
	Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
	Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
	Haswell Server (GT2+), Haswell SDV Desktop (GT1),
	Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
	Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
	Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
	Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
	Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
	Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
	Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
	Haswell ULT Server (GT1), Haswell ULT Server (GT2),
	Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
	Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
	Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
	Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
	Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
	ValleyView PO board
[    14.072] (II) VESA: driver for VESA chipsets: vesa
[    14.072] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    14.072] (II) FBDEV: driver for framebuffer: fbdev
[    14.072] (++) using VT number 7

[    14.756] vesa: Ignoring device with a bound kernel driver
[    14.756] (WW) Falling back to old probe method for vesa
[    14.800] (WW) Falling back to old probe method for modesetting
[    14.800] (II) modesetting(2): using default device
[    14.800] (II) Loading sub module "fbdevhw"
[    14.800] (II) LoadModule: "fbdevhw"
[    14.800] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    14.800] (II) Module fbdevhw: vendor="X.Org Foundation"
[    14.800] 	compiled for 1.13.0, module version = 0.0.2
[    14.800] 	ABI class: X.Org Video Driver, version 13.0
[    14.800] (**) FBDEV(3): claimed PCI slot 0@0:2:0
[    14.800] (II) FBDEV(3): using default device
[    14.800] (EE) Screen 0 deleted because of no matching config section.
[    14.800] (II) UnloadModule: "vesa"
[    14.800] (EE) Screen 0 deleted because of no matching config section.
[    14.800] (II) UnloadModule: "modesetting"
[    14.800] 
Fatal server error:
[    14.800] Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[    14.800] 
[    14.800] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    14.800] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    14.800] (EE) 
[    14.807] Server terminated with error (1). Closing log file.

[Floaty]

Hello, I have the same problem. I did find a workaround however annoying.

I often end up with the "Your system is running in low-graphics mode"
Reboot does not help.
I found that if I, when the error occurs, reinstall lightdm then it's all ok for a while.
Like this:
I see the error and press ctrl+alt+F1 and login.
sudo su
service lightdm stop
aptitude reinstall lightdm
reboot
*** edit***
I just found a different method.
ctrl+alt+F1 and login
sudo service lightdm restart
***/edit***

Then things are ok for a while. How come it's necessary to do that?
Can it be fixed somehow?

Ubuntu 12.10 with Unity
Asus P8Z77-V pro/Thunderbolt
Intel Core i7 3770
Intel HD4000

[pesho21]

This works only for the first boot after reboot. After that the problem has appeared again.

[fjgaude]

I'm using Intel HD3000 and have the same issue on both 12.10 and 12.04, but only from partitions that are on SSDs.

ctrl+alt+F1 and login
sudo service lightdm restart

The above works for me when I get a black screen with the cursor blinking in the upper left-hand corner.

On an HDD with 12.04 and 11.10, installed early in the dev cycles I have no such issue. I even DDed the 12.04 to an SSD partition and the issue returned. So I think it is a 'race' problem with the speed of an SSD and lightdm loading. Just a guess, of course.

Anyone here have a permanent fix for this?