The first sign of this was that on startup gnome started up in safe mode and I can't access system settings from the gui menu.
$ uname -a
Linux mymachine 3.7.2-204.fc18.i686.PAE #1 SMP Wed Jan 16 16:31:26 UTC 2013 i686 i686 i386 GNU/Linux
dmesg
[ 54.190910] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[ 54.280239] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts
[ 973.080049] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 973.085561] i915: render error detected, EIR: 0x00000010
[ 973.085572] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[ 973.085587] i915: render error detected, EIR: 0x00000010
[ 1027.080050] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 1027.084135] i915: render error detected, EIR: 0x00000010
[ 1027.084149] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[ 1027.084162] i915: render error detected, EIR: 0x00000010
[ 1030.084053] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 1030.084241] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
[ 1030.084246] [drm:i915_reset] *ERROR* Failed to reset chip.
[ 3049.196863] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
from /var/log/Xorg.0.log
[ 28.112] (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
[ 28.122] (II) VESA: driver for VESA chipsets: vesa
I assume the intel driver above is the right one for this graphics card? How do I stop the built-in graphics card from hanging?
