Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Look at @eminemmm's previous posts. It's a 13" 2011 MacBook Pro. It's HD 3000 only. It's not a dual GPU machine.

Somehow it's having trouble removing the kexts that are left over from the dosdude Catalina patcher's Legacy GPU Patch, and that's why kmutil is failing.

@eminemmm I have another set of instructions to try. I'm having trouble figuring out how my previous instructions would not have worked, but try this before I suggest anything more drastic.

First, make sure you've done a Time Machine backup, as I've mentioned in a few previous posts.

Next, try doing the following:

Boot from the patched installer USB. Open Terminal. Then run the following commands:
Code:
cd /Volumes
mount -uw "Volume Name" (such as "MY KINGSTON SSD" or "Macintosh HD" or whatever your Big Sur volume is)
cd "Volume Name"
cd System/Library
rm -rf Extensions
rm -rf Extensions.old
Then quit Terminal, start the Installer, and reinstall Big Sur. See if you're able to make WiFi and Ethernet work afterward.
After doing those commands and installing Big Sur , will I try again to apply patch.kexts from USB ?
 
Look at @eminemmm's previous posts. It's a 13" 2011 MacBook Pro. It's HD 3000 only. It's not a dual GPU machine.

Somehow it's having trouble removing the kexts that are left over from the dosdude Catalina patcher's Legacy GPU Patch, and that's why kmutil is failing.

@eminemmm I have another set of instructions to try. I'm having trouble figuring out how my previous instructions would not have worked, but try this before I suggest anything more drastic.

First, make sure you've done a Time Machine backup, as I've mentioned in a few previous posts.

Next, try doing the following:

Boot from the patched installer USB. Open Terminal. Then run the following commands:
Code:
cd /Volumes
mount -uw "Volume Name" (such as "MY KINGSTON SSD" or "Macintosh HD" or whatever your Big Sur volume is)
cd "Volume Name"
cd System/Library
rm -rf Extensions
rm -rf Extensions.old
Then quit Terminal, start the Installer, and reinstall Big Sur. See if you're able to make WiFi and Ethernet work afterward.
I tried your commands but ended with same error I guess.
 

Attachments

  • image.jpg
    image.jpg
    471.4 KB · Views: 195
Im so glad alot of you guys already got it up and running smooth with wifi....Its just to many steps to follow for me and my computer skills right now...I cant wait for dosdude to post.....os big sur on an unsupported mac...It should be out any day now i would think?..He lately waits for it come out from apple to the public before creating his utube video on how to install it with a 16gb stick or larger..cant wait for that...
 
  • Like
Reactions: TimothyR734
Im so glad alot of you guys already got it up and running smooth with wifi....Its just to many steps to follow for me and my computer skills right now...I cant wait for dosdude to post.....os big sur on an unsupported mac...It should be out any day now i would think?..He lately waits for it come out from apple to the public before creating his utube video on how to install it with a 16gb stick or larger..cant wait for that...
Sorry to break it to you, kid, but dosdude1 most likely isn't making a patcher this year
 
  • Like
Reactions: TimothyR734
Why wouldnt he?...he always does?..how do you know this?
I don´t think this is a forum for this question. We all are happy to get help from Barry and others. You should take what you can get.If there are questions belonging dosdude you should try to contact himself. As I know he very early told us that it is not his intention to make an approach to a patcher.
 
Slightly off topic:

Does anyone experience new (inet) connection problems with Safari on BS Beta 10 (and possibly other internal service like spotlight) ?

While Firefox and ping on terminal shows me that there is a working connection to my router and from there to the internet Safari constantly refuses to work. DNS is working, too (nslookup). Disabled WIFI and cable Ethernet one by one and no changes.

Created a new different user account with the same behaviour.

Writing this message from the Big Sur Beta 10 using Firefox. Problem came up after startup this morning (changed router firmware lats night and selected WPA2/WPA3). No changes within Big Sur, not experimental kexts - I promise :)

EDIT - this is a local problem on this particular machine
 
Last edited:
  • Like
Reactions: TimothyR734
Slightly off topic:

Does anyone experience new (inet) connection problems with Safari on BS Beta 10 (and possibly other internal service like spotlight) ?

While Firefox and ping on terminal shows me that there is a working connection to my router and from there to the internet Safari constantly refuses to work. DNS is working, too (nslookup). Disabled WIFI and cable Ethernet one by one and no changes.

Created a new different user account with the same behaviour.

Writing this message from the Big Sur Beta 10 using Firefox. Problem came up after startup this morning (changed router firmware lats night and selected WPA2/WPA3). No changes within Big Sur, not experimental kexts - I promise :)
if you made any changes to the router, it is no longer the same. Delete all existing wifi connections saved in the system and add them again, I recommend even resetting your router and clearing DNS caches on macOS.
 
if you made any changes to the router, it is no longer the same. Delete all existing wifi connections saved in the system and add them again, I recommend even resetting your router and clearing DNS caches on macOS.
Thanks, I started to look into this. Since I have two running connections (cable and WIFI) and other software like Firefox remains unaffected I ask myself how a (possibly) non working secondary and sometimes even disabled WIFI connection could block the Safari from connecting. Even using the IP of the connected router does not work (while in Firefox).

Even in a newly created account the behaviour remain the same, so it cannot be the account. Just swicthed on another iMac (not used for three days) and this one runs fine with Big Sur B10 and the same router and WIFI and Safari....
 
Last edited:
Thanks, I started to look into this. Since I have two running connections (cable and WIFI) and other software like Firefox remains unaffected I ask myself how a (possibly) non working secondary and sometimes even disabled WIFI connection could block the Safari from connecting. Even using the IP of the connected router does not work (while in Firefox).

Even in a newly created account this behaviour remains, so it cannot be the account. Just swicthed on another iMac (not used for three days) and this one runs fine with Big Sur B10 and the same router and WIFI and Safari....
don't forget the NVRAM, it loads information from the wifi.
 
  • Like
Reactions: TimothyR734
If we agree all that there will be no @dosdude1 patcher in near future @Barry K. Nathan and/or @jackluke should add some info about the current state of the development to the first post (not that I expect every new user to find it and read it). But we could at least add the GitHub link and something similar to a "support list"? I just added a * to the iMac 12,x which can be upgraded with a Metal GPU and a WiFi/BT4.x ac card, too.
 
If we agree all that there will be no @dosdude1 patcher in near future @Barry K. Nathan and/or @jackluke should add some info about the current state of the development to the first post (not that I expect every new user to find it and read it). But we could at least add the GitHub link and something similar to a "support list"? I just added a * to the iMac 12,x which can be upgraded with a Metal GPU and a WiFi/BT4.x ac card, too.

Hello, what is that? Can't install Big Sur with the micropatcher 0.4.4. iMac at the end of 2012.
 

Attachments

  • image.jpg
    image.jpg
    614.9 KB · Views: 192
  • Like
Reactions: Pinarek
Hello, what is that? Can't install Big Sur with the micropatcher 0.4.4. iMac at the end of 2012.
To properly troubleshoot it, I will need to see the installer log. (I guess I should add instructions to the README about how to save the installer log.)

The quick-and-dirty approach is to just try again with a different USB stick. If a different stick works, then your first stick is broken.
 
  • Like
Reactions: iMac-iPad
To properly troubleshoot it, I will need to see the installer log. (I guess I should add instructions to the README about how to save the installer log.)

The quick-and-dirty approach is to just try again with a different USB stick. If a different stick works, then your first stick is broken.
This is the same usb stick with which I already patched the iMac 9.1 of 2009. The mistake is new to me.
 
probably Hopper Disassembler can't deal with the ARM instruction set anyway, it may ignore ARM code already while reading the exec file.

I made some searching and noticed that Disassembler can understand till ARMv7 and ARM64 (that is ARMv8) while any recent iOS hardware device and Apple Silicon Mac should use ARMv8.4-A .
 
Last edited:
don't forget the NVRAM, it loads information from the wifi.
At the very end I had to reinstall the Big Sur Beta 10 over this existing installation - this solved this particular Safari problem.

Bright side of all this: I could check the latest micro patcher 0.4.4 with some enhancements I made for the iMac12,x family (but still no H.264 HD3000 iGPU).

EDIT:

Installing the 19H2 patched CoreBrightness.framework breaks Safari on my iMac. While the NightShift is working nicely with the Framework installed I cannot use the Safari to browse any longer :) This is a really nice one.
This machine is using the iMacPro1,1 ID....
 

Attachments

  • CoreBrightnessBlocksSafari.png
    CoreBrightnessBlocksSafari.png
    144.8 KB · Views: 141
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.