Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Disabled 'Metal' in OSX, need to re-enable via Terminal but don't know the commands

M

moosed

macrumors member
Original poster
Mar 10, 2017
45
0
Hi. I was trying to fix an issue with image persistence on my Imac 5k using a suggestion from this thread https://forums.macrumors.com/threads/imac-5k-screen-burn-in-high-sierra.2072828/page-8 where someone suggests disabling Metal via these two commands

sudo defaults write /Library/Preferences/com.apple.CoreDisplay useMetal -boolean no

sudo defaults write /Library/Preferences/com.apple.CoreDisplay useIOP -boolean no

However after running the two commands i have lots of visual artefacts and the computer takes about 20 minutes to load to a now unresponsive desktop.

I have managed to log into terminal via recovery mode but i don't know what commands to put in to undo the changes made from entering the above 2 commands.

If anyone can help it would great.

Thanks in advance
 
Hi. Thanks for the quick response.

So in terminal when i enter

sudo defaults write /Library/Preferences/com.apple.CoreDisplay useMetal -boolean yes

it tells me command not found

if i remove 'sudo' however it seems to accept the command however when i restart the computer the issues seems to remain as if the commands haven't been applied.
 
Yes both commands were entered whilst in recovery mode (minus the sudo bit at the start which was making it say 'command not found')
 
I dont particularly want to do it but if i was to restore my mac via time machine to a time before i made the change would that undo it ?
 
Are you sure you are in safe mode?

If you are, then only option is editing .plist file from single user mode.
[automerge]1600625508[/automerge]
moosed said:
I dont particularly want to do it but if i was to restore my mac via time machine to a time before i made the change would that undo it ?
Click to expand...

If you have a restore point, yes, try.
 
  • Like
Reactions: moosed
Ok turns out my mac keyboard decided to run out of battery and thus holding shift wasn't loading into safe mode.

enterting the commands via safe mode has fixed it.

Thank you very much for taking the time out to help, it's very much appreciated :)

Time to buy a new screen for my Imac so i don't get tempted into trying anymore 'fixes'.
 
moosed said:
Ok turns out my mac keyboard decided to run out of battery and thus holding shift wasn't loading into safe mode.

enterting the commands via safe mode has fixed it.

Thank you very much for taking the time out to help, it's very much appreciated :)

Time to buy a new screen for my Imac so i don't get tempted into trying anymore 'fixes'.
Click to expand...


Hey, just wanted to add some context to your experiences, so you understand what happened :)

So the commands to write to the defaults assumed you were booted into the OS. While booted into recovery the root "/" no longer belongs to your OS installation, so writing to that path would write to a different file than the one inside the OS; You could mount the main OS with read write from recovery to edit it from there if need be, but the path would be different.

As for sudo; It stands for "super-user do" and performs a subsequent command as the root user. - However, when you're in recovery mode, your login prompt in Terminal is effectively already the root user, so sudo doesn't need to exist there - all commands have root privileges
 
  • Like
Reactions: StellarVixen and moosed
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back