Jump to content
fantomas1

Apple unveils "macOS Sierra"

408 posts in this topic

Recommended Posts

Advertisement

Working on my Asus H97M-E/CSM mobo. Problem is how to install Apps not downloaded from App Store as the option "Install from anywhere" is no longer available. Any workaround?

Share this post


Link to post
Share on other sites

Anyone here could test the old AppleHDA Patcher

I made a small change in the script bcc9 for
to support 10.12.

I got this , (ALC892

EDIT : I got sound using  AppleALC.kext from page 8 but no Mic

Number found where operator expected at ./patch-hda.pl line 147, near "0x11d4198b"
	(Missing semicolon on previous line?)
syntax error at ./patch-hda.pl line 147, near "0x11d4198b"
Execution of ./patch-hda.pl aborted due to compilation errors.
Copying README file
Creating zip file
Done.

Share this post


Link to post
Share on other sites

 

I got this , (ALC892

EDIT : I got sound using  AppleALC.kext from page 8 but no Mic

Number found where operator expected at ./patch-hda.pl line 147, near "0x11d4198b"
	(Missing semicolon on previous line?)
syntax error at ./patch-hda.pl line 147, near "0x11d4198b"
Execution of ./patch-hda.pl aborted due to compilation errors.
Copying README file
Creating zip file
Done.

@Mirone you are missing comma at line 146 

post-1425204-0-41615400-1466069543_thumb.png

so i added and updated your app AppleHDAPatcher.zip

 

@ham4ever try this 

Share this post


Link to post
Share on other sites

@Mirone you are missing comma at line 146 

attachicon.gifScreen Shot 2016-06-16 at 3.01.37 PM.png

so i added and updated your app attachicon.gifAppleHDAPatcher.zip

 

@ham4ever try this 

but I figured it out yesterday but was already late at night,
why I did check the ID's
in binary of AppleHDA using a Hex editor
on windows ({censored}) program.

Share this post


Link to post
Share on other sites

 

but I figured it out yesterday but was already late at night,
why I did check the ID's
in binary of AppleHDA using a Hex editor
on windows ({censored}) program.

 

that's why i hate windows 

i can confirm that binary patching is doing good as required , i check in using HexFiend ..

Share this post


Link to post
Share on other sites

that's why i hate windows 

i can confirm that binary patching is doing good as required , i check in using HexFiend ..

you come to test the old AppleHDA Patcher?
an update of the new version made by me and Micky this
for coming.

Share this post


Link to post
Share on other sites

Here it is guys, a working VoodooPS2Controller kext, RM patched it yesterday for Sierra as it seems, I'm using it atm (still need to use it on a clean OS as the AppleSmartTouchpad did some stuff, but it works). 

VoodooPS2Controller.kext.zip

 

https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads

Check here

Share this post


Link to post
Share on other sites

New VoodooPS2 works well. No more panic and no more jumpy mouse pointer with the other kext. Nice job RehabMan :)

 

Seems the Trackpad prefpane is broken in Sierra because it still doesn't load. In the Console there seems to be a conflict between it and the Mouse one.

Share this post


Link to post
Share on other sites

New VoodooPS2 works well. No more panic and no more jumpy mouse pointer with the other kext. Nice job RehabMan :)

 

Seems the Trackpad prefpane is broken in Sierra because it still doesn't load. In the Console there seems to be a conflict between it and the Mouse one.

I can confirm that too!

Share this post


Link to post
Share on other sites

I tried moving the Mouse prefpane out of it's folder (and deleting the prefpane cache) and the Trackpad pane still doesn't load. The warning is gone from the Console though. Guess they'll fix it later, assuming it's a bug and not something to do with our trackpads. I wonder if it's broken on Macs as well?

 

And now that we're slowing checking things off the list, is there a fix for the garbled bootscreen with HD4000? The old IOGraphicsFamily patch isn't working here for Sierra.

Share this post


Link to post
Share on other sites

I tried moving the Mouse prefpane out of it's folder (and deleting the prefpane cache) and the Trackpad pane still doesn't load. The warning is gone from the Console though. Guess they'll fix it later, assuming it's a bug and not something to do with our trackpads. I wonder if it's broken on Macs as well?

Mostly, but I think they mostly made it for their devices, I dont think apple would let this pass by even on DP1 release, so it should be on our part (maybe apple is making devices limitations now, locking the OS even more?)

 

Anyway, I found that the driver that I built from RM sources have a problem (bug?): I cannot make key combination that involves numbers (like Screenshot combination keys) and it outputs a letter for some reason.

 

---later this day---

 

Guys, why can't I rebuild caches on this thing! I need CodecCommander to work!

Share this post


Link to post
Share on other sites

Seems the Trackpad prefpane is broken in Sierra because it still doesn't load. In the Console there seems to be a conflict between it and the Mouse one.

Post output of console that shows this 'conflict'...

 

It may be time to create a special prefpane...

I tried moving the Mouse prefpane out of it's folder (and deleting the prefpane cache) and the Trackpad pane still doesn't load. The warning is gone from the Console though. Guess they'll fix it later, assuming it's a bug and not something to do with our trackpads. I wonder if it's broken on Macs as well?

It could be they removed support for the old trackpad prefpane, as it seems they plan on removing support for older Macs in this release...

Share this post


Link to post
Share on other sites

Anyway, I found that the driver that I built from RM sources have a problem (bug?): I cannot make key combination that involves numbers (like Screenshot combination keys) and it outputs a letter for some reason.

My guess is you're pressing number keys along with the ALT key, and you have the debug version installed.

 

It is not a bug.. it is a feature (it is for typing ADB codes directly for testing). Install Release kext.

Hey my IDT92HD87B1.zip not works :(

If you're patching 0x11d4198b, you need to zero out codec 0x11d4198a.

Share this post


Link to post
Share on other sites

My guess is you're pressing number keys along with the ALT key, and you have the debug version installed.

 

It is not a bug.. it is a feature (it is for typing ADB codes directly for testing). Install Release kext.

 

If you're patching 0x11d4198b, you need to zero out codec 0x11d4198a.

Woah! totally forgot that, but I'm building it from source, I only get the Debug version for some reason, What should I do to get the Release one?

 

EDIT: Just checked your Bitbucket, a new version has been released!

Share this post


Link to post
Share on other sites

Post output of console that shows this 'conflict'...

Jun 16 13:35:54 Sammy System Preferences[402]: objc[402]: Class AssetQuery is implemented in both /System/Library/PreferencePanes/Trackpad.prefPane/Contents/MacOS/Trackpad (0x109460090) and /System/Library/PreferencePanes/Mouse.prefPane/Contents/MacOS/Mouse (0x107b41310). One of the two will be used. Which one is undefined.
Jun 16 13:35:54 Sammy System Preferences[402]: objc[402]: Class BTDeviceManager is implemented in both /System/Library/PreferencePanes/Trackpad.prefPane/Contents/MacOS/Trackpad (0x109460770) and /System/Library/PreferencePanes/Mouse.prefPane/Contents/MacOS/Mouse (0x107b41720). One of the two will be used. Which one is undefined.

Share this post


Link to post
Share on other sites

Yes.

I want to confirm something: The volume buttons work on 10.11 but not on 10.12, I'm using the latest kext you provided on both. Can you check that up?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo

      View full article
×