Bug #9224

Document that video is broken with double-video-card Mac hardware

Added by BitingBird 2015-04-10 20:23:27 . Updated 2015-08-12 10:10:49 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2015-04-10
Due date:
% Done:

80%

Feature Branch:
doc/9224-Mac_double_video
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The problem was reported in Bug #7505. This should be added in the known issues.

The possible workaround should be documented too.


Subtasks


Related issues

Related to Tails - Bug #7505: Video is broken with switchable graphics Rejected 2014-07-06

History

#1 Updated by BitingBird 2015-04-10 20:23:36

  • related to Bug #7505: Video is broken with switchable graphics added

#2 Updated by BitingBird 2015-04-10 20:24:14

  • Description updated

#3 Updated by BitingBird 2015-04-10 20:24:45

  • Assignee set to BitingBird
  • Target version set to Tails_1.4.1

#4 Updated by intrigeri 2015-04-11 09:42:20

> The problem was reported in Bug #7505. This should be added in the known issues.

IMO one should first check if Tails/Jessie is affected.

#5 Updated by BitingBird 2015-05-09 22:04:26

Noted that in Bug #7505, where it’s relevant. I don’t see how it could block documenting the problem.

#6 Updated by BitingBird 2015-05-09 22:09:00

  • Status changed from Confirmed to In Progress
  • Feature Branch set to bitingbird:doc/9224-Mac_double_video

#7 Updated by BitingBird 2015-05-09 22:56:22

  • Assignee changed from BitingBird to sajolida
  • % Done changed from 0 to 30
  • QA Check set to Ready for QA

Added a new section for those computers. Please review :)

#8 Updated by sajolida 2015-05-22 17:47:21

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Dev Needed
  • Feature Branch changed from bitingbird:doc/9224-Mac_double_video to doc/9224-Mac_double_video

I was very happy with this one :)

I pushed a bunch of minor changes, but the essential is here and well presented.

There is still a mejor issue that I didn’t fix. You are not explaining in which file should be written the code snippet. I suspect this is meant for /etc/X11/xorg.conf but I think you should try to do apply the workaround and explain better:

  • Where this has to be written.
  • When to do that, I suspect once the Greeter has appeared and then on every boot.
  • How. I suspect changing to a terminal with Ctrl+Alt+F1. Maybe we can pretend that we won’t take people by the hand too much on this one, and that mentioning the need to switch to a terminal is enough.
  • How to change the root password. I suspect that setting a new one in the Greeter might be enough but that needs to be verified.

I understand that this requires quite a bit of geeking but I think that’s all stuff that you have the skills to do. Otherwise, assign it to me and I’ll do it.

Bonus point if you verify whether this could be made part of a dotfile in persistence (I suspect it would work).

#9 Updated by BitingBird 2015-05-22 19:23:43

  • Assignee changed from BitingBird to alant
  • QA Check changed from Dev Needed to Info Needed

I took both workarounds from Bug #7505. Alan documented this one, but intri said it was not easy to apply for users, informations in it have to be adapted, and the root password gives security risks. I ended up documenting it briefly and warning about the root password, but I hesitated removing the workaround completely - I didn’t because there is no other for non-Mac users.

Alan didn’t mention where to write that or such, intri said it’s for advanced users anyways.

I don’t really feel like I can do the research needed, but maybe we can just ask alan for the missing information? Since he did it, he probably has all those answers :)

#10 Updated by alant 2015-06-15 10:42:17

  • Assignee changed from alant to BitingBird
  • QA Check changed from Info Needed to Dev Needed

sajolida wrote:
> I was very happy with this one :)
>
> I pushed a bunch of minor changes, but the essential is here and well presented.
>
> There is still a mejor issue that I didn’t fix. You are not explaining in which file should be written the code snippet. I suspect this is meant for /etc/X11/xorg.conf but I think you should try to do apply the workaround and explain better:
>
> * Where this has to be written.

in /etc/X11/xorg.conf.d/$SOMETHING.conf

> * When to do that, I suspect once the Greeter has appeared and then on every boot.

The greeter doesn’t appear as X doesn’t start. So one shoul do that when nothing else happens.

> * How. I suspect changing to a terminal with Ctrl+Alt+F1.

> Maybe we can pretend that we won’t take people by the hand too much on this one, and that mentioning the need to switch to a terminal is enough.

Yes. Anyway I don’t think this is a viable workaround fo non-geek users.

> * How to change the root password. I suspect that setting a new one in the Greeter might be enough but that needs to be verified.

That’s not enough, as the admin password in the greeter as a sudoer password for the amnesia user. One has to unset the root password with the passwd command as root.
>
> I understand that this requires quite a bit of geeking but I think that’s all stuff that you have the skills to do. Otherwise, assign it to me and I’ll do it.
>
The whole point of documenting this horrible workaround that must be redone at every boot let me doubtful, but I’m not the one doing user support.

However, if we actually want to better support these apple hardware, adding script that applies this workaound automatically may be easier. I could imagine working on that provided I have access to an affected hardware the time needed for the developpment. One can however argue that this work must be done in X or debian (perhaps trying unstable on such hardware would be a good start).

> Bonus point if you verify whether this could be made part of a dotfile in persistence (I suspect it would work).

It wouldn’t work as the file must be in /etc/ as X starts as root and before any user session.

#11 Updated by BitingBird 2015-07-01 04:02:19

  • Target version changed from Tails_1.4.1 to Tails_1.5

#12 Updated by BitingBird 2015-07-06 08:35:22

  • Assignee changed from BitingBird to sajolida
  • % Done changed from 30 to 50
  • QA Check changed from Dev Needed to Ready for QA

So, I added the path where to add the file, I think we’ll let power users deal with the rest :)

Please review!

#13 Updated by sajolida 2015-08-04 04:58:32

  • Target version deleted (Tails_1.5)

#14 Updated by BitingBird 2015-08-04 05:17:53

  • Target version set to Tails_1.6

#15 Updated by sajolida 2015-08-09 12:02:54

  • Assignee changed from sajolida to BitingBird

All-right, I see how documenting this is problematic. This is the case where not documenting things might have been the proper solution (acknowledging it as too complicated and too unpractical to be worth it). But since we were almost there already I polished a bit the work of BitingBird with 0139597..975b038 and this that now it’s ready for merge.

By the way BitingBird, I think that you forgot to push your commit with fixed the path of the file, so I did that again (that was a minor change). Tell me if I missed anything else important.

So please review and tell me if I can merge.

#16 Updated by BitingBird 2015-08-10 05:30:40

  • Assignee changed from BitingBird to sajolida
  • % Done changed from 50 to 80
  • QA Check changed from Ready for QA to Pass

Review passes, please merge :)

#17 Updated by intrigeri 2015-08-11 01:26:55

Saying “Once the computer is started” feels weird to express “once the GNOME session has started”, given this section is for “Expert Linux users”. (For average users I know and understand why we simplify things this way, but for experts I suspect it will just confuse them. No big deal though, and probably we’ve already put way enough energy into this problem.)

#18 Updated by sajolida 2015-08-11 04:30:08

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

Applied in changeset commit:01320197ef400087481ce982df4bbc30d7a990d2.

#19 Updated by sajolida 2015-08-11 04:34:06

  • Assignee deleted (sajolida)
  • % Done changed from 100 to 80
  • QA Check deleted (Pass)

Merged, and fixed intrigeri’s concern with f087b0c.

#20 Updated by intrigeri 2015-08-11 06:17:55

Thanks!

I have another small concern: it’s not obvious that the passwd command must be run with root privs, and if it’s run as the amnesia user then the root password will remain public knowledge.

#21 Updated by sajolida 2015-08-12 10:10:49

Damn! Fixed again in 8bde9a9 :)