Hacker News new | past | comments | ask | show | jobs | submit login

The commonality there is Intel. My XPS doesn't even have a recent driver package for its integrated Vega GPU because Intel refused to support it.

Also, the 2017-2019 Intel MacBook Pros are poorly suited to "professional" workloads, throttling under load or if, get this, the "wrong" (Intel) TB controller is used. There are reproducible TB bugs that are abandoned, and I still believe T2/BridgeOS was Apple's response to Intel's poor security design; they were forced to design adversarially against components they couldn't trust.




> The commonality there is Intel. My XPS doesn't even have a recent driver package for its integrated Vega GPU because Intel refused to support it.

Intel website shows their most recent Vega M release is 1/27/22. If Dell isn't keeping their drivers up to date, that's their problem, but the Vega M drivers are out there, Dell probably just isn't putting out releases.

https://www.intel.com/content/www/us/en/download/19269/radeo...

anyway, more broadly, this is, unfortunately, just AMD's driver support model. For the longest time they would not even put out iGPU driver updates for their own processors, instead offloading this responsibility to the laptop vendors themselves (who, of course, did not give a shit). i.e. exactly what's happening with your dell.

https://www.notebookcheck.net/Better-late-than-never-Radeon-...

And I don't know what people really expect here - Intel is dependent on AMD for drivers, they absolutely cannot write and support a whole new driver stack for an AMD product, if AMD sandbags (like they did previously to OEMs) then Intel is pretty much stuck. AMD got shamed into supporting their own products, finally, but they're absolutely not going to give Intel an inch more than they are contractually obligated to. It's in their financial interest to make your experience as shitty as they can.

Of course, it was probably a mistake for Intel to attempt to collaborate with their largest competitor, and they definitely should have made sure the contract was airtight. But there's really no good reason for these not to be supported by mainstream Adrenalin drivers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: