Bug #12039
Tail 2.9.1 no longer booting on 2011 (Early) MacBook Pro
0%
Description
While it earlier was not possible to setup a tails drive at all using that macbook, it then worked starting ~2.1 iirc. Updates where flakey and sometimes a manual update was necessary. But tails worked well until ~2.6.
Then I updated to 2.9.1 and ran into various issues:
1. 2.9.1 update could not be done using that mac (4GB ram). It worked using another mac w more ram.
2. 2.9.1 tails not booting on that macbook: I see the boot selection, then I select Live, see three dots, white dot goes from first to last dot, then the screen is black and nothing happens.
2.9.1 boots just fine on the second mac w more ram.
Hope this info is useful and maybe something can be done to make tails run on 4GB older macs.
Subtasks
Related issues
Related to Tails - |
Rejected | 2017-02-17 |
History
#1 Updated by intrigeri 2016-12-20 10:21:30
- Assignee set to steve
- QA Check set to Info Needed
> Then I updated to 2.9.1 and ran into various issues:
> 1. 2.9.1 update could not be done using that mac (4GB ram). It worked using another mac w more ram.
What exactly happened when attempting the update on the MAC with 4GB of RAM?
> 2. 2.9.1 tails not booting on that macbook: I see the boot selection, then I select
> Live, see three dots, white dot goes from first to last dot, then the screen is black
> and nothing happens.
Please try “failsafe” (sic) mode.
How was the USB stick installed initially?
#2 Updated by steve 2016-12-25 11:00:08
hi intrigeri,
intrigeri wrote:
> > Then I updated to 2.9.1 and ran into various issues:
>
> > 1. 2.9.1 update could not be done using that mac (4GB ram). It worked using another mac w more ram.
>
> What exactly happened when attempting the update on the MAC with 4GB of RAM?
Sorry I am not 100% sure anymore. As mentioned I was on 2.6 and tried the auto-update process. I was able to download the update file, but installation never started. I saw an error message, but was unable to re-initiate the auto-update (found no UI option to do so). Then tried rebooting into tails, but booting no longer worked. tails started, I selected “live” and then saw three dots (first white, other two red, white dot moves), I briefly see a page of text, the last row being: “Started Update UTMP (?) …” and then just a black screen that stays on forever.
next attempt: boot into Live (failsafe):
Loading /live/vmlinuzZ… ok
Loading /live/initrd2.img …ok
then nothing
interestingly when booting tails from that stick on a mac with more ram, it offered me the 2.9.1 update. so it seems the update from 2.6 to 2.7 indeed happened. and from then on I am now unable to boot into tials on the macbook 2011 early 4gb ram. evereything works fine on the second mac.
>
> > 2. 2.9.1 tails not booting on that macbook: I see the boot selection, then I select
> > Live, see three dots, white dot goes from first to last dot, then the screen is black
> > and nothing happens.
>
> Please try “failsafe” (sic) mode.
>
> How was the USB stick installed initially?
via the firefox add-on download option.
hope some of this info is useful.
#3 Updated by intrigeri 2017-03-20 14:39:42
Please try:
- Tails 2.11
- Tails 3.0~beta3
- adding
edd=off
to the options in the boot menu
#4 Updated by intrigeri 2017-03-20 14:40:18
- related to
Bug #12244: Booting intermediary Tails on MBP9,2 might requires editing boot menu commanddline added
#5 Updated by Anonymous 2017-06-27 15:18:10
ping steve
Can you try again using the latest Tails (3.0)? And then add
edd=off@ to the options in the boot menu
Please report back.
#6 Updated by steve 2017-06-28 11:41:41
u wrote:
> ping steve
> Can you try again using the latest Tails (3.0)? And then add
edd=off@ to the options in the boot menu
> Please report back.
Hi u,
MacBookPro8,2, 2011 early boots without problems and without editing options. Consider this solved. Thanks for the great update. Can you add the specific mac to the wiki page of supported devices please?
#7 Updated by intrigeri 2017-06-28 17:10:42
- Status changed from New to Resolved
- Assignee deleted (
steve) - QA Check deleted (
Info Needed)
steve wrote:
> MacBookPro8,2, 2011 early boots without problems and without editing options. Consider this solved.
Thanks, closing.
> Can you add the specific mac to the wiki page of supported devices please?
I’m not aware of any such page. Please clarify if I’m confused :)
#8 Updated by steve 2017-06-29 08:38:39
intrigeri wrote:
> steve wrote:
> > MacBookPro8,2, 2011 early boots without problems and without editing options. Consider this solved.
>
> Thanks, closing.
>
> > Can you add the specific mac to the wiki page of supported devices please?
>
> I’m not aware of any such page. Please clarify if I’m confused :)
See this link: https://tails.boum.org/support/known_issues/index.en.html#index17h2
Unsure if that is still correct “MacBook Pro (early 2011) fails to boot from DVD since Tails 1.1.” but who uses DVD anyways. Maybe remove that info.
And the following is now incorrect “MacBook Pro 8,2 (late 2011) fail to boot from a USB stick created by Tails Installer.” 8,2 is early 2011 btw. But I’d assume late and early both work as expected with Tails 3.0 usb stick.
Not sure how to best maintain such infos. Also they need to be re-evaluated for new releases. Maybe the remaining issues are no longer valid as well. Now you just have a list which is frightening and confusing users.
It would be important to add a date for such info to then know when it was added. if that was 5 years ago, I’d say, remove that info and wait for new reports to come in.
#9 Updated by intrigeri 2017-06-29 15:40:33
steve wrote:
> And the following is now incorrect “MacBook Pro 8,2 (late 2011) fail to boot from a USB stick created by Tails Installer.” 8,2 is early 2011 btw. But I’d assume late and early both work as expected with Tails 3.0 usb stick.
OK, will remove it. Thanks!
> Not sure how to best maintain such infos. Also they need to be re-evaluated for new releases. Maybe the remaining issues are no longer valid as well. Now you just have a list which is frightening and confusing users.
Indeed. The best we can do might be to rely on user reports such as yours :)
> It would be important to add a date for such info to then know when it was added. if that was 5 years ago, I’d say, remove that info and wait for new reports to come in.
This seems like a good idea! I’ll ensure newly documented known issues have a Tails version annotation.