AnonyManx

Hey, I was tied up with other things for a bit and now am back to trying to get BT resurrected. I looked at the RehabMan things, but am not sure what I would do with some of that. Here's a RunMe of the current state of things, which may differ (ever so slightly) from the previous RunMe. Help? Send me HouseKitty.zip

Haven't had a chance to look at this again yet... will report back soon. Thanks.

Nope. No change. Still "Bluetooth not available". Fortunately my BT Magic touchpad works as USB when charging.

Oh, yeah. Here it is. (I posted this yesterday. Well, I thought I posted it yesterday. Here I go again.) Send me HouseKitty.zip

MacOS 10.14.4 Asus Prime Z390-a i7 8700k 32 GB RAM Radeon RX580 8GB Crucial 1TB SSD (SATA) [other drives temporarily disconnected during repairs] BCM94360CD on PCI adapter Things have been up and running for a while, and I have been taking the "it's working so don't mess with it" approach. On Friday evening, we had a power outage (it's been 10 years since our last one, so it was a surprise) and my machine went down hard. When I powered it back on, it threw a memory allocation error and wouldn't boot. Power cycle; same result. Damn! Well, I back things up by cloning the drive after any major changes... so time to boot to the backup, right? Wrong. Same behavior. Damn, this is going to involve actual work. And if I'm going to work on things, I may as well work on things, right? So far I have: Updated the motherboard BIOS (I was a few versions back) and made sure it still had the proper settings. Updated Clover and kexts. I have also pestered another person with the same motherboard who has updated more recently than I have, and he has been a helpful extra brain. At this point things are almost right again. Almost. MacOS doesn't recognize my Bluetooth, which was working before. It's a natively-supported card, and the wifi portion of the card is working. Kexts in play are: AirportBrcmFixup.kext AppleALC.kext FakeSMC.kext IntelMausi.kext Lilu.kext WhateverGreen.kext (probably not needed) Drivers in play are: ApfsDriverLoader.efi AptioMemoryFix.efi FSInject.efi HFSPlus.efi NTFS-64.efia (not needed at the moment, but there) Patches in play are: DSDT.aml SSDT-Z390-A.aml Any idea what I'm missing regarding the Broadcom card? As I said, wifi is fine; the Bluetooth potential of the card isn't even identified. I suppose there's the chance that the card took damage when the system went down, but it seems unlikely.

MacOS 10.14.4 Asus Prime Z390-a i7 8700k 32 GB RAM Radeon RX580 8GB Crucial 1TB SSD (SATA) [other drives temporarily disconnected during repairs] BCM94360CD on PCI adapter Things have been up and running for a while, and I have been taking the "it's working so don't mess with it" approach. On Friday evening, we had a power outage (it's been 10 years since our last one, so it was a surprise) and my machine went down hard. When I powered it back on, it threw a memory allocation error and wouldn't boot. Power cycle; same result. Damn! Well, I back things up by cloning the drive after any major changes... so time to boot to the backup, right? Wrong. Same behavior. Damn, this is going to involve actual work. And if I'm going to work on things, I may as well work on things, right? So far I have: Updated the motherboard BIOS (I was a few versions back) and made sure it still had the proper settings. Updated Clover and kexts. I have also pestered another person with the same motherboard who has updated more recently than I have, and he has been a helpful extra brain. At this point things are almost right again. Almost. MacOS doesn't recognize my Bluetooth, which was working before. It's a natively-supported card, and the wifi portion of the card is working. Kexts in play are: AirportBrcmFixup.kext AppleALC.kext FakeSMC.kext IntelMausi.kext Lilu.kext WhateverGreen.kext (probably not needed) Drivers in play are: ApfsDriverLoader.efi AptioMemoryFix.efi FSInject.efi HFSPlus.efi NTFS-64.efia (not needed at the moment, but there) Patches in play are: DSDT.aml SSDT-Z390-A.aml Any idea what I'm missing regarding the Broadcom card? As I said, wifi is fine; the Bluetooth potential of the card isn't even identified.

Dumb question: If the USB weirdness were the 15-port limit, why would it still work with thumb drives? It sees thumb drives without any issue; it doesn't see SATA/USB drives (SSD or spinny). Follow up to the dumb question: This problem doesn't happen under HighSierra at all. Under HighSierra, I can plug the same SATA/USB drives in anywhere and they pop up right away. Same Clover/kext lineup for both Mojave and High Sierra right now.

Thanks for the pointer! I'm assuming that script simply runs the terminal command to set hibernate mode to 0? I didn't run your script because I'd rather learn the steps myself... but your instructions told me what command to seek out! I do still get the unallocated error boot fail occasionally - a reboot seems to cure it and the system is rock-solid while in use. I can play Civ6! WooHOO! Also, the system won't recognize internal SATA-type drives when connected by a SATA/USB adapter. The adapter is fine, and the drives are recognized when I boot into HighSierra on the same system... Any guidance? P.S. I sent you beer money.

Greetings! I upgraded from HighSierra to Mojave (basically, just to see what would happen) and it made a lot of things better. The recurring issue I'm having is that I will walk away with the machine in screen saver mode and return an hour later to it having crashed/rebooted and it's at a memory allocation error black screen. Manually rebooting brings all things right, and it then plays nicely... It seems like I might need a new DSDT patch for Mojave? I still have a HighSierra drive as well, if that matters at all. Send me iMac.zip

Attached is the RunMe results from within Mojave. I still have a partition booting HighSierra, by the way, and may keep that for a while... or may not, since my MacBookPro seems to be toes-up. Send me iMac.zip

WiFi works in Mojave. Upgrading to Mojave totally fixed that. The Mojave headache is recognizing USB drives (like a SATA SSD connected by USB) and ejecting any drives. So I have no problem getting USB thumb drives recognized, but ejecting doesn't happen. But I will throw that into the 10.13 Clover kext folder and see what happens. After my current project (cloning the Mojave drive to a spare SSD) finishes.

Over the past few weeks, I've managed to assemble a fairly-functional Hackintosh. With some help from this site specifically, I even ended up with HighSierra behaving properly for shutdown/restart! The only remaining gremlins were a WiFi glitch (sees networks; can't actually connect) and the Thunderbolt expansion card debacle. Here's the hardware info: Asus Prime Z390-A Intel i7-8700k Radeon RX 580 8 GB 32 GB 2400 MHz DDR4 Broadcom BCM94360CD BT/WiFi on PCIe adapter Asus Thunderbolt 3 expansion card 3 SSDs at 1 TB each: 1 currently with HighSierra, 1 currently with Mojave, & 1 with a small Windows partition (unactivated) & also an exFAT data partition in case I decide to activate Windows (seems unlikely) Oh, and a spiffy Corsair mechanical keyboard. When I installed drivers for it (GitHub project - not actual Corsair drivers), all sorts of headaches were spawned. So I removed the drivers, and was considering nuking that drive when I instead updated my HighSierra installation thumb drive and installed a second HighSierra drive. That install went *almost perfectly* (still the WiFi glitch). That's the drive from which I'm writing this post, by the way, because... ...the original HighSierra drive was wanting to be upgraded to Mojave. I thought, "Why not see what happens? This should be fun." I told it to install Mojave. It did. Perfectly and with no errors. And installing Mojave solved the WiFi glitch! Sweet! I noticed that Mojave wants to point /Documents to iCloud. Brilliant! Love it! Let's put all the things on iCloud! So I connect to my MacBook and start trying to pull things over... and get errors. Weird ones. My MacBook is old (late-2011 17" MacBook Pro with 16 GB RAM & 1 TB SSD), but has always been rock-solid reliable (except when the video chip failure hit it; that was covered by Apple). But suddenly the MacBook is being squirrelly and I want to get the data off of it. No big deal - I have a USB Time Machine backup as well. So Mojave won't recognize the existence of internal SATA drives connected by a USB/SATA adapter. I have tried with 3 different drives (the Time Machine drive is spinny, but the others are SSDs) and 2 different USB/SATA adapters. No go. Mojave will recognize thumb drives without a hitch, though. Oh, and ejecting drives is... not always successful. So somethings not right in Mojave. But most things are. Since I want continuity of data, and since I have this HighSierra partition, I booted into this and attached the Time Machine USB drive and POOF! I have access to my backups. Brilliant! I have just copied the things that are important onto the exFAT partition so that I can do what I will with them from there (not to iCloud yet because I haven't put my AppleID into this install). ANYHOW, It seems like I may need some different kexts for Mojave? I'm truly not sure. The recognizing USB/SATA drives thing is annoying and I definitely want to be able to do that. I love pulling hard drives and hooking 'em up USB to do quick tweaks. Also the drive eject command not working right is a sign of a problem. Other than that, any guidance on the Thunderbolt card would be appreciated, but at this point I'm leaning towards taking it to a gun range and using it as target practice (and also selling my Thunderbolt Display and buying a new 4k monitor)... I have attached the CLOVER folder from the EFI partition on my Mojave drive. It is the same as on this HighSierra drive. Maybe it shouldn't be completely the same? CLOVER.zip

Hardware: Asus Prime Z390-A (BIOS is up-to-date) Intel i7-8700k 32 GB 2400 MHz DDR4 Radeon RX 580 8192 MB Crucial 1 TB SSD (Mojave drive - there are others) And I have the Asus Thunderbolt 3 expansion card. It's the only thing not working. I do have a Windows drive, and I have attempted to install the Thunderbolt card through Windows without success. I know the identity of its PCIe slot in which it is located. I have enabled Thunderbolt in the BIOS. I have connected the Thunderbolt card to the Thunderbolt header on the motherboard. Windows Device Manager does not appear to detect the card to allow driver installation. Any suggestions are welcome. My goal is to use the Thunderbolt card to connect my Apple Thunderbolt Display to the system. If this endeavor fails, I will just use the failure as an excuse for a spiffy new 4k monitor and either keep the Thunderbolt Display with my MacBook Pro or sell it to MacOfAllTrades.

Thanks [ref]erroruser[/ref], . I already had SMBIOS set to iMac18,3 and just set darkwake to 8. Experimenting continues.

Greetings and thanks in advance for helping! I am running a home-built machine, High Sierra, with: - i7-8700k processor - Asus Prime Z390-A motherboard - G.Skill 32GB 2400MHz DDR4 - Radeon RX 580 video card - Broadcom BCM94360CD WiFi/BT/continuity card (on adapter) - Asus Thunderbolt 3 expansion card (not yet working) The BIOS is up-to-date (first thing I did during hardware assembly). This is a from-scratch High Sierra installation where I have been working the Clover configuration & kext selections myself (with research). I couldn't tell with Olarila Clover folder would be applicable to a Z390 chipset, but I have attached my kext file and config.plist for reference/suggestions. Video card works. Sound works. Ethernet works but sometimes loses link when system is idle; fix is to unplug/replug cable. Bluetooth works. WiFi card sees networks but can't actually join (tells me wrong password; password is not wrong). Sleep/shutdown/restart don't work properly. Oh, and for some reason there is a debris install partition that shows in Clover. It doesn't work and I'd love for it to go away. EDIT to add: Just rebooted and got a screen that ends in: but after a couple of hard reboots I was able to get back in. kexts & config.zip Send me Jenifers-iMac.zip