On Tuesday, 15 November 2016 10:28:52 UTC+11, Marek Marczykowski-Górecki  wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On Mon, Nov 14, 2016 at 02:33:50PM -0800, dumbcyber wrote:
> > On Tuesday, 15 November 2016 09:02:56 UTC+11, dumbcyber  wrote:
> > > On Tuesday, 15 November 2016 08:47:30 UTC+11, dumbcyber  wrote:
> > > > From the beginning I have to ask for forgiveness - I am new to Qubes 
> > > > and have no knowledge of changing boot managers beyond trial and error.
> > > > 
> > > > My hardware is a Macbook 11,1. In fact I don't have any other machines 
> > > > at home.
> > > > 
> > > > I want to create a bootable USB drive with Qubes R3.2. I had the usual 
> > > > problem of seeing the 4-item menu to install but nothing working 
> > > > regardless of option chosen.  I tried some forum suggestions like 
> > > > adding /noexitboot=1 to the cfg file. No luck.
> > > > 
> > > > I created a working Qubes USB on a Lenovo computer at work. I was able 
> > > > to create new VM's and set firewall rules. So I know it works.
> > > > 
> > > > Then my uninformed head took over. What if I took that USB and tried 
> > > > booting it on my Macbook? The Macbook does not even recognise the USB 
> > > > at boot time. If I boot into OSX I can get to the USB drive through 
> > > > terminal and mount it.
> > > > 
> > > > I then tried copying rEFInd to the Qubes USB stick but that just hangs 
> > > > the Macbook after selecting the EFI boot option. I'm resisting 
> > > > installing rEFInd on the Macbook itself until I know more about it 
> > > > especially the need to disable SIP.
> > > > 
> > > > My question is: would that even work - copying rEFInd to the working 
> > > > USB drive built on a Lenovo?  Are there any other options I could try?
> > > > 
> > > > Many thanks.
> > > 
> > > 
> > > I also tried copying the EFI/qubes folder to EFI/BOOT and renaming the 
> > > two xen files to BOOTX64 - this hangs after selecting the EFI boot option 
> > > on Mac startup.
> > 
> > Stupidly, when I copied EFI/qubes to EFI/BOOT I left the /noexitboot 
> > options in the CFG file. I removed them from EFI/BOOT/bootx64.cfg and 
> > retried.
> > 
> > I can now boot into Qubes as far as the disk password prompt. The progress 
> > bar on the bottom centre of the screen progresses all the way across but I 
> > can not enter any characters into the password field.
> 
> Macs have USB keyboard, which makes them incompatible with USB VM (at
> least in default configuration). In particular, enabling USB VM prevent
> USB controllers being initialized in dom0 - even during disk passphrase
> prompt. To disable this part, you need to remove 'rd.qubes.hide_all_usb'
> from kernel parameters.
> Also the problem may be caused by missing USB controller (or keyboard
> itself) driver in initramfs, but AFAIR it was fixed long ago.
> 
> - -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJYKkivAAoJENuP0xzK19csPKUIAJjnVSSSTj1oJGyisBEFhNZk
> 56thercS0SFlvMpdBmY4xXF+F+TuEuoK8VPFXJeQGUhyH8UtjuWYavC0wzWTsl2H
> c3yMucbxHVvzmTTwth3ToYvfcaQUO+Zu89J9CfwsfzRsr2p53n4x6OECfuhuc/Hs
> ftqPUDWOG87jXzaJVKS3SbWdg/8ifrDkEWgYCpXy/jTZiC3Zpd3K50aU0dFSG6Ww
> Xv61SKSZjRbZNtrjBVgkUXxXgw5lD0rRuddlsUNqJJX4r+n/VlF7acukjYXfyfRM
> TMvFoR9k5RH4leniSTMNTeQqQcSUgGAbPaa+dJ/OdyY+x5y6djtCBb72izQVY0k=
> =5rjy
> -----END PGP SIGNATURE-----

Thanks for the info. For me a noob, how do I remove that parameter from kernel? 
 Thank you.

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/981eb4dd-6a27-48be-ae15-f7dc69714fd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to