Jump to content

Apple unveils OS X 10.11 "El Capitan"

fantomas

By fantomas,
in Front Page News and Rumors

 Share
178 posts in this topic

Recommended Posts

Guest
Guest
Posted
Posted

Sounds very low indeed, but I might have an explanation for that.

While monitoring the frequencies, I have seen that the GPU is not stepping up in Cinebench. It is doing so however in Valley for example, where I get decent results (Extreme HD is ~15-20% lower as Windows equivalent).

 

Could you tell me what settings you injected for SMBIOS? At least the 

As I have a 6-core i7 980, I am running as "MacPro5,1" currently. Are you using something more recent like iMac14,2 ?

 

Also, for Cinebench at least, the CPU frequency makes quite a difference (don't ask me why...).

What frequency is your CPU running? Are you doing overclocking ?

Link to comment
Share on other sites
JahStories
JahStories
Posted
Posted

come on super fast!

 

I think that yes, the processor makes the difference, but don't ask me why...

 

I'm running my 3.6 ghz processor at 4.2 ghz watercooled, temps are super low 27° idle, no more than 50° gaming

  • Like 1
Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

post-270804-0-58241500-1434072064_thumb.png

 

OK, so I am writing this on my El Cap partition.  That's a good thing.  I got past the KP's due to the AirPortBrcm4360.kext by removing the DSM method for my wifi in my DSDT.  I determined that I no longer have to make my wifi card compatible because the chipset is now.  I wish the same were true with my Bluetooth.  My Firmware injector is not working. Also, my VoodooHDA.kext is not working and it's the most current version.  I'm still using cpus=1 because I have an HP laptop and the Clover patch does not work with El Cap.  Lastly, my SMBIOS up until now has been MacBookPro9,2.  I cannot seem to boot with that SMBIOS for El Cap and have had to use the Clover default, MacBookAir5,2.  I'm hoping that does not mess up my ability to use Messages and FaceTime.  Wisely or unwisely, I have the same iCloud account for both partitions, Yos and El Cap.  Other than that, my experience with El Cap is basically positive.  I sure would like to get the debug mode enabled in Disk Utility but may just have to use Third-Party software for more advanced functions that older versions of Disk Utility with Debug mode enabled could handle.

 

Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

I was able to get sound to work by using VoodooHDA.kext version 2.8.5 instead of 2.8.8.  I installed it in S/L/E of El Cap because I am still using version 2.8.8 for Yosemite, which is in my EFI kexts.  Does anyone know if Clover will just use the kexts in a folder entitled 10.11 for El Cap?  So far, it hasn't made any difference whether my EFI kexts are in a folder called 10.10 or 10.11.  When that is functioning, I can take my VoodooHDA kext out of S/L/E and put it into my EFI partition in a 10.11 folder.  Next project is to get Bluetooth working.

  • Like 1
Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

I was able to get sound to work by using VoodooHDA.kext version 2.8.5 instead of 2.8.8.  I installed it in S/L/E of El Cap because I am still using version 2.8.8 for Yosemite, which is in my EFI kexts.  Does anyone know if Clover will just use the kexts in a folder entitled 10.11 for El Cap?  So far, it hasn't made any difference whether my EFI kexts are in a folder called 10.10 or 10.11.  When that is functioning, I can take my VoodooHDA kext out of S/L/E and put it into my EFI partition in a 10.11 folder.  Next project is to get Bluetooth working.

 

Same here on Gigabyte GA-H97-HD3. VoodooHDA 2.8.8d1 works fine at install but fail to load on next boot. I tried both in S/L/E & EFI/EFI/Clover/kexts/10.11 but no way. VoodooHDA 2.8.4 & AppleHDADisabler.kext works fine in EFI/EFI/Clover/kexts/10.11

 

So yes, Clover r3224 knows and uses 10.11 folder :

9:750  0:004  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.11
9:752  0:001    Extra kext: EFI\CLOVER\kexts\10.11\RealtekRTL8111.kext
9:759  0:006    Extra kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext
9:764  0:004      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
9:767  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
9:771  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext
9:786  0:015      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext
9:794  0:007    Extra kext: EFI\CLOVER\kexts\10.11\VoodooHDA.kext
9:807  0:012    Extra kext: EFI\CLOVER\kexts\10.11\AppleHDADisabler.kext
  • Like 1
Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

 

Same here on Gigabyte GA-H97-HD3. VoodooHDA 2.8.8d1 works fine at install but fail to load on next boot. I tried both in S/L/E & EFI/EFI/Clover/kexts/10.11 but no way. VoodooHDA 2.8.4 & AppleHDADisabler.kext works fine in EFI/EFI/Clover/kexts/10.11

 

So yes, Clover r3224 knows and uses 10.11 folder :

9:750  0:004  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.11
9:752  0:001    Extra kext: EFI\CLOVER\kexts\10.11\RealtekRTL8111.kext
9:759  0:006    Extra kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext
9:764  0:004      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
9:767  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
9:771  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext
9:786  0:015      Extra PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext
9:794  0:007    Extra kext: EFI\CLOVER\kexts\10.11\VoodooHDA.kext
9:807  0:012    Extra kext: EFI\CLOVER\kexts\10.11\AppleHDADisabler.kext

 

Yeah, I figured that out shortly after I made the post above.  However, I tried putting VoodooHDA.kext version 2.8.8 in the 10.10 folder and version 2.8.5 in the 10.11 folder and I got a KP when trying to boot El Cap and I lost sound in Yosemite.  When I removed version 2.8.5 from 10.11 and put it back in El Cap's S/L/E, everything went back to normal, so there must be something going on in Clover that is not yet right. I'm sure it will all get sorted out in time.

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

What revision of Clover are you using ? There's must be somtething wrong cause I don't have any problem when booting back to Yosemite. Make sure you also use AppleHDADisabler.kext to prevent KP.

 

Clover automatically detects it as 10.10 and loads the appropriates kexts :

11:765  0:004  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
11:776  0:011    Extra kext: EFI\CLOVER\kexts\10.10\RealtekRTL8111.kext
11:810  0:033    Extra kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext
11:818  0:007      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
11:822  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
11:825  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext
11:829  0:004      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext
11:837  0:007    Extra kext: EFI\CLOVER\kexts\10.10\realtekALC.kext

I also made different "kexts to patch" settings int he GUI section for Yosemite and El Capitan so the AppleHDA Clover patch + realtekALC.kext does not applies when booting OS X 10.11.

 

See attached screenshots :

post-1163891-0-27647900-1434141150_thumb.png

post-1163891-0-34890600-1434141152_thumb.png

Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

What revision of Clover are you using ? There's must be somtething wrong cause I don't have any problem when booting back to Yosemite. Make sure you also use AppleHDADisabler.kext to prevent KP.

 

Clover automatically detects it as 10.10 and loads the appropriates kexts :

11:765  0:004  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
11:776  0:011    Extra kext: EFI\CLOVER\kexts\10.10\RealtekRTL8111.kext
11:810  0:033    Extra kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext
11:818  0:007      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
11:822  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
11:825  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext
11:829  0:004      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext
11:837  0:007    Extra kext: EFI\CLOVER\kexts\10.10\realtekALC.kext

I also made different "kexts to patch" settings int he GUI section for Yosemite and El Capitan so the AppleHDA Clover patch + realtekALC.kext does not applies when booting OS X 10.11.

 

See attached screenshots :

 

I'm using Clover 3215.  I have separate config files for Yosemite and El Cap because I need different DSDT's for each installation.  Once I can get past the LAPIC kp that most HP laptops get without a kernel patch, I will switch to El Cap and won't need the two DSDT's.  But then, I won't need your method either.

 

BTW, I got Bluetooth working by installing a kext for my Bluetooth card in S/L/E that I found on this site.  The handoff patch for Yosemite does not appear to work for El Cap.  I'm sure a new patch will come out once someone finds the new location for the code that needs patching.

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

I'm sure a new patch will come out once someone finds the new location for the code that needs patching.

 

Have you tried the patch proposed by lisai9093 ?

 

And you should really try Clover r3224. I'm not sure but this could fix the "OS detection" issue you met :D.

 

BTW, could you tell how you do that : "I have separate config files for Yosemite and El Cap because I need different DSDT's for each installation" ?

 

I'd like to do the same but since I have only one EFI partition with Clover to manage all my OS, I can't figure how to do this :unsure:…

Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

Have you tried the patch proposed by lisai9093 ?

 

And you should really try Clover r3224. I'm not sure but this could fix the "OS detection" issue you met :D.

 

BTW, could you tell how you do that : "I have separate config files for Yosemite and El Cap because I need different DSDT's for each installation" ?

 

I'd like to do the same but since I have only one EFI partition with Clover to manage all my OS, I can't figure how to do this :unsure:…

 

I tried lisai9093's new handoff patch without success.  It may be due to the modded IOBluetoothFamily.kext I'm using.  I prefer to inject the firmware with a separate kext rather than to modify the apple kext but that is a project for another day.

 

I am slow to get new builds of Clover so I haven't seen any links for Clover r3224.  3215 is the newest one I have seen.

 

Having separate config files for Yosemite and El Cap is super-easy.  Right next to my config.plist file is a file called config2.plist.  When I boot to Clover, I select options and the first option is to select the config.plist.  The default is "config" so I just type "2" at the end and it calls up that config.  For me, I have different boot args, a different DSDT, which I call DSDT2.aml (it sits next to my DSDT.aml in ACPI/Patched, and now I have different Handoff patches (even if the patch for El Cap isn't working yet.)

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted
I am slow to get new builds of Clover so I haven't seen any links for Clover r3224.  3215 is the newest one I have seen.

 

Having separate config files for Yosemite and El Cap is super-easy.  Right next to my config.plist file is a file called config2.plist.  When I boot to Clover, I select options and the first option is to select the config.plist.  The default is "config" so I just type "2" at the end and it calls up that config.  For me, I have different boot args, a different DSDT, which I call DSDT2.aml (it sits next to my DSDT.aml in ACPI/Patched, and now I have different Handoff patches (even if the patch for El Cap isn't working yet.)

 

 

See here for Clover r3224.

 

Thanks for the config.plist tip but I know that. Actually, I was asking if there's a way to load a specific config.plist automatically depending of what OS Clover detects.

 

In exemple :

Loads config1.plist if Clover detects Mavericks, loads config2.plist if it's Yosemite, loads config3.plist if it's El Capitan etc.

Link to comment
Share on other sites
crusher
crusher
Posted
Posted

Hi there!

 

Someone in OS X El Capitan have problem with nsurlstoraged process?

 

Thanks

Like this:

Jun 13 10:05:28 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/root/Library/Caches/com.apple.QuickLookDaemon
Jun 13 10:05:28 Crushers-iMac nsurlstoraged[299]: The read-connection to the DB=/var/root/Library/Caches/com.apple.QuickLookDaemon/Cache.db is NOT valid.  Unable to determine schema version.
Jun 13 10:05:28 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/root/Library/Caches/com.apple.QuickLookDaemon
Jun 13 10:05:28 Crushers-iMac nsurlstoraged[299]: ERROR: unable to determine file-system usage for FS-backed cache at /var/root/Library/Caches/com.apple.QuickLookDaemon/fsCachedData. Errno=13
Jun 13 10:05:32 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/root/Library/Caches/ocspd
Jun 13 10:05:32 Crushers-iMac nsurlstoraged[299]: The read-connection to the DB=/var/root/Library/Caches/ocspd/Cache.db is NOT valid.  Unable to determine schema version.
Jun 13 10:05:32 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/root/Library/Caches/ocspd
Jun 13 10:05:32 Crushers-iMac nsurlstoraged[299]: ERROR: unable to determine file-system usage for FS-backed cache at /var/root/Library/Caches/ocspd/fsCachedData. Errno=13
Jun 13 10:05:45 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/db/locationd/Library/Caches/com.apple.locationd
Jun 13 10:05:45 Crushers-iMac nsurlstoraged[299]: The read-connection to the DB=/var/db/locationd/Library/Caches/com.apple.locationd/Cache.db is NOT valid.  Unable to determine schema version.
Jun 13 10:05:45 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/db/locationd/Library/Caches/com.apple.locationd
Jun 13 10:05:45 Crushers-iMac nsurlstoraged[299]: ERROR: unable to determine file-system usage for FS-backed cache at /var/db/locationd/Library/Caches/com.apple.locationd/fsCachedData. Errno=13
Jun 13 10:38:26 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/root/Library/Caches/ocspd
Jun 13 10:38:26 Crushers-iMac nsurlstoraged[299]: The read-connection to the DB=/var/root/Library/Caches/ocspd/Cache.db is NOT valid.  Unable to determine schema version.
Jun 13 10:38:26 Crushers-iMac nsurlstoraged[299]: realpath() returned NULL for /var/root/Library/Caches/ocspd
Jun 13 10:38:26 Crushers-iMac nsurlstoraged[299]: ERROR: unable to determine file-system usage for FS-backed cache at /var/root/Library/Caches/ocspd/fsCachedData. Errno=13
Link to comment
Share on other sites
Frank Nitty
Frank Nitty
Posted
Posted

 

I call it Yosemite 2.0   :P

SL was what Leopard should have been

ML was what Lion should have been

Mavericks was and still is what it should have been

El Capitan is what Yosemite should have been

basically it's comparable to windows 7's absolution for vista and window 10's 'supposed' absolution for windows 8?

  • Like 2
Link to comment
Share on other sites
MattsCreative
MattsCreative
Posted
Posted

basically it's comparable to windows 7's absolution for vista and window 10's 'supposed' absolution for windows 8?

windows 10 is what 7 should have been and windows 8.1 was what 8 should have been and longhorn was what vista should have been 

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...