I spent some time with BigMac 2.0 as the advice says and yeah I got it to work. That's not exactly why I'm writing this. Let me explain : After the BM2.0 install I did notice some weirdness using FW (firewire). At the time I was deciding if that the driver for my FW device (MOTU 896mk3 hybrid (which mean it has both FW and USB)) was at fault but I know that when I used the big-sur-micropatcher on a 2011 MBP and hooked the same device into either the FW or USB or thunderbolt (I have the FW->Thunderbolt adapter) port on the 2011 MBP that the device and the application using this device was happy. Getting into the details of the behavior is another story which if people want to know I'd be happy to share.
Anyways because my MOTU 896mk3 was working on my micro-patched 2011 MBP I said to myself "gee maybe let me give this another try on my MacPro3,1. Now since the 1st time I tried this I updated my MacPro to have a BCM94360CD. This has made a world of difference. The big-sur-micropatcher got me through the big sur install and into the "reboot loop" at which point I booted off the "big-sur-micropatcher USB" and then I ran the patch-kexts.sh --2010 ... and then the next reboot got me to the OS setup questions (language picker). Literally within an hour ... not 9 days if you followed what I wrote on BM2.0).
SO MY POINT IS the big-sur-micropatcher works on a MacPro 3,1 folks AND a 2011 MBP. Awesomeness !
Ok so now my plea for advice : I'm still seeing weirdness with my FW device from my MacPro3,1 THAT I DON'T SEE FROM THE MACBOOKPRO that again both of them had BigSur 11.1 loaded using big-sur-micropatcher which is why I decided to share the mixed news here. I don't know if this is the MOTU device driver (although the same driver work for a 2011 MacBookPro to hook the 896mk3 up over FW or USB or thunderbolt (as this 2011 MBP has them all) OR maybe there's something about FW under BigSur on a MacPro3,1 which doesn't natively have thunderbolt and that it's just time to add thunderbolt to this MacPro 3,1 with a "GC Titan Ridge" card. Did that make sense ? What do people think ?
Either way spending the $35 for the BT update and potentially another $175 for the correctly programmed GC Titan Ridge card IS BETTER THAN GETTING A NEW MAC cause the software I'm running on the MacPro3,1 still handles the load I'm throwing at it (as verified by Catalina setup on my MacPro 3,1 .. and the same MOTU device driver). I don't think the driver is the issue ... cause if it was then I'd see the same weirdness on my big-sur-micropatcher'd 2011 MBP.
Lol did that make sense to anyone ? Hopefully this helps let people know that at least I do see the big-sur-micropatcher working as well provided you aren't using the FW bus (or an audio interface over FW or USB on a MacPro 3,1:)
I can certainly get the trace from the application too ... I'm not sure who that helps here.
I spent some time with BigMac 2.0 as the advice says and yeah I got it to work. That's not exactly why I'm writing this. Let me explain : After the BM2.0 install I did notice some weirdness using FW (firewire). At the time I was deciding if that the driver for my FW device (MOTU 896mk3 hybrid (which mean it has both FW and USB)) was at fault but I know that when I used the big-sur-micropatcher on a 2011 MBP and hooked the same device into either the FW or USB or thunderbolt (I have the FW->Thunderbolt adapter) port on the 2011 MBP that the device and the application using this device was happy. Getting into the details of the behavior is another story which if people want to know I'd be happy to share.
Anyways because my MOTU 896mk3 was working on my micro-patched 2011 MBP I said to myself "gee maybe let me give this another try on my MacPro3,1. Now since the 1st time I tried this I updated my MacPro to have a BCM94360CD. This has made a world of difference. The big-sur-micropatcher got me through the big sur install and into the "reboot loop" at which point I booted off the "big-sur-micropatcher USB" and then I ran the patch-kexts.sh --2010 ... and then the next reboot got me to the OS setup questions (language picker). Literally within an hour ... not 9 days if you followed what I wrote on BM2.0).
SO MY POINT IS the big-sur-micropatcher works on a MacPro 3,1 folks AND a 2011 MBP. Awesomeness !
Ok so now my plea for advice : I'm still seeing weirdness with my FW device from my MacPro3,1 THAT I DON'T SEE FROM THE MACBOOKPRO that again both of them had BigSur 11.1 loaded using big-sur-micropatcher which is why I decided to share the mixed news here. I don't know if this is the MOTU device driver (although the same driver work for a 2011 MacBookPro to hook the 896mk3 up over FW or USB or thunderbolt (as this 2011 MBP has them all) OR maybe there's something about FW under BigSur on a MacPro3,1 which doesn't natively have thunderbolt and that it's just time to add thunderbolt to this MacPro 3,1 with a "GC Titan Ridge" card. Did that make sense ? What do people think ?
Either way spending the $35 for the BT update and potentially another $175 for the correctly programmed GC Titan Ridge card IS BETTER THAN GETTING A NEW MAC cause the software I'm running on the MacPro3,1 still handles the load I'm throwing at it (as verified by Catalina setup on my MacPro 3,1 .. and the same MOTU device driver). I don't think the driver is the issue ... cause if it was then I'd see the same weirdness on my big-sur-micropatcher'd 2011 MBP.
Lol did that make sense to anyone ? Hopefully this helps let people know that at least I do see the big-sur-micropatcher working as well provided you aren't using the FW bus (or an audio interface over FW or USB on a MacPro 3,1:)
I can certainly get the trace from the application too ... I'm not sure who that helps here.