Search results

For anyone with a similar issue, the BIOS refresh had reset to defaults and MacOS needs the SATA interface to be in AHCI mode rather than IDE mode - switched in the BIOS and SATA has re-appeared in System Report.

Weird one, aren’t they all! Everything working fine then flashed the BIOS (to the same version it transpires!) and installed a pair of Xeon 5690’s. Re-fit drives, I boot into Clover via a SATA SSD and have a SATA archive drive, both detected in the BIOS. Clover then installs the NVMe driver...

Booted normally today. So seems to have fixed itself. Only suggestion I can make for others is to enter Recovery and it appears that Time Machine makes snapshot backups which it saves locally (not on a Time Capsule) and restoring to a point prior to the problem appearing, appears to have solved...

Boot into Recovery and even though I have a Time Capsule connected, the Recovery App could only see the recent Time Machine snapshots located on my normal boot drive. If I wind back to Dec 22nd then the Hackintosh boots fine and everything appears to work. If I then reset, I get the same effect...

I was just about to suggest that. Circa 1000rpm is basic tickover / normal operation. Normal PC fans run up to 5000rpm when things get warm, more likely a bearing issue as you discovered. Glad its sorted.

p.s. Its not exactly hanging, just not reaching the OSX sign in screen.

Hi, just recovering from COVID (not recommended) so my brain isn't functioning correctly at the moment, any pointers on where to start? High Sierra, boots through Clover fine, Apple symbol, progress bar updates, 3 monitors all go black, then where I would normally get the familiar sign in...

The groove the C-clip hooks into can catch on the two nylon washers as you push the pin out (into the case). Just waggling the pin sorts that out. The pin connects the rear catch to the plastic rail.

Just finger nail on one side and flat blade screwdriver on the other and push the C-Clip off the pin. I’ve done 3 and none very tight (it’s only a thin and small C-Clip). The grey rail just drops off once all fasteners are removed.

It does mean you need another (SATA or USB) device that has Clover on, which just has Clover. That then finds your NVMe device.

Normally your computer BIOS points at the drive/partition that then boots the operating system (Windows / macOS etc). In a Clover based Hackintosh Clover sits in-between the BIOS and the Operating System. So your BIOS needs to point at the partition that has Clover on it. Clover effectively...

The BIOS doesn't need to support is as the Clover NVMe driver doesn't use the BIOS and neither does macOS.

100% do it. Especially as you have PCIe 3.0. I have PCIe 2.0 and get 1500+ MB/s Read/Write (Corsair Force MP510 SSD 960GB or thereabouts). It doesn't matter if your BIOS natively supports NVMe drives on the PCI bus or not, because Clover is your boot software then macOS is your operating system...

Very simple, but very good idea - that makes a lot of sense. Clover may not like the spaces and enclosing in quotes makes sure they are included. Good idea thanks.

I know what you mean, but can't complain given Clover is infinitely lovely compared with its cost :-)

When I installed Windows 10 on a blank drive the installer created 4 partitions. I deleted two of them post install just using Win10 Computer Management / Manage Disks ... But be careful and be prepared to have to re-install Windows. ie something to do immediately after a fresh install.

I think clover looks for files named boot.efi - I would create a usb stick to boot from, boot from it then rename the folder & file/s you think are suspect and reboot to see if the option vanishes. If there’s an issue the usb stick then means you can reboot and change the filenames back to their...

Check the partition list on all other drives you have in your system. When I installed Windows 10 on my Hackintosh the Windows installer created its temp boot efi on my backup drive. That kept being listed within clover and I thought it was on the Windows boot installation drive but no UUID etc...

Looks like Clover lists bootable volumes AND scans volumes for what it thinks is bootable items. So with the install left overs you end up with more than one Clover boot item for your operating system volume. Clover then auto runs the first thing it lists so keeps calling the installer instead...

Solved. For anyone reading the above see: https://www.tonymacx86.com/threads/guide-how-to-remove-boot-os-x-install-from-partition-from-clover-bootloader.185201/ It looks like Clover scans for bootable Volumes, but it also scans the Volumes themselves for boot.efi or similar. Installations of...