Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.12 Sierra Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Sedulous said:
I understand that concern. However, signing a kext someone made isn't hacking macOS. Even specifically in this case, adding a USB driver to the system does not seem to be a violation. The only thing Apple could say is they don't like how dosdude1 used a kext that "you" posted somewhere. What dosdude1 does with it isn't your problem.
[doublepost=1486550979][/doublepost]
Yes, but those kexts are not critical. Loss of USB is serious and complicates recovery. It would be great if someone could sign at least the USB.kext... I have thought about signing up for a dev license (it is $99) but I'd have no use for it other than this project.
Click to expand...

You need more than just an Apple Developer subscription, kernel extensions are vetted through a separate process for which you must contact Apple about the purpose of the extension before getting a cert, as noted in https://developer.apple.com/contact/kext
 
Last edited:
  • Like
Reactions: Codewarrior77
foxlet said:
You need more than just an Apple Developer subscription, kernel extensions are vetted through a separate process for which you must contact Apple about the purpose of the extension before getting a cert, as noted in https://developer.apple.com/contact/kext
Click to expand...
If a person has the Command-Line Dev Tools installed, can you command-line compile and self-sign a KEXT? Does that pass muster with SIP?

(I'm just dangerous enough to be able to compile xprojs, but once it gets into the nitty-gritty intersection of "policy" and certificate-signing, it just gets weird. I sorta rather remember something doing with one of the Jailbreak apps for iOS and command-line self-signing however. I created a "special" Dev account at Apple to do it.)
 
gpatpandp said:
While it is apparent that for this poster, just finding a working solution was the primary objective, after researching other alternatives, I wanted to share a much more simpler/inexpensive internal Wi-Fi replacement for the BCM94321MC Card in macOS Sierra.

For exactly $4 US dollars Total (included both the card & shipping), I picked up a Atheros AR5BXB92 (Apple Part #: 607-3758-A) and simply unscrewed the T6 fastener screw, detached the two (2) Wi-Fi connector cables, and removed the unsupported BCM4321. I then installed the Atheros AR5BXB92 in the very same socket, reconnected the cables, and tightened the same T6 screw (which aligned perfectly), closed up the 24" iMac 8,1 A1225 case and done.
Click to expand...


Does your card support 802.11ac and Bluetooth 4.0?
[doublepost=1486603107][/doublepost]I think Im going to try something. Right now, I am using Clover Bootloader with a smbios that makes my 2007 iMac think its a late 2013 so that Night Shift works natively.
2007 iMacs only support CPU's with a 800 FSB. Im wondering if now that it thinks it is a later iMac, will it boot with a cpu that has a 1066 FSB
 
nandor690 said:
Does your card support 802.11ac and Bluetooth 4.0?
[doublepost=1486603107][/doublepost]I think Im going to try something. Right now, I am using Clover Bootloader with a smbios that makes my 2007 iMac think its a late 2013 so that Night Shift works natively.
2007 iMacs only support CPU's with a 800 FSB. Im wondering if now that it thinks it is a later iMac, will it boot with a cpu that has a 1066 FSB
Click to expand...
No, the chipset doesn't support CPUs with a 1066MHz FSB, and therefore will not start up whatsoever.
 
gpatpandp said:
While it is apparent that for this poster, just finding a working solution was the primary objective, after researching other alternatives, I wanted to share a much more simpler/inexpensive internal Wi-Fi replacement for the BCM94321MC Card in macOS Sierra.

For exactly $4 US dollars Total (included both the card & shipping), I picked up a Atheros AR5BXB92 (Apple Part #: 607-3758-A) and simply unscrewed the T6 fastener screw, detached the two (2) Wi-Fi connector cables, and removed the unsupported BCM4321. I then installed the Atheros AR5BXB92 in the very same socket, reconnected the cables, and tightened the same T6 screw (which aligned perfectly), closed up the 24" iMac 8,1 A1225 case and done.
Click to expand...
I did a little research. The card you are using does not support 802.11ac OR bluetooth 4.0. So..... While it is apparent that for this poster (you), just finding the cheapest solution was the primary objective, while for some of us we are looking for functionality. So keep your condescending comments and your useless N card to yourself. Thanks!
[doublepost=1486605835][/doublepost]
dosdude1 said:
No, the chipset doesn't support CPUs with a 1066MHz FSB, and therefore will not start up whatsoever.
Click to expand...
Thanks thanks for the info
 
Anyone know off hand which kext l need to look at for iSight camera not working on 10.12.4 beta 1 or 2? The camera shows up in Hardware but does not turn on. Im doing research but wanted to get input from here as well. Will post back what I find in case it helps someone else.
 
ScooterComputer said:
If a person has the Command-Line Dev Tools installed, can you command-line compile and self-sign a KEXT? Does that pass muster with SIP?

(I'm just dangerous enough to be able to compile xprojs, but once it gets into the nitty-gritty intersection of "policy" and certificate-signing, it just gets weird. I sorta rather remember something doing with one of the Jailbreak apps for iOS and command-line self-signing however. I created a "special" Dev account at Apple to do it.)
Click to expand...

No, the system only recognizes Apple's kext root certs as a valid parent (alongside hash-based exceptions). You still have to disable SIP.
 
fischersd said:
You don't think Apple has employees participating in these forums? Any dev signing kexts and distributing them to get around Apple's policies on which systems are supported would not only lose their license, but likely be blacklisted.
Click to expand...
I do think some Apple employees must visit here since periodically macrumors posts about unreleased builds hitting the site. However I do not see why Apple would reject a driver signing request since it meets the standard for kernel environment inclusion and presumably is not malicious in nature. The legacyUSBinjector.kext (or whatever name it gets submitted with) could be used by a developer looking to drive some USB connection to some hardware they are developing. Why would Apple object?
 
Sedulous said:
I do think some Apple employees must visit here since periodically macrumors posts about unreleased builds hitting the site. However I do not see why Apple would reject a driver signing request since it meets the standard for kernel environment inclusion and presumably is not malicious in nature. The legacyUSBinjector.kext (or whatever name it gets submitted with) could be used by a developer looking to drive some USB connection to some hardware they are developing. Why would Apple object?
Click to expand...
They'd have to have some pretty specific reasons why they want to alter and sign one of Apple's existing kexts. Apple doesn't exactly have a sense of humour about things like this. Pleading ignorance after they discover it's being used to keep unsupported macs running wouldn't buy you anything.
The only person that should gamble in this way is someone that doesn't actually want a dev license - go ahead and gamble your $100. People that rely on that for their livelihood would be pretty foolish to do so.
 
We
fischersd said:
They'd have to have some pretty specific reasons why they want to alter and sign one of Apple's existing kexts. Apple doesn't exactly have a sense of humour about things like this. Pleading ignorance after they discover it's being used to keep unsupported macs running wouldn't buy you anything.
The only person that should gamble in this way is someone that doesn't actually want a dev license - go ahead and gamble your $100. People that rely on that for their livelihood would be pretty foolish to do so.
Click to expand...

We requested the kext signing ability to drive some custom designed hardwares, and i don't wan't to risk that dev account and current partnership with Apple (mFI membership, developer membership with kext signing). Anyone can request kext signing with a simple form submit for thier dev account.
 
WARNING!!!

I haven't seen if this has been posted anywhere, but after upgrading my MBP 15" mid-2009 (a model with hardware that is apparently fully supported even though it has been blacklisted on the official list) I have had two instances where the keyboard and trackpad have become unresponsive at the login window for no apparent reason after many many weeks of working flawlessly. Just out of the blue, I reboot the Mac, and the input devices don't work and the cursor is frozen in the top left corner of the screen (I don't have an external USB keyboard or mouse, so I wasn't able to see if that made a difference).

I have tried every Mac secret keypress I can do to get it to work (reset PMU, NVRAM, single user mode, etc...). You name it. Nothing could get it working again and the keyboard wouldn't even work in single user mode. However, if I booted into Recovery or another boot disk it was fine (not a hardware issue). The only way to fix it was to completely reinstall OS X.

Now that this has happened twice with Sierra, and has never ever happened on this Mac with any previous version of OS X, I am permanently downgrading to El Capitan.

Has anyone else had this happen and did you find a fix?

Thanks!
 
bbbggg said:
WARNING!!!

I haven't seen if this has been posted anywhere, but after upgrading my MBP 15" mid-2009 (a model with hardware that is apparently fully supported even though it has been blacklisted on the official list) I have had two instances where the keyboard and trackpad have become unresponsive at the login window for no apparent reason after many many weeks of working flawlessly. Just out of the blue, I reboot the Mac, and the input devices don't work and the cursor is frozen in the top left corner of the screen (I don't have an external USB keyboard or mouse, so I wasn't able to see if that made a difference).

I have tried every Mac secret keypress I can do to get it to work (reset PMU, NVRAM, single user mode, etc...). You name it. Nothing could get it working again and the keyboard wouldn't even work in single user mode. However, if I booted into Recovery or another boot disk it was fine (not a hardware issue). The only way to fix it was to completely reinstall OS X.

Now that this has happened twice with Sierra, and has never ever happened on this Mac with any previous version of OS X, I am permanently downgrading to El Capitan.

Has anyone else had this happen and did you find a fix?

Thanks!
Click to expand...

Sometimes in the past you cleared NVRAM or enabled SIP. OS X regenerated prelinkedkernel before you reboot and the new prelinkedkernel can't contain the legacy usb support kext (because it is not signed). You need to boot recovery and run a terminal and disable SIP with csrutil and remove the prelinkedkernel from /System/Library/PrelinkedKernels and and touch the /System/Library/Extensions folder to recreate prelinkedkernel. I can't write the full commands currently because i'am from iPad. You need someone else for the details or need to figure out myself or wait for me because afternoon (in CEST timezone) i can help with complete commands.
 
2007 20" iMac. I can report that with 10.12.4 beta 1 and 2 iSight does not work. it is listed in hardware but doesn't come on with FaceTime or anything
 
Czo said:
Did you installed VirtualBox? Still not working after a complete power cycle? (poweroff and power back on, not reset!)
Click to expand...
Yeah iv tried all that. I reinstalled 10.12.3 and it works fine. its only when I update to 10.12.4 beta 1 or 2. Something had to of changed in a kext between 12.3 and 12.4. It seems weird that they would do it then.

NOTE: I do use clover to make my iMac think its a late 2013 so Night Shift will work. BUT, the iSight camera does not work either way, Using clover OR booting natively.

Thanks for the reply
 
nandor690 said:
Yeah iv tried all that. I reinstalled 10.12.3 and it works fine. its only when I update to 10.12.4 beta 1 or 2. Something had to of changed in a kext between 12.3 and 12.4. It seems weird that they would do it then.

NOTE: I do use clover to make my iMac think its a late 2013 so Night Shift will work. BUT, the iSight camera does not work either way, Using clover OR booting natively.

Thanks for the reply
Click to expand...

Clover not required to enable night shift, simply patching the required library can be enable it on anything. Have you any other UVC compatible webcam and can you try it?
 
Czo said:
Clover not required to enable night shift, simply patching the required library can be enable it on anything. Have you any other UVC compatible webcam and can you try it?
Click to expand...
Which library? Iv tried other things but could never get it to work. And no, I don't have any other camera
 
nandor690 said:
I did a little research. The card you are using does not support 802.11ac OR bluetooth 4.0. So..... While it is apparent that for this poster (you), just finding the cheapest solution was the primary objective, while for some of us we are looking for functionality. So keep your condescending comments and your useless N card to yourself. Thanks!
[doublepost=1486605835][/doublepost]
Thanks thanks for the info
Click to expand...

Geez...the climate in this forum seems to be SO overwhelmingly volatile. I am sitting here trying to comprehend how on earth you twisted and distorted my stating the fact that you effectively accomplshed finding a solution that works well for you into something offensive/condescending. Nonetheless the fact you had no issue whatsoever in taking a completely over the top offensive stance via your reply speaks volumes.

Anyway, rest assure that my only intent was to share a simple/affordable alternative to a common issue that has been frequently discussed within this forum...no more, no less.
 
Last edited:
RafaelMac said:
[doublepost=1486457517][/doublepost]also having a issue searching updates with asu seed on (latest)
edit: sorry for Dutch ;)
Click to expand...

I'm having the same problem. Anyone found a solution yet?

For example the iTunes 12.5.5 update is not appearing in software update. When I do a manual search in iTunes it says there's an update but when I click update an error occurs...

Thanks!

Dave
 
Czo said:
https://pikeralpha.wordpress.com/2017/01/30/4398/
Click to expand...
iv seen that. I got the offset and the dump but when I tried to edit the iMac section it causes display preferences to crash system preferences when I click on it
https://www.tonymacx86.com/threads/...rebrightness-macos-10-12.213764/#post-1435420
[doublepost=1486660939][/doublepost]
gpatpandp said:
Geez...the climate in this forum seems to be SO overwhelmingly volatile. I am sitting here trying to comprehend how on earth you twisted and distorted my stating the fact that you effectively accomplshed finding a solution that works well for you into something offensive/condescending. Nonetheless the fact you had no issue whatsoever in taking a completely over the top offensive stance via your reply speaks volumes.

Anyway, rest assure that my only intent was to share a simple/affordable alternative to a common issue that has been frequently discussed within this forum...no more, no less.
Click to expand...
It must have been the way you worded it that caught me off guard. I apologize for taking it the wrong way
 
nandor690 said:
iv seen that. I got the offset and the dump but when I tried to edit the iMac section it causes display preferences to crash system preferences when I click on it
https://www.tonymacx86.com/threads/...rebrightness-macos-10-12.213764/#post-1435420
[doublepost=1486660939][/doublepost]
It must have been the way you worded it that caught me off guard. I apologize for taking it the wrong way
Click to expand...

And just for the record, I believe that if it is an individuals intent to upgrade to both 802.11ac and Bluetooth 4.0, that your provided suggestion is a good one.
 
  • Like
Reactions: nandor690
fischersd said:
They'd have to have some pretty specific reasons why they want to alter and sign one of Apple's existing kexts. Apple doesn't exactly have a sense of humour about things like this. Pleading ignorance after they discover it's being used to keep unsupported macs running wouldn't buy you anything.
The only person that should gamble in this way is someone that doesn't actually want a dev license - go ahead and gamble your $100. People that rely on that for their livelihood would be pretty foolish to do so.
Click to expand...
I think you may not be familiar with the process. You do not need "specific reasons" to have a kext sign request. It simply needs to be a driver used by the system or be something that needs to run for many users.
 
Czo said:
Sometimes in the past you cleared NVRAM or enabled SIP. OS X regenerated prelinkedkernel before you reboot and the new prelinkedkernel can't contain the legacy usb support kext (because it is not signed). You need to boot recovery and run a terminal and disable SIP with csrutil and remove the prelinkedkernel from /System/Library/PrelinkedKernels and and touch the /System/Library/Extensions folder to recreate prelinkedkernel. I can't write the full commands currently because i'am from iPad. You need someone else for the details or need to figure out myself or wait for me because afternoon (in CEST timezone) i can help with complete commands.
Click to expand...

Thanks! Yes please do reply with the full instructions on how to fix this. I would like to upgrade back to Sierra but only if I can be sure how to fix this problem if / when it happens again.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back