3 ms·
> disabling SIP is a requirement to run third-party graphics cards. While Google may have contributed to this problem, disabling SIP to use some hardware seems
by zamalek 7y ago
> disabling SIP is a requirement to run third-party graphics cards.
While Google may have contributed to this problem, disabling SIP to use some hardware seems like the actual issue here. If users have to frequently disable a feature then that feature simply doesn't work.
- pfranz 7y agoI guess it's both, but I'm confident the number of people who disable SIP is very low. Third party graphics cards (and the lack of a variety of first party GPUs) has been an issue on Macs for decades. I'm sure their disputes with Nvidia has just made this worse. I assumed I would need to disable SIP when it was added just because of the things I tend do to, but haven't ever had a need. The first thing this story made me think of was when Steam accidentally ran rm -rf /* https://www.theregister.co.uk/2015/01/17/scary_code_of_the_week_steam_cleans_linux_pcs/ https://www.theregister.co.uk/2015/01/17/scary_code_of_the_w...
- tinus_hn 7y agoYeah, on Windows you never had to click past these nasty dialogs warning you about unsigned drivers, and you certainly never had to disable Device Guard because a driver used Windows 3.1 era APIs. Except all the time, until Microsoft makes it impossible and forces the manufacturers hand. Unsigned drivers are already impossible to load and drivers that don’t work with Device Guard are next.
- zamalek 7y agoI haven't had an unsigned driver problem since Win8.1. I have certainly never needed to disable WPS in any version of Windows [where it exists], even in the face of unsigned drivers.