mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
Merge branch 'PROTechThor-macbook-troubleshooting'
This commit is contained in:
Andrew David Wong
commit
f4b5da2d42
241
external/troubleshooting/macbook-troubleshooting.md
vendored
Normal file
241
external/troubleshooting/macbook-troubleshooting.md
vendored
Normal file
@ -0,0 +1,241 @@
|
|||||||
|
---
|
||||||
|
layout: doc
|
||||||
|
title: Apple MacBook Troubleshooting
|
||||||
|
permalink: /doc/macbook-troubleshooting/
|
||||||
|
---
|
||||||
|
|
||||||
|
# Apple MacBook Troubleshooting
|
||||||
|
|
||||||
|
## System freezes after attaching Broadcom BCM43602 Wi-Fi card
|
||||||
|
|
||||||
|
You may experience system freezes or crashes after attaching a Broadcom Wi-Fi adapter to the sys-net VM. This issue has been reported to exist on both Qubes 3.2 and 4.0.
|
||||||
|
|
||||||
|
### Qubes 3.2
|
||||||
|
|
||||||
|
To fix this issue on Qubes 3.2:
|
||||||
|
|
||||||
|
1. During VM setup, force a reboot and press `OPTION` key.
|
||||||
|
|
||||||
|
2. You will reach the grub shell
|
||||||
|
~~~
|
||||||
|
configfile /EFI/qubes/grub.cfg
|
||||||
|
~~~
|
||||||
|
|
||||||
|
3. Press Fn+F10 to boot without XEN support.
|
||||||
|
|
||||||
|
4. Once booted, press Fn+CTRL+ALT+F4 to open a shell.
|
||||||
|
|
||||||
|
5. Log into the system
|
||||||
|
~~~
|
||||||
|
sudo su -
|
||||||
|
systemctl disable qubes-netvm
|
||||||
|
~~~
|
||||||
|
|
||||||
|
6. Press Fn+F2 and complete the setup.
|
||||||
|
7. Reboot Qubes.
|
||||||
|
8. DO NOT launch the sys-net qube.
|
||||||
|
Rather, open its setting and remove the Wi-Fi adapter from the Selected devices using the Qubes Manager.
|
||||||
|
You can also remove it from the command line, if you know the BDF of the adapter.
|
||||||
|
You can see the list of devices attached to sys-net and their associated BDFs by running:
|
||||||
|
~~~
|
||||||
|
qvm-pci -l sys-net
|
||||||
|
~~~
|
||||||
|
For a device with a BDF of `04:00.0`, you can remove it with:
|
||||||
|
~~~
|
||||||
|
qvm-pci -d sys-net 04:00.0
|
||||||
|
~~~
|
||||||
|
9. In a dom0 terminal, run:
|
||||||
|
~~~
|
||||||
|
sudo su -
|
||||||
|
xl pci-assignable-list
|
||||||
|
echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive
|
||||||
|
qvm-start sys-net
|
||||||
|
xl pci-attach sys-net DEVICE_BDF
|
||||||
|
~~~
|
||||||
|
Be sure to replace "DEVICE_BDF" with the actual BDF of the Wi-Fi adapter.
|
||||||
|
|
||||||
|
After following the above steps, you should be able to launch sys-net with Wi-Fi access. These steps can be automated in a custom `systemd` service.
|
||||||
|
|
||||||
|
### Qubes 4.0
|
||||||
|
|
||||||
|
For Qubes 4.0, you may have to remove the wireless card from sys-net or replace it, as described in the [PCI Troubleshooting](/doc/pci-troubleshooting/#broadcom-bcm43602-wi-fi-card-causes-system-freeze) guide.
|
||||||
|
|
||||||
|
It is a bit tricky to execute, but you may be able to successfully attach a Broadcom BCM43602 to sys-net by executing the `attach` command immediately after starting sys-net. Follow these steps:
|
||||||
|
|
||||||
|
1. Disable "Start qube automatically on boot" for sys-net and sys-firewall in the Qubes Manager.
|
||||||
|
2. Manually start sys-net using the `qvm-start sys-net` command.
|
||||||
|
3. Immediately (About 2 seconds later) after stating sys-net, attach the device to sys-net using permissive mode:
|
||||||
|
`sudo xl pci-attach sys-net 'DEVICE_BDF,permissive=1`
|
||||||
|
Replace `DEVICE_BDF,` with the BDF of your wireless card. If you can immediately attach the device to sys-net while it is still starting up, it could work. If it is attached too late, the VM doesn't seem to detect it.
|
||||||
|
|
||||||
|
You can use the following script to do the above steps quickly after each boot:
|
||||||
|
|
||||||
|
~~~
|
||||||
|
#!/bin/bash
|
||||||
|
qvm-start sys-net &
|
||||||
|
sleep 3
|
||||||
|
sudo xl pci-attach sys-net '03:00.0,permissive=1'
|
||||||
|
~~~
|
||||||
|
|
||||||
|
## Broadcom BCM4360 doesn't work in a Fedora-based qube
|
||||||
|
|
||||||
|
Several people have been unable use the Broadcom BCM4360 Wireless card on a Fedora-based qube. This issue appears to be [related to Fedora](https://ask.fedoraproject.org/t/cant-connect-to-wifi-after-update-bcm4360-with-broadcom-wl-driver/482?page=2), not Qubes.
|
||||||
|
|
||||||
|
To get internet access in sys-net, try shutting down all your VMs, then changing sys-net to use the Debian 10 template. Finally, install the [broadcom-sta-dkms](https://pkgs.org/download/broadcom-sta-dkms) package.
|
||||||
|
|
||||||
|
## Boot freezes at "Setting up networking"
|
||||||
|
|
||||||
|
After installing Qubes 3.2 on a MacBook Air 13" mid-2011 (MacBookAir 4,2), it may freeze at "Setting up networking" during booting. This issue is caused by the Broadcom Wireless adapter, if you have one.
|
||||||
|
|
||||||
|
To fix the problem, you need to [remove the Wi-Fi card from your Mac][bluetooth-replacement] or put the Wi-Fi adapter into PCI passthrough, as explained below:
|
||||||
|
|
||||||
|
1. Run in a terminal:
|
||||||
|
~~~
|
||||||
|
# diskutil list
|
||||||
|
(find your usb device)
|
||||||
|
# bless –device /dev/diskX –legacy –setBoot –nextonly # bless the disk not the partition
|
||||||
|
# reboot
|
||||||
|
~~~
|
||||||
|
|
||||||
|
2. Insert your Qubes 3.2 USB flash drive. The ISOLINUX boot screen should come up.
|
||||||
|
Select Troubleshooting and Boot the Rescue image. Enter your disk password when
|
||||||
|
prompted. Select continue and after mounting the HD filesystem and launching a
|
||||||
|
shell, `chroot` as instructed.
|
||||||
|
|
||||||
|
3. Find your Wi-Fi card:
|
||||||
|
~~~
|
||||||
|
# lspci
|
||||||
|
...
|
||||||
|
02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
|
||||||
|
~~~
|
||||||
|
In the above example, the device has a BDF of `02:00.0`.
|
||||||
|
To assign this device to the sys-net VM:
|
||||||
|
~~~
|
||||||
|
# qvm-pci -a sys-net 02:00.0
|
||||||
|
~~~
|
||||||
|
|
||||||
|
4. Create `/etc/systemd/system/qubes-pre-netvm.service` with:
|
||||||
|
~~~
|
||||||
|
[Unit]
|
||||||
|
Description=Netvm fix for Broadcom
|
||||||
|
Before=qubes-netvm.service
|
||||||
|
|
||||||
|
[Service]
|
||||||
|
ExecStart=/bin/sh -c 'echo 02:00.0 > /sys/bus/pci/drivers/pciback/permissive'
|
||||||
|
Type=oneshot
|
||||||
|
RemainAfterExit=yes
|
||||||
|
|
||||||
|
[Install]
|
||||||
|
WantedBy=multi-user.target
|
||||||
|
~~~
|
||||||
|
|
||||||
|
5. To enable the `qubes-pre-netvm` services, run:
|
||||||
|
|
||||||
|
~~~
|
||||||
|
systemctl enable qubes-pre-netvm.service
|
||||||
|
~~~
|
||||||
|
|
||||||
|
6. After reboot, boot Mac OS X again by running in a terminal:
|
||||||
|
|
||||||
|
~~~
|
||||||
|
# diskutil list
|
||||||
|
(find the HD device where you installed Qubes)
|
||||||
|
# bless –device /dev/diskX –legacy –setBoot # bless the disk not the partition
|
||||||
|
# reboot
|
||||||
|
~~~
|
||||||
|
|
||||||
|
## Can't boot the installer
|
||||||
|
|
||||||
|
You can install Qubes 3.2 on a MacBook Pro Retina, 15 inch, Mid-2015 (MacBookPro 11,5) using BIOS or UEFI (If one method fails, try the other):
|
||||||
|
* BIOS/CSM/Legacy
|
||||||
|
* UEFI plain: Here, the grub menu appears, but any gives a quick flash and returns the main menu. Then, you can boot it manually and fix the `grub.cfg` file by adding the commands `linuexefi` and `initrdefi` and pointing to the proper files in `/efi/boot`. After boot, you may end up with no root file system.
|
||||||
|
* UEFI, using rEFInd: This method may prove successful, but there are some issues to be fixed manually after the installation is complete.
|
||||||
|
1. Download [rEFInd] refind-bin-0.10.4.zip. Note that this file is not signed, so decide if you trust it or not. The SHA1 sum is 3d69c23b7d338419e5559a93cd6ae3ec66323b1e
|
||||||
|
2. Unzip it and run the installer, which installs rEFInd on the internal SSD
|
||||||
|
3. If installation fails due to SIP, reboot in recovery mode, open a terminal and run the command:
|
||||||
|
~~~
|
||||||
|
csrutil disable
|
||||||
|
~~~
|
||||||
|
4. Reboot. You will see some icons.
|
||||||
|
5. Choose Boot EFI\BOOT\xen.efi from ANACONDA. After a while, the graphical installer is up (keyboard and touchpad working)
|
||||||
|
|
||||||
|
## Can't boot using GRUB2
|
||||||
|
|
||||||
|
After installing Qubes 3.2 on a MacBook Mid-2015, you may be unable to boot using `EFI/qubes/xen.efi` because the [XEN bootloader configuration is broken](/doc/macbook-troubleshooting/#cant-boot-using-xen-bootloader).
|
||||||
|
You can't also boot using GRUB2 without XEN support because the GRUB configuration is broken as well.
|
||||||
|
|
||||||
|
To start fixing this issue manually, switch to the console by pressing Fn+CTRL+ALT+F2.
|
||||||
|
|
||||||
|
It can be very useful – during troubleshooting – to have a rescue system at hand. It could help you boot Qubes, even without XEN support. This troubleshoot assumes you are performing a [UEFI boot, using rEFInd](/doc/macbook-troubleshooting/#cant-boot-the-installer).
|
||||||
|
|
||||||
|
At this point, the GRUB configuration file is using some wrong commands, which are not compatible with grub2-efi
|
||||||
|
|
||||||
|
~~~
|
||||||
|
chroot /mnt/sysimage
|
||||||
|
sed -i.bak -e "s/multiboot/chainloader/" -e "s/module.*--nounzip/initrdefi/" -e "s/module/linuxefi/" /etc/grub.d/20_linux_efi
|
||||||
|
exit
|
||||||
|
~~~
|
||||||
|
|
||||||
|
Now, despite XEN configuration is still broken, you have a rescue system booting vmlinux from rEFInd screen.
|
||||||
|
TBV1: chainloading XEN does not work, unless you specify the right disk prefix, eg: (hd1,gpt4)
|
||||||
|
TBV2: grub.cfg set the wrong disk in "set root" command
|
||||||
|
TBV3: in case you reach grub shell, you can
|
||||||
|
~~~
|
||||||
|
ls
|
||||||
|
~~~
|
||||||
|
and also reload config file and change it manually before booting
|
||||||
|
~~~
|
||||||
|
configfile /EFI/qubes/grub.cfg
|
||||||
|
~~~
|
||||||
|
Then press "e", edit `grub.cfg` and boot by pressing Fn+F10.
|
||||||
|
|
||||||
|
|
||||||
|
## Can't boot using XEN bootloader
|
||||||
|
|
||||||
|
You may be unable to boot Qubes 3.2 using `EFI/qubes/xen.efi` on a MacBook Mid-2015 because the XEN bootloader configuration is broken. This issue is accompanied by the GRUB2 configuration being broken as well. After [fixing the GRUB configuration](/doc/macbook-troubleshooting/#cant-boot-using-grub2), follow the following steps to fix the bootloader. This troubleshoot assumes you are performing a [UEFI boot, using rEFInd](/doc/macbook-troubleshooting/#cant-boot-the-installer).
|
||||||
|
|
||||||
|
* Fix grub2 configuration, which uses wrong command for EFI boot
|
||||||
|
* Analyzing `/mnt/sysimage/var/log/anaconda/program.log`, you may find the faulty commands issued by the Anaconda installer.
|
||||||
|
~~~
|
||||||
|
chrooot /mnt/sysimage
|
||||||
|
~~~
|
||||||
|
* Edit the `/boot/efi/EFI/qubes/xen.cfg` file to add the following content:
|
||||||
|
~~~
|
||||||
|
[global]
|
||||||
|
default=4.4.14-11.pvops.qubes.x868_64
|
||||||
|
|
||||||
|
[4.4.14-11.pvops.qubes.x868_64]
|
||||||
|
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
|
||||||
|
kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64
|
||||||
|
ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img
|
||||||
|
~~~
|
||||||
|
|
||||||
|
* The main mistake is that `efibootmgr` needs the right commands. Just in case, reapply all the commands, adapting them to your own disk layout (`-d /dev/sdxxx -p partition_number`)
|
||||||
|
|
||||||
|
~~~
|
||||||
|
grep Running /mnt/sysimage/var/log/anaconda/program.log | tail -n 20
|
||||||
|
efibootmgr -b 0000 -B
|
||||||
|
efibootmgr -c -w -L Qubes -d /dev/sda -p 4 -l \\EFI\\qubes\\xen-4.6.1.efi
|
||||||
|
/usr/libexec/mactel-boot-setup
|
||||||
|
kernel-install add 4.4.14-11.pvops.qubes.x86_64 /boot/vmlinuz-4.4.14-11.pvops.qubes.x86_64
|
||||||
|
systemctl disable qubes-netvm
|
||||||
|
reboot
|
||||||
|
~~~
|
||||||
|
|
||||||
|
At the rEFInd screen, choose Boot EFI/qubes/xen-4.6.1.efi.
|
||||||
|
Everything should now be ok, Qubes OS boots using EFI and you will get the last setup screen.
|
||||||
|
Select "Qubes OS", do not change anything and click on "Done".
|
||||||
|
VMs are created, including NetVM.
|
||||||
|
|
||||||
|
## System freezes often for 20 seconds
|
||||||
|
|
||||||
|
Using Qubes 3.2 on the MacBook Mid-2015 was reported to have frequent freezes, which lasts for 20 seconds. Upon looking at the `journalctl` output, you may see that pulseaudio locks the CPU for 20 seconds, very often.
|
||||||
|
|
||||||
|
To fix this issue, kill audio support with this quick workaround:
|
||||||
|
1. Open a dom0 terminal as root
|
||||||
|
2. Edit `/etc/pulse/client.conf` and add `autospawn = no`
|
||||||
|
3. As normal user, kill pulseaudio with the command `pulseaudio --kill`
|
||||||
|
|
||||||
|
|
||||||
|
[bluetooth-replacement]: https://www.ifixit.com/Guide/MacBook+Air+13-Inch+Mid+2011+AirPort-Bluetooth+Card+Replacement/6360
|
||||||
|
[rEFInd]: http://www.rodsbooks.com/refind/getting.html
|
||||||
@ -1,328 +0,0 @@
|
|||||||
---
|
|
||||||
layout: doc
|
|
||||||
title: Apple MacBook Troubleshooting
|
|
||||||
permalink: /doc/macbook-troubleshooting/
|
|
||||||
---
|
|
||||||
|
|
||||||
Apple MacBook Troubleshooting
|
|
||||||
=============================
|
|
||||||
|
|
||||||
MacBook Air 13" mid 2011 (MacBookAir 4,2)
|
|
||||||
-----------------------------------------
|
|
||||||
|
|
||||||
In this section, I explain how to install Qubes on a MacBook Air 13" mid 2011
|
|
||||||
(MacBookAir 4,2).
|
|
||||||
|
|
||||||
This model has the following features:
|
|
||||||
|
|
||||||
* Dual Intel i7-2677M 1.80 Ghz CPU (2 dual cores)
|
|
||||||
* Intel HD Graphics 3000
|
|
||||||
* 4Gb RAM
|
|
||||||
* 256Gb SDD
|
|
||||||
* Broadcom BCM43224 802.11 a/b/g/n wifi and Bluetooth adapter
|
|
||||||
* Intel DSL2310 Thunderbolt controller
|
|
||||||
* It has 1 DVI/Thunderbolt display port, 2 USB2.0 ports, a Magsafe power
|
|
||||||
adapter, a standard 3.5mm audio jack and SD reader.
|
|
||||||
|
|
||||||
I first tried to install Qubes using the UEFI boot, but it failed. Not wanting
|
|
||||||
to waste too much time, I quickly opted for the legacy BIOS install.
|
|
||||||
|
|
||||||
### 1. Boot from Mac OS X (or Internet Recovery Image with `CMD`+`R` during bootup)
|
|
||||||
|
|
||||||
Run in a terminal [[1]]:
|
|
||||||
|
|
||||||
~~~
|
|
||||||
# diskutil list
|
|
||||||
(find your usb device)
|
|
||||||
# bless –device /dev/diskX –legacy –setBoot –nextonly # bless the disk not the partition
|
|
||||||
# reboot
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Insert your Qubes 3.2 USB flash drive. The ISOLINUX boot screen should come up.
|
|
||||||
Install Qubes normally.
|
|
||||||
|
|
||||||
If you try to boot Qubes now, it will freeze while "setting up networking." You
|
|
||||||
need to put the Broadcom wireless device into PCI passtrough [[2],[3]]. Or, as
|
|
||||||
an alternative [remove it from your Mac][bluetooth-replacement] and Qubes will
|
|
||||||
boot up smoothly. If you choose to remove the card, jump to step 3.
|
|
||||||
|
|
||||||
### 2. Boot from Mac OS X again
|
|
||||||
|
|
||||||
Run in a terminal:
|
|
||||||
|
|
||||||
~~~
|
|
||||||
# diskutil list
|
|
||||||
(find your usb device)
|
|
||||||
# bless –device /dev/diskX –legacy –setBoot –nextonly # bless the disk not the partition
|
|
||||||
# reboot
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Insert your Qubes 3.2 USB flash drive. The ISOLINUX boot screen should come up.
|
|
||||||
Select Troubleshooting and Boot the Rescue image. Enter your disk password when
|
|
||||||
prompted. Select continue and after mounting the HD filesystem and launching a
|
|
||||||
shell, `chroot` as instructed.
|
|
||||||
|
|
||||||
Then find your Bluetooth card:
|
|
||||||
|
|
||||||
~~~
|
|
||||||
# lspci
|
|
||||||
..
|
|
||||||
02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
|
|
||||||
…
|
|
||||||
# qvm-pci -a sys-net 02:00.0 # this assigns the device to sys-net VM
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Then create `/etc/systemd/system/qubes-pre-netvm.service` with:
|
|
||||||
|
|
||||||
~~~
|
|
||||||
[Unit]
|
|
||||||
Description=Netvm fix for Broadcom
|
|
||||||
Before=qubes-netvm.service
|
|
||||||
|
|
||||||
[Service]
|
|
||||||
ExecStart=/bin/sh -c 'echo 02:00.0 > /sys/bus/pci/drivers/pciback/permissive'
|
|
||||||
Type=oneshot
|
|
||||||
RemainAfterExit=yes
|
|
||||||
|
|
||||||
[Install]
|
|
||||||
WantedBy=multi-user.target
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Run:
|
|
||||||
|
|
||||||
~~~
|
|
||||||
systemctl enable qubes-pre-netvm.service
|
|
||||||
~~~
|
|
||||||
|
|
||||||
And that's it.
|
|
||||||
|
|
||||||
### 3. After reboot, boot Mac OS X again
|
|
||||||
|
|
||||||
Run in a terminal:
|
|
||||||
|
|
||||||
~~~
|
|
||||||
# diskutil list
|
|
||||||
(find the HD device where you installed Qubes)
|
|
||||||
# bless –device /dev/diskX –legacy –setBoot # bless the disk not the partition
|
|
||||||
# reboot
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Results:
|
|
||||||
|
|
||||||
* System booted and running smoothly
|
|
||||||
* Youtube video: OK (including full screen after configuration)
|
|
||||||
* Trackpad: OK
|
|
||||||
* Audio control: OK
|
|
||||||
* Brightness control: OK
|
|
||||||
* Keyboard light control:OK
|
|
||||||
* SD card access: OK (tested at dom0)
|
|
||||||
* Lid-close suspend: OK
|
|
||||||
* Wifi: +10%-20% ICMP packet loss when comparing with OSX (have similar rates
|
|
||||||
with Tails Linux, more tests are required)
|
|
||||||
|
|
||||||
### References
|
|
||||||
|
|
||||||
1. <https://github.com/QubesOS/qubes-issues/issues/794>
|
|
||||||
2. <https://github.com/QubesOS/qubes-issues/issues/1261>
|
|
||||||
3. <https://www.qubes-os.org/doc/assigning-devices/>
|
|
||||||
|
|
||||||
|
|
||||||
MacBook Air 2012 (MacBookAir 5,1)
|
|
||||||
---------------------------------
|
|
||||||
|
|
||||||
Please see [this thread o the qubes-devel mailing list][macbook-air-2012-5-1].
|
|
||||||
|
|
||||||
|
|
||||||
[1]: https://github.com/QubesOS/qubes-issues/issues/794
|
|
||||||
[2]: https://github.com/QubesOS/qubes-issues/issues/1261
|
|
||||||
[3]: /doc/assigning-devices/
|
|
||||||
[bluetooth-replacement]: https://www.ifixit.com/Guide/MacBook+Air+13-Inch+Mid+2011+AirPort-Bluetooth+Card+Replacement/6360
|
|
||||||
[macbook-air-2012-5-1]: https://groups.google.com/d/topic/qubes-devel/uLDYGdKk_Dk/discussion
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
MacBook Pro Retina, 15 inch, Mid-2015 (MacBookPro 11,5)
|
|
||||||
-------------------------------------------------------
|
|
||||||
|
|
||||||
In this section, I explain how I installed Qubes 3.2 on a MacBook Pro Retina 2015 (MacBookPro 11,5).
|
|
||||||
Good news: the relevant stuff works.
|
|
||||||
Bad news: still some minor issue to investigate.
|
|
||||||
|
|
||||||
For the time being, my setup is just for testing purposes and help to bypass some blocking issues: do not use it in production or on machine where security is a concern!
|
|
||||||
I hope to improve it as soon as possible.
|
|
||||||
|
|
||||||
During my nights trying to get Qubes OS working, I faced two main and blocking issues:
|
|
||||||
* no boot, due to empty xen.cfg file
|
|
||||||
* system freeze, due to Broadcom BCM43602 wifi card
|
|
||||||
|
|
||||||
I am already using Qubes for my daily job on Intel NUC. For the time being, I installed Qubes on Macbook for test purposes. Later on I will review the security implications.
|
|
||||||
|
|
||||||
This model has the following features:
|
|
||||||
|
|
||||||
* 2,5 GHz Intel Core i7-4870HQ (2 quad cores)
|
|
||||||
* Dual Graphic Card
|
|
||||||
* Intel Iris Pro
|
|
||||||
* AMD Radeon R9 M370X
|
|
||||||
* 16Gb RAM
|
|
||||||
* 512Gb SDD
|
|
||||||
* Broadcom BCM43602 802.11ac wifi adapter
|
|
||||||
|
|
||||||
### 1. Reclaim space to be able to multiboot OSX
|
|
||||||
|
|
||||||
For security reasons, you should install Qubes using the whole disk. I preferred to keep OSX, so I shrunk OS partition:
|
|
||||||
* reboot in recovery mode
|
|
||||||
* run disk utility and shrink OSX partition, eg 150GB for OSX and the remaining space for Qubes OS
|
|
||||||
* reboot
|
|
||||||
|
|
||||||
|
|
||||||
### 2. Boot installer
|
|
||||||
|
|
||||||
Download and prepare a USB with Qubes 3.2
|
|
||||||
|
|
||||||
You can install Qubes using BIOS or UEFI:
|
|
||||||
* BIOS/CSM/Legacy: I have not been able to install using legacy, but I did not spend a lot of time on it.
|
|
||||||
* UEFI plain: grub menu appears, but any gave me a quick flash and returned the main menu. I can boot it manually fixing the grub.cfg file, adding commands linuexefi and initrdefi, pointing proper files in /efi/boot. After boot, I end up with no root file system.
|
|
||||||
* UEFI, using rEFInd: I have been successful, despite some issues to be fixed manually, after installation completion
|
|
||||||
* download [rEFInd] refind-bin-0.10.4.zip: this file is not signed, so decide if you trust it or not. SHA1 sum is 3d69c23b7d338419e5559a93cd6ae3ec66323b1e
|
|
||||||
* unzip it and run installer, which installs rEFIind on the internal SSD
|
|
||||||
* if installation fails due to SIP, reboot in recovery mode, open a terminal and issue command
|
|
||||||
~~~
|
|
||||||
csrutil disable
|
|
||||||
~~~
|
|
||||||
* reboot and you will see some icons
|
|
||||||
* choose Boot EFI\BOOT\xen.efi from ANACONDA
|
|
||||||
* after a while the graphical installer is up (keyboard and touchpad working)
|
|
||||||
|
|
||||||
### 3. Installation
|
|
||||||
|
|
||||||
* As a general rule, keep the default values proposed during installation: you can change them later on
|
|
||||||
* Keep English, as language, locale
|
|
||||||
* My Macbook has a US keyboard, so I cannot say what happens if you change keyboard layout
|
|
||||||
* DO NOT CHANGE the timezone, because it will trigger the wifi card, leading to a system freeze
|
|
||||||
* Choose the "installation destination": do not change anything and press DONE button
|
|
||||||
* Insert your password for Full Disk Encryption
|
|
||||||
* If you do not already have free space on internal SSD disk, you will be prompted to reclaim some space:
|
|
||||||
* If you shrunk OSX partition, disk utility left an empty partition: delete useless partition (e.g.: if you shrunk OSX partition, diskutil created an empty partition)
|
|
||||||
* Press on "reclaim space"
|
|
||||||
* Press on "begin installation"
|
|
||||||
* create your user and password
|
|
||||||
* after a while, installation completes
|
|
||||||
* DO NOT press "Reboot button"
|
|
||||||
|
|
||||||
Qubes OS is now installed, but you cannot boot it due to some issues, with bootloader configuration and wifi card.
|
|
||||||
You cannot Qubes boot using EFI/qubes/xen.efi because XEN bootloader configuration is broken.
|
|
||||||
You cannot even Qubes without XEN support, using GRUB2, because its configuration is broken too.
|
|
||||||
|
|
||||||
Let's fix it manually, switch to console, pressing Fn+CTRL+ALT+F2
|
|
||||||
|
|
||||||
### 4. Fix GRUB configuration
|
|
||||||
|
|
||||||
You can skip this section, but I found it very useful - during troubleshooting - to have a rescue system at hand. I could boot Qubes, without XEN support
|
|
||||||
|
|
||||||
Grub configuration file is using some wrong commands, which are not compatible with grub2-efi
|
|
||||||
~~~
|
|
||||||
chroot /mnt/sysimage
|
|
||||||
sed -i.bak -e "s/multiboot/chainloader/" -e "s/module.*--nounzip/initrdefi/" -e "s/module/linuxefi/" /etc/grub.d/20_linux_efi
|
|
||||||
exit
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Now, despite XEN configuration is still broken, you have a rescue system booting vmlinux from rEFInd screen.
|
|
||||||
TBV1: chainloading XEN does not work, unless you specify the right disk prefix, eg: (hd1,gpt4)
|
|
||||||
TBV2: grub.cfg set the wrong disk in "set root" command
|
|
||||||
TBV3: in case you reach grub shell, you can
|
|
||||||
~~~
|
|
||||||
ls
|
|
||||||
~~~
|
|
||||||
and also reload config file and change it manualy before booting
|
|
||||||
~~~
|
|
||||||
configfile /EFI/qubes/grub.cfg
|
|
||||||
~~~
|
|
||||||
then press "e", edit grub cfg and boot pressing Fn+F10
|
|
||||||
|
|
||||||
|
|
||||||
### 5. Fix bootloader
|
|
||||||
|
|
||||||
* Fix grub2 configuration, which uses wrong command for EFI boot
|
|
||||||
* analyzing /mnt/sysimage/var/log/anaconda/program.log I found the faulty commands issues by Anaconda installer
|
|
||||||
|
|
||||||
~~~
|
|
||||||
chrooot /mnt/sysimage
|
|
||||||
~~~
|
|
||||||
* edit /boot/efi/EFI/qubes/xen.cfg file putting the following content
|
|
||||||
|
|
||||||
~~~
|
|
||||||
[global]
|
|
||||||
default=4.4.14-11.pvops.qubes.x868_64
|
|
||||||
|
|
||||||
[4.4.14-11.pvops.qubes.x868_64]
|
|
||||||
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
|
|
||||||
kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64
|
|
||||||
ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img
|
|
||||||
~~~
|
|
||||||
|
|
||||||
* The main mistake is the efibootmgr, that needs the right commands. Just in case, re-apply all the commands, adapting to your own disk layout (-d /dev/sdxxx -p partition_number)
|
|
||||||
|
|
||||||
~~~
|
|
||||||
grep Running /mnt/sysimage/var/log/anaconda/program.log | tail -n 20
|
|
||||||
efibootmgr -b 0000 -B
|
|
||||||
efibootmgr -c -w -L Qubes -d /dev/sda -p 4 -l \\EFI\\qubes\\xen-4.6.1.efi
|
|
||||||
/usr/libexec/mactel-boot-setup
|
|
||||||
kernel-install add 4.4.14-11.pvops.qubes.x86_64 /boot/vmlinuz-4.4.14-11.pvops.qubes.x86_64
|
|
||||||
systemctl disable qubes-netvm
|
|
||||||
reboot
|
|
||||||
~~~
|
|
||||||
|
|
||||||
At rEFInd screen, choose Boot EFI/qubes/xen-4.6.1.efi
|
|
||||||
Everything should now be ok, Qubes OS boots using EFI and you will get the last setup screen
|
|
||||||
* select "Qubes OS", do not change anything and click on "Done"
|
|
||||||
* VMs are created, including NetVM
|
|
||||||
|
|
||||||
### 6. Fix pulseaudio, which locks CPU freezing the system often for 20 seconds
|
|
||||||
|
|
||||||
My Macbook has frequent freezes. Looking at journalctl output I saw that pulseaudio locks CPU for 20 seconds, very often.
|
|
||||||
|
|
||||||
You can fix this issue, killing audio support with this quick workaround:
|
|
||||||
* open a dom0 terminal, as root and edit /etc/pulse/client.conf
|
|
||||||
* add "autospawn = no"
|
|
||||||
* Then, as normal user, issue command "pulseaudio --kill"
|
|
||||||
|
|
||||||
### 7. Fix system freezes due to Broadcom BCM43602
|
|
||||||
|
|
||||||
* If you experience a system freeze, during VM setup, force a reboot and press OPTION key.
|
|
||||||
* You will reach grub shell
|
|
||||||
~~~
|
|
||||||
configfile /EFI/qubes/grub.cfg
|
|
||||||
~~~
|
|
||||||
press Fn+F10 to boot without XEN support
|
|
||||||
* Once booted, press Fn+CTRL+ALT+F4 to open a shell
|
|
||||||
* Log into system
|
|
||||||
~~~
|
|
||||||
sudo su -
|
|
||||||
systemctl disable qubes-netvm
|
|
||||||
~~~
|
|
||||||
Press Fn+F2 and complete setup
|
|
||||||
* reboot and you finally have your Qubes OS
|
|
||||||
* DO NOT launch sys-net machine
|
|
||||||
* Open its setting and remove wifi adapter from the Selected devices, using Qubes Manager or use the following command line. Get the BFD of the adapter and remove it. On my Macbook BFD is 04:00.0 and you will use it later on, also
|
|
||||||
~~~
|
|
||||||
qvm-pci -l sys-net
|
|
||||||
qvm-pci -d sys-net 04:00.0
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Ok, setup is complete and we are almost done.
|
|
||||||
* Open a dom0 terminal
|
|
||||||
~~~
|
|
||||||
sudo su -
|
|
||||||
xl pci-assignable-list
|
|
||||||
echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive
|
|
||||||
qvm-start sys-net
|
|
||||||
xl pci-attach sys-net 04:00.0
|
|
||||||
~~~
|
|
||||||
|
|
||||||
These latest steps are required to launch sys-net with wifi access. They can be automated in a custom systemd service.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
[rEFInd]: http://www.rodsbooks.com/refind/getting.html
|
|
||||||
@ -115,7 +115,7 @@ You can also configure strict reset directly from the Qubes interface by followi
|
|||||||
|
|
||||||
## Broadcom BCM43602 Wi-Fi card causes system freeze ##
|
## Broadcom BCM43602 Wi-Fi card causes system freeze ##
|
||||||
|
|
||||||
You may face the problem where the BCM43602 Wi-Fi chip causes a system freeze whenever it is attached to a VM. To fix this problem on a Macbook, follow the steps in [Macbook Troubleshooting](/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602).
|
You may face the problem where the BCM43602 Wi-Fi chip causes a system freeze whenever it is attached to a VM. To fix this problem on a Macbook, follow the steps in [Macbook Troubleshooting](/doc/macbook-troubleshooting/#system-freezes-after-attaching-broadcom-bcm43602-wi-fi-card).
|
||||||
|
|
||||||
For other non-Macbook machines, it is advisable to replace the Broadcom BCM43602 with one known to work on Qubes, such as the Atheros AR9462.
|
For other non-Macbook machines, it is advisable to replace the Broadcom BCM43602 with one known to work on Qubes, such as the Atheros AR9462.
|
||||||
|
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user