Bug #12482

Stuck on 'Start job waiting...' using Radeon driver with 3.0-betax

Added by Gelgamek 2017-04-26 15:51:38 . Updated 2020-04-28 15:10:47 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2017-04-26
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The tails 3.0 betas won’t start on one of my machines unless I disable the Radeon modeset driver. When starting Tails normally the greeter loads, but I get stuck with a ‘Start job waiting’ message when AppArmor loads (it usually gets stuck waiting for TOR to bootstrap). Trying to start Tails in Troubleshooting Mode results in a flashing screen and a system lock when it attempts to load GNOME during boot.

The GPU does have known issues as it’s a Cedar (AMD 5450) but Tails 2.x runs without issue.

It’s possibly related to Bug Bug #11095.

Subtasks

Related issues

Related to Tails - Bug #11095: GNOME session fails to start with some AMD/ATI radeon GPU Resolved 2016-02-09
Related to Tails - Bug #17379: black screen after the greeter with AMD Radeon HD 7520G Resolved

History

#1 Updated by Gelgamek 2017-04-26 16:19:57

The two different messages it can display when getting stuck are:

‘Start job is running for hold until boot process finishes up’
‘Start job is running for wait for tor to be bootstrapped’

Having looked at the issue getting into troubleshooting mode, I found it works if I set the `nomodeset` flag to just disable the radeon driver rather than all of them. I have a weird setup in that I have an Nvidia, AMD and Intel GPU all in this same machine so the flashing screen and lock I get trying to use Troubleshooting Mode may be partially related to another driver.

#2 Updated by intrigeri 2017-04-29 10:56:33

  • related to Bug #11095: GNOME session fails to start with some AMD/ATI radeon GPU added

#3 Updated by intrigeri 2017-04-29 10:59:22

  • Category set to Hardware support
  • Assignee set to Gelgamek
  • QA Check set to Info Needed
  • Type of work changed from Graphics to Research

> When starting Tails normally the greeter loads, but I get stuck with a ‘Start job waiting’ message when AppArmor loads (it usually gets stuck waiting for TOR to bootstrap).

I don’t understand what happens exactly in this case: what happens once you log into the session from Tails Greeter?

Also, is radeon.modeset=0 to fix the problem?

#5 Updated by intrigeri 2017-05-25 07:57:02

  • Status changed from New to Confirmed

We got a similar bug report about “Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] (rev 83)” with PCI ID 1002:6660. Waiting for more test results.

#6 Updated by Anonymous 2018-08-17 09:21:42

Gelgamek: did the above instructions help? Do you still experience this problem with a more recent Tails? DId you try the same with a Debian Stretch live?

#7 Updated by intrigeri 2019-03-08 14:51:12

  • Status changed from Confirmed to Rejected
  • Assignee deleted (Gelgamek)
  • QA Check deleted (Info Needed)

Not actionable without the requested info.

#8 Updated by goupille 2019-10-22 08:36:55

I think Bug report: c7fbbeff3d5a140be981fad5ddc1c3d0 is another occurence of that bug with tails-4.0rc1, unfortunately the user didn’t left any contact info…

#9 Updated by intrigeri 2019-12-28 15:22:59

  • related to Bug #17379: black screen after the greeter with AMD Radeon HD 7520G added

#10 Updated by GreedyMagpie 2020-04-28 13:35:57

Recently I made a stick with Tails. (AMD64 4.2.2)
It was supposed to be used with a thinkpad E135, which uses a Radeon HD 7340 (1002:9808)

I configured everything, including persistent storage etc.
Then i tested it with the E135 and it worked fine.

FFW 2 Month or so, I finally got time to start my planed project.
I boot up the machine: There’s an update for Tails!

So, for my own security I instantly installed the new update.

Now, Tails seems to Freeze immediately in the first screen (where you do language setup and decrypt ps)
When I reboot in TS Mode, it says GDM couldn’t start because of problems with my GPU.
That Message linked to https://tails.boum.org/support/known_issues/graphics/#index1h2

I tried both kernel params, separately not together, nothing changed.
Now I’m here and desperate for help, especially noticing that this bug here might not even be related to me, since with 4.2.2 everything worked fine.

Can anyone give me a hint to where to start looking for more info?
In TS Mode i can open a TTY, but I don’t know how to login, since I can’t setup a root PW.
When I boot normally it seems like a complete freeze. No reaction to ANY input, except force halt.

I tried booting TS Mode with disabled bootsplash, which showed that systemd seems to have an error when starting the “Load Kernel Modules” job.
Very likely thats related, but without a login i can’t get the exact error logs.

And buying a different machine is not an option. Rather I’d use an older version of Tail or take a look into other alternatives.

#11 Updated by GreedyMagpie 2020-04-28 15:10:47

Forget my post for now.
My GPU isn’t listed as affected, it works with a fresh 4.5 install.
I propbably fu the update, I’ll try manually updating that stick and will see if that will make it work again.
Otherwise I also found the troubleshooting info in the guides mentioning some trick that might help if it won’t help.
I try to figure this out on my own.