第一个迹象是,在启动gnome时,gnome是以安全模式启动的,我无法从gui菜单访问系统设置。
$ 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德梅斯
[ 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.来自/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我想上面的英特尔驱动程序对这个显卡来说是对的吗?如何阻止内置显卡挂起?
发布于 2013-01-21 22:08:23
发布于 2013-12-03 21:52:28
我见过这种由坏主板引起的问题。在我的例子中,当引导Fedora19时,一切都正常,直到系统开始为KDE呈现图形。然后,它挂着一条关于呈现环失败的错误消息,鼠标仍然工作,我可以进入文本模式,系统以前已经工作过,没有任何更改。
我的主板大约有10年历史,在用尽其他可能性之后,我仔细观察了一下板,发现许多电解电容器(带塑料袖子的铝罐)都失败了。这些电容器过滤尖峰,由逻辑开关,从电源线路,你通常可以松几个,从来没有注意到,但当足够多的故障时,尖峰变得足够大,以耦合回逻辑。因为逻辑在渲染时切换到了高速,这是你第一次看到效果的时候。
电容器失效是因为它们中的液体电解液慢慢蒸发,当它降到足够低时,电容器短路,加热剩余的电解液,直到它沸腾并破裂罐,然后短暂地以蒸汽射流的形式逸出。帽子通常会被烧开,这样电脑就能继续工作了。为了检查这个,检查盖子顶部有一个X印,X在那里是为了削弱罐,这样它就会破裂而不会发生灾难性的爆炸。如果盖以这种方式失效,顶部将是轻微的圆顶,而不是扁平,你可能会看到一个小洞,其中的蒸汽泄漏,可能有一点棕色或白色的残留物附近的孔。
这就提出了更换上限的问题。我在另一个棋盘上试过一次,结果还是没成功。你永远不能确定你得到了所有的,并做了这么多的解除焊接的结果是一个很高的可能性,损坏的董事会。
https://unix.stackexchange.com/questions/62074
复制相似问题