Search results

Here are all my disks since you asked. I have a bootcamp partition on the samsung SSD, and a windows data drive on the 2 TB samsung NVME.the mac drive and main boot is a WD black 500. the other drives are for data and my time machine

Not sure, I don’t have verbose booting set up since like 95% of the time it reboots fine.

I just have the issue with missing drives. I’ll pull the list of them. Have a mix of nvme and ssd drives

No, I am using a WD Black 500GB - Yeah I had seen that Samsung have some issues so stayed away. Refreshing OC and resetting NVRAM seems to have fixed it. But it's annoying, and I am not sure what makes it happen. Running disk until now and will see if anything comes from that. I am still on...

Hoping someone can give me an idea where to start. on occasion my hackintosh will take forever to start, when it finally does, it only recognizes the system drive and non of the other drives in the machine. Sometimes i can reboot and fix it, sometimes it seems to fix it self after a few...

Thanks, that did the trick!

Well, I upgraded to Ventura - Current version which is 13.5. Everything seems good, except my Ethernet stopped working. Apple VTD is on, I reset NVRAM and restarted. I'll try shutting down later and see if that helps but a quick search really didn't come up with much for me to try.

Final question for the moment, I have the latest version of Montgomery installed, can I just run the Ventura upgrade and be all set, or do I need to do any prep first, other than a backup. I searched the thread I didn’t see anything obvious that changed in the update.

Perfect thank you

Thanks for the update! One quick thing - I am on the latest OC release, the OCAT tool seems to think my Lilu, VirtualSMC and WhateverGreen are "newer" version than it can find. Should I allow the tool to downgrade these files? Its been a while since I messed with updating these, so I am not...

Anyone else here just still running the original BIOS? I have not updated mine after hearing all the problems folks had. Maybe we can have @CaseySJ put a quick not in the build post with the newest known working version of the BIOS so folks know what is safe? I think F23 was?

This worked for me thank you, I had a few minor issues but managed to get the machine to see the mac updates and update to the latest of Monterey. Now I am really tempted to try an update to Ventura! Thanks again! Mike

Yeah I was going to do a full CCC backup of the machine's disk. I thought it was already making a backup as I of course get the error using hackDrom that there is not enough space on the EFI partition to do the upgrade. B/C of course I have to have every problem imaginable :) After that I need...

Interestingly they are not checked so I will do some more looking after work and get the settings right. I also still have the original Bios on the board and never updated it since I got it. All of the updates seemed to break crap. It seems that the latest revisions f23 is safe to update to...

Also, @CaseySJ the first section of the main post where is says MacPro7,1 users click here for additional information about RestrictEvents. That link does not seem to work anymore - clicking it just takes me to the top of the 1st page of the thread.

Do I do that, then run the upgrade, or vice versa? Am just worried about getting into a non-bootable state EDIT: Thinking about it I would guess using the latest opencore configurator would have the right settings, so update the config, then upgrade.

Hello, I'm currently running on Monterey 12.2, OC version 7.8 - been a while since I updated b/c everything runs pretty well. I realized that the mac software updates were not downloading, so I decided I would start getting everything up to date and maybe upgrade to ventura. So, to upgrade...

Not sure there are widespread problems. I for one have been running on an SN850 since day one with Monterey with no issues. Other NVME drives that have problems with MacOs are generally trim related, there are a few ways to address that I think. Mike

Yup that’s about what I figured. I would imagine getting the code out of the Apple silicon would be difficult anyway. Not like they are making all the diagnostic tool available for us to use

Isn’t the Thunderbolt controller built in to the M1? I’m not sure extracting it would help but I am far from an expert Mike