Intel snippet in config causes X crash

bigbenaugust · 2019-09-19 12:47:52

I have Lithium on my workstation (Lenovo P50), and X mysteriously quit working after a reboot yesterday. This was showing up in the logs, which was a little confusing:

[1812253.549] (II) intel: Driver for Intel(R) HD Graphics
[1812253.549] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[1812253.549] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[1812253.549] (EE) No devices detected.
[1812253.549] (EE) 
Fatal server error:
[1812253.549] (EE) no screens found(EE) 
[1812253.549] (EE)

I had to remove /etc/X11/xorg.conf.d/20-intel.conf, which was provided by the bunsen-configs package:

baugust@hatchibombotar:/var/log$ sudo dpkg -S /etc/X11/xorg.conf.d/20-intel.conf
[sudo] password for baugust: 
bunsen-configs: /etc/X11/xorg.conf.d/20-intel.conf

Reinstalling the package doesn't put the file back, so I can't retest that.
Might have something to do with my machine using the Nouveau driver, though. smile

System info:

baugust@hatchibombotar:~$ inxi -F
System:    Host: hatchibombotar Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Awesome 4.3 
           Distro: BunsenLabs GNU/Linux 10.0 (Lithium) 
Machine:   Type: Laptop System: LENOVO product: 20EQS07U00 v: ThinkPad P50 serial: <root required> 
           Mobo: LENOVO model: 20EQS07U00 v: SDK0J40709 WIN serial: <root required> UEFI [Legacy]: LENOVO 
           v: N1EET57W (1.30 ) date: 08/03/2016 
Battery:   ID-1: BAT0 charge: 84.3 Wh condition: 84.3/90.0 Wh (94%) 
CPU:       Topology: Quad Core model: Intel Core i7-6820HQ bits: 64 type: MT MCP L2 cache: 8192 KiB 
           Speed: 800 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 
           7: 800 8: 800 
Graphics:  Device-1: NVIDIA GM107GLM [Quadro M1000M] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz, 1920x1200~60Hz 
           OpenGL: renderer: NV117 v: 4.3 Mesa 18.3.6 
Audio:     Device-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel 
           Device-2: NVIDIA driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
           IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: 50:7b:9d:f6:96:b9 
           Device-2: Intel Wireless 8260 driver: iwlwifi 
           IF: wlp4s0 state: up mac: 44:85:00:c0:89:e7 
Drives:    Local Storage: total: 238.47 GiB used: 78.68 GiB (33.0%) 
           ID-1: /dev/sda vendor: Samsung model: MZNLN256HCHP-000L7 size: 238.47 GiB 
Partition: ID-1: / size: 222.65 GiB used: 78.55 GiB (35.3%) fs: xfs dev: /dev/dm-1 
           ID-2: /boot size: 235.3 MiB used: 134.9 MiB (57.3%) fs: ext2 dev: /dev/sda1 
           ID-3: swap-1 size: 15.46 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 
Sensors:   System Temperatures: cpu: 51.5 C mobo: N/A gpu: nouveau temp: 47 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 216 Uptime: 16m Memory: 15.14 GiB used: 1.75 GiB (11.5%) Shell: bash inxi: 3.0.36

I fixed my issue, so no big deal, I'm just leaving this here for science.

DeepDayze · 2019-09-19 14:12:56

@Bigbenaugust, does your machine have both Intel and nvidia graphics? Try disabling the intel one

bigbenaugust · 2019-09-19 15:21:48

lspci -vvv says I only have one VGA Compatible Controller and it is the NVIDIA one:

01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: Lenovo GM107GLM [Quadro M1000M]

It has an Intel chipset, that is for sure, but not graphics that I can tell.

DeepDayze · 2019-09-19 15:23:58

bigbenaugust wrote:

lspci -vvv says I only have one VGA Compatible Controller and it is the NVIDIA one:
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: Lenovo GM107GLM [Quadro M1000M]
It has an Intel chipset, that is for sure, but not graphics that I can tell.

Ahh, perhaps there was something weird that made X server think you had an intel GPU in there, thus it failing. So good you got it all working again smile

bigbenaugust · 2019-09-19 19:11:50

DeepDayze wrote:

Ahh, perhaps there was something weird that made X server think you had an intel GPU in there, thus it failing. So good you got it all working again

Yeah, came back from afternoon meeting, restarted my box and... nothin'! Oh well, my spare machine running MX was all ready to go while I troubleshot this one. smile

hhh · 2019-09-20 02:50:04

We've already decided to remove the intel conf for just this reason, it can mess up a system that doen't need that fix.

It works for me on my ten-plus year old Inspiron, so I suggested it and, since there is also an Arch Wiki entry for it, it was accepted by the devs. User and Dev feedback has proved that this was a BAD MOVE, and should only be implemented by the User if needed and if it works for them.

That file has been removed in the latest Git, many apologies for the inconvenience.

dolly · 2019-09-20 08:03:28

Thanks for the quick fix guys. smile

DeepDayze · 2019-09-20 16:16:47

hhh wrote:

We've already decided to remove the intel conf for just this reason, it can mess up a system that doen't need that fix.
It works for me on my ten-plus year old Inspiron, so I suggested it and, since there is also an Arch Wiki entry for it, it was accepted by the devs. User and Dev feedback has proved that this was a BAD MOVE, and should only be implemented by the User if needed and if it works for them.
That file has been removed in the latest Git, many apologies for the inconvenience.

Maybe script it so that this intel fix is ONLY installed on systems that have an Intel GPU.

hhh · 2019-09-20 20:31:03

DeepDayze wrote:

Maybe script it so that this intel fix is ONLY installed on systems that have an Intel GPU.

That's a great idea, but will have to wait for a later date unless a forum member comes up with a script. I'm useless in that department, @twoion has enough on his plate with website administration, forum admin and maintaining the repository, I wouldn't want to distract @malm from the rapid jgmenu development that's been happening and @johnraff is doing so much heavy lifting to get lithium off the ground (ha!) ATM that... just, no.

Future development? +100.

johnraff · 2019-09-21 02:24:42

Re: the intel X crash thing - this appeared on my QEMU VM Lithium install just after the Debian Buster 10.1 upgrade, so it might be that something changed in X's handling of those config snippets? My host machine has an Intel CPU but I don't know how qemu would present that to the VM. Anyway, the BL file is a tweak intended to improve performance, so safer to leave it out for now and go with vanilla settings.

/etc/X11/xorg.conf.d/20-intel.conf will be removed with the next bunsen-configs upgrade (soon probably) but anyone else who hits the issue, please remove that file. And thanks to bigbenaugust for spotting and bringing it up! It's great to have users keeping an eye on the evolution of Lithium, and reporting stuff like this.

bigbenaugust · 2019-09-21 02:52:35

DeepDayze wrote:

Maybe script it so that this intel fix is ONLY installed on systems that have an Intel GPU.

I was trying to think through this, and I don't have enough machines to test on, but you could theoretically do some logic on an lsmod or lspci perhaps to detect the existence of the right Intel hardware. Who knows, I might actually concoct something.

For the record, my Dell Latitude E7240 at home took that file just fine and still has it, I only needed to add back in the line for preventing the display-sleeping-and-never-waking-up behavior:

Section "Device"
  Identifier  "Intel Graphics"
  Driver      "intel"
    Option "AccelMethod"      "sna"
    Option "TearFree"         "true"
    Option "DRI"	"2"
EndSection

hhh · 2019-09-23 00:18:49

^ Cool. Per-user setup is the way we'll proceed, I think. It's a big help that we have intel users on the forums to suggest the manual fix possibilities.

hhh · 2019-09-23 00:23:42

bigbenaugust wrote:

... I only needed to add back in the line for preventing the display-sleeping-and-never-waking-up behavior:
Section "Device"
  Identifier  "Intel Graphics"
  Driver      "intel"
    Option "AccelMethod"      "sna"
    Option "TearFree"         "true"
    [b]Option "DRI"	"2"[/b]
EndSection

The line I added a bold tag to, I presume.

What is your xfce4-power-manager-settings>Display config (a scrot would be easiest)?

bigbenaugust · 2019-09-23 15:45:15

I'll get you a nice pic tonight.
The Dell in question has a Haswell chipset and graphics.

bigbenaugust · 2019-09-26 02:35:52

Here it is. I played with the defaults some, but changing the X config was the only way to get it to stop doing the thing. That came from the Arch wiki: https://wiki.archlinux.org/index.php/In … RI3_issues

https://scrot.moe/image/x7IT3

For the record, this happens with other modern distros, as I had it happen on Fedora 30 also (but not Stretch/Helium or *buntu 18.04). I'll check my Lenovo W530 in the office and see what chipset it has, since I think it did this too.

#1 2019-09-19 12:47:52

Intel snippet in config causes X crash

#2 2019-09-19 14:12:56

Re: Intel snippet in config causes X crash

#3 2019-09-19 15:21:48

Re: Intel snippet in config causes X crash

#4 2019-09-19 15:23:58

Re: Intel snippet in config causes X crash

#5 2019-09-19 19:11:50

Re: Intel snippet in config causes X crash

#6 2019-09-20 02:50:04

Re: Intel snippet in config causes X crash

#7 2019-09-20 08:03:28

Re: Intel snippet in config causes X crash

#8 2019-09-20 16:16:47

Re: Intel snippet in config causes X crash

#9 2019-09-20 20:31:03

Re: Intel snippet in config causes X crash

#10 2019-09-21 02:24:42

Re: Intel snippet in config causes X crash

#11 2019-09-21 02:52:35

Re: Intel snippet in config causes X crash

#12 2019-09-23 00:18:49

Re: Intel snippet in config causes X crash

#13 2019-09-23 00:23:42

Re: Intel snippet in config causes X crash

#14 2019-09-23 15:45:15

Re: Intel snippet in config causes X crash

#15 2019-09-26 02:35:52

Re: Intel snippet in config causes X crash

Board footer