Nah, I should have looked around the rest of the site for an answer before asking. I have been coming here for the past few years and always just head straight for Casey's threads. I sometimes forget there's a whole other site beyond his threads.
Although I will say I did read the first couple...
I'm considering going the Asus ProArt route with a i9-13900 CPU (upgrading from my i9-9900K on a Designaire).
One thing I am a little confused/concerned about is how to deal with E-Cores and P-Cores on these newfangled chips, and how it will affect overall performance for my primary use-case...
No OCS or other warnings
Big Sur boots and appears to be working properly.
Bluetooth works (magic trackpad) and I can enable/disable
Bluetooth works if I boot into windows then restart (warm) and boot into macOS.
So, because of some app incompatibilities I had to roll back to Big Sur for the time being.
I did that yesterday, and everything was fine.
This afternoon I started noticing that that if I leave my computer unattended for a little while it will panic, and on logging back in I get this in the...
well rats. I am being bitten by the smallTreeIntel82576 issue. I need both of my network ports. ONe is for my regular ethernet and one is for my Waves Soundgrid audio interface.
Any workarounds for the smallTree issue that anyone knows of or do I need to roll back to Big Sur?
The firmware is 2B2QEXM7.
I have now reinstalled Windows on my Samsung 970 (macOS Installed on the Inland Premium), and the boot time is still sub 25 seconds.
Now if only I hadnt accidentally blown away the partition for my audio projects volume, today would have been a great day. :D...
OK, I reinstalled Monterey on an Inland Premium 2TB NVME and then restored settings and files from my CCC backup disk via the Transfer Assistant.
Boot time is now 23 seconds vs close to two minutes on the Samsung 970 plus
Ahh Windows left behind an EFI partition.
edit: Well, I thought that there was a EFI partition left over, but that is not the case.
There is something weird going on though. I cant seem to get a bootable backup working. :/
Ahha.. Looks like Carbon Copy Cloner does not create bootable backups...
Yeah that is exactly what I did.
But when I boot, OC sees the MacOS volume on the Samsung, and an EFI volume, but not the newly imaged "Monterey" volume on the Inland Premium.
weird.
I can also confirm that the boot time on my wifes little hackintosh has increased with Monterey using a 970 as well..
I am in the process of trying to clone my system from my 970 onto a Inland Premium, which uses a different controller.
Having some trouble getting a bootable copy using Carbon...
No I don't think they are.
I think they were installed along with the EFI I grabbed in the OC 7.4 miniguide, or got installed when I was working on things and I never got around to removing them
It doesn't seem to have reduced it.
Here is my EFI folder. maybe you see something else I did wrong?
Interesting. Just noticed that my EFI partition name changed to EFI-SAM-79R.
Guess that happened during the Monterey upgrade..
This is probably not a reasonable amount of time for TRIM?
"kernel: (apfs) spaceman_scan_free_blocks:3153: disk5 scan took 0.921803 s, trims took 93.611921 s"
Yeah, I have windows installed on a 2TB Inland premium with a phison controller.
Maybe Ill move my macOS install over there and reinstall Windows on this samsung.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.