Yes i have gone through that in my last post i have downloaded and installed the dev betas as stated before.
The public beta of 10.12.4 beta 3 was released two days ago. i am not signed up for public betas.
Got a tip for us?
Let us know
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
- Thread starter redheeler
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
The public beta of 10.12.4 beta 3 was released two days ago. i am not signed up for public betas.
Yep, log confirms SIP is disabled.
Looks like it's a storage / filesystem problem.
Feb 22 11:24:29 Mac-mini Unknown[498]: [/BuildRoot/Library/Caches/com.apple.xbs/Sources/Bom/Bom-193.8/Storage/BOMStream.c:280] buffer overflow!
Several lines later the crash log viewer process is kicked off so it can record a crash dump.
Feb 22 11:24:41 Mac-mini ReportCrash[569]: Crashed Thread: 7 Dispatch queue: Filesystem Classifier
It created the recovery partition ok previously. That's making me think that the hard drive cable should be ok (or you should have run into problems doing that already).
You should run some diagnostics on that hard drive. Likely some issues with it.
This is the same USB installer you used for the first two, right?
Really? Have a look at this article and tell me what you think: https://forums.macrumors.com/thread...-public-beta-for-public-beta-testers.2033772/
@L Caputo: Thanks for the info; I also could not "see" this update. I have "reinstalled" the macOSSierraBetaAccessUtility (or however it is called). With additionally AUSEnabler I could install this update.
[doublepost=1487864133][/doublepost]
I think that I was wrong
On my computer it did not appear. Thank you, too!
[doublepost=1487864133][/doublepost]
I think that I was wrong
On my computer it did not appear. Thank you, too!
Has anybody managed to update to the 3rd iteration of Developer Beta 10.12.4, that was released last week.
No matter what I try either AUSEnabler seed branch or CZO patch no developer beta is available for me in the App Store.
if you managed to get it installed, please let me know, I am most confused as downloads were available and installed before.
No matter what I try either AUSEnabler seed branch or CZO patch no developer beta is available for me in the App Store.
if you managed to get it installed, please let me know, I am most confused as downloads were available and installed before.
I just installed it. It wasn't showing up for me because SIP got reenabled somehow. once I disabled it using the recovery partition it showed up in AppStore
[doublepost=1487952614][/doublepost]
Alternatively, because none of the patches really ever work for me, I created a Clover USB with a smbios that supports macOS Sierra and I boot from that and then pick my ssd with macOS and the updates show up that way too flawlessly
Yes I too found SIP had been reenabled somehow. So yesterday i reenabled it hoping to update but no.
yes AUSEnabler seems be hit or miss, and I am not sure that CZOs patch is doing anything.
so what steps does one take to create a Clover USB, what do you need etc?
CZO's patch circumvents the hardware check in softwareupdate daemon (which solely cares about OS updates). Foxlet's AUSEnabler is using an apple software distribution server to mask this check (but you still get the updates from Apple).
Not sure why you would use both??
Edit: Did the AUSEnabler patch work for getting you developer beta updates in the past or just public beta updates?
Asking, as they're not the same CatalogURL, and I thought Foxlet only had options for beta or production catalogs.
Dev url being:
https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz
Beta url being:
https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz
You could always set your CatalogURL to the dev one, reboot or restart softwareupdated and see if you get the Dev update.
Last edited:
Thank you for the feedback
1) no ..the first two were done with a prior patch. I wanted to use the latest build (v4.2.3) since
Updates could now run via a patch preference, as opposed to foxlets tool. Why would that matter?
2) its a brand new Samsung 500GB 850 EVO SSD. The same exact one used in my first mini. Truth be told, i did have some odd anomolies, when i first installed it, then restoring it to El Capitan 10.11.6, from the minis orinal time machine backup. The normal process one would do when upgrading a drive. It took multiple boots and reboots, with each startup getting better over time, as if things were getting fixed/repaired/improved, with each restart. Not what am experienced to seeing after upgrading a drive. Afterwards, it boots up as expected from an SSD drive. Lickity split.
***Since I still have both the original drive and the time machine backup, do you think a complete erase/reformat, then clean install of El Capitan OR macOS Sierra (?), then using migration assistant, from the TM Backup, might clear out the cruft?
My single fear with migration assistant approach, is having to reinstall a few key apps, for which i have no installer/software key.
PS. ...Disk utility says the drive is fine and no repairs/first aid is required.
Thank you again for all your help and support
1) If it was the same USB, then there's little likelihood that's what the storage crash is about.
2) Strange. Makes you wonder if there's areas of the flash memory that are defective and getting masked by the SSD's scavenger routines built into its firmware. (likely the only thing that would tell you the true state of the drive would be to get something like Hiren's boot CD and run the Seagate diagnostic tools on it). http://www.hirensbootcd.org if you're interested. Just suggesting that's what it sounds like....with things seeming to gradually get more stable.
If apps aren't compatible with Sierra, it likely won't matter which approach you take - TM restore, then Sierra upgrade overtop or a clean Sierra install, then use migration assistant with the original drive (presumably you have a USB enclosure you've put that one into?).
If I were you, I'd remake the Sierra patched installer, to rule it out (but, if you had the old one kicking around, I would have used that one, as it worked)
It's not the version of the tool, it's that people have had issues with their USB drives having glitches.Me, I'd still want to run Samsung's diags on that SSD to make sure as well. Being a brand new drive, if there's any glitches in it, I'd be returning it pretty quick (but you need the diags to tell you that).
Last edited:
Well I started out using AUSEnabler and it was never consistent in its workings, so I tried CZOs patch.
I was downloading Developer Betas not Public Betas.
However today I managed to get the Dev Beta 3 version downloaded and installed with AUS Enabler using the seed branch.
First a big thanks to @dosdude1 for making MacOs Sierra possible on my good old Macbook 5,2 (Early 2009)
As we all know this model works perfectly fine with Apple's newest OS with the only downside being the limited trackpad functionality (recognized only as a mouse pointing device with limited features (no tap-to-click, no rightclick - scrolling works)
Now for the adventurous Mac Users around, I've got a hot tip for you. Basically follow this MacRumor User's Guide to replace the trackpad with another trackpad of a Macbook Pro (2008). I just did it (2nd try to be honest, first tried it a few years ago and failed) and I even got 3- & 4-finger gestures now
It's possible!
(Screenshot by @Tartarus not by me. To clarify, I now got a Macbook white that looks like this, running Sierra, with full trackpad functionality)
As we all know this model works perfectly fine with Apple's newest OS with the only downside being the limited trackpad functionality (recognized only as a mouse pointing device with limited features (no tap-to-click, no rightclick - scrolling works)
Now for the adventurous Mac Users around, I've got a hot tip for you. Basically follow this MacRumor User's Guide to replace the trackpad with another trackpad of a Macbook Pro (2008). I just did it (2nd try to be honest, first tried it a few years ago and failed) and I even got 3- & 4-finger gestures now
It's possible!
(Screenshot by @Tartarus not by me. To clarify, I now got a Macbook white that looks like this, running Sierra, with full trackpad functionality)
I had the isight problem. What worked for me is the following:
- I booted up my old Windows XP installation in VirtualBox, and since iSight was listed in USB devices, I went to "devices>USB>iSight" and tried to attach it to VirtualBox. It wouldn't, Windows acted as if it didn't exist. So I shutdown VirtualBox. But since then iSight has worked on MacOS.
Last edited:
Hi guys,
Mail and Screen Ruler apps cause kernel panic constantly. All log files are saying:
...
Kernel Extensions in backtrace:
com.apple.GeForceTesla(10.0.2)
dependency: com.apple.iokit.IOPCIFamily(2.9)
dependency: com.apple.iokit.IONDRVSupport(514.7)
dependency: com.apple.iokit.IOGraphicsFamily(514.7)
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.2)
BSD process name corresponding to current thread: WindowServer
...
I did Force Cache Rebuild and run system-prelinked-kernel & -system-caches commands several times but seems it didn't help.
I would greatly appreciate any suggestions.
MacBook Pro Mid 2009
Mail and Screen Ruler apps cause kernel panic constantly. All log files are saying:
...
Kernel Extensions in backtrace:
com.apple.GeForceTesla(10.0.2)
dependency: com.apple.iokit.IOPCIFamily(2.9)
dependency: com.apple.iokit.IONDRVSupport(514.7)
dependency: com.apple.iokit.IOGraphicsFamily(514.7)
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.2)
BSD process name corresponding to current thread: WindowServer
...
I did Force Cache Rebuild and run system-prelinked-kernel & -system-caches commands several times but seems it didn't help.
I would greatly appreciate any suggestions.
MacBook Pro Mid 2009
Maybe your GPU is starting to burning out. Apple always had problems with dedicated GPU's (all of mine with dGPU is failed, nearly all of it more than one time).
I also have a Mac Pro Early 2009/GT120 with the 5,1 rom running Sierra 10.12.4 Beta (16E175b)
I have the exact same panic, started on the BETA just prior to 10.12.4 Beta (16E175b) ( updated yesterday in a weak hope to solve the issue)
I was getting panics every 5 - 10 minutes yesterday when working with Safari and after a complete tear down and dusting of the system I ran almost 24 hours before it happened again. Card is the original GT 120. Should I roll back to the non beta Sierra, get a new card or wait to see if Apple finds an issue with the drivers?
[UPDATE] - After this mornings panic I just noticed my aftermarket USB 3.0 card no longer works or shows up in the System Information. This happened yesterday and I needed to reset PRAM to make it work. I'm going to leave it in but not reset PRAM to see if the system panics again.
[UPDATE] - Day two without the USB 3.0 card being recognized (see note above) and no kernel panics.
[UPDATE] - Two days with out issue and then a panic while installing Kubuntu using Paralles.
Last edited:
I have been unable to download Beta 4 ( I have beta 3 installed). I tried to run the Sierra patcher, in an effort to prompt a download of beta 4. I allowed the patcher to include USB "injection" kernel, which I believe I deselected when originally installing Sierra.
The result was first, in many years time, kernel panic with trace suggesting USB related problem.
I reinstalled the Sierra using the original 10.12 I still had on my drive. Note here, that I did not erase the disk, I reinstalled over the existing system. Subsequently, when I checked for updates, using foxlet's patch, I was able to download combined update all the way to 10.12.4 beta 3. When running post install patch, however, I *deselected* the USB kernel modification choice. Rebooted successfully, and no Kernel panic since.
Try to reinstall operating system going back to first 10.12 release, then use updater to patch all the way to 10.12.4 (beta 3). Deselect Kernel USB "injection" choice when running post install patcher. It may be possible for you to update to 10.12.4 beta 4.
I still can't get beta 4 update, and currently Foxlet's update patch returns NSURLErrorDomain error -1100; is it possible that Foxlet no longer supports this patch (?), or is it that apple pulled the beta 4 due to ensuing problems ?
Could anybody test if hibernation using hibernatemode 25 works for you? On my Macbook white (Early 2009) running Sierra I've got trouble getting it to work. Reset SMC & NVRAM to no avail. Problem persists on clean install with new user account.
Please test issuing the following command in Terminal:
My pmset -g output:
It seems to think it goes to hibernate mode, but actually never does:
My Mac goes to sleep when closing the lid and has the Power-LED blinking, but never hibernates completely: I never get the grey screen+progress bar / need to press the power button to wake it. It just wakes on its own from normal Sleep when opening the lid later on.
It seems various other users have the same issue, at least there are reports in the apple community, see thread 1, thread 2, thread 3
Please test issuing the following command in Terminal:
Code:
sudo pmset -a hibernatemode 25My pmset -g output:
Code:
TeutonesMacBook:~ Teutone$ pmset -g
System-wide power settings:
Currently in use:
womp 1
autorestart 0
halfdim 1
sms 1
hibernatefile /var/vm/sleepimage
networkoversleep 0
disksleep 10
sleep 10
hibernatemode 25
ttyskeepawake 1
displaysleep 10
acwake 0
lidwake 1It seems to think it goes to hibernate mode, but actually never does:
Code:
pmset -g log | grep -i "wake from"
[...]
2017-03-08 02:31:39 +0100 Wake Wake from Hibernate [CDNVA] due to OHC1/HID Activity: Using AC (Charge:100%)
2017-03-08 02:36:46 +0100 Wake Wake from Hibernate [CDNVA] due to EC LID0/HID Activity: Using AC (Charge:100%)
2017-03-08 11:10:08 +0100 Wake Wake from Hibernate [CDNVA] due to OHC1/HID Activity: Using BATT (Charge:80%)My Mac goes to sleep when closing the lid and has the Power-LED blinking, but never hibernates completely: I never get the grey screen+progress bar / need to press the power button to wake it. It just wakes on its own from normal Sleep when opening the lid later on.
It seems various other users have the same issue, at least there are reports in the apple community, see thread 1, thread 2, thread 3
I was poking around looking at the URL's this morning and it seems Foxlet's tweaked catalog shows an index date of 24-Feb. The url's in there are stale which is the cause of the error, so seems to need an update.