Apple releases OS X 10.10.4 with Mail, Photos improvements, 'discoveryd' fix

13»

Comments

  • Reply 41 of 53
    dr. xdr. x Posts: 282member
    Quote:
    Originally Posted by Dr. X View Post

     

    Hi,

     

    I have the 840 EVO 1TB SSD from Samsung which I purchased from Amazon last year. I haven't experienced any issues so far and use TRIM Enabler.

     

     Since I haven't experienced any corruption issue so far, doesn't this mean I'm in the clear?

     

    Should I update from 10.10.3 to 10.10.4? I currently use TRIM Enabler on OS X 10.10.3.

     

    Could someone elaborate?




    I found these instructions for anyone who wishes to update their firmware on a Samsung 840 EVO SSD on OS X. http://blog.conradchavez.com/2014/10/30/running-the-samsung-840-evo-ssd-performance-restoration-tool-on-a-mac/

     

    I hope this helps those who have Samsung Evo 8x SSDs

     0Likes 0Dislikes 0Informatives
  • Reply 42 of 53
    dr. xdr. x Posts: 282member
    Quote:
    Originally Posted by MagMan1979 View Post

     



    Damnit! You beat me to it!!! Was gonna be the first to proclaim that :D

     

    I have it enabled already, KEXT signing restored, and TRIM is working perfectly!

     

    Trim Enabler, good riddance!


     

     

    Quote:
    Originally Posted by hillstones View Post

     

    Thank you.  I will try that.

     

    Edit: It worked like a charm!  Tested it on my MacBook Pro 2011 before applying it to my main Mac.  "sudo trimforce enable" worked perfectly.  I stopped using Trim Enabler because any time I disabled it to install an update, it would not disable properly and got the big NO symbol and had to reinstall OS X.


     

    @MagMan1979, @hillstones, I don't think TRIM Enabler is dead yet. The developer is coming out with an update today or later tonight. See https://www.cindori.org/forums/topic/trim-enabler-with-os-x-el-capitan/page/7/#post-37319

     

    He said:

    Disk Sensei and Trim Enabler updates are finished. They will be available tomorrow.

    With these updates, you will be able to enable Trim safely on OS X 10.10.3 and above, including El Cap (and 10.10.4).

    With safe enabling, I mean:


    1. Disabling kext signing is no longer necessary

    2. The “gray boot screen/stop sign” issue is gone

    3. Your system is no longer modified in any way

    4. Trim will no longer reset on updates

    Stay tuned. ;) 

     

    ___

     

    I would think using TRIM Enabler is much safer then the "sudo trimforce enable" command in Terminal for those that are hesitant using the sudo commend in terminal and having something break. Also, Today, Trim Enabler and Disk Sensei will receive updates that will make them the easiest and safest utilities to enable Trim on OS X.

     0Likes 0Dislikes 0Informatives
  • Reply 43 of 53



    I thought they removed it on iOS devices as well, but no such luck. It seems we'd have to bear with discoveryd for a few more months until iOS 9 is released.

     0Likes 0Dislikes 0Informatives
  • Reply 44 of 53
    ge forcege force Posts: 4member
    Looks like the ROOTPIPE exploit hasn't been fixed yet. I asked APPLE about it , and they had no response? I take it then that the ROOTPIPE exploit is an NSA approved backdoor.
     0Likes 0Dislikes 0Informatives
  • Reply 45 of 53
    melgrossmelgross Posts: 33,697member
    konqerror wrote: »
    Pure FUD. Trim corruption hasn't been an issue for the last 5 years. Windows enables it without asking. You're saying every Samsung drive will corrupt itself under Windows? You're saying that Samsung can't write Trim code even though Apple builds in Samsung drives?

    You are so totally wrong. You have no idea as to what this is all about.

    This is an example of what this problem is all about.

    https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
     0Likes 0Dislikes 0Informatives
  • Reply 46 of 53
    melgrossmelgross Posts: 33,697member
    ge force wrote: »
    Looks like the ROOTPIPE exploit hasn't been fixed yet. I asked APPLE about it , and they had no response? I take it then that the ROOTPIPE exploit is an NSA approved backdoor.

    Apple never responds to individual requests about security problems. Most companies don't, though some will send some general response that means nothing. Don't be so paranoid.
     0Likes 0Dislikes 0Informatives
  • Reply 47 of 53
    dr. xdr. x Posts: 282member
    Quote:

    Originally Posted by melgross View Post





    Apple never responds to individual requests about security problems. Most companies don't, though some will send some general response that means nothing. Don't be so paranoid.

     

    @melgross, the only way for Apple to respond to security issues or any other issue is to file a bug port via the Apple Bug Reporter. I've filed security reports and a number of other issues over the years via Apple Bug Reporter and they actually respond either to say that it's already submitted and is a duplicate or to say that they are working on addressing the issue I submitted.

     

    Anyone with an Apple ID should be able to singin to the bug reporter to submit this issue.

     

    I'd suggest to submit this via the Apple Bug Reporter and see what happens. It's doesn't matter if it is marked as a duplicate as you'll know that it's been submitted already. if not, you'll let Apple know to address the issue.

     

    It's pretty straight forward to file a report via the Apple Big Reporter, one just has to follow the instructions on how to submit a report.

     

    Hope this helps.

     0Likes 0Dislikes 0Informatives
  • Reply 48 of 53
    melgrossmelgross Posts: 33,697member
    dr. x wrote: »
    <a data-huddler-embed="href" href="/u/17018/melgross" style="display:inline-block;">@melgross</a>
    , the only way for Apple to respond to security issues or any other issue is to file a bug port via the Apple Bug Reporter. I've filed security reports and a number of other issues over the years via Apple Bug Reporter and they actually respond either to say that it's already submitted and is a duplicate or to say that they are working on addressing the issue I submitted.

    Anyone with an Apple ID should be able to singin to the bug reporter to submit this issue.

    I'd suggest to submit this via the Apple Bug Reporter and see what happens. It's doesn't matter if it is marked as a duplicate as you'll know that it's been submitted already. if not, you'll let Apple know to address the issue.

    It's pretty straight forward to file a report via the Apple Big Reporter, one just has to follow the instructions on how to submit a report.

    Hope this helps.

    That's true. But those responses are almost always generic responses. I don't remember when there was an actual response to a submission that was written specifically as a response to that particular submission. I imagine that if you're a larger developer, and you're tagged as such, you might get a specific response.
     0Likes 0Dislikes 0Informatives
  • Reply 49 of 53
    philboogiephilboogie Posts: 7,675member
    melgross wrote: »
    ^ post

    Completely off topic here, but I registered a friends' business over at mapsconnect.apple.com and after my submission of all info of his business, location and hours open they mailed us back to verify. When the location was inaccurate they asked for a photo of the front door entrance. So I took a picture and told them the GPS coordinates were in the file. Sure enough they verified and approved our submission.
     0Likes 0Dislikes 0Informatives
  • Reply 50 of 53

    Yes - this is aweful and I can't find a fix

     0Likes 0Dislikes 0Informatives
  • Reply 51 of 53

    Sorry if wrong place for this question....... but how do you import/load/direct the OSX 10.10.4 screensaver to display your personal photos vs. the preset ones.   There is no select option to direct it to your photos.

     0Likes 0Dislikes 0Informatives
  • Reply 52 of 53
    lssmit02lssmit02 Posts: 15member

    Update on TRIM issues with Samsung Drives. melgross posted a link to a blog post that supported the argument that there is a problem with enabling TRIM on Samsung drives. However, according to a July 17 update on that post, Algolia no longer believes that their problem was with the drive:

     

    Quote:

     Samsung had a concrete conclusion that the issue is not related to Samsung SSD or Algolia software but is related to the Linux kernel.


     

    https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/

     

    Therefore, if it Algolia post is the basis of the support that there is a TRIM problem with Samsung drives, that post no longer supports this argument. Therefore, it would seem that turning TRIM on for 3rd party drives in OS X is likely safe (or at least, there is no proof that it is unsafe). Of course, still a problem with Linux.

     0Likes 0Dislikes 0Informatives
  • Reply 53 of 53
    prjeffprjeff Posts: 1member

    My touch scrolling is now disabled after the update. Urg.

     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.