macOS 10.12 Sierra Unsupported Macs Thread

[Carcode]

Urgent help needed: No trackpad, no keyboard, no Bluetooth anymore.

Situation: MBP 5,2 17" display, early 2009, running your wonderful patch with actually 10.12.3 since a long time, all OK, but now:
After starting again 12 hours ago the bluetooth gadget in the upper status bar shows no Bluetooth sign anymore but a ~ line, the trackpad and keyboard does not work anymore, they are dead.

Already done so far: NVRAM reset, SMC reset (battery removed and replaced). Start in safe mode doesn't work, repair harddrives in repair mode OK but no change, Boot into single user mode shows this lines:

localhost:/ root# 000004.590419 AppleBusPowerControllerUSB@: AppleBusPowerControllerUSB::requestServicePowerLocked: power supply unavailable, assuming successful power for PRT1 of 500 mWWakePower and 0 mWSleepPower

The line above repeated 10 times (each 2 times for PRT1 to PRT5)

Then 3 lines each with: SmartBattery: finished polling type 1
And then nothing anymore, no cursor, nothing...

Cannot restart but only with force of the power button switch off and after that the usual requester about a hard switch off without the possibility to start with or without the former running apps.

Trackpad and keyboard works in the apple repair mode (system not loaded and disk-repair, system-repair etc. available). So I assume not a hardware failure.

I don't want to switch back to El Capitain, any other choice?

Carcode

 

[virk]

I cannot be of much support, but of little and quick one. Can you start your terminal, type "csrutil status" and post the output here.

 

[Carcode]

I cannot be of much support, but of little and quick one. Can you start your terminal, type "csrutil status" and post the output here.

Thanks for the quick reply.
Actually I'm not even able to start in repair mode. My several attemps seems to invoke a harddisk evaluation.
Ah, just finished, it's there now:

Repair mode is the only way to start a Terminal. So the output is:
"System Integrity Protection status: enabled."

 

[virk]

As far as I know you can do the following:
- Start from your USB-stick, from which you installed Sierra
- Then start terminal and type in "csrutil disable" and hit 'Return'.
- Eventually apply mac-Sierra-post install (But I am not sure about this. Perhaps you also need to reboot from USB-stick a 2nd time)
- Then try to restart your machine
- Report whether it has worked

 

[Carcode]

As far as I know you can do the following:
- Start from your USB-stick, from which you installed Sierra
- Then start terminal and type in "csrutil disable" and hit 'Return'.
- Eventually apply mac-Sierra-post install (But I am not sure about this. Perhaps you also need to reboot from USB-stick a 2nd time)
- Then try to restart your machine
- Report whether it has worked

Thanks again, but I cannot start from the USB-Stick. It is not shown when leaving the repair mode to start over. Nor it is shown when trying to start with the C key pressed. It seems I'm blocked now.

 

[virk]

You could try to restart your computer with the USB-stick being put into the computer. Directly press "alt"-key and then you perhaps can chose the stick for to boot from.

P.S.: Where from Germany you are. I am from Aachen

 

[dosdude1]

Thanks for the quick reply.
Actually I'm not even able to start in repair mode. My several attemps seems to invoke a harddisk evaluation.
Ah, just finished, it's there now:

Repair mode is the only way to start a Terminal. So the output is:
"System Integrity Protection status: enabled."

That's your issue... SIP needs to be disabled and the post-install patch needs to be re-run (or, at least, the kextcache needs to be rebuilt).

 

[Carcode]

Yes. thanks.
Unfortunately the stick is not formated to boot. I try make one.
I'm in Hannover.

 

[virk]

You can take the same thick from which you installed Sierra.

 

[Carcode]

That's your issue... SIP needs to be disabled and the post-install patch needs to be re-run (or, at least, the kextcache needs to be rebuilt).

Thanks.
But why this had happened? All has run OK since several weeks and suddenly SIP enabled?
[doublepost=1486308250][/doublepost]

You can take the same thick from which you installed Sierra.

I will do, but actually it is not bootable. Must make a new one first.

 

[virk]

I think/believe SIP is enabled after starting with cmd-alt-p-r. Most probably there are also more possibilities to reenable SIP.
Perhaps you experienced your problem concerning Bluetooth and USB and your "repair activities" made it even worse

 

[Carcode]

I think/believe SIP is enabled after starting with cmd-alt-p-r. Most probably there are also more possibilities to reenable SIP.
Perhaps you experienced your problem concerning Bluetooth and USB and your "repair activities" made it even worse

I guess so. The repair activities makes it worse but has started AFTER trackpad and keyboard has gone.

 

[virk]

On page 168 of this thread user "thephdj" reported similar problem to yours. Maybe this is helpful for you, somehow.

 

[Carcode]

On page 168 of this thread user "thephdj" reported similar problem to yours. Maybe this is helpful for you, somehow.

Yes, thanks. This is the same problem. Will be a nice evening today for me...

 

[dosdude1]

Yes, thanks. This is the same problem. Will be a nice evening today for me...

All you need to do is make sure SIP is disabled, and re-run the post-install patch with Force Cache Rebuild selected before rebooting.

 

[Carcode]

All you need to do is make sure SIP is disabled, and re-run the post-install patch with Force Cache Rebuild selected before rebooting.

Yes, thank you.
First I have re-animated my partition with El Capitan. Then I will try to start Sierra again at the other partition.

Start-partition El Capitan works. SIP is disabled. But starting the Sierra partition there is still no trackpad and no keyboard. So how to run the post-install patch when I'm unable to open a Terminal or type something ?

 

[virk]

You need to start from your patched Sierra-USB-Stick and not from Sierra. Did you do that and do not have access to keyboard? In this case I do not know what to do. Perhaps a usb mouse can help; but I do not know.

 

[Carcode]

You need to start from your patched Sierra-USB-Stick and not from Sierra. Did you do that and do not have access to keyboard? In this case I do not know what to do. Perhaps a usb mouse can help; but I do not know.

Yes, I know but I can't. I do have an USB mouse as well as an USB keyboard from the iMac. But both are dead as well when connected to the MBP and starting the Sierra partition. Other ways are blocked also: There is a TimeMachine available via WiFi, there is an extern Thunderbolt harddrive and so on. Thank you anywhere for your help.

 

[Czo]

Yes, I know but I can't. I do have an USB mouse as well as an USB keyboard from the iMac. But both are dead as well when connected to the MBP and starting the Sierra partition. Other ways are blocked also: There is a TimeMachine available via WiFi, there is an extern Thunderbolt harddrive and so on. Thank you anywhere for your help.

Disable SIP from recovery (why you turned it on?) and remove prelinkedkernel from /System/Library/PrelinkedKernels, and touch /System/Library/Extensions to create a new prelinkedkernel. Maybe a reboot is required after sip status change.

 

[Carcode]

Disable SIP from recovery (why you turned it on?) and remove prelinkedkernel from /System/Library/PrelinkedKernels, and touch /System/Library/Extensions to create a new prelinkedkernel. Maybe a reboot is required after sip status change.

I will try this later in the afternoon today and will report the result. Thanks

 

[BuffyzDead]

I successfully and fully upgraded my Late 2009 Mac Mini (3,1),
inclusive of the required Wifi card: BroadCom BCM943224PCIEBT.

The machine has been running PERFECTLY without any issue whatsoever.
Thank You again to dosdude1 for the brilliant patch and Foxlet for the upgrade utility !!

My issue today is I am looking forward to doing the same exact upgrade on an identical MacMini BUT
the BroadCom BCM943224PCIEBT card is becoming difficult to find.

Is there a known, proven Wifi USB dongle, Known to work when plugged into a Late 2009 Mac Mini (3,1)
Supporting macOS Sierra, in lieu of the BCM943224PCIEBT card, please?

Thank you for a response.

 

[dosdude1]

I successfully and fully upgraded my Late 2009 Mac Mini (3,1),
inclusive of the required Wifi card: BroadCom BCM943224PCIEBT.

The machine has been running PERFECTLY without any issue whatsoever.
Thank You again to dosdude1 for the brilliant patch and Foxlet for the upgrade utility !!

My issue today is I am looking forward to doing the same exact upgrade on an identical MacMini BUT
the BroadCom BCM943224PCIEBT card is becoming difficult to find.

Is there a known, proven Wifi USB dongle, Known to work when plugged into a Late 2009 Mac Mini (3,1)
Supporting macOS Sierra, in lieu of the BCM943224PCIEBT card, please?

Thank you for a response.

You can simply use the WiFI card from a white Unibody MacBook, model A1342. The card is fully compatible with that machine and Sierra, but is slightly smaller that the original card, so you may have to get creative with the mounting.

 

[RafaelMac]

How is it going with the night shift for unsupported Macs?
[doublepost=1486457517][/doublepost]also having a issue searching updates with asu seed on (latest)
edit: sorry for Dutch

 

[virk]

...night shift for unsupported Macs...

Check this https://pikeralpha.wordpress.com/2017/01/30/4398/

 

[Carcode]

Czo said:
Disable SIP from recovery (why you turned it on?) and remove prelinkedkernel from /System/Library/PrelinkedKernels, and touch /System/Library/Extensions to create a new prelinkedkernel. Maybe a reboot is required after sip status change.

I will try this later in the afternoon today and will report the result. Thanks

It has worked now, many, many thanks to all. BUT:
Some things are misunderstanding for a user not every day working in Terminal mode.
First of all there is no manpage available for the csrutil command:

Running `/usr/bin/csrutil` by itself prints out a listing of currently available commands:
1. computername:~ username$ /usr/bin/csrutil
2. usage: csrutil <command>
3. Modify the System Integrity Protection configuration. All configuration changes apply to the entire machine.
4. Available commands:
5.
6.
7. clear
8. Clear the existing configuration. Only available in Recovery OS.
9. disable
10. Disable the protection on the machine. Only available in Recovery OS.
11. enable
12. Enable the protection on the machine. Only available in Recovery OS.
13. status
14. Display the current configuration.
15.
16.
17. netboot
18. add <address>
19. Insert a new IPv4 address in the list of allowed NetBoot sources.
20. list
21. Print the list of allowed NetBoot sources.
22. remove <address>
23. Remove an IPv4 address from the list of allowed NetBoot sources.
24. computername:~ username$

`/usr/bin/csrutil disable` - Turns SIP off of the boot drive. Must be run from Recovery with a reboot to take effect.
If run while SIP already disabled, command does nothing.

When disabled, running `/usr/bin/csrutil status` on the boot drive will give the following output:
1. computename:~ username$ csrutil status
2. System Integrity Protection status: enabled (Custom Configuration).
3.
4.
5. Configuration:
6. Apple Internal: disabled
7. Kext Signing: disabled
8. Filesystem Protections: disabled
9. Debugging Restrictions: disabled
10. DTrace Restrictions: disabled
11. NVRAM Protections: disabled
12.
13.
14. This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

`/usr/bin/csrutil enable` - Turns SIP on for the boot drive. Must be run from Recovery with a reboot to take effect. If run while SIP already enabled, command does nothing.

When enabled, running `/usr/bin/csrutil status` on the boot drive will give the following output:
1. computername:~ username$ csrutil status
2. System Integrity Protection status: enabled.
3. computername:~ username$
Note: If you run `/usr/bin/csrutil enable` followed by `/usr/bin/csrutil disable` (or vice-versa) only the first command is actually run.
`/usr/bin/csrutil netboot add` - Adds an IPv4 address to the list of allowed NetBoot sources. Must be run from Recovery.
`/usr/bin/csrutil netboot list` - Prints the list of allowed NetBoot sources. Can be run from either Recovery or the boot drive.
`/usr/bin/csrutil netboot add` - Removes an IPv4 address from the list of allowed NetBoot sources. Must be run from Recovery.
`/usr/bin/csrutil clear` - Resets SIP status and clears NetBoot list. After reboot, SIP is enabled if it was not previously. Running `csrutil netboot list` shows that no NetBoot IPs are listed.

That are the docs for csrutil so far as I have found.

Next step was the hint of Czo to get a new PrelinkedKernels. I found out if not done this there is still no trackpad and no keyboard etc. in my Sierra partition.

So I go into Recovery mode starting from my El Capitan partition.
There I opened the Terminal and go to with CD command to: /Volumes/Sierra/ (my Sierre partition) and further on with CD command to /System/Library/
Using the "pwd" command I see: /Volumes/Sierra/System/Library
Command "ls" shows its contents of several directories.
I renamed the dir PrelinkedKernels to PrelinkedKernelsorg while having in mind if something fails I will have a stored version. The command for this procedure was: mv PrelinkedKernels PrelinkedKernelsorg
Now I deleted PrelinkedKernels with commands:
cd PrelinkedKernels
rm *.*
cd ..
rmdir PrelinkedKernels
Doing a ls command shows there is only PrelinkedKernelsorg left now.
I then make a touch command with the date of today:
touch -t 201702070000 *.*

Closed Terminal, started the MBP again but first in the El Capitan partition. Then I started again with heart beating in the Sierra partition by pressing the Alt key and...
It has worked: Trackpad and keyboard are there again and Bluetooth gadget in the upper bar is there as usual.
[doublepost=1486472864][/doublepost]All this above takes some days because of needed information what to do etc.
But the other way to revert back to the old El Capitan was blocked:
The system will not allow me to restore all my apps, my work etc. from TimeMachine.
Nor the Migration app in utilities will do that. They always say: "Upgrade your system first."
After all experienced users are smarter than me and don't need some steps explained above.
E.g. it might be not needed to store a copy of PrelinkedKernels. But how knows?