Ir para o conteúdo principal

Model A1286. Released February 2011 / 2.0, 2.2, or 2.3 GHz Quad-core Intel Core i7 Processor

588 Perguntas Visualizar todos

Did the terminal command sudo mess with my GPU?

Hi there. I was cleaning out my early MacBook pro 2011 i7 2.2 and decided to use Omni Disksweeeper. I read that many were successful using the software with the terminal command: sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper. I used the youtube video: https://www.youtube.com/watch?v=aBiXCNRd... for reference. After putting in the command I got a strange message: OCCCrashCatcher: Not enabling crash catching since we're connected to a tty (and thus presumably in gdb) . I saw others used this same command and had the same cryptic message, but everything was fine. Within seconds, my computer’s graphics went haywire. The screen was flickering, turning different colors, discoloration, graphics all over the place, and within twenty minutes the computer was stuck on the boot screen. I tried everything. I used SMC NVPRAM resets, attempted recovery mode/disk utility but ended up with a dark blue screen, safe mode, and even tried the Apple Hardware Test. The test passed successfully, but I continued to have problems. I then consulted Apple who told me to go through the same procedures to no avail. I then went to verbose or single user mode(one of the two) and I saw too significant failures in the code(I am not a pro and I looked up the meanings of the code). The two that really stood out were ConfigureInterests - nElements <= 0! Failed to configure interests and IO80211Controller::addSubscription() Failed to addSubscription for group Chip subgroup. I kept trying to fix the MacBook until I gave up at about 4am in the morning . I woke up to attempt to turn the computer on and the computer(albeit with a slight graphical issue in the boot(strange line), booted up successfully and now the MacBook’s desktop and everything else looks fine. I forgot to mention that I used target disk mode with a MacBook air and the hard drive was perfectly fine. Did the terminal command Sudo damage my GPU or cause havoc on the logic board? If its working perfectly fine(for now) was there ever an issue with the GPU in the first place. Any help would be great, because I’m not sure if this happen again in the 24-48 hrs. Thank you.


Responder a esta pergunta Também tenho esse problema

Esta é uma boa pergunta?

Pontuação 0
Adicionar um comentário

1 resposta

The GPU is a known issue on this model and there was a class action law suit on it, resulting in a now expired repair program.

A brilliant kid who calls himself DosDude came up with a couple of way of disabling the integrated graphics on the GPU.

Install gfx cardstatus https://gfx.io

or for a permanent fix do this

http://dosdude1.com/gpudisable/

Esta resposta foi útil?

Pontuação 0

1 comentário:

Thank you. Is it possible the Sudo Command messed it up? I had this replaced in Dec of 2016. I did use the repair program for the flat rate repair(including logic board).

por

Adicionar um comentário

Adicionar a sua resposta

Marc Maged será eternamente grato(a).
Exibir estatísticas:

Últimas 24 horas: 1

Últimos 7 dias: 3

Últimos 30 dias: 12

Duração total: 274