Hi, I've mac pro 5.1 mid2010, dual x5690, 96gb memory, vega 64, system in nvme samsung 970 evo plus, very fast, i have Mojave latest version updated, i installed opencore 0.5.9, got hardware acceleration + boot select, but i found that the boot is a little slow, once i start the mac it takes a long time to get to the opencore selectboot, then it goes fast, but is there any way to speed up the boot? I have an nvme anyway and my rom is updated 140.0.0.0.0, thank you
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Boot too slow with opencore and nvme
- Thread starter mohnumber7
- Start date
- Sort by reaction score
oK, I understant, in the past I have 8 gb memory, and now 96gb, so for that the boot is slow until the screen of selecting boot, after that, the speed is here, so thanks for these informations.
I have the same problem,
the time between pressing the computer switch and the chime is quite long but it's because of the RAM I have installed (128GB)
but it has always been like that, whether with OpenCore or without,
but from some update of the OC I have to wait a long time from the chime until the OC menu appears,
it is noticeably longer than before and the computer is 100% in the same configuration
is your ROM actually 140.0.0.0, I ask only because I believe the latest version is 144.0.0.0 as is mine.
OpenCore has gotten more complex with each release as more features are added. You could test to see whether you notice a speed jump if you disconnect any disks connected to PCIe Slots before booting as compared to them connected. If you do, then the issue is probably with the adapter.
yes, it's 140.0.0.0.0, is there any advantage to go with the 144.0.0.0.0? I think it's included in Catalina no?
[automerge]1599258779[/automerge]
The only disk connected to Pcie is the system (nvme samsung), all others are sata.
It will POST slowly, it's 96 GB of RAM which is tested using only one thread on a single CPU. Only then both CPUs kick in.
The POST time is further slowed down as the computer checks for presence of all the SATA disks and then probes the PCIe bus, your Samsung is probably in the top slot (#4), which will be checked last, as far as I remember.
It's by design and there is not much you can do about it.
The POST time is further slowed down as the computer checks for presence of all the SATA disks and then probes the PCIe bus, your Samsung is probably in the top slot (#4), which will be checked last, as far as I remember.
It's by design and there is not much you can do about it.
He is talking about the time taken to load OpenCore after the chime. I.E., after all you mentioned has taken place.
yes, samsung is in the last slot, there is also 4 hard drive, and an ssd samsung evo 860 in the sata of dvd burner, so there a lot to test, with 96gb or memory too, so I can't do anything to slow the time before and after the chime.
and the best thing is when the computer wakes up at night and all the drives start to take off like the Millennium Falcon from Star Wars
I did some tests and here are my results:
normal boot, Vega64 slot 1,
NVMe WD Black SN750 1TB slot 2,
USB 3.1 slot 3,
WiFi AC Apple slot 4,
3xHDD, from 1 to 3
time from switching on to the chime 36 seconds,
time from chime to OpenCore menu 43 seconds,
the next test was the same,
the USB card, WiFi, HDD were removed,
NVMe and Vega 64 remained
time from switching on to the chime 34 seconds
time from chime to OpenCore menu 42 seconds
Last edited:
and the best thing is when the computer wakes up at night and all the drives start to take off like the Millennium Falcon from Star Wars
Fortunately doesn't happen for me (disabled "wake for network access").
Your timing seems comparable with mine, never bothered to actually measure it but it's about that long.
Are you able to load OpenCore without the NVMe connected? I.E., with it on a SATA Drive and the NVMe pulled?
My chime to OpenCore load time is about 6 Seconds btw.
it will be a difficult job but I will do it, because now I remembered that previously I had OC on the sata III disk and it was noticeably faster, I think
I think having it on SATA with the NVMe still connected will still be slow.
Just wanted to test without the NVMe attached at all to see if this makes a difference.
There are strange issues with drives in PCIe Slots.
The Shutdown/Restart options provided in OpenCore are from an issue I raised a while back because of PCIe drive issues.
The OpenCore Team also has a related pending bug report with the TianoCore Project which provides the build environment for OpenCore.
So just curious on whether not having a disk there makes a difference as opposed to having one connected but not booting from this (this was my situation).
Just wanted to test without the NVMe attached at all to see if this makes a difference.
There are strange issues with drives in PCIe Slots.
The Shutdown/Restart options provided in OpenCore are from an issue I raised a while back because of PCIe drive issues.
The OpenCore Team also has a related pending bug report with the TianoCore Project which provides the build environment for OpenCore.
So just curious on whether not having a disk there makes a difference as opposed to having one connected but not booting from this (this was my situation).
I was requesting a test to see.
Some background:
By the time OpenCore shows a bootpicker, it had already been started by the system firmware a while beforehand. I.E., firmware had scanned your hard drives for a loader, selected OpenCore and started it off.
The time taken to scan your drives for boot loaders is trivial. I have seven drives connected and it takes a fraction of a second to scan all seven and select a bootloader.
OpenCore is basically started less than a second after boot chime and the 40 odd seconds from chime to bootpicker seen is basically all within OpenCore. Something that can eat a lot of time however, is connecting device handles to controllers.
I had SSD connected to a PCIe Slot and on occasion in my case, there would be a glitch and an extra 30+ seconds would be added to the time to bootpicker.
Hooking the SSD to a SATA port (from the DVD Bay) instead eliminated this issue. I suspect it might have been the adapter at fault and wondering whether the same also applies for NVMe drives. Hence the request for a test from those that have such drives/adapters which I don't.
This connection issue also affects Refind but does not seem to affect the native boot. Anyway, interested to see what the outputs are if someone has the option to compare a boot with NVMe drive connected (doesn't have to be booted from this ... just active) and with it disconnected.
If you install any type of PCIe drive, the EFI firmware has to scan and enumerate all PCIe address space, this takes time. NVMe takes even more time since the enumeration and initialisation is more complex.
Boot time is even worse if you have switched adapters, but a dumb adapter installed without drive is not active (it's just a format converter, from PCIe x4 to M.2) and won't be scanned/enumerated.