Xorg broken after update (Solved)

Issues related to applications and software problems
Post Reply
monzer4819
Posts: 3
Joined: 2014/07/21 15:43:51

Xorg broken after update (Solved)

Post by monzer4819 » 2015/06/24 23:42:41

So after a long stretch I did a yum update on my graphical workstation.

First thing to happen was a kernel panic. I remember a while back that I was playing around with the Intel i915 power settings, and had set these kernel parameters:
i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1.

Removing them fixed the kernel panic, but I was booted into text mode.

This is an excerpt from my Xorg.0.log

Code: Select all

[   246.973] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[   246.973] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[   246.973] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[   246.973] (++) using VT number 1

[   249.022] intel: waited 2020 ms for i915.ko driver to load
[   249.061] (EE) No devices detected.
[   249.061] (EE) 
Fatal server error:
[   249.061] (EE) no screens found(EE) 
[   249.061] (EE) 

lsmod seems ok:

Code: Select all

lsmod |grep i915
i915                  929459  1 
i2c_algo_bit           13413  1 i915
drm_kms_helper         98226  1 i915
drm                   311588  3 i915,drm_kms_helper
i2c_core               40325  5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
video                  19263  2 i915,asus_wmi
Any ideas?
Last edited by monzer4819 on 2015/06/29 21:19:26, edited 1 time in total.

monzer4819
Posts: 3
Joined: 2014/07/21 15:43:51

Re: Xorg broken after update (Solved)

Post by monzer4819 » 2015/06/29 21:19:00

Managed to solve it.

First I noticed my Xorg.0.log wasn't being updated after multiple reboots. So I checked what systemd was up to, and after running "systemctl list-jobs" I saw that it was stuck on running intial-setup ??? Somehow initial-setup (text-mode) was also triggered after my update. Strange I couldn't see it on the console, all I saw was the usual systemd startup messages that hung after successfully starting fprint daemon.

So yum remove initial-setup and boom back to graphical login.

Post Reply