- Joined
- Oct 29, 2012
- Messages
- 13
- Motherboard
- ASUS X99A
- CPU
- E5 2658v3
- Graphics
- GTX 1070
- Mac
- Mobile Phone
Hello
I have installed macOS Sonoma on the following hardware:
1st Issue:
Sleep: Although I've set the internal USB header where the Bluetooth card is connected to "Internal," my Hackintosh has a problem where it won't go to sleep properly. It briefly enters sleep mode but is instantly awakened. I was able to pinpoint the problem more precisely:
I've now done USB mapping in three different ways:
After creating the USB-Map.kext, I have removed SSDT-RHUB.aml and kept the USB-Map.kext.
Bluetooth PCIe card is on Port HS07 -> set to "Internal." But the Bluetooth USB Header for the PCIe Card appears under a USB 2.0 Hub.
What I found particularly interesting is that it seems like four ports on the back of my PC are connected through a USB hub on my motherboard. Whenever I connect a device to one of these four ports, it gets assigned to the same port "HS05" and is listed under the individual AppleUSB20HubPort:
IOREG of the ports using my manually created USBMap.kext:
System Profiler:
My question: Do I need to map something individually for these ports, or is it okay as is? I don't know how I could map them otherwise since they seem to be connected to a USB Hub (even the Gigabyte Motherboard manual states that these ports are connected via a USB 2.0 Hub)
I've also mapped this strange "ITE Device" as "Internal" since it's likely internal to the motherboard (I don't have any other devices connected via USB 2.0 except the Bluetooth USB header for the BT/WiFi PCIe card or USB 3.0 header on the motherboard. I only use the rear IO USB ports and the one USB header on the motherboard for the WiFi/Bluetooth PCIe card).
I also tried to create a USB Map using USBToolbox but I still have the same problem as with my manually created USBMap.kext
When I put it to sleep, it wakes up immediately. I could solve the whole problem with the SSDT-GPRW.aml, but then the wake via USB doesn't work (which is understandable since this .aml disables USB). I can only wake it using the power button. I could identify the problem: when I disconnect the USB header from the WiFi/USB PCIe card, sleep works perfectly. Therefore, my suspicion is that there might be some issue with the USB mapping. I can't say what the problem is, as the ports, which are not on the rear IO, are mapped as "Internal." My suspicion is that the Bluetooth USB host controller isn't directly attached to the port, and there's a USB 2.0 hub in between, but that's just a vague guess...
2nd Issue:
I am an Android developer, or cross-platform developer, and I need Android Studio and Android emulators. However, I can't use Android x86_64 images with qemu on the Hackintosh because I only get a black screen on the emulator, and the device doesn't work. The x86 Android images work flawlessly, but the highest Android version you can use as an x86 image is Android 11, which is outdated for my testing purposes. Does anyone know how to resolve this? AppleVTD and DMAC work on my Hackintosh (Docker and iOS emulator work, by the way).
Does anyone possibly know what I might have done wrong here?
My current SSDTs are:
I have installed macOS Sonoma on the following hardware:
- Motherboard: Gigabyte B760M Gaming X DDR4
- CPU: Intel Core i5 12400F
- RAM: 16GB DDR4 3200 Mhz
- GPU: AMD Radeon RX5700
- WiFi: ABWB 802.11 AC WI-FI + Bluetooth 4.0 PCI-Express (PCI-E) BCM94360CS2
1st Issue:
Sleep: Although I've set the internal USB header where the Bluetooth card is connected to "Internal," my Hackintosh has a problem where it won't go to sleep properly. It briefly enters sleep mode but is instantly awakened. I was able to pinpoint the problem more precisely:
I've now done USB mapping in three different ways:
- 1x Manually:
After creating the USB-Map.kext, I have removed SSDT-RHUB.aml and kept the USB-Map.kext.
Bluetooth PCIe card is on Port HS07 -> set to "Internal." But the Bluetooth USB Header for the PCIe Card appears under a USB 2.0 Hub.
What I found particularly interesting is that it seems like four ports on the back of my PC are connected through a USB hub on my motherboard. Whenever I connect a device to one of these four ports, it gets assigned to the same port "HS05" and is listed under the individual AppleUSB20HubPort:
IOREG of the ports using my manually created USBMap.kext:
System Profiler:
My question: Do I need to map something individually for these ports, or is it okay as is? I don't know how I could map them otherwise since they seem to be connected to a USB Hub (even the Gigabyte Motherboard manual states that these ports are connected via a USB 2.0 Hub)
I've also mapped this strange "ITE Device" as "Internal" since it's likely internal to the motherboard (I don't have any other devices connected via USB 2.0 except the Bluetooth USB header for the BT/WiFi PCIe card or USB 3.0 header on the motherboard. I only use the rear IO USB ports and the one USB header on the motherboard for the WiFi/Bluetooth PCIe card).
I also tried to create a USB Map using USBToolbox but I still have the same problem as with my manually created USBMap.kext
When I put it to sleep, it wakes up immediately. I could solve the whole problem with the SSDT-GPRW.aml, but then the wake via USB doesn't work (which is understandable since this .aml disables USB). I can only wake it using the power button. I could identify the problem: when I disconnect the USB header from the WiFi/USB PCIe card, sleep works perfectly. Therefore, my suspicion is that there might be some issue with the USB mapping. I can't say what the problem is, as the ports, which are not on the rear IO, are mapped as "Internal." My suspicion is that the Bluetooth USB host controller isn't directly attached to the port, and there's a USB 2.0 hub in between, but that's just a vague guess...
2nd Issue:
I am an Android developer, or cross-platform developer, and I need Android Studio and Android emulators. However, I can't use Android x86_64 images with qemu on the Hackintosh because I only get a black screen on the emulator, and the device doesn't work. The x86 Android images work flawlessly, but the highest Android version you can use as an x86 image is Android 11, which is outdated for my testing purposes. Does anyone know how to resolve this? AppleVTD and DMAC work on my Hackintosh (Docker and iOS emulator work, by the way).
Does anyone possibly know what I might have done wrong here?
My current SSDTs are:
Last edited: