/qubes-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

R4.0-rc3 installer doesn't run on Macbook Pro 11,4 (Mid 2015 Retina) #3427

Open
andzaytsev opened this Issue Dec 24, 2017 · 6 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 4.0 updates
6 participants
@andzaytsev @matthazinski @ideologysec @eduncan911 @marmarek @andrewdavidwong
@andzaytsev

andzaytsev commented Dec 24, 2017 •
edited by andrewdavidwong
Edited 1 time
  • @andrewdavidwong andrewdavidwong edited Mar 1, 2018 (most recent)

Qubes OS version:

R4.0-rc3

Affected TemplateVMs:

N/A

Steps to reproduce the behavior:

I am trying to install the latest release of Qubes 4.0 (rc3) on my Macbook Pro Mid 2015 Retina (MacBook Pro 11,4) following the suggestions here (those are for 3.2, but I expected them to work on 4.0 as well).

First, I installed rEFInd 0.11.2 on my Mac using the Recovery mode. After that, I created a bootable Qubes USB-drive using Unetbootin and the latest iso from the website.

REFInd showed all the USB boot options correctly, so I chose EFI\BOOT\xen.efi from the USB-drive (I tried all the other options, but got the same result).

Expected behavior:

I expected an installer to appear to proceed with the installation of the OS.

Actual behavior:

Instead of the installer, I saw a lot of ACPI errors, following the prompt for the emergency console. It also said that /dev/root doesn't exist. I was able to copy the rdsosreport.txt (the boot log) onto my local partition and am attaching it here.

I believe the most relevant errors are the following:

[    0.000000] localhost kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/0 (20170531/tbfadt-603)


[    0.067254] localhost kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.067537] localhost kernel: ACPI Error: Needed type [Reference], found [Integer] ffff880464db0ca8 (20170531/exresop-103)
[    0.067537] localhost kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170531/dswexec-461)
[    0.067537] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20170531/psparse-550)`

[    0.229058] localhost kernel: pci 0000:00:01.0:   bridge window [mem 0xa0b00000-0xa0bfffff]
[    0.229068] localhost kernel: pci 0000:06:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
[    0.229069] localhost kernel: pci 0000:06:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.229070] localhost kernel: pci 0000:06:04.0: BAR 14: no space for [mem size 0x00200000]
[    0.229071] localhost kernel: pci 0000:06:04.0: BAR 14: failed to assign [mem size 0x00200000]


[    1.819719] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.819745] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU1._CST, AE_NOT_FOUND (20170531/psparse-550)
[    1.819843] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.819869] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU2._CST, AE_NOT_FOUND (20170531/psparse-550)
[    1.819947] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.819972] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU3._CST, AE_NOT_FOUND (20170531/psparse-550)
[    1.820098] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.820124] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU4._CST, AE_NOT_FOUND (20170531/psparse-550)
[    1.820228] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.820253] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU5._CST, AE_NOT_FOUND (20170531/psparse-550)
[    1.820339] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.820364] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU6._CST, AE_NOT_FOUND (20170531/psparse-550)
[    1.820463] localhost kernel: ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    1.820488] localhost kernel: ACPI Error: Method parse/execution failed \_PR.CPU7._CST, AE_NOT_FOUND (20170531/psparse-550)`

rdsosreport.txt

General notes:

It seems I have the exact same machine referenced in the Macbook Troubleshooting, so I'm wondering if this is a specific R4.0 issue. In addition, I believe other Linux distros can be installed on this machine, so this seems to be a Qubes-specific issue.

Related issues:

@andrewdavidwong andrewdavidwong added bug C: doc C: installer labels Dec 24, 2017

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Dec 24, 2017

@matthazinski

This comment has been minimized.

Show comment
Hide comment
@matthazinski

matthazinski Dec 27, 2017

I just installed 4.0-RC3 on a Macbook Pro 11,4 and didn't hit any major issues during the installer (although I did have issues post-install).

Lack of Unetbootin support is a known issue (#1415).

matthazinski commented Dec 27, 2017 •
edited
Edited 1 time
  • @matthazinski matthazinski edited Dec 27, 2017 (most recent)

I just installed 4.0-RC3 on a Macbook Pro 11,4 and didn't hit any major issues during the installer (although I did have issues post-install).

Lack of Unetbootin support is a known issue (#1415).
@andzaytsev

This comment has been minimized.

Show comment
Hide comment
@andzaytsev

andzaytsev Dec 27, 2017

Interesting! What tool did you use to write the ISO to a USB drive?

andzaytsev commented Dec 27, 2017

Interesting! What tool did you use to write the ISO to a USB drive?
@matthazinski

This comment has been minimized.

Show comment
Hide comment
@matthazinski

matthazinski Dec 27, 2017

I just used dd:

sudo dd if=Downloads/Qubes-R4.0-rc3-x86_64.iso of=/dev/rdisk2 bs=1m

matthazinski commented Dec 27, 2017

I just used dd:

sudo dd if=Downloads/Qubes-R4.0-rc3-x86_64.iso of=/dev/rdisk2 bs=1m
@ideologysec

This comment has been minimized.

Show comment
Hide comment
@ideologysec

ideologysec Dec 29, 2017

Etcher (https://etcher.io) should also work, but definitely use dd or some other block copying device (Unetbootin is...strange).

ideologysec commented Dec 29, 2017

Etcher (https://etcher.io) should also work, but definitely use dd or some other block copying device (Unetbootin is...strange).
@eduncan911

This comment has been minimized.

Show comment
Hide comment
@eduncan911

eduncan911 Feb 11, 2018

I've been trying to get Qubes installed on an MacBook Pro 11,3 15" Retina Nvidia 750M GPU for about a year myself.

Qubes' 4.0 rc4 installer actually works perfectly flashed to a USB3 stick. Used other dd and Etcher, and they both boot the installer just fine. I prefer Etcher as it validates when done and has caught some bad flashes.

Under macOS, if not using Etcher:

sudo dd if=~/Downloads/Qubes-R4.0-rc4-x86_64.iso of=/dev/rdisk2 bs=1M status=progress

(Note that I have the GNUTools utils loaded under brew and use only the GNU dd version, which supports newer options such as status=progress to get a progress report)

I can get Qubes installed on both the internal SSD and an external M.2 SSD I have in an USB3 enclosure.

However, my problem is that the Anaconda installer does not create the proper /EFI/Qubes/ entries, leaving them blank and empty. Instead, it always boots to the dreaded grub> prompt.

For a few days I've been struggling to figure out the properties Xen + Fedora + EFI configuration to get it to load without success. But not having a valid 4.0rc4 install anywhere means I can't create a rescue disk to even debug this.

The only way I've been able to debug this is to:

  • Install Qubes 4.0rc4 (either on SSD or external SSD)
  • Do not exit installer: instead of clicking Finish, press Fn+Ctrl+Alt-F2 to get to the prompt.
  • chroot /mnt/sysimage to get into the system and configure and test.
  • Reboot and home it works! Which, it never does yet... Very time consuming.

There is also issue #3505 from a couple of days ago that looks to have bypassed Grub completely for EFI and just boot EFI directly - which is exactly what I'm after!

eduncan911 commented Feb 11, 2018 •
edited
Edited 3 times
  • @eduncan911 eduncan911 edited Feb 11, 2018 (most recent)
  • @eduncan911 eduncan911 edited Feb 11, 2018
  • @eduncan911 eduncan911 edited Feb 11, 2018

I've been trying to get Qubes installed on an MacBook Pro 11,3 15" Retina Nvidia 750M GPU for about a year myself.

Qubes' 4.0 rc4 installer actually works perfectly flashed to a USB3 stick. Used other dd and Etcher, and they both boot the installer just fine. I prefer Etcher as it validates when done and has caught some bad flashes.

Under macOS, if not using Etcher:

sudo dd if=~/Downloads/Qubes-R4.0-rc4-x86_64.iso of=/dev/rdisk2 bs=1M status=progress

(Note that I have the GNUTools utils loaded under brew and use only the GNU dd version, which supports newer options such as status=progress to get a progress report)

I can get Qubes installed on both the internal SSD and an external M.2 SSD I have in an USB3 enclosure.

However, my problem is that the Anaconda installer does not create the proper /EFI/Qubes/ entries, leaving them blank and empty. Instead, it always boots to the dreaded grub> prompt.

For a few days I've been struggling to figure out the properties Xen + Fedora + EFI configuration to get it to load without success. But not having a valid 4.0rc4 install anywhere means I can't create a rescue disk to even debug this.

The only way I've been able to debug this is to:

  • Install Qubes 4.0rc4 (either on SSD or external SSD)
  • Do not exit installer: instead of clicking Finish, press Fn+Ctrl+Alt-F2 to get to the prompt.
  • chroot /mnt/sysimage to get into the system and configure and test.
  • Reboot and home it works! Which, it never does yet... Very time consuming.

There is also issue #3505 from a couple of days ago that looks to have bypassed Grub completely for EFI and just boot EFI directly - which is exactly what I'm after!
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2018

Member

Thanks to @eduncan911 this should be fixed by QubesOS/qubes-installer-qubes-os#20. @andzaytsev If you're brave enough, you can grab iso from https://openqa.qubes-os.org/tests/210/asset/iso/Qubes-DVD-x86_64-20180228.iso and try.
Member

marmarek commented Feb 28, 2018

Thanks to @eduncan911 this should be fixed by QubesOS/qubes-installer-qubes-os#20. @andzaytsev If you're brave enough, you can grab iso from https://openqa.qubes-os.org/tests/210/asset/iso/Qubes-DVD-x86_64-20180228.iso and try.

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0, Release 4.0 updates Mar 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment