Project

General

Profile

Bug #16447

Regression on some Intel GPU (Braswell, Kaby Lake)

Added by mercedes508 12 days ago. Updated 9 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
02/08/2019
Due date:
% Done:

0%

QA Check:
Info Needed
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

Well, since Tails 3.12, many users have been complaining that they get the "Error starting GDM" issue, and finally I got answers confirming that there hardware were working fine with Tails 3.11, so that's a regression.

Here is the list of affected GPU that were working fine with 3.11:

  • Intel Corporation Atom/Celeron/Pentium Precessor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) - (2 reports)
  • Intel UHD 620 [8086:5917] rev07
  • Intel Corporation 82915G/GV/940GL: integrated Graphics controller [8086:2582] (rev 04)

Here is the list of potential regression (not sure about 3.11 behavior):

  • Integrated Graphics Controller [8086:0a16] (rev0b)
  • Intel Corporation HD Graphics 630 [8086:591b] (rev 04) - (2 reports)

And from the few users who answered back, none of the following workaround works:

https://tails.boum.org/support/known_issues/graphics/#index3h2


Related issues

Related to Tails - Bug #16224: Black screen after the boot menu with Intel GPU (i915) Resolved 12/13/2018

Associated revisions

Revision 5baca24d (diff)
Added by intrigeri 11 days ago

Document another possible workaround (refs: #16447).

For cards listed in /usr/share/live/config/xserver-xorg/intel.ids,
that is, by default we would force the "intel" X.Org driver,
when things break it might be worth trying to revert to the defaults,
i.e. the "modesetting" X.Org driver.

History

#1 Updated by mercedes508 12 days ago

  • Related to Bug #16224: Black screen after the boot menu with Intel GPU (i915) added

#2 Updated by mercedes508 12 days ago

  • Description updated (diff)

#3 Updated by intrigeri 11 days ago

  • Status changed from Confirmed to In Progress

#4 Updated by intrigeri 11 days ago

  • Assignee changed from intrigeri to mercedes508
  • QA Check set to Info Needed

Hi,

Here is the list of affected GPU that were working fine with 3.11:

  • Intel Corporation Atom/Celeron/Pentium Precessor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) - (2 reports)
  • Intel UHD 620 [8086:5917] rev07

Here is the list of potential regression (not sure about 3.11 behavior):

  • Integrated Graphics Controller [8086:0a16] (rev0b)
  • Intel Corporation 82915G/GV/940GL:tegrated Graphics controller [8086:2582] (rev 04)
  • Intel Corporation HD Graphics 630 [8086:591b] (rev 04) - (2 reports)

Thanks a lot for the comprehensive report. This is excellent aggregated data i.e. exactly

All of those, except 8086:0a16 (unclear if that one is a regression at this point), are listed in /usr/share/live/config/xserver-xorg/intel.ids; that is, we force the intel X.Org driver for them. It would be worth testing how they behave with the default driver (modesetting), so I've added this workaround to https://tails.boum.org/support/known_issues/graphics/#intel ⇒ please try affected users to test with xorg-driver=modesetting.

Also, I see that Linux 4.19.16 has a fix for some gen7 GPU issue, so please ask the affected users to try a build from the devel branch (better wait for today's build, which should land there in ca. 1h, as previous builds were using outdated APT snapshots). This could be relevant in particular for the UHD 620 and HD Graphics 630. I need at least the results without any workaround (bonus points if there are results with the 5 documented workarounds too).

Finally, it would be sweet if one of these users was technical enough to add rootpw=sillypassword, switch to a text console, log is as root with "sillypassword", extract the output of journalctl, and send it to me, so I have more info than "X.Org won't start" :) But forget it if they need guidance to do that.

Thanks in advance!

FTR here are the corresponding Intel generations:

  • recent hardware:
    • Braswell (2017-2018): x5-E8000/J3xxx/N3xxx
    • 7th gen Kaby Lake (2017): UHD 620, HD Graphics 630
  • 10+ years old: 82915G/GV/940GL (could be Pentium 4, Celeron D, from 2004, or Core/Core 2 mobile from 2006)

I could not spot any related recent bug filed against xserver-xorg-video-intel. But we did not update it so the problem could be tracked elsewhere, e.g. Mesa, libglvnd, or Linux.

#5 Updated by intrigeri 11 days ago

  • Subject changed from Regression on some Intel GPU to Regression on some Intel GPU (Braswell, Kaby Lake)

#6 Updated by mercedes508 9 days ago

For Intel Corporation Atom/Celeron/Pentium Precessor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35)

Neither "xorg-driver=modesetting" nor using Tails from devel branch works.

Also available in: Atom PDF