Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
why does everyone assume it's Apples fault when it comes to Nvidia. Nvidia has been the ones playing the hardball with Apple. even the pc people/mfgrs know they are asses. but gamers spill tears on tears. get ready to cry more. Nvid are and have been backing themselves into a corner with a few devs. Seen it before. ABOBE shitshills and a few high end devs of 3d softs. others are catching up fast. so the cashing in is what it is for now.
 
  • Like
Reactions: martyjmclean
Updated to the latest 10.13.4 to use an external gpu (supported OWC enclosure and Radeon 580) when it got released, the "disconnect GPU" never really worked and had multiple problems (reboot, system unresponsive) while connecting/disconnecting the external GPU. I hope this beta and future releases help address some of these issues... unless I am the only one experiencing this behavior.
 
Have they sorted an issue I have which is Apple Watch auto-unlock breaking when switching user accounts?
Wow, I didn’t realise that was when Auto Unlock failed to work. It seemed so random to me, but user switching would explain it.
 
  • Disagree
Reactions: B4U
I'm not upgrading until they let me use Nvidia cards in my eGPU. This feud of theirs is hurting me as an artist and it makes me real mad.

You can, but it's not plug-and-play. You need to do the install from egpu.io everytime there is a new macos update.
 
GPU Kernel Panic !
Since 10.13.4 release my 2010 MacBook Pro has been throwing random GPU kernel panics (NVIDIA GT330M GPU). It seems to be more likely when waking from sleep with a Safari window active, but can happen at any time...
Anyone else seeing graphics related kernel panics from the release or know if the eGPU changes are to blame?
I hope this gets picked up in the next release (10.13.5).
 
This. The eyes of the tech world are on Apple due to the millions of Mac users impacted.

I don’t (fully) blame Apple. Apparently DisplayLink has known about this since February and didn’t notify customers OR start work on a potential workaround.

Now Apple could have pushed back changes until there was a solution but that isn’t their job.

And from the looks of DisplayLink kayLinks support thus far I honestly don’t think DisplayLink cares and won’t issue a fix.
 
  • Like
Reactions: Jetpaction
I don’t (fully) blame Apple. Apparently DisplayLink has known about this since February and didn’t notify customers OR start work on a potential workaround.

Now Apple could have pushed back changes until there was a solution but that isn’t their job.

And from the looks of DisplayLink kayLinks support thus far I honestly don’t think DisplayLink cares and won’t issue a fix.
There's two positions on this which defines who is to blame. If the DL people were using illegal interfaces then that's one thing but they're not. That firmly places the blame at the feed of Apple who have changed stable interfaces to break third party drivers. This latter situation is totally scandalous.
 
I think we meant from stable sierra to stable high sierra. Last time I've updated, I had a couple of issues. Mostly slower performance - benchmarks of the new filesystem are not appealing -, and some softwares weren't compatible yet. It was in October 2017 I've done the tests though. Maybe now everything is better?

There was never a stable Sierra either in some people’s minds and that’s the problem with anecdotal user reviews. As for softwares being compatible that’s entirely up to the developer. Again you will always read reports of this or that not working for some people. You will always read reports of bugs or glitches on some people’s systems. Keep in mind though that many of those reported bugs are caused by things installed by the users themselves. On the Apple discussion forums you wouldn’t believe what some people have done to their systems to hose them. When asked to post the results of an Etrecheck scan the lists of crappy AV software, malware, adware, is endless but the user always blames Apple’s macOS for their troubles. As for myself High Sierra 10.13.4 is very stable now and it cleared up some minor glitches that were not showstoppers.
 
No APFS for Fusion Drives???

This is the one that annoys me the most. They promised it when High Sierra came out but still have not delivered. But as much as I may be annoyed I sure as hell don’t want Apple to release it before it’s perfect. I just assume it’s turned out to be a really hard nut to crack.
 
  • Like
Reactions: antmarobel
If the DL people were using illegal interfaces then that's one thing but they're not.

Except they are. DisplayLink is using kernel extensions for their software to work. Same goes for Duet. Apple has never supported and encouraged the use of 3rd party kernel extensions and has always warned it could potentially impact stability of the OS.

In fact, there's a high probability that macOS 10.14 won't allow kernel extensions at all anymore, unless signed by Apple. So there's a large list of vendors who have some work to do if they want to have their software work in future macOS versions.

https://developer.apple.com/library...//apple_ref/doc/uid/TP30000905-CH205-BEHJDFCA

Here's a nice long list of vendors who will be impacted by this: https://docs.google.com/spreadsheets/d/1IWrbE8xiau4rU2mtXYji9vSPWDqb56luh0OhD5XS0AM/edit#gid=0
 
  • Like
Reactions: gymrat2k
Still waiting for the new file system to be compatible with spinning hard drives.
What's taking so freaking long?

it’s been compatible with spinning hard drives since day one. It’s the combo SSD/HD Fusion drives Apple makes that it doesn’t work with yet. My traditional external hard drives are all converted. I am waiting for my internal Fusion drive to be supported.
 
Except they are. DisplayLink is using kernel extensions for their software to work. Same goes for Duet. Apple has never supported and encouraged the use of 3rd party kernel extensions and has always warned it could potentially impact stability of the OS.

In fact, there's a high probability that macOS 10.14 won't allow kernel extensions at all anymore, unless signed by Apple. So there's a large list of vendors who have some work to do if they want to have their software work in future macOS versions.
Kernel extensions != illegal interface.
 
Will download it once I finish my school work. Pretty hard to do school online when a computer is updating. ;)
 
Whenever you feel you want to install HS, just ask yourself 2 things:
1. How the new OS will positively impact my Mac?
2. Should I trust the company that gave me iOS11 and then forces me to stay on it?
 
HI Steve333,
I have a late 2010 iMac with a 1Tb WD Spinner that I now only use as part of my backup routine. I formatted it as APFS some time back. Works without any problems.

it’s been compatible with spinning hard drives since day one. It’s the combo SSD/HD Fusion drives Apple makes that it doesn’t work with yet. My traditional external hard drives are all converted. I am waiting for my internal Fusion drive to be supported.

I thought APFS was only compatible with SSD and that's why it didn't work with Fusion Drives?
 
Wow, I didn’t realise that was when Auto Unlock failed to work. It seemed so random to me, but user switching would explain it.

I've contacted Apple Support a number of times about it and am in the middle of doing so again now. I didn't think it could just be me who was affected by it.

2 or 3 updates ago they said they were passing the issue to the engineering team but so far that hasn't done anything.
 
This is the one that annoys me the most. They promised it when High Sierra came out but still have not delivered. But as much as I may be annoyed I sure as hell don’t want Apple to release it before it’s perfect. I just assume it’s turned out to be a really hard nut to crack.

Wow. I hear many of you guys not to happy with the update especially when Apple has failed to make it right. I’m gld that I’m holding on to update my MacBook Air! I hope it gets better.
 
I've contacted Apple Support a number of times about it and am in the middle of doing so again now. I didn't think it could just be me who was affected by it.

2 or 3 updates ago they said they were passing the issue to the engineering team but so far that hasn't done anything.

Thanks for following up on this. I just submitted a bug report for both the Apple Watch and macOS products. Hopefully more reports will make for quicker resolution.
 
  • Like
Reactions: timsutcliffe
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.