- Joined
- Mar 18, 2017
- Messages
- 1,042
- Motherboard
- ASUS ROG Rampage VI Extreme
- CPU
- i9-7940X
- Graphics
- 2 X VEGA 56
- Mac
-
- Mobile Phone
-
The ASMedia.kext is linked here : #1,254
You should see your RPXX ---> PXSX on your IOReg with this kext, that's why it's strange to me if you can't see with : let me know.
[ edit : and when your USB.kext is ok you can remove the ASMedia.kext ]
On my Asus X299 Prime Deluxe I use full SSDTs and SSDT-PMC but from where I am writing now, on my Asus X299 Rampage Build, I only use the required SSDTs and two for my VEGA GPUs.
So SSDT-PMC is not the cause of the problem.
Maybe some progress RP13 is the internal USB C :@Jasoncole98 - still need to get that PXSX controller renamed before you can really start I think.
Good news over here - I am writing this post from Big Sur booted and working well on Gigabyte X299 Aorus Ultra Pro, NVRAM is working, Bluetooth and WiFi also working natively (its not the on board Killer AC WiFi for anyone stumbling on this, I swapped the mini M2 card on the back panel for BCM43960CS).
I've still got to tidy up some basics first, but its working and I need the machine for work tomorrow, but after that I'll start to take a look at the USB mapping and see if we can move this Gigabyte thing forward
(EDIT: Spoke too soon, I have the same problem as you, on the same 4 back panel ports, no devices detected - and I thought they were attached to the X299 chipset and wouldn't be a problem. Thats even with USBInjectAll and XhciPortLimit true. Will dig deeper tomorrow)
Device (\_SB.PC00.RP13.XHC2)
{
Name (_ADR, Zero) // _ADR: Address
Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
If (LEqual (Arg2, Zero))
{
Return (Buffer (One)
{
0x03
})
}
Store (Package (0x1B)
{
"AAPL,slot-name",
Buffer (0x09)
{
"Built In"
},
"built-in",
Buffer (One)
{
0x00
},
"device-id",
Buffer (0x04)
{
0x42, 0x21, 0x00, 0x00
},
"name",
Buffer (0x17)
{
"ASMedia XHC Controller"
},
"model",
Buffer (0x29)
{
"ASMedia ASM3142 USB 3.1 Type-C Internal "
},
"AAPL,current-available",
0x0834,
"AAPL,current-extra",
0x0A8C,
"AAPL,current-in-sleep",
0x0A8C,
"AAPL,max-port-current-in-sleep",
0x0834,
"AAPL,device-internal",
Zero,
"AAPL,clock-id",
Buffer (One)
{
0x01
},
"AAPL,root-hub-depth",
0x1A,
"AAPL,XHC-clock-id",
One,
Buffer (One)
{
0x00
}
}, Local0)
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}
}
Hi,No one has responded to the request for an explanation of exactly what MacOS does with SMBIOS, which I guess means its not very clear, so I've been thinking we should do some structured testing around that and I'd welcome input from everyone else, so we can compare performance, stability and availability of key features.
Im thinking run a suite of benchmarks, note any failures or crashes, check for differences while under load, like CPU frequency, number of active cores, which frame buffer is in use etc those kind of things, see if we can identify what is affected by the change, and see if there are genuine benefits or drawbacks of each SMBIOS for X299 outside the obvious ones like MacPro memory notification which are mostly cosmetic. I haven't really finished thinking through how it would work, something like:
Geekbench 5 - CPU and GPU tests
FCPX - BruceX
VideoProc - to check HEVC and H264 hardware acceleration
VDADecoder
Cinebench - 10 min run, multi and single core scores,
Black Magic disk speed test
No USB issues by my side : some minor modifications #1,405 & #1,376 and all works as on Catalina without ASMedia.kext.@rustEswan Thank you for your valiant efforts, sorry to hear that you are experiencing the same level of frustration I am, tell you what, later tonight or tomorrow, I'll boot into windows and see what those ports show up as and the paths. This may give us a clue how to do it in Mac OS.
@Loloflatsix I saw your code, but I wasn't sure where to inject it, and I used @rustEswan .aml file instead, what are your thoughts on our USB issues?