On Wednesday, June 15, 2016 at 4:18:44 AM UTC-4, qubes...@gmail.com wrote: > Congrats on the install. I for one would be really interested in a > step-by-step description of what you did to get it working. Although not > quite the same, I have an old MacBook Pro on which I'd like to install Qubes! > :-)
As I'm still trying to go through different things to get a better write up for the post with the HCL (and getting the HCL report to run- it's not outputting files, for some reason), I'll give the Q&D. I'm uncertain if I made things easier or harder on myself by wanting the machine to single boot Qubes, no OS X. My first go at this machine a few weeks ago, I was attempting to dual boot, and was able to get past the installation step, but failed at a point during Qubes setting itself up on first boot, which I was able to overcome in this go around by checking the box that says, "Don't setup anything at all- I got this," * Create USB installer * Create rEFInd USB stick * Use Recovery Partition on Mac to erase drive. Working under the presumption that Qubes didn't support UEFI (which I later found out is not true, although the Apple implementation of UEFI seems to have had a bit of shade thrown at it), I formatted the drive MBR and FAT, one partition. * Attached the rEFInd USB stick, and held down the alt key, and booted from it. It was the only option. * Once the rEFInd booted, I then connected the Qubes installer USB drive to the other USB port. Refreshed. Here came the first round of headaches. rEFInd gives about four choices for booting the Qubes installer, "vmlinuz from ANACONDA", "xen.efi from ANACONDA", "Legacy something something". Apologizes for not having the specific texts, but three of the four would not permit a successful boot into the installer. The one that worked for me was something to the effect of "Legacy fallback whole disk" (the choice was all the way on the right). Initially I had not chosen this one because I had thought it was referring to the hard drive in the computer which had no OS on it at all. This is the one that worked. * Once booted into the installer, I reclaimed all the space on the drive and left everything else at defaults. Started it installing, made myself some tea. * There are guides that explain how to fix up the Broadcom stuff at this point, I ignored all of them and probably caused myself more headaches by doing so. * On first boot Qubues goes through it's setups. The first time through, I left all the defaults, somewhere when it's starting up the networking stuff, it locks up and then refuses to boot up properly from there on out. There is /probably/ a way of fixing this, but I just went back a few steps, erased the drive, reinstalled Qubes. * This time, I went with the advanced option and asked Qubes to not setup anything automatically for me. I did this to avoid it setting up the net-vm, which freaks out with the Broadcom chip in the computer. The biggest problem with this is that it doesn't setup any of the default VMs for you, and that's a /really/ nice thing. * Once into the booted operating system, I followed the "Assigning Devices" page on Qubes's website: https://www.qubes-os.org/doc/assigning-devices/ * I spent a bunch of time on that, until finally, I (as mentioned in previous message) trashed the net-vm which was running from the Debian template and re-created it using the Fedora template and the kernel in there knows how to talk Broadcom. * After all that, time to start making VMs. tl;dr * Booted USB installer from USB rEFInd drive, skipped the automatic setup and used Fedora as the template for my net-vm. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9a45d9d6-061b-4f22-a1cb-cea44c40bdaa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
