NoIs it possible to run HD 3000 GPU acceleration on macbook pro 2011?
NoIs it possible to run HD 3000 GPU acceleration on macbook pro 2011?
Here is an interesting website that has a lot of info on most all Macs , it seems there is more than one version of the 2012 MacBook ProThat's where I got the info from that I posted at the end of my message. Doesn't say "Retina"
More info:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro9,1
Processor Name: Quad-Core Intel Core i7
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Hyper-Threading Technology: Enabled
Memory: 16 GB
Boot ROM Version: 233.0.0.0.0
SMC Version (system): 2.1f175
Some newer macs come with ARM processors. What I mean is full support. Some apps will only run on ARM processor.Not really. Think macpro 2019. it cannot become obsolete next year.
Hi guys,
first of all many thanks to everybody for this great work. Without you I never could install Big Sur in my iMac.
On saturday I finally installed Big Sur on my late 2012 iMac.
View attachment 1671144
Everything works great, except my instant personal hotspot. I already searched this thread but didn't find a solution. Sorry, if I ask again.
I can see the hotspot in my WiFi status. If I select it, I can see, that the hotspot is activated on my iPhone. The switch toggles instantly and WiFi switches to LTE. But then I get a message on my iMac that the personal hotspot could not be activated.
View attachment 1671147
On my 2015 MacBook everything works fine.
I tried two iPhones and two users with different iCloud accounts. Both with same result.
Is this problem already known and is there a solution for this problem?
Many thanks for your help!
boot off catalina dosdude usb. run the disk utility. delete existing raid. launch raid assistant. select (2) internal hdd which are now blank because you deleted the raid. create raid0 and select HFS+, GUID for raid set. inside of the raid0 set create an APFS partition. clone usb drive to raid0 APFS container. sometimes i use disk partition by clicking on the raid0 apfs container and select restore and choose the usb drive. sometimes i use CCC for cloning. bless failed error message but DOSDude APFS loader sees the RAID0 APFS as an internal HDD. reboot after clone and give it 1 minute to detect and boot. there are other ways to do this which require more terminal commands. google raid0 catalina boot drive and a bunch comes up. good luck!I’ve tried what you’re suggesting at least 10 times with different scenarios with CCC but it always fails at around 52% of the operation. Only succeeds if the disk is not a RAID member. Send a screenshot showing you’re running BigSur off a RAID array. Otherwise, Your answer is a total BS.
Same issue here with a mini 2011 (HD3000 integrated GPU)Is anyone else having trouble with video playback in the TV app? On streamed videos It will play a second or 2 of the video and then just drop back to the main app screen. For downloaded videos in my library it is audio only and black screen. This is on a 2011 IMac with an 860M video card. Everything else seems to work fine including youtube videos.
This was no clean install.
/patch-kexts.sh: line 747: zip: Command not found
zip -q -r -X AppleGraphicsControl.kext.zip AppleGraphicsControl.kext
Hi @Ausdauersportler
I did a clean install again (with your patch-kexts.sh) and I don't understand something.
The following error is again indicated:
Code:/patch-kexts.sh: line 747: zip: Command not found
The line concerned is:
Code:zip -q -r -X AppleGraphicsControl.kext.zip AppleGraphicsControl.kext
I looked in the micropatcher USB key, the zip utility is not in /usr/bin/, there is /usr/bin/unzip but not /usr/bin/zip.
There is also the file AppleGraphicsControl.kext.zip file on the micropatcher USB stick.
Looks like this is a patcher bug or I misunderstand something ?
/Volumes/Install\ macOS\ Big\ Sur/patch-kexts.sh
Check out the micro patcher docs, last section on the website...Whats the easiest way to enable System File editing in Big Sur? since "sudo mount -uw /" no longer works. Cheers!
Please download again, this is surely not a new problem and surely not a Big Sur related one.I'm trying to install on a Late 2012 Mac Mini. I download the InstallAssistant.pkg, used createinstallmedia to create the installer, then used the latest micropatcher, reboot to EFI, turn back on, and boot from the installer. When I choose to install Mac OS Big Sur, it says the InstallAssistant is damaged.
I've tried this with 2 different USB drives, USB 2.0 and USB 3.0. I'm following the directions 100% but I can't seem to get a working installer.
I've downloaded it from at least 3 different apple CDN links. Doesn't seem to change the outcome. Unless I just haven't found the latest.Please download again, this is surely not a new problem and surely not a Big Sur related one.
Having received recently the same model I will upgrade with 16 Gb of memory, I would like to know if you are using the original internal DD or a SSD who replaced it and which method you used to install Big Sur. Thanks for the infos
I'm using an internal 1TB Samsung SSD (the original HDD is in the other bay) and worked with @barrykn's big-sur-micropatcher.Having received recently the same model I will upgrade with 16 Gb of memory, I would like to know if you are using the original internal DD or a SSD who replaced it and which method you used to install Big Sur. Thanks for the infos
Please, until I fixed this run the patch-kext.sh from the running Big Sur! Open a terminal, enter
Code:/Volumes/Install\ macOS\ Big\ Sur/patch-kexts.sh
Wrote this yesterday, unfortunately not explicitly enough!
The next version of the mc or patch-kext.sh will not need any user interaction for iMac 11,x or 12,x users. Found a way to detect the graphics card used and the system so the patcher logic can choose all needed extensions automatically. Hope it will work out...OK ! Thank for all the help 👍 . While waiting for the next version of the patch, I will read again the micropatcher documentation and your other importants posts again , to better understand the kernels extensions and other important files
Have a good day![]()
I know this works for Catalina because I have no problem running Catalina off a RAID 0. My only question to you is does this method work for Big Sur?!!! I’m gonna give it a shot but I doubt It’ll work for Big Sur because I’ve tried similar methods.boot off catalina dosdude usb. run the disk utility. delete existing raid. launch raid assistant. select (2) internal hdd which are now blank because you deleted the raid. create raid0 and select HFS+, GUID for raid set. inside of the raid0 set create an APFS partition. clone usb drive to raid0 APFS container. sometimes i use disk partition by clicking on the raid0 apfs container and select restore and choose the usb drive. sometimes i use CCC for cloning. bless failed error message but DOSDude APFS loader sees the RAID0 APFS as an internal HDD. reboot after clone and give it 1 minute to detect and boot. there are other ways to do this which require more terminal commands. google raid0 catalina boot drive and a bunch comes up. good luck!
Nov 19 14:12:33 xxx Mail[5966]: getattrlist failed for /System/Library/Frameworks/OpenGL.framework/Resources//GLRendererFloat.bundle/GLRendererFloat: #2: No such file or directory
Nov 19 14:29:10 xxx com.apple.xpc.launchd[1] (application.com.apple.mail.1152921500311907838.1152921500311907843[5966]): Service exited with abnormal code: 1
Nov 19 14:29:20 xxx Mail[6330]: getattrlist failed for /System/Library/Extensions/AppleIntelHD4000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsGLDriver: #2: No such file or directory
Nov 19 14:29:20 xxx Mail[6330]: getattrlist failed for /System/Library/Frameworks/OpenGL.framework/Resources//GLRendererFloat.bundle/GLRendererFloat: #2: No such file or directory
For me its almost flawless. Top bar takes a long time to load after login for me. Something like 20s. It is longer than boot itself. Maybe not a clean install related?Thanks to @Glemp, @pyedog, and everyone else on this forum of their assistance. My MacMini late 2012 runs like a charm on Big Sur and I must say that I don't understand why it is not supported officially. I have 16GB RAM, which makes a bigly difference, but I have yet to experience any glitches and everything works smoothly and is fast.
There seems to be a lot of variation on this. For me (mac mini 2012 2.3Ghz i7 16GB RAM 2 FHD displays) drift runs smoothly. For other folks with almost identical hardware it seems to stutter ... it's not clear where the difference lies ... some folks with 2018 macs claim drift stutters for them.Another point is screensaver lag. Drift and even Flurry are stuttering like mad. Something like 5fps.