Yosemite on NVME MacBook

[naquaada]

Hello,

 

I have a 2015 MacBookPro11,5 and a MacBookPro11,4. It's the same but without the Radeon.

 

I've planned a huge task: Backup all my data from 20 years hackintosh and sell the old drives to data recovering

companies. That's why I needed Yosemite which has the original Disk Utility. Because I'm planning mostly to do

compressed disk images for backups, this is the version to go.

 

The MPB11,4 has a 256 GB SATA SSD, the MBP11,5 has a 4 TB NVMe SSD. Both are using OCLP and working fine

with Sequoia. I still have the old 512 GB original Apple NVME SSD from the 11,5, so I wanted to add it in the 11,4.

I've cloned the Yosemite installation from the 11,4 to the 11,5 and it won't boot 'still waiting for root device'.

 

I've tracked down NVMeGeneric.kext, modified the info.plist from 10.11 to 10.10 and the kext is loaded on the 11,4.

I haven't transferred this version to the 11,5 yet, I want to do some more optimizations first.

 

Has someone else made tests with NVMe on older OS X versions on real Macs? Is it possible to use OCLP for

NVMe support? Is it possible to inject the NVMeGeneric.kext?

 

 

Greets, naquaada.

[LockDown]

No need for OCLP. flag it with kext-dev-mode=1 and install nvmegeneric

Edited Wednesday at 07:39 AM by LockDown

[naquaada]

Yes, I had kext-dev-mode=1 in /Library/SystemConfiguration/com.apple.boot.plist

and now it's also added in NVRAM using the nvram command.

Kext dev mode is activated in Yosemite, I could see it in the Kext Utility.

 

But I still need some time until It is configured well enough to be cloned to the 11,5.

[LockDown]

I Pm'd you earlier with the version i had success long time ago

[naquaada]

I haven't seen it until now. The binary in your version is identical, but you have a different info.plist.

[naquaada]

Yep, now it works. On both MacBooks and my OSx86 machine.

[luxinhaus]

what made it work?

Edited Friday at 02:48 AM by luxinhaus

[naquaada]

I installed all kexts to System/Library/Extensions on my SATA MacBook and recreated the kextcache.

Then I created from the installer disk utility a dmg of this volume.

I wrote it on a partition on my NVME MacBook and it's working.

 

My desktop system has a Core i7 3770S and a Sapphire GPRO 4200 GPU, which is based on the

Radeon R7 250x. It also uses AMD7000Controller.kext like the R9 370X in the MacBookPro11,5.

The MacBook version doesn't need the OSx86 drives and most of the OSx86 tools.

 

My Kingston 4 TB SSD has 2.1 GB read and 2.6 GB write.

Counting from the Apple logo, Yosemite needs just 9 seconds to reach the desktop.

[naquaada]

Does anybody know why Yosemite has always volume muted after rebooting?

I happens on both Mac and Hackintosh.

Edited 5 hours ago by naquaada

[deeveedee]

@naquaada Did you try a web search or asking an AI chatbot?  There are several reasons that can happen with Yosemite.

 

This is the response from ChatGPT

Spoiler

On macOS Yosemite (10.10), the volume should normally be restored to the level it was at before shutdown. If your Mac always starts up muted, it's usually due to one of a few causes:
Startup chime and volume setting
On older Macs with Yosemite, the startup chime volume is tied to the system output volume.
If the volume was muted or set to zero when you shut down, it may remain muted after reboot.
External audio device
If you're using USB speakers, an HDMI monitor, DisplayPort audio, or Bluetooth audio, macOS may not restore the previous output correctly during startup.
Check System Preferences → Sound → Output after logging in to see which device is selected.
Corrupted audio preferences
The file that stores audio settings can become corrupted, causing the volume to reset or mute at every boot.
PRAM/NVRAM issue
Macs store certain settings, including speaker volume, in NVRAM (formerly PRAM). If it's corrupted, volume settings may not persist.
Resetting NVRAM often fixes this:
Shut down the Mac.
Turn it on and immediately hold Option + Command + P + R.
Keep holding the keys for about 20 seconds (or until you hear the startup chime a second time on older Macs).
Login items or third-party utilities
Some audio utilities (Boom, SoundFlower, Audio Hijack, etc.) or scripts can mute audio at login.
Things to check
Does the speaker icon in the menu bar show a mute symbol immediately after login?
If you unmute it and reboot, is it muted again every time?
Does this happen using the internal speakers, or only with external speakers/headphones?
Is the startup chime audible, or is it silent as well?
A quick test
Open Terminal and run:
osascript -e "output volume of (get volume settings)"

After setting the volume to about 50%, reboot and run the command again. If it returns 0, something is resetting the volume during startup.
Could you tell me:

Is this a MacBook, iMac, or Mac Pro?
What is the exact Yosemite version (10.10.0 through 10.10.5)?
Is the mute present before login (no startup chime) or only after you log in?

 

 

[naquaada]

I noticed something: The volume is set to mute after a reboot, but I still have sound.

If I press the mute key the first time, the volume is un-muted in the menu bar icon.

After pressing it the second time the mute function is working.

 

Weird. I didn't had this issue in any version of macOS. But it's not so dramatic.

 

@deeveedee

 

Resetting the PRAM on a real Mac with OpenCore Legacy Patcher can be a bit

problematic, especcially if you are using a version which is not supported by OCLP.

 

Edited 1 hour ago by naquaada

[deeveedee]

17 minutes ago, naquaada said:

Resetting the PRAM on a real Mac with OpenCore Legacy Patcher can be a bit

problematic, especcially if you are using a version which is not supported by OCLP.

 

That might be true.  Why would you be booting Yosemite on a real Mac with OCLP?

 

I probably misunderstood what you said.  If so, my apologies.

Edited 52 minutes ago by deeveedee