- Joined
- Jul 26, 2012
- Messages
- 36
- Motherboard
- P8P67 Pro
- CPU
- i5 2500K
- Graphics
- Radeon 6850
- Mac
-
- Classic Mac
-
- Mobile Phone
-
After many hours of trying all sorts of voodoo, I have finally, RELIABLY, gotten iMessage working on my Hackintosh—and I think I've figured out a piece of the puzzle that I have not read anywhere else during my research.
Simply, there is an incompatibility between how the FileNVRAM fix works, and how OS X RAID 0 needs to use the Boot OS X partition and kernelcache. While iMessage CAN WORK on a system that is booting from an OS X RAID volume, I have deduced that you cannot SET IT UP from scratch while booted from RAID.
I noticed that when putting the FileNVRAM dynlib into Extra/Modules on the Boot OS X partition, successive boots never actually CREATED the NVRAM file in Extra on the Boot OS X partition. It did, however, create it in Extra on the main data volume. But then this would never get loaded on subsequent boots, since booting from RAID looks to the Boot OS X partition. You can copy it over, but it won't help. I think there needs to be continuous access/communication.
Additionally, it seems that FileNVRAM needs to boot with usekernelcache=no in order to work, however RAID boot currently needs usekernelcache=yes in order to work. Not compatible.
I fixed it by cloning my RAID volume to a single drive, booting into that, then following all the voodoo here:
http://www.tonymacx86.com/general-help/110471-how-fix-imessage.html
It was simple getting iMessage working when booted to the single drive by following the detailed instructions on that post, however trust me... following all that stuff while booted in RAID does NOT work. In fact, I followed all those instructions while booted in RAID (no go), and then just cloned it to a single drive and it worked.
It's important to note that there were some slight changes needed to get my RAID volume booted in USB (i.e., different chameleon.plist boot args, but most everyone here knows that, of course... important is changing usekernelcache to NO, and removing the UUID identifier to boot from the RAID).
I then cloned the working single drive back to the RAID, recopied the created FileNVRAM file back to the Boot OS X partitions on the RAID, and booted the RAID.
iMessage and iCloud now work.
BUT, if you ever get disconnected or logout or whatever, you will have to go back through these steps.
I am of the opinion that FileNVRAM dynlib needs to be fixed so that it can run from/access/whatever the Boot OS X partition. No doubt, Chimera (and Chameleon) need to be changed too? Uncertain. But I am very certain that there is some incompatibility surrounding FileNVRAM, RAID, and using the kernel cache.
Thoughts??
Simply, there is an incompatibility between how the FileNVRAM fix works, and how OS X RAID 0 needs to use the Boot OS X partition and kernelcache. While iMessage CAN WORK on a system that is booting from an OS X RAID volume, I have deduced that you cannot SET IT UP from scratch while booted from RAID.
I noticed that when putting the FileNVRAM dynlib into Extra/Modules on the Boot OS X partition, successive boots never actually CREATED the NVRAM file in Extra on the Boot OS X partition. It did, however, create it in Extra on the main data volume. But then this would never get loaded on subsequent boots, since booting from RAID looks to the Boot OS X partition. You can copy it over, but it won't help. I think there needs to be continuous access/communication.
Additionally, it seems that FileNVRAM needs to boot with usekernelcache=no in order to work, however RAID boot currently needs usekernelcache=yes in order to work. Not compatible.
I fixed it by cloning my RAID volume to a single drive, booting into that, then following all the voodoo here:
http://www.tonymacx86.com/general-help/110471-how-fix-imessage.html
It was simple getting iMessage working when booted to the single drive by following the detailed instructions on that post, however trust me... following all that stuff while booted in RAID does NOT work. In fact, I followed all those instructions while booted in RAID (no go), and then just cloned it to a single drive and it worked.
It's important to note that there were some slight changes needed to get my RAID volume booted in USB (i.e., different chameleon.plist boot args, but most everyone here knows that, of course... important is changing usekernelcache to NO, and removing the UUID identifier to boot from the RAID).
I then cloned the working single drive back to the RAID, recopied the created FileNVRAM file back to the Boot OS X partitions on the RAID, and booted the RAID.
iMessage and iCloud now work.
BUT, if you ever get disconnected or logout or whatever, you will have to go back through these steps.
I am of the opinion that FileNVRAM dynlib needs to be fixed so that it can run from/access/whatever the Boot OS X partition. No doubt, Chimera (and Chameleon) need to be changed too? Uncertain. But I am very certain that there is some incompatibility surrounding FileNVRAM, RAID, and using the kernel cache.
Thoughts??
