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
I ran the post installation tool and the keyboard and trackpad doesn't work. What I did was to download the latest tool version 4.0.7 (about 40 minutes ago) you have and still the keyboard and trackpad doesn't work. Wonder if Apple is getting sneaky.
I downloaded the beta on a supported Mac and installed the beta from there.
Yes, it is safe to do, but I will tell you now that in my case, doing that about half an hour ago did not help. I am still without my iSight camera.
From an upgraded mbp 5,3 where video works. May be useful to compare.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildMachineOSBuild</key>
<string>15A284</string>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>QuickTimeUSBVDCDigitizer</string>
<key>CFBundleGetInfoString</key>
<string>2.9.3 Copyright © 2004-2013 Apple Inc. All Rights Reserved.</string>
<key>CFBundleIdentifier</key>
<string>com.apple.QuickTimeUSBVDCDigitizer</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>QuickTime USB Video Class Digitizer</string>
<key>CFBundlePackageType</key>
<string>thng</string>
<key>CFBundleShortVersionString</key>
<string>2.9.3</string>
<key>CFBundleSignature</key>
<string>appl</string>
<key>CFBundleSupportedPlatforms</key>
<array>
<string>MacOSX</string>
</array>
<key>CFBundleVersion</key>
<string>2.9.3</string>
<key>CSResourcesFileMapped</key>
<true/>
<key>DTCompiler</key>
<string>com.apple.compilers.llvm.clang.1_0</string>
<key>DTPlatformBuild</key>
<string>8R174l</string>
<key>DTPlatformVersion</key>
<string>GM</string>
<key>DTSDKBuild</key>
<string>16A275a</string>
<key>DTSDKName</key>
<string>macosx10.12internal</string>
<key>DTXcode</key>
<string>0800</string>
<key>DTXcodeBuild</key>
<string>8R174l</string>
</dict>
</plist>
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildVersion</key>
<string>2477</string>
<key>CFBundleShortVersionString</key>
<string>2.9.3</string>
<key>CFBundleVersion</key>
<string>2.9.3</string>
<key>ProjectName</key>
<string>USBVideoClass</string>
<key>SourceVersion</key>
<string>293004002000000</string>
</dict>
</plist>Can you also dump your /System/Library/QuickTime/QuickTimeUSBVDCDigitizer.component info.plist and version.plist to help @foxletYes, it is safe to do, but I will tell you now that in my case, doing that about half an hour ago did not help. I am still without my iSight camera.
I just posted my working one.
I am the same way. I have never felt comfortable talking to my computer, so I don't. I played with Siri once or twice when I first installed the betas, because I had been waiting a long time for Apple to implement it on desktop computers. However, once I saw how deficient Siri is on desktops, I said "Forget this! This is half-baked!".
I have also been impressed by the stability and the easy transition -- minus the broken iSight camera, of course -- but that is about it.
[doublepost=1474603652][/doublepost]
I did a clean install from PB 7 to 16A319, and an upgrade from 16A319 to 16A323. I have the iSight problem.
Did you by any chance ever try resetting SMC (per a previous post)?I am the same way. I have never felt comfortable talking to my computer, so I don't. I played with Siri once or twice when I first installed the betas, because I had been waiting a long time for Apple to implement it on desktop computers. However, once I saw how deficient Siri is on desktops, I said "Forget this! This is half-baked!".
I have also been impressed by the stability and the easy transition -- minus the broken iSight camera, of course -- but that is about it.
[doublepost=1474603652][/doublepost]
I did a clean install from PB 7 to 16A319, and an upgrade from 16A319 to 16A323. I have the iSight problem.
Also, see previous post about supporting @foxlet with dumps of your quicktime plugin.
THE MISTERY IS RESOLVED
It's because I selected an UPGRADE instead of a clean install! I just did all again, but this time with a clean install and my iSight works! Seems that get an upgrade produce this iSight issue somehow.. It's not the best world (installing all apps/config again), but at least this might shed some light on this problem. Thanks all the support
[doublepost=1474606072][/doublepost]
No, you don't respect my angst because you know nothing about my angst and why it's so important. And this is not just about me, but the others that will come through this (bring this issue on the table might save a lot of confusion to everyone). I'm here trying to help and doing my best. Yes, I tried Google a lot before (how you think I came here?). I don't mean to offend anyone just emphasized that there must be a way or figure out what is going on. So if you preach civility practice what you preach
It's because I selected an UPGRADE instead of a clean install! I just did all again, but this time with a clean install and my iSight works! Seems that get an upgrade produce this iSight issue somehow.. It's not the best world (installing all apps/config again), but at least this might shed some light on this problem. Thanks all the support
[doublepost=1474606072][/doublepost]
No, you don't respect my angst because you know nothing about my angst and why it's so important. And this is not just about me, but the others that will come through this (bring this issue on the table might save a lot of confusion to everyone). I'm here trying to help and doing my best. Yes, I tried Google a lot before (how you think I came here?). I don't mean to offend anyone just emphasized that there must be a way or figure out what is going on. So if you preach civility practice what you preach
Last edited:
Yes, but while the "incorrect permissions" error message is gone, I am still getting the following when I run that command in the Terminal:
/ locked; waiting for lock.
Lock acquired; proceeding.
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
KernelCache ID: A3DF8E0C4EF96A3EA9F10DDE5091E4E0
File at path '/System/Library/PrelinkedKernels/prelinkedkernel' changed, cannot be used
How do I fix that? I just checked in that folder, and because of that command that I ran earlier, I now have two files in that folder: "prelinkedkernel" and "saved-prelinkedkernel".
Do you think it would make any difference if I deleted "prelinkedkernel" and then renamed "saved-prelinkedkernel" back to "prelinkedkernel" and used that instead. Probably not, right?
As noted in my updated message #2802, no. I verified that it is indeed disabled, because I use two other apps that require that it is disabled.
Again, as noted in message #2802 above, doing this did not help.
I even ran "sudo kextcache -system-prelinked-kernel" in the Terminal, and as you can see above, I am still getting that "File at path '/System/Library/PrelinkedKernels/prelinkedkernel' changed, cannot be used" message.
Oh joy! Oh bliss! All of this fiddling around trying to fix the camera may have messed up something somewhere else. I just discovered that I can neither boot in safe mode, or in recovery mode. In both cases, I get the prohibited symbol. A regular boot works just fine, and all of my apps work fine . . . except for those that need the iSight camera.
But what in the world would break booting up in safe mode and recovery mode?[/quote][/QUOTE]
[doublepost=1474607032][/doublepost]
I am counting on you buddy, because I am this close with trying to do a clean install straight from 16A323 final. You may recall that I installed 16A323 on top of 16A319. Whether or not that is what created this mess, who knows.
I really don't look forward to having to go that route, because not only is there no guarantee that it will even help fix the iSight camera, but it will also mean seven long hours of migrating my user files as well.
[doublepost=1474607799][/doublepost]
Here is the Info.plist contents . . .
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildMachineOSBuild</key>
<string>16A276</string>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>QuickTimeIIDCDigitizer</string>
<key>CFBundleGetInfoString</key>
<string>7.7.3 Copyright Apple Inc. 2001-2016</string>
<key>CFBundleIdentifier</key>
<string>com.apple.QuickTimeIIDCDigitizer</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>QuickTime IIDC Digitizer</string>
<key>CFBundlePackageType</key>
<string>thng</string>
<key>CFBundleShortVersionString</key>
<string>7.7.3</string>
<key>CFBundleSignature</key>
<string>appl</string>
<key>CFBundleSupportedPlatforms</key>
<array>
<string>MacOSX</string>
</array>
<key>CFBundleVersion</key>
<string>2974</string>
<key>CSResourcesFileMapped</key>
<true/>
<key>DTCompiler</key>
<string>com.apple.compilers.llvm.clang.1_0</string>
<key>DTPlatformBuild</key>
<string>8R174l</string>
<key>DTPlatformVersion</key>
<string>GM</string>
<key>DTSDKBuild</key>
<string>16A276</string>
<key>DTSDKName</key>
<string>macosx10.12internal</string>
<key>DTXcode</key>
<string>0800</string>
<key>DTXcodeBuild</key>
<string>8R174l</string>
</dict>
</plist>And here is the version.plist contents . . .
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildAliasOf</key>
<string>QuickTime</string>
<key>BuildVersion</key>
<string>2</string>
<key>CFBundleShortVersionString</key>
<string>7.7.3</string>
<key>CFBundleVersion</key>
<string>2974</string>
<key>ProjectName</key>
<string>QTOtherComponents</string>
<key>SourceVersion</key>
<string>2974000000000000</string>
</dict>
</plist>Hope that helps in some way.
Attachments
@RumorzGuy
Did you remember to check patch Recovery Partition the last time you post-installed? Otherwise Recovery Mode won't work.
Are you running the "manual" force cache rebuild (sudo kextcache etc...) from your (patched) Sierra boot disk or off-line (USB Installer) ?
Important. I always rebuild caches from either recovery or an external boot disk, ever since Apple clamped down with SIP etc...
See a previous post about this point.
Last thing - try SMC resetting and responding to @foxlet with your plist files if video still doesn't work.
I scoured the Apple Developer forums about Sierra and video, and nothing relevant to report except for SMC and killing some video related daemons.
Did you remember to check patch Recovery Partition the last time you post-installed? Otherwise Recovery Mode won't work.
Are you running the "manual" force cache rebuild (sudo kextcache etc...) from your (patched) Sierra boot disk or off-line (USB Installer) ?
Important. I always rebuild caches from either recovery or an external boot disk, ever since Apple clamped down with SIP etc...
See a previous post about this point.
Last thing - try SMC resetting and responding to @foxlet with your plist files if video still doesn't work.
I scoured the Apple Developer forums about Sierra and video, and nothing relevant to report except for SMC and killing some video related daemons.
No, that is probably about the only thing I haven't tried yet . . . but going by our track record here, I am wondering if it is even worth trying at this point. Being as recovery mode and safe mode don't even work for me now, it would seem that I may be forced to do clean install straight from 16A323, and then endure seven hours of migrating files again. Blah!
Already did that . . . although in reply to you, and not to foxlet.
Last edited:
EDIT : Do you have any external devices jacked into your system?
[doublepost=1474609009][/doublepost]
No, that is probably about the only thing I haven't tried yet . . . but going by our track record here, I am wondering if it is even worth trying at this point. Being as recovery mode and safe mode don't even work for me now, it would seem that I may be forced to do clean install straight from 16A323, and then endure seven hours of migrating files again. Blah!
Alright did that . . . although in reply to you, and to foxlet.
lol. SMC is quick and painless. You may just be surprised. Doesn't hurt to try.
And yes, you are close to having to bite the bullet here. I think you manually replaced a kext, so not sure what your current state is...
Good news is , some report that a clean install restores their video.
The following is a bit long, but I am providing as much info as possible, in the hope that it will help someone here to figure out how to fix the iSight problem.
Aside from losing one app due to an issue with macOS Sierra, up until now, I had
assumed that I remained immune to all of the issues which have been discussed here as of late.
However, this morning it dawned on me that since first installing the Sierra betas, GMs and then the final release, I had not used the FaceTime app on my early 2009 iMac with 16A323 installed.
Well, I did just now, and to my dismay, this is what I see on the right side of FaceTime's window:
"No Camera Available
To use FaceTime, connect a camera."
So I launched the "System Information" app in the /Applications/Utilities folder, and under Hardware/Camera it likewise says . . .
"No video capture devices were found."
In the System Information app under Hardware/USB, it states the following:
Built-in iSight:
Product ID: 0x8502
Vendor ID: 0x05ac (Apple Inc.)
Version: 2.19
Serial Number: 8J97VP3242CX3E00
Speed: Up to 480 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x24400000 / 2
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0
Built-In: Yes
Here is what I have tried so far:
1. I tried Czo's suggestion to delete . . .
/System/Library/PrelinkedKernels/prelinkedkernel
. . . to recreate kernel cache. While the kernel cache was recreated, it did not resolve the issue.
2. Next, I tried Czo's suggestion to replace the "AppleUSBVideoSupport.kext" file with the El Capitan kernel extension that dosdude1 uploaded here.
To play it safe, I first copied the original kext file that is in . . .
/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/
. . . to the desktop, and then I moved the El Capitan version of the same into the above folder, overwriting the original kext file.
Doing this did not help either. Both FaceTime and the System Information app still report that no camera is available.
3. Next, I tried the two Terminal commands that pkouame suggested.
When I ran "sudo kextcache -system-prelinked-kernel", the Terminal spit out this . . .
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
AppleUSBVideoSupport.kext has incorrect permissions; omitting.
KernelCache ID: B095BE6F5826D16EF7A57745CEE0521D
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
I am assuming that the incorrect permissions is because I replaced the original kext file with the one that dosdude1 uploaded.
So I launched "BatChmod" and dropped the "IOUSBFamily.kext" file on it.
"Owner" was already set to "root", and "Group" was set to "wheel". Likewise, permissions were already set to 755.
So, I just clicked on the "Apply to enclosed" box and hit the "Apply" button.
After doing that, I ran "sudo kextcache -system-prelinked-kernel" again, and this time, the "incorrect permissions" error for "AppleUSBVideoSupport.kext" was gone, but I was still getting this:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
KernelCache ID: E219698F35EAFE132996D8B5BFF59EBB
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
So once again I deleted the "prelinkedkernel" file and ran "sudo kextcache -system-prelinked-kernel" yet again. This time I got this:
/ locked; waiting for lock.
Lock acquired; proceeding.
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
KernelCache ID: E219698F35EAFE132996D8B5BFF59EBB
File at path '/System/Library/PrelinkedKernels/prelinkedkernel' changed, cannot be used
So I am not sure what I can do about that.
BTW, each time that I ran "sudo kextcache -system-caches", nothing appeared in the Terminal window, but the result is still the same. There is supposedly no camera available.
4. Next, I compared the "com.apple.Boot.plist" file that foxlet uploaded with my own that is in "/Library/Preferences/SystemConfiguration".
Similar to "hadnet", mine also only said "-no_compat_check", so I made the file writable in BBEdit and changed it to "-no_compat_check kext-dev-mode=1 mbasd=1". I also used BatChmod to check ownership and permissions on the file after I edited it.
Once again, doing this did not fix my iSight camera.
5. Next, I tried foxlet's suggestion of resetting the NVRAM, or zapping the PRAM, as we used to call it. The results were scary.
I shut down my iMac completely, waited about fifteen seconds, and then did the option-command-p-r combo.
After the first bong, I waited for the second bong. Instead, I got the gray startup screen with the prohibited symbol on it. Then my iMac just shut down. Freaked me out a bit, man!
So I rebooted, hoping for the best, and everything was back to normal . . . PHEW! . . . Well, minus my iSight camera.
6. Next, I tried pkouame's suggestion of trying to rebuild the kext cache from an external hard drive via the Terminal.
I got the same results as when I tried doing the same thing from my startup drive. In fact, when I used the Terminal from my external hard drive, the permissions error for the "AppleUSBVideoSupport.kext" file returned.
This mystified me, because I am certain that even after putting back the original kext file, I used BatChmod to check ownership and permissions on the file.
Well, after rebooting my iMac using the regular internal startup drive, I ran BatChmod again, and checked the file. Sure enough, "owner" is still set to root, and "Group" is set to wheel. Permissions are set to 755.
So after verifying that, I ran "sudo kextcache -system-prelinked-kernel" in the Terminal again -- that is, from my startup drive -- and once again it is reporting the same permissions error:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
AppleUSBVideoSupport.kext has incorrect permissions; omitting.
KernelCache ID: DFD1113AF11177F010D4FA71820137FE
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
I even tried setting permissions to 644, and I still get that "incorrect permissions" error.
The only way I was able to get rid of the error for the "AppleUSBVideoSupport.kext" file was by chmodding the whole IOUSBFamily.kext file to root, wheel and 755.
7. Next, I rebooted my iMac using my USB 16A323 installer drive -- it is actually a partition on one of my WD external hard drives -- and I did the following:
- Ran "csrutil disable" in the Terminal, just to make sure that SIP was disabled. I was already pretty certain that it was, because I use two apps that require for SIP to be disabled.
- Ran "First Aid" in the Disk Utility app to make sure there was nothing wrong with my internal startup hard drive. No problems were detected.
- Ran dosdude1's post-install tool in order to use the "forced rebuild" option. I also enabled the "Recovery Partition Patch" as well. I am not exactly sure what that patch does, but when earlier I tried to boot in recovery mode using command-r, I wasn't able to.
8. After my machine rebooted from its internal hard drive, I checked FaceTime again. Still no iSight camera is detected.
9. I ran "sudo kextcache -system-prelinked-kernel" in Terminal yet again, being as the post-install tool said that I might have to. This time the Terminal spit out this:
/ locked; waiting for lock.
Lock acquired; proceeding.
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
KernelCache ID: A3DF8E0C4EF96A3EA9F10DDE5091E4E0
File at path '/System/Library/PrelinkedKernels/prelinkedkernel' changed, cannot be used
Exactly what does that last line mean, and how do I fix it?
So after doing all of that, I am back to square one.
Being as doing all of the above made no difference, I am going to replace both my "AppleUSBVideoSupport.kext" and "com.apple.Boot.plist" files with the originals that I removed, and make sure that their permissions are set properly via BatChmod.
Until dosdude1 or some other "brainiac" here figures this out for us, I guess we are left without iSight-dependent apps.
i also followed some of your procedures ... but nothing is working hope @dosdude1 comes with solution ..
i think problem is with upgrading ..not clean install
Exactly the same problem I have. Can someone provide some instructions how to fix this problem with kernel using Terminal in Recocery partition or from the USB installer? I suspect that the problem USB related to forced cache rebuild after the system update. (It wasn't a fresh install).
Thank you for all your help!
As I noted in step #7 of message #2802, yes, I did in fact enable that option before I rebooted. Despite doing that, recovery mode and safe mode are still broken.
If you are referring to the "sudo kextcache -system-caches" command, I ran it from my startup disk.
The "sudo kextcache -system-prelinked-kernel" command has also been repeatedly run from my startup disk.
I may have run the latter from my USB 16A323 installer external drive -- I don't remember for sure -- but I am pretty certain that I have not run "sudo kextcache -system-caches" from my USB 16A323 installer external drive.
Well, as mentioned earlier, I did enable the "forced rebuild" option from the USB 16A323 installer external drive when I used dosdude1's tool.
As already mentioned, I already posted my dumps. I'll give the SMC setting a shot . . . but with low expectation.
Well, this iMac has four USB ports which are taken up by the following:
1. Hard-wired mouse.
2. Canon printer.
3. WD 2 TB external hard drive.
4. WD 8 TB external hard drive.
Also, ethernet cable from iMac to Apple Airport Extreme.
Please refer to message #2802 for more details.
[doublepost=1474611192][/doublepost]
Yes, father. Give this old man a break. I am getting to it.
No, no, no! I don't like biting bullets! Besides, I don't have any teeth left. Not a single one! Seriously.
Well, yes, I did replace a kext file. That is mentioned in step #2 in message #2802. Here it is again:
Go away! You are not supposed to be saying that! You are not supposed to be telling me that I have to do a clean install! You are supposed to continue giving me false hope. What is wrong with you? Enduring migrating files for seven hours afterwards is not something I look forward to.
As I noted in step #7 of message #2802, yes, I did in fact enable that option before I rebooted. Despite doing that, recovery mode and safe mode are still broken.
If you are referring to the "sudo kextcache -system-caches" command, I ran it from my startup disk.
The "sudo kextcache -system-prelinked-kernel" command has also been repeatedly run from my startup disk.
I may have run the latter from my USB 16A323 installer external drive -- I don't remember for sure -- but I am pretty certain that I have not run "sudo kextcache -system-caches" from my USB 16A323 installer external drive.
Well, as mentioned earlier, I did enable the "forced rebuild" option from the USB 16A323 installer external drive when I used dosdude1's tool.
As already mentioned, I already posted my dumps. I'll give the SMC setting a shot . . . but with low expectation.
Well, this iMac has four USB ports which are taken up by the following:
1. Hard-wired mouse.
2. Canon printer.
3. WD 2 TB external hard drive.
4. WD 8 TB external hard drive.
Also, ethernet cable from iMac to Apple Airport Extreme.
Please refer to message #2802 for more details.
[doublepost=1474611192][/doublepost]
Yes, father. Give this old man a break. I am getting to it.
No, no, no! I don't like biting bullets! Besides, I don't have any teeth left. Not a single one! Seriously.
Well, yes, I did replace a kext file. That is mentioned in step #2 in message #2802. Here it is again:
Go away! You are not supposed to be saying that! You are not supposed to be telling me that I have to do a clean install! You are supposed to continue giving me false hope. What is wrong with you? Enduring migrating files for seven hours afterwards is not something I look forward to.
Geez why does your "migration" take so long...I wouldn't look forward to that either...
Yet another exercise in futility. Doing so did not fix my iSight camera.
Man, I can already taste that stinkin' bullet in my mouth! Blah!
But . . . but what if I do a clean install, and that still doesn't fix it? Seven hours of migration for nothing. Sierra, are you really worth it???
CRUNCH!!! There goes RumorzGuy biting that darn bullet. I'll see you all on the other side . . . I hope.
Last edited:
If you have some free space on your system, consider clean installing patched Sierra to a new Partition without migration, just to see if it fixes your video issues.Yet another exercise in futility. Doing so did not fix my iSight camera.
Man, I can already taste that stinkin' bullet in my mouth! Blah!
But . . . but what if I do a clean install, and that still doesn't fix it? Seven hours of migration for nothing. Sierra, are you really worth it???
Well, I do have space on my internal hard drive to make another partition, but that is still going to take time, since Disk Utility will have to move all of my current data in order to make space for the new partition.
My plan is to back up my internal hard drive one more time to one of my external partitions in order to get the freshest possible data -- which I am currently in the process of doing -- and then do a clean install of 16A323 to my internal hard drive.
Then, before I migrate, check to see if the camera is even working.
Whether it does or not, I guess I should still then do the migration, being as my safe mode and recovery mode are broken already anyway. Hopefully, a clean install will fix safe mode and recovery mode, plus replace any changed or damaged files, plus give me the right ownership and permissions on all system files.
I am thinking that, at this point, even if someone does come up with a solution to fix the camera, it probably won't fix my safe mode and recovery mode, so I might as well bite the bullet and get it over with.
OK
Have tried this twice now with no success.
I used dosdude1 app to download Sierra and move it to USB stick.
Tried re-downloading and making bootable USB twice.
Booted from USB and started an Upgrade install over El Capitan.
About 4 minutes into the install an error message pops up saying that the operation could not be completed and was not permitted - with the option to retry - fails again.
MacBook Pro mid 2009 15" 5.3
I have an SSD drive installed.
Error message attached below.
Any clues?
Thanks
Adam
Have tried this twice now with no success.
I used dosdude1 app to download Sierra and move it to USB stick.
Tried re-downloading and making bootable USB twice.
Booted from USB and started an Upgrade install over El Capitan.
About 4 minutes into the install an error message pops up saying that the operation could not be completed and was not permitted - with the option to retry - fails again.
MacBook Pro mid 2009 15" 5.3
I have an SSD drive installed.
Error message attached below.
Any clues?
Thanks
Adam
Attachments
Adam, others here may disagree, but given all of the different problems that so many of us have been having on our unsupported machines, I think your best bet for success might be to do a full backup of your El Capitan startup disk, and then closely follow dosdude1's instructions for his patch tool, making sure that you conduct a clean install, instead of trying to install on top of El Capitan. I obviously cannot guarantee that this will bring you success, but it may eliminate some currently unseen problems. FWIW, I plan on doing the very same thing shortly by erasing my current 16A323 installation, and doing a clean install as well, in the hope that it will get my iSight camera recognized again.
Last edited:
I know you don't want to hear this but...Yes, sounds like a good safe plan: test all your devices on a totally clean un-migrated patched Sierra first.
I would add, since you will be down for a while anyway and you have the space, why not ...
- take this opportunity and restore to your previous fully operational El Cap (assuming that was the case)
- create a new partition for patching Sierra, following your plan.
Just belts and suspenders, so you always have a working system to go back to. Taking the time ( I know its a pain ) to make sure your previous OS with data will always be available, considerably lowers my blood pressure when I experiment. And who knows, by the time you are setup to restart from scratch so to speak, maybe someone will come up with a solution. By the way, 10.12.1 is already in beta, checking my developer account to see if there's anything video related.
Oh and Safe Mode is known to bork with many devices attached to your system. Well known issue for a while now.
Your call and Good luck. Make sure you do all of this well rested. See you on the flip side.
I have VirtualBox installed with a Mountain Lion VM in it, which I was using to run SheepShaver. However, I haven't used it in a while, since I am currently running SheepShaver directly under Sierra at the moment.
At any rate, can you please provide specific instructions regarding how to detach the iSight camera from VirtualBox?
I guess it is worth a try before I am forced to conduct a clean install of 16A323.
Thanks.