- #Boot legacy linux with clover boot loader how to
- #Boot legacy linux with clover boot loader install
- #Boot legacy linux with clover boot loader drivers
And finally, learn to dual and tripple boot OS's. Is Clover at fault or is Fedora or my machine?Ĥ. Figure out why the OS set CFQ as the default I/O Scheduler, when it should be "none". That should give me plenty of time to enter clover if I need to.ģ. I need to set Clover to auto boot Fedora in 1 second. Learn Clover like a Pro! First and foremost.Ģ. Samsung SM961 NVMe SSD 256GB (using Asus M.2 MINI x4 adapter on full x16 slot #3)Īll sata ports disabled, onboard usb 3.0 disabled, no other operating systems, just Fedora 26 on NVMe device.ġ. So, the question is, Should I be modifying Clover for a better experience, or is the default good enough? Below is my machine.Īsus Rampage III Extreme x58 (legacy BIOS set to PnP=Yes) I have made TWO Clover usb drives of course, just in case I break one with experiments, which I already done several times, haha.
#Boot legacy linux with clover boot loader how to
Is the default Clover setup "Out of the Box" good enough or should I be modifying Clovers plist file for an even better experience? I have already taken a look at the plist file using CCE, but LOL I had no clue what to do in their, not yet anyway, not until I can find some documentation on how to use CCE.
Now I have a working Fedora 26 booting on NVMe PCIe on a 2010 x58 system.
#Boot legacy linux with clover boot loader install
However, I have already killed the install twice before when setting it up on my own (in dual boot), so on this 3rd try I simply let Fedora DIY it, not changing anything (single OS boot claiming the entire SSD). Then, once I got Fedora booted I simply pointed Anaconda at the brand new Samsung SM961 NVMe SSD. Booted to Clover, went into the shell and commenced to booting and installing from the Live Distro. First off though, I managed to format the USB using "GPT for UEFI" formatted via Rufus in Windows 10.
#Boot legacy linux with clover boot loader drivers
I have already created the Fedora USB installer, booted it using Clover and dropped in all of the efi drivers from the "driversOFF" folder to the "drivers64" folder (was this correct?). It is obvious Clover is more tuned for macOS, but it also seems to be OS agnostic at the same time? As you can see in the image below how Fedora set itself up on that NVMe device. I feel like I should be manually installing Linux, not using automatic defaults. However, something seems a wee bit off, and I am not sure I did it right. Using a freshly created Clover r4128 USB 2.0 device today, and thanks to that I already have a booting Fedora 26 on a NVMe device, on a legacy BIOS machine, woohoo.
Building a CustoMac Hackintosh: Buyer's Guide
0 kommentar(er)
