Tails

#6 Updated by mercedes508 2019-02-11 12:34:09

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.

#7 Updated by intrigeri 2019-03-10 08:18:47

mercedes508, emmapeel , @goupille: we have less than one week left to apply any fix in time for 3.13. What’s the status here? Is there any chance we get reports from these users? It’s been a month so perhaps it’s worth pinging them, in case you did not do it yet?

(I see you’ve added this to the “Hot topics on our help desk” which made me remember I was waiting for input here :)

#8 Updated by goupille 2019-03-10 12:05:17

I asked the users affected if they would be able to get the logs, with no answers yet. one user with a Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) repoted that :

- in normal mode, after the greeter, the Tails desktop appears transiently for a few seconds then the screen goes black.

- “nomodeset”, “nomodeset xorg-driver=vesa”, “xorg-driver=intel”, “xorg-driver=modesetting”, or the Troubleshooting mode are giving the “Error starting GDM” screen

#9 Updated by mercedes508 2019-03-11 17:40:16

I’m pinging right now the few users who didn’t answer already.

#10 Updated by intrigeri 2019-03-11 18:12:47

> I’m pinging right now the few users who didn’t answer already.

Thanks :)

#12 Updated by intrigeri 2019-03-12 14:10:28

> * Intel UHD 620 [8086:5917] rev07

goupille, mercedes508: I’m wondering if there’s some confusion here. According to the report I’ve seen from one user of this hardware, the Greeter appears just fine and they don’t see “Error starting GDM” (as long as they don’t break stuff by adding boot options to debug the problem); instead, the Greeter appears but the screen goes black after login, once the desktop has been briefly displayed.

So could you please check which one(s), on the list of affected GPUs in the ticket description, are actually instances of the regression this ticket is about, and which ones are about the different issue that this user is facing?

#14 Updated by goupille 2019-03-12 14:21:02

the only user who gave a substancial description of their problem (ans answered back) is the one with the Intel UHD 620 [8086:5917] rev07 (same user I forwareded you the email). I assumed that it was an expression of this issue since this exact model is listed above.

#17 Updated by intrigeri 2019-03-14 12:18:33

goupille, mercedes508, @emmapeel, please point users affected by one of the two bugs this ticket is about to: https://lists.autistici.org/message/20190314.121121.001cf4cb.en.html

#19 Updated by fedionso 2019-03-30 06:52:27

Hi guys I’m getting this error on 3.13.1 and want to try the latest 3.14 drop from
https://nightly.tails.boum.org/build_Tails_ISO_stable/lastSuccessful/archive/build-artifacts/

Problem: the key used to sign the tails-build-artifacts.shasum (0xD83A438B2F916605) is not listed anywhere on https://tails.boum.org/doc/about/openpgp_keys/index.en.html

I found the following key details at https://pgp.surfnet.nl/pks/lookup?search=0xD83A438B2F916605&fingerprint=on&op=index

pub 4096R/2F916605 2013-09-23 jenkins.tails.boum.org artifact signing key
Fingerprint=AA65 3423 DBE1 0866 0B18 3B17 D83A 438B 2F91 6605

Is this the correct key?

#20 Updated by intrigeri 2019-04-03 09:30:16

> Is this the correct key?

The one I have is “AA65 3423 DBE1 0866 0B18 3B17 D83A 438B 2F91 6605”.
Still, note that these are experimental, unsupported images. Only use them for testing.

#21 Updated by mercedes508 2019-05-21 17:09:23

CAFoG=RrV0LSPOF33kJT4=GDfT96kpcoMy7QkGaq-+fHKoyE4GQ@mail.gmail.com
Intel Corporation HD Graphics 630 [8086:591b] (rev 04)

#23 Updated by mercedes508 2019-05-25 10:48:48

CABXq-uYHJ42NjXDCVvqPP6tjLf7_og9hMPQnijyPgS8EYBeEFw@mail.gmail.com
Intel Corporation HD Graphics 630 [8086:591b] (rev 04)

#26 Updated by mercedes508 2019-05-26 20:21:20

CALqX=LBRW8r-VfThaeZLqsDizVTH-KVwpm2a6BipgbZCHo7CUQ@mail.gmail.com
Intel Corporation HD Graphics 630 [8086:591b] (rev 04)

#27 Updated by goupille 2019-05-29 13:33:23

CAE7oKbr4j+PDCxj7QbxDitrBVUkEywb2BdxH4QryxCTDT1iBrw@mail.gmail.com

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

I already forwarded the outputs of journalctl

#29 Updated by intrigeri 2019-06-01 09:33:02

It would be sweet to know which workaround (https://tails.boum.org/support/known_issues/graphics/#intel) was tested on which hardware and what the results are. In particular, I’d love to see the Journal for xorg-driver=modesetting on one of the affected cards.

#31 Updated by mercedes508 2019-06-04 11:20:31

intrigeri wrote:
> It would be sweet to know which workaround (https://tails.boum.org/support/known_issues/graphics/#intel) was tested on which hardware and what the results are. In particular, I’d love to see the Journal for xorg-driver=modesetting on one of the affected cards.

I forwarded you the reports, will you ask the journal or shall I? Just to avoid duplicate demands.

#33 Updated by intrigeri 2019-06-07 10:33:05

> will you ask the journal or shall I? Just to avoid duplicate demands.

Please gather this info and reassign once you’ve made it available to me. Thanks! :)

#35 Updated by mercedes508 2019-06-10 12:26:12

intrigeri wrote:
> @mercedes508, see above.

OK, just asked, let’s wait for answers now.

#36 Updated by goupille 2019-06-15 19:44:41

Message-ID: <c9b9fa06-e5ce-98ed-0503-941b954f7d46@

#37 Updated by dngray 2019-07-01 17:24:49

I’m not sure if this is the right bug, if someone could please advise what to do I will do the research. Hopefully this can be fixed before 3.15 as Tails no longer works for me at all and I cannot stay with vulnerable versions 3.14.0, 3.14.1.

• I have a Dell XPS 13" 9370 (i7-8550U) with a Kaby Lake processor.
• I have found that 3.14.2 will not boot for me, whereas 3.14.0 did.
• I can create an intermediary usb stick with both ie: dd if=tails-amd64-3.14.2.img of=/dev/device and it will work with both versions.

However when booting 3.14.2 after I have used the Tails installer to clone the current 3.14.2 install from the intermediary usb stick I get:

(initramfs) aufs not available

If I boot from the troubleshooting mode I get:

Error starting GDM with your graphics card: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07). Please take note of this error and visit https://tails.boum.org/gdm for troubleshooting.

I tried the Intel startup options however they did not allow the system to boot.

#39 Updated by dngray 2019-07-03 16:59:32

1. (initramfs) aufs not available

I’m not quite sure what was causing this. I was able to reproduce it with two USB sticks yesterday, but not today.

Today I booted my machine in BIOS mode and the problem didn’t occur, so then I tried UEFI mode with secure boot disabled, no issue. Also no issue with secure boot enabled (as long as I signed BOOTX64.EFI, BOOTIA32.EFI and vmlinuz, ie (sudo sbsign --key db.key --cert db.crt --output {{file to sign}} {{file to sign}}, not doing the signing causes a different very explicit error on my machine anyway.

1. Error starting GDM with your graphics card: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07). Please take note of this error and visit https://tails.boum.org/gdm for troubleshooting. This was being caused because I was not deleting nomodesetting from the kernel options when booting troubleshooting mode.. Oops.
2. The issue in #38 seemed to go away as soon as I chose xorg-driver=intel or xorg-driver=modesetting. I can only reproduce it when I don’t set either of those options. Both give me 300fps, though I think the intel driver is smoother than the modesetting one.

#40 Updated by dngray 2019-07-07 04:44:36

It would seem (initramfs) aufs not available is caused by unclean dismounts.

I solved this by formatting the Tails partition (that’s the unencrypted FAT32 partition with the boot, hidden, legacy_boot, esp flags. Ie mkfs.vfat -F32 /dev/disk and then running the Tails installer again.

Sorry to mess up your bug with this unrelated information.

#42 Updated by emmapeel 2019-08-19 15:08:08

intrigeri wrote:
> > * Intel UHD 620 [8086:5917] rev07
>
> goupille, mercedes508: I’m wondering if there’s some confusion here. According to the report I’ve seen from one user of this hardware, the Greeter appears just fine and they don’t see “Error starting GDM” (as long as they don’t break stuff by adding boot options to debug the problem); instead, the Greeter appears but the screen goes black after login, once the desktop has been briefly displayed.

ey there! ill forward you now a report from a user with this card, UHD Graphics 620 [8086:5917]

The user could not start Tails after trying several options:

- xorg-driver=intel
- nomodeset
- nomodeset xorg-driver=vesa
- xorg-driver=modesetting

#49 Updated by numbat 2019-11-11 10:29:10

User reports - Skylake cpu with Intel graphics HD 515 graphics controller crashes during boot.
Bug report: 8cf624e98e0e8214abfbbf52f1fb30eb / no email so I can’t ask for more details.

#50 Updated by intrigeri 2019-11-11 10:58:50

> User reports - Skylake cpu with Intel graphics HD 515 graphics controller crashes during boot.
> Bug report: 8cf624e98e0e8214abfbbf52f1fb30eb / no email so I can’t ask for more details.

I’ve taken a look and (of course) the WhisperBack report was sent from another machine, with an AMD GPU, so not much we can do about it :/
There’s no indication that it’s a regression, and it’s Skylake, so I’ll assume it’s a different problem than what this ticket is about.