FS#67068 - [linux] i915 driver not working

Attached to Project: Arch Linux
Opened by Santiago Pastorino (spastorino) - Sunday, 21 June 2020, 19:34 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 14:10 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

After upgrading to kernel 5.7.4 (from 5.6.15-arch1-1) the graphics (i915) are not showing up on my system. Downgrading to 5.6.15-arch1-1 fixes the problem again.

I see the following in the logs ...

Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (==) Matched intel as autoconfigured driver 0
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (==) Matched modesetting as autoconfigured driver 1
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (==) Matched fbdev as autoconfigured driver 2
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (==) Matched vesa as autoconfigured driver 3
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (==) Assigned the driver to the xf86ConfigLayout
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) LoadModule: "intel"
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (WW) Warning, couldn't open module intel
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (EE) Failed to load module "intel" (module does not exist, 0)
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) LoadModule: "modesetting"
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) Module modesetting: vendor="X.Org Foundation"
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: compiled for 1.20.8, module version = 1.20.8
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: Module class: X.Org Video Driver
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: ABI class: X.Org Video Driver, version 24.1
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) LoadModule: "fbdev"
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (WW) Warning, couldn't open module fbdev
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (EE) Failed to load module "fbdev" (module does not exist, 0)
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) LoadModule: "vesa"
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (WW) Warning, couldn't open module vesa
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (EE) Failed to load module "vesa" (module does not exist, 0)
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (II) modeset(0): using drv /dev/dri/card0
Jun 14 14:44:33 galago /usr/lib/gdm-x-session[929]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
This task depends upon

Closed by  freswa (frederik)
Sunday, 13 September 2020, 14:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  This is not a packaging issue. Please report upstream. Thank you
Comment by loqs (loqs) - Sunday, 21 June 2020, 19:45 GMT
Please post the full output of dmesg and Xorg.0.log or the journal for one boot with the issue as attachment(s).
Comment by Santiago Pastorino (spastorino) - Sunday, 21 June 2020, 21:58 GMT
Attaching the dmesg and journalctl output but ... I've found something new. It seems like the boot process finishes and you still see the console but the gdm has already started. I see that pressing alt + -> to switch to next virtual terminal and then pressing alt + <- to go back you are able to see gdm login graphic interface.
Still seems like an issue to need to switch the virtual terminals to be able to see gdm.
   journalctl.log (175.3 KiB)
   dmesg.log (76.3 KiB)
Comment by loqs (loqs) - Sunday, 21 June 2020, 22:27 GMT
Some similarities to https://bbs.archlinux.org/viewtopic.php?id=256523
Comment by Constantine (Hi-Angel) - Wednesday, 24 June 2020, 09:57 GMT
Can you try manually regenerate initramfs after the new kernel is loaded, and then reboot? I had a problem just like you describe half a year ago, except with radeon driver and obviously older kernel. Back then switching to a tty and regenerating iniramfs fixed that for me.
Comment by Santiago Pastorino (spastorino) - Wednesday, 24 June 2020, 13:51 GMT
> Some similarities to https://bbs.archlinux.org/viewtopic.php?id=256523

Indeed it seems very similar if it's not the very same problem :).
Comment by Santiago Pastorino (spastorino) - Wednesday, 24 June 2020, 14:06 GMT
> Can you try manually regenerate initramfs after the new kernel is loaded, and then reboot? I had a problem just like you describe half a year ago, except with radeon driver and obviously older kernel. Back then switching to a tty and regenerating iniramfs fixed that for me.

Was going to do it but also saw a kernel update, so using 5.7.4 updated to 5.7.5 which regenerates initramfs running already 5.7 and I'm still having the same problem.
Comment by Rowisi (Rowisi) - Friday, 14 August 2020, 22:29 GMT
I had the same problem a month ago. I Solved it by setting early KMS for my i915

https://wiki.archlinux.org/index.php/Kernel_mode_setting#Early_KMS_start

don't forget to regenerate the initramfs.
Comment by Santiago Pastorino (spastorino) - Saturday, 15 August 2020, 12:46 GMT
Upgrading to 5.8.1 doesn't fix this neither. As @Rowisi suggested setting early KMS for i915 fixes the issue.
Anyway, I guess it would be nice if this is fixed somehow upstream.
Comment by loqs (loqs) - Saturday, 15 August 2020, 12:54 GMT
@spastorino see [1].

[1] https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs

Loading...