Open lalicatala opened 9 years ago
Use the following Terminal command:
xattr -d com.apple.quarantine /System/Library/Extensions/SATSMARTDriver.kext
-Al- On Tue, Nov 18, 2014 at 12:28AM, lalicatala wrote:
How can I stop this alert" (MBP 10.9.5) https://cloud.githubusercontent.com/assets/9818367/5084317/623796ae-6f0d-11e4-9ab9-3fa69e0e878a.jpg Thanks
Lee
Apparently removing the extended attribute is not sufficient to load the driver on Yosemite:
sif:Extensions adib$ sudo xattr -d com.apple.quarantine /System/Library/Extensions/SATSMARTDriver.kext
xattr: /System/Library/Extensions/SATSMARTDriver.kext: No such xattr: com.apple.quarantine
sif:Extensions adib$ sudo kextutil -t /System/Library/Extensions/SATSMARTDriver.kext
Notice: /System/Library/Extensions/SATSMARTDriver.kext has debug properties set.
Diagnostics for /System/Library/Extensions/SATSMARTDriver.kext:
Code Signing Failure: not code signed
ERROR: invalid signature for fi.dungeon.driver.SATSMARTDriver, will not load
sif:Extensions adib$
On Fri, Nov 28, 2014 at 11:20 PM, Sasmito Adibowo wrote:
Apparently removing the extended attribute is not sufficient to load the driver on Yosemite
What version are you trying to install? From a previous discussion:
kasbert commented 19 days ago Seems that Yosemite blocks unsigned kernel extensions. However, there is a list of exceptions to that rule (inside one Apple kext). I have no idea how SATSmartDriver got into that list, but versions 0.8 and 0.9 are there and they will work with Yosemite.
Al Varnell Mountain View, CA
I tried to install version 0.10.
Version 0.9 kind of doesn't work on Yosemite – it freezes Disk Utility while starting and only workable via smartctl
, albeit there is a lengthy delay between the drive information dump and the actual SMART data dump when running smartctl -a
.
Sasmito Adibowo http://basilsalad.com
On 29 Nov 2014, at 15:26, Al Varnell notifications@github.com wrote:
On Fri, Nov 28, 2014 at 11:20 PM, Sasmito Adibowo wrote:
Apparently removing the extended attribute is not sufficient to load the driver on Yosemite
What version are you trying to install? From a previous discussion:
kasbert commented 19 days ago Seems that Yosemite blocks unsigned kernel extensions. However, there is a list of exceptions to that rule (inside one Apple kext). I have no idea how SATSmartDriver got into that list, but versions 0.8 and 0.9 are there and they will work with Yosemite.
-Al-
Al Varnell Mountain View, CA — Reply to this email directly or view it on GitHub.
I have stuck with 0.8 and have had no issues, as that’s still the one distributed with SMART Utility and DriveDX and it has worked with all the drives I need to access routinely. The newer ones were primarily to satisfy special needs that I don’t seem to have.
-Al-
On Nov 29, 2014, at 3:24 AM, Sasmito Adibowo notifications@github.com wrote:
I tried to install version 0.10.
Version 0.9 kind of doesn't work on Yosemite – it freezes Disk Utility while starting and only workable via
smartctl
, albeit there is a lengthy delay between the drive information dump and the actual SMART data dump when runningsmartctl -a
.Thanks
Sasmito Adibowo http://basilsalad.com
On 29 Nov 2014, at 15:26, Al Varnell notifications@github.com wrote:
On Fri, Nov 28, 2014 at 11:20 PM, Sasmito Adibowo wrote:
Apparently removing the extended attribute is not sufficient to load the driver on Yosemite
What version are you trying to install? From a previous discussion:
kasbert commented 19 days ago Seems that Yosemite blocks unsigned kernel extensions. However, there is a list of exceptions to that rule (inside one Apple kext). I have no idea how SATSmartDriver got into that list, but versions 0.8 and 0.9 are there and they will work with Yosemite.
-Al-
Al Varnell Mountain View, CA
I use Yosemite and 0.8 too and it works well. All my external HDs are supported.
I don't know what we can do that Apple put 0.10 in the well known kext list.
Unfortunately this issue it's a real pain, especially because I've two enclosures, one USB (sunplus) and the other FW (oxford - manpower), none of them are recognized, version 0.8 nor version 0.9 recognize them out of the box and I can't modify the Info.plist due to the signature invalidation on Yosemite.
Would not be possible to have different way to add enclosure data, instead of modifying the Info.plist?
How can I stop this alert" (MBP 10.9.5)
Thanks
Lee
lalicata at aol dot com