- Joined
- Jul 25, 2012
- Messages
- 6,663
- Motherboard
- Gigabyte GA-Z77X-UP5 TH
- CPU
- i7-3770K
- Graphics
- HD 4000+GT 710
- Mac
- Mobile Phone
Ok great, thanks guys. That has worked. I can now boot to Sierra without the USB connected.
Clearly though I need to add a few kexts and boot flags etc to get most if not all of the components working properly. Off to look up how to use clover and start testing.
Before I do anything too drastic though, just a couple of queries to which any help would be appreciated:
1) is there a way of viewing or accessing the bootlog (i.e. the text contained in verbose mode) so I can analyse it to identify any issues during boot? is the bootlog saved somewhere or are there commands to dump it to a text file somewhere?
2) can I back up my system (including the UEFI state) as it is now, prior to any clover additions, in a way that can be easily restored at a later date? as indicated above, multibeast kept causing the system to be unbeatable (even from the USB) and I'd have to somehow reset the bios and then reinstall Sierra, which is a time consuming process, especially if I'm going to be testing various kexts etc on a trial and error basis. I read somewhere that I can create a 'test' clover USB - would this approach leave my current installation untouched (including any UEFI stuff) and any temporary clover stuff from the USB not affect the currently bootable and clean system as it currently is?
Essentially, with regard to point 2) above, what's the best way of testing stuff out without having to start from scratch with a fresh Sierra install each time?
You can access , view and save a copy of your Clover boot log easily using "Clover Configurator" (https://www.tonymacx86.com/resources/clover-configurator.328/) . As you may have already figured out that this is useful more for a retrospective analysis of a non-fatal booting problem where as a verbose boot flag (-v) can help you with concurrent analysis of a serious problem like Kernel Panics during installation. You know you can also view and edit your Clover Config.plist with this GUI tool, Clover Configurator.
If you want to analyze panics/crashes after installation on the hard disk, the Mac application "Console" from Applications Folder is a handy tool.
When you launch the Clover Configurator you can find an option to click : "Boot.log" shown under "Tools " on the Left Pane of this window toward its bottom 1/3rd. The displayed log can be copied or a copy generated and saved on the desktop to be opened and viewed later.
Hope this helps
The other important question posed has been already answered.