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.

tankerthebub

macrumors member
Aug 11, 2020
35
59
That doesn’t make any sense
well not sure how that doesn't make sense I think what I asked was pretty simple. I need the model of your computer and asked for screenshots during boot up. I need to add the model of the computer and your dsdt which is unique to what ever system your using in order for it to work. If you don't know what that is or doesn't make sense don't try it! If you open system extensions and open any one of the graphics kexts you'll see in the plist models of Macs. These drivers don't have that. They were never finished hence development driver. My buddy had to show me how they wrote the plist files when they were compiled I'm then having to pull of the mach_kernel to add the system specific dsdt so that it boots with the development drivers rather then the stock and kexts.....so you would replace your mach_kernel in root directory and then rename the old kexts to kext.old so Mac OS doesn't try to boot it and then my modified kernel boots my system specific developmental kexts. If that's to much or you don't know id read through the forums...but like I said I really only want someone to try that has little bit of terminal/plist editing because I really don't want to go back and forth especially if 100 people are going to ask at the same time. Not to be rude man. I just don't have a lot of time and most of the time I'm responding from my phone. I was really hesitant on posting this because I don't want to maintain something that people will get mad at me when apple updates come out and my patcher breaks for the Mac pro. God bless dosdude I just don't have that time to maintain it if something breaks. And I'm married so those who know the married life know what I'm talking about :p
 

Attachments

  • Screen Shot 2020-08-15 at 11.31.48 AM.png
    Screen Shot 2020-08-15 at 11.31.48 AM.png
    121.9 KB · Views: 166
Last edited:

GSXB

macrumors regular
Jun 21, 2018
246
198
England
well not sure how that doesn't make sense I think what I asked was pretty simple. I need the model of your computer and asked for screenshots during boot up. If need to add the model of the computer and your dsdt which is unique to what ever system your using in order for it to work. I you don't know what that is or doesn't make sense don't try it! If you open system extensions and open any one of the graphics kexts you'll see in the plist models of Macs. These drivers don't have that. They were never finished hence development driver. My buddy had to show me how they wrote the plist files when they were compiled I'm then having to pull of the mach_kernel to add the system specific dsdt so that it boots with the development drivers rather then the stock and kexts.....so you would replace your mach_kernel in root directory and then rename the old kexts to kext.old so Mac OS doesn't try to boot it and then my modified kernel boots my system specific developmental kexts. If that's to much or you don't know id read through the forums...but like I said I really only want someone to try that has little bit of terminal/plist editing because I really don't want to go back and forth especially if 100 people are going to ask at the same time. Not to be rude man. I just don't have a lot of time and most of the time I'm responding from my phone.
What about the patch tool for Macpro’s
 
  • Like
Reactions: TimothyR734

tankerthebub

macrumors member
Aug 11, 2020
35
59
What about the patch tool for Macpro’s
GSXB Im working on it now I should have it later tonight or early in the AM. I have to work at 3PM. IM updating open core because the version I'm using is a tad older..and was problematic with public beta..are you running 144.0.0.0.0 boot rom and is it a flashed 4,1 to 5,1 or genuine 5,1? My buddy brought his 4,1 over and my patcher worked but gave a weird issue were desktop froze narrowed it down to opencore and it worked after I applied newer opencore on beta 4. So I'm going to recompile the patcher and ill upload it.
 
Last edited:
  • Like
Reactions: TimothyR734

D00m

macrumors newbie
Aug 14, 2020
4
5
Germany
What Sense would it make by creating one Specific Customized Mach Kernel only working for this Specific Mac and Operating System.
As you said, it would be required replacing the standard Mach Kernel each Time there's an Update, isn't it ?
Wouldn't it be much more Practical adding all ID's just as they are at standard Hardware kext's and Compiling it that way you'll get something more Universal in the End.
 

ASentientBot

macrumors 6502a
Jun 27, 2018
863
3,421
SkyLight.framework
UPDATE #3 on my patcher:
I have pretty much finalized the patching part. It works. It's awesome. I am now working on my website and will be making an app to run the patcher, so it feels more fluid without copying and pasting code. It may take me a LONG time to make an app. In order to get the patcher out ASAP, can anyone recommend me a free no-code or low-code desktop app builder? I will still work on an app developed with SwiftUI in Xcode, but would like to get the patcher out soon.
You could try AppleScript if the UI is going to be very simple?
 

tankerthebub

macrumors member
Aug 11, 2020
35
59
no not every time you update....its every time apple comes out with a point release it overwrites a new Mac_kernel each time.....so every time you'd have to return replace the mach_kernel and that doesn't even guarantee it would be bootable unless I physically update it or works out of the box and then Id have to go into the kernel update what needs to be updated and then id have to release an updated kernel. You can't just add all the ID's in one kext because the development drivers are system specific(I tried adding ids for Mac Pro and iMac and every way I did it kernel paniced) like I said they were designed with one machine in mind...this is why up until now there hasn't been a fix...I did find one weird thing though "PowerArch" was at the bottom of one of the plists for those that don't know "Powerarch" is in the same plist file fill listed on rosetta two which is what translates Intels apps to work on Arm Macs. I noticed it the other day when I unboxed my development kit ARM Mac Mini I got a few weeks ago from apple......these drivers drivers were compiled on 04/02/2011 that means apples been considering the switch for a long time if code starts showing up way back then........its interesting anyhow...........its the reason I really was hesitant to make a patcher for use outside of myself and close friends because its just to much work Id rather contribute my part and send my stuff for the community to do with what they please. One team one dream!
 
Last edited:
  • Like
Reactions: TimothyR734

GSXB

macrumors regular
Jun 21, 2018
246
198
England
GSXB Im working on it now I should have it later tonight or early in the AM. I have to work at 3PM. IM updating open core because the version I'm using is a tad older..and was problematic with public beta..are you running 144.0.0.0.0 boot rom and is it a flashed 4,1 to 5,1 or genuine 5,1? My buddy brought his 4,1 over and my patcher worked but gave a weird issue were desktop froze narrowed it down to opencore and it worked after I applied newer opencore on beta 4. So I'm going to recompile the patcher and ill upload it.
Yes my Mac Pro is on 144.0.0.0.0 boot rom and it’s a 4.1 flashed to a 5.1
 
  • Like
Reactions: TimothyR734

thatsmeonlyme

macrumors regular
May 30, 2018
222
303
Loewenstein Germany
hallo guys,
is there anybody having the same problem as me: I am running BS DP 4 on a mid 2012 MBp 13,3“. All is working fine also Airdrop and Handoff after patching with jackluke‘s prelinked kernel. After applying the command and reboot also WIFI is working but after rebooting or shutdown and restart WIFI won‘t work until applying the command again. Any idea? Any Solution?
 
Last edited:
  • Like
Reactions: TimothyR734

ribero

macrumors newbie
Dec 17, 2017
21
33
I have one of those and temperatures are normal.

Yes, mee to I have one ;), temperature is not normal compared to how it work under Mojave/Catalina with the switch GPU option enabled.

The graphics card doesn't switch, hopefully someone will solve this in the future. It doesn't sem to affect the power consumption very much

Yes I found that, I tried gfxCardStatus and I had to kill displaypolicyd before switching it to intel integrated GPU :

Screenshot 2020-08-15 at 22.11.43.png

Temperature is still higher than with Mojave or Catalina (may be the switching partially failed and did not power off the NVIDIA GPU). need more testing here
 

Attachments

  • Screenshot 2020-08-15 at 22.11.43.png
    Screenshot 2020-08-15 at 22.11.43.png
    488.2 KB · Views: 119
Last edited:
  • Like
Reactions: TimothyR734

apfelbaum

macrumors member
Aug 31, 2014
69
114
Germany
Hello, I tried now for more than 1 hour to patch the USB installation media with big-sur-micropatcher (Version 0.1.0), however I always get the "Failed to locate Big Sur recovery USB stick for patching." error.

I downloaded the InstallAssistant.pkg of the public beta 1 via the link posted here before and it created the installation app under Applications.

After that I used the normal method in Terminal the make the bootable USB installation media via the createinstallmedia tool, so I have the "Install macOS Big Sur Beta" called USB-stick now.

However when I run micropatcher.sh I always get the same error, also when I drag and drop the USB-media into the terminal or type the path manually.

By now I tried this on two different Macs and with two different USB-sticks and always got the same error. Is this a known problem, maybe with the public beta 1?
 
  • Like
Reactions: TimothyR734

tankerthebub

macrumors member
Aug 11, 2020
35
59
Yes, mee to I have one ;), temperature is not normal compared to how it work under Mojave/Catalina with the switch GPU option enabled.



Yes I found that, I tried gfxCardStatus and I had to kill displaypolicyd before switching it to intel integrated GPU :

View attachment 944477
Temperature is still higher than with Mojave or Catalina (may be the switching partially failed and did not power off the NVIDIA GPU). need more testing here
wait were you able to get gfxcardstatus working. I haven't been able to get it working since Mojave... I had to write some script to get the gpu to switch over? Did you use a fork from GitHub or straight from his site?
 
  • Like
Reactions: TimothyR734

tankerthebub

macrumors member
Aug 11, 2020
35
59
Hello, I tried now for more than 1 hour to patch the USB installation media with big-sur-micropatcher (Version 0.1.0), however I always get the "Failed to locate Big Sur recovery USB stick for patching." error.

I downloaded the InstallAssistant.pkg of the public beta 1 via the link posted here before and it created the installation app under Applications.

After that I used the normal method in Terminal the make the bootable USB installation media via the createinstallmedia tool, so I have the "Install macOS Big Sur Beta" called USB-stick now.

However when I run micropatcher.sh I always get the same error, also when I drag and drop the USB-media into the terminal or type the path manually.

By now I tried this on two different Macs and with two different USB-sticks and always got the same error. Is this a known problem, maybe with the public beta 1?
I had the same same issue if you right click the bigsur installer and then show package contents go to contents and then resources in there you'll find createinstallmedia you want to type sudo first and then hit space drag the "createmediainstall" file to terminal and then hit space --volume then drage the install media into terminal and it should do the trick. just remember before install to disable sip and set bootargs
 
  • Like
Reactions: TimothyR734

apfelbaum

macrumors member
Aug 31, 2014
69
114
Germany
I had the same same issue if you right click the bigsur installer and then show package contents go to contents and then resources in there you'll find createinstallmedia you want to type sudo first and then hit space drag the "createmediainstall" file to terminal and then hit space --volume then drage the install media into terminal and it should do the trick. just remember before install to disable sip and set bootargs

Thanks for writing back, however I had no issues so far with the creation of the USB-installer running createmediainstall always worked. But when I run micropatcher.sh from the big-sur-micropatcher it always fails to see this USB-drive, even though I didn't change the name (as recommended in the Readme) and dragging the USB-drive manually into the terminal windows also didn't help.
 
  • Like
Reactions: TimothyR734

kegan forbes

macrumors member
Jun 14, 2017
56
23
michigan
I know this is most likely already known but I don’t feel like going through 130 pages. Just want to say I got excited just now when my cmp 5,1 booted from my Big Sur ssd before I could add open core or adjust the platform support plist the only thing done so far was set no compat check. I can’t believe I spent the last week trying to get open core to work on it when I didn’t even need it. I hope everyone else is having as good of luck as I just had.
 
  • Like
Reactions: TimothyR734

avisavis

macrumors newbie
Jun 26, 2018
6
8
wait were you able to get gfxcardstatus working. I haven't been able to get it working since Mojave... I had to write some script to get the gpu to switch over? Did you use a fork from GitHub or straight from his site?

It is working for me on Catalina - 15" early 2013 mbp(nvidia 650m).
Yes, it is fork from GitHub. Below is the link

 

gccering

macrumors newbie
Aug 15, 2020
2
1
question on change default startup after install:
I was able to install public beta on my 2013 imac using micropatcher. Now how do I make the startup disk default to Big Sur? I tried to change it in setting -> startup disk. Big Sur would show up as an option for a couple second and disappears. Is there a way that I can change from bash?
 
  • Like
Reactions: TimothyR734

oldmacs

macrumors 601
Sep 14, 2010
4,941
7,182
Australia
Sorry if this is a dumb question or has been answered already. I have a Mid 2012 MacBook Pro 13 inch Non Retina with the upgraded Wifi/Bluetooth card. What is the best way for me to try to install the public beta? Is there a specific patcher I should use?
 
  • Like
Reactions: TimothyR734

GSXB

macrumors regular
Jun 21, 2018
246
198
England
I know this is most likely already known but I don’t feel like going through 130 pages. Just want to say I got excited just now when my cmp 5,1 booted from my Big Sur ssd before I could add open core or adjust the platform support plist the only thing done so far was set no compat check. I can’t believe I spent the last week trying to get open core to work on it when I didn’t even need it. I hope everyone else is having as good of luck as I just had.
What method did you use to install big sur
I’ve been trying for two weeks and got nowhere. I’m on a Macpro 4.1/5.1
 
  • Like
Reactions: TimothyR734

Wania

macrumors member
Apr 3, 2020
73
25
question on change default startup after install:
I was able to install public beta on my 2013 imac using micropatcher. Now how do I make the startup disk default to Big Sur? I tried to change it in setting -> startup disk. Big Sur would show up as an option for a couple second and disappears. Is there a way that I can change from bash?
Hold alt/option when powerup mac, then select big sur and tap ctrl+enter
 
  • Like
Reactions: TimothyR734

ribero

macrumors newbie
Dec 17, 2017
21
33
wait were you able to get gfxcardstatus working. I haven't been able to get it working since Mojave... I had to write some script to get the gpu to switch over? Did you use a fork from GitHub or straight from his site?

Got it from here Download gfxCardStatus v2.3

I had to kill the process displaypolicyd which prevent GfxCardStatus to work then I was able to "switch" the GPU.
I'm not 100% convinced it worked as expected as I found the MBP still too hot (which is the case when the NVIDIA card is powered-on). So it may switch to Intel (as shown in the screenshot) but may not completely work as macOS does in Mojave.

I'm very interested by your script to switch GPU. May be you can share it ?
 

avisavis

macrumors newbie
Jun 26, 2018
6
8
Thanks ! I updated from 2.3 to 2.4.4i

Did you had to kill displaypolicyd before being able to switch to intel GPU ?

No, I didn't kill displaypolicyd.

If there are no dependencies(like some apps using dgpu), we can switch manually as well.
Added some screenshots for reference.
screenshot1: On igpu
screenshot2: Changed to dgpu manually. Parallels is using dgpu. So, couldn't change to igpu.
screenshot3: Closed parallels. And no dependencies are there
screenshot4: Changed to igpu manually again.
 

Attachments

  • gfxcardstatus Screenshot1 2020-08-16 at 14.31.46.png
    gfxcardstatus Screenshot1 2020-08-16 at 14.31.46.png
    116 KB · Views: 282
  • gfxcardstatus Screenshot2 2020-08-16 at 14.32.01.png
    gfxcardstatus Screenshot2 2020-08-16 at 14.32.01.png
    137.7 KB · Views: 270
  • gfxcardstatus Screenshot3 2020-08-16 at 14.33.01.png
    gfxcardstatus Screenshot3 2020-08-16 at 14.33.01.png
    132.8 KB · Views: 250
  • gfxcardstatus Screenshot4 2020-08-16 at 14.33.07.png
    gfxcardstatus Screenshot4 2020-08-16 at 14.33.07.png
    117.1 KB · Views: 248
Last edited:
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.