davidm71

Mine is an nvme raid card. Never worked.

Hi, Recently did a Sonoma upgrade using Opencore patcher and booted into Sonoma and went online and now I keep on getting these WifiAgent Quit Unexpectedly popups. Every thing seems to be working. Just need to silence this popup. Thanks

Saw reference to highpoint card working on a hackintosh. Curious and want to know more please.

Well there must be something I'm missing. Must be an ACPI device not addressed correctly or the system has a firewall preventing the web interface from seeing it. Still not going to give up. Appreciate the help anyhow. Thank you

@J Lamp I installed both pkg's from Highpoint's support site and installed the manufacturer supplied kext installer and the web gui pkg. I also disabled SIP security and TPM as advised. Tried my best to disable secure boot as well. The problem is the web gui states that the adapter is not found and thus the driver is not found. Running 'Kextstat' I see that the Highpoint kext is running. I see it also in system profiler. Not sure where the kext is installed. I think its in Library/Extensions. As far as your Areca cards go try an SSDT. Since I figured out how to do mine I'm willing to help with yours if you need it. I think it can be done in config.plist deviceproperties section but haven't worked out the details how. The spoofing gets rid of that annoying message at boot asking to initialize or ignore or whatever. Would be very helpful with Intel raids you dual boot and don't want Mac to see the array. Thanks for your suggestions and help. Heres my ssdt code to turn drives internal for all four drives: DefinitionBlock ("", "SSDT", 2, "hack", "NVMe", 0x00000000) { External (_SB_.PCI0.PEG0.PEGP, DeviceObj) Device (_SB.PCI0.PEG0.PEGP.PBR0) { Name (_ADR, 0x00090000) // _ADR: Address Device (PBR1) { Name (_ADR, Zero) // _ADR: Address Device (PBRA) { Name (_ADR, 0x00080000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRB) { Name (_ADR, 0x00090000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRC) { Name (_ADR, 0x00100000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRD) { Name (_ADR, 0x00110000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } } } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRA.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRB.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRC.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRD.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } } And here is the method code to hide the drives spoofing their class code id: If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x04) { "class-code", Buffer (0x04) { 0xFF, 0x08, 0x01, 0x00 // .... }, "built-in", Buffer (One) { 0x00 // . } })

Still think this issue is ACPI related. For one didn't realize the drives were showing up as external drives. Fixed it by creating an SSDT. However the Highpoint Web portal manager still states that it can't find the controller or the driver. Finally I gave up and modified the ssdt to spoof another device based on another guide and now at least the four nvme drives do not get recognized or come up with that annoying message 'ignore or initialize..'.

I originally did have them listed in config.plist using data from Hackintool but I probably didn't put in the correct code and maybe made a mistake with the acpi addressing. These drives were actually nested behind three switches from the motherboard onto the Highpoint card. I went with SSDTs thinking the reason the card doesn't work is related to ACPI. I am sure either or method works equally as well. Thank you for the suggestion.

Was able to finally access each solid state nvme drive on the Highpoint card. Depending on the method I used I can either hide them all or mark them all as internal. The following is internal DefinitionBlock ("", "SSDT", 2, "hack", "NVMe", 0x00000000) { External (_SB_.PCI0.PEG0.PEGP, DeviceObj) Device (_SB.PCI0.PEG0.PEGP.PBR0) { Name (_ADR, 0x00090000) // _ADR: Address Device (PBR1) { Name (_ADR, Zero) // _ADR: Address Device (PBRA) { Name (_ADR, 0x00080000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRB) { Name (_ADR, 0x00090000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRC) { Name (_ADR, 0x00100000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRD) { Name (_ADR, 0x00110000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } } } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRA.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRB.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRC.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBR1.PBRD.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } } Changing the method code to this hides them which is fine considering I still can't get the highpoint card working and seeing four individual drives pop up for initialization at boot is annoying. Hides them: If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x04) { "class-code", Buffer (0x04) { 0xFF, 0x08, 0x01, 0x00 // .... }, "built-in", Buffer (One) { 0x00 // . } })

Redid the code. At work and can't test: DefinitionBlock ("", "SSDT", 2, "hack", "NVMe", 0x00000000) { External (_SB_.PCI0.PEG0.PEGP, DeviceObj) Device (_SB.PCI0.PEG0.PEGP.PBR0) { Name (_ADR, 0x00900000) // _ADR: Address Device (PBRA) { Name (_ADR, 0x00080000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRB) { Name (_ADR, 0x00090000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRC) { Name (_ADR, 0x00100000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } Device (PBRD) { Name (_ADR, 0x00100000) // _ADR: Address Device (SSD0) { Name (_ADR, Zero) // _ADR: Address } } } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBRA.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBRB.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBRC.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } Method (_SB.PCI0.PEG0.PEGP.PBR0.PBRD.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x02) { "built-in", Buffer (One) { 0x00 // . } }) } }

Hi, Having trouble addressing Nvme drives that are behind two bridge switches as follows. The first switch is at address _SB_.PCI0.PEG0.PEGP at address 0x0009000. Then nested down we have four more at 0x00110000,0x00100000,0x00800000, + 0x00900000. Hopefully I'm writing those addresses correctly. Took down the ACPI paths from Windows Device Manager. Here they are: ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(1100)#PCI(0000) ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(1000)#PCI(0000) ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(0800)#PCI(0000) ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(0900)#PCI(0000) These four Nvme drives installed in a raid card that show up as external and despite my best attempt I can't get them to go 'Internal'. Was able to get it to work with another drive with only one parent bridge directly off the motherboard but these four drives being doubly nested is making it difficult. Furthermore not sure if I'm writing the built in Buffer code correctly either. On a single drive and switch bridge it works. The code Rehabman posted makes it disappear however which I find useful in cases of dual booting sometimes you want to hide a drive from macos. Anyhow my main objective is to get these four drives to show up as Internal drives and if I'm lucky get the Highpoint controller card working if not hide them from osx. Heres my experimental ssdt code: DefinitionBlock ("", "SSDT", 2, "hack", "NVMe", 0x00000000) { External (_SB_.PCI0.PEG0.PEGP, DeviceObj) Device (_SB.PCI0.PEG0.PEGP.HPC1) { Name (_ADR, 0x00090000) // _ADR: Address Device (SSD0) { Name (_ADR, 0x00110000) // _ADR: Address } } Method (_SB.PCI0.PEG0.PEGP.HPC1.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x04) { "built-in", Buffer (0x0A) { "NVMe SSD" } }) } } Have a thread here describing the issue. Please place comments there: Thank you

Hi, Been trying to make my nvme drives appear as Internal using SSDT patches. The problem is I can do it for a single disk behind a single bridge but having trouble writing to code for this layout: ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(1100)#PCI(0000) ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(1000)#PCI(0000) ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(0800)#PCI(0000) ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0900)#PCI(0000)#PCI(0900)#PCI(0000) DefinitionBlock ("", "SSDT", 2, "hack", "NVMe", 0x00000000) { External (_SB_.PCI0.PEG0.PEGP, DeviceObj) Device (_SB.PCI0.PEG0.PEGP.HPC1) { Name (_ADR, 0x00090000) // _ADR: Address Device (SSD0) { Name (_ADR, 0x00110000) // _ADR: Address } } Method (_SB.PCI0.PEG0.PEGP.HPC1.SSD0._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (!Arg2) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x04) { "built-in", Buffer (0x0A) { "NVMe SSD" } }) } } There are four drives which are installed in a highpoint raid controller If I could only access then via SSDT I could make them appear as internal drives as opposed to external drives. Maybe even get the raid card working. Wishful thinking. Thanks

Hi, First of all thanks for your replies and trying to help out on this one. I just want to stress however this is a non-bootable drive and is only a data drive. The manufacturer has indeed released official drivers for OSX including Catalina, Big Sur and newer. Second Fixnvme kext does nothing. Not even sure the card itself is being recognized. I suspect its something to do with Opencore. Not sure. Anyhow not sure how to use AHCIPortInjector you recommend using and or what good it will do. Thanks again. Found this in the Kernel logs:kernel: (HighPointNVMe) [RSNVMeController:init]2022-10-08 14:00:20.768498-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768504-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe) [12 ][RSNVMeControllerrobe]2022-10-08 14:00:20.768505-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768514-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe) return null2022-10-08 14:00:20.768515-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768516-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe) [12 ][RSNVMeControllerrobe] fail.2022-10-08 14:00:20.768518-0400 0xef Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768642-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe) [RSNVMeController:init]2022-10-08 14:00:20.768643-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768648-0400 0xef Default 0x0 0 0 kernel: (IONVMeFamily) AppleNVMe Assert failed: ( 0 != data )2022-10-08 14:00:20.768650-0400 0xef Default 0x0 0 0 kernel: (IONVMeFamily) ReleaseIDNode2022-10-08 14:00:20.768651-0400 0xef Default 0x0 0 0 kernel: (IONVMeFamily) file: /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp2022-10-08 14:00:20.768653-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe) [7 ][RSNVMeControllerrobe]2022-10-08 14:00:20.768654-0400 0xef Default 0x0 0 0 kernel: (IONVMeFamily) line: 54782022-10-08 14:00:20.768655-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768656-0400 0xef Default 0x0 0 0 kernel: (IONVMeFamily)2022-10-08 14:00:20.768660-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe) return null2022-10-08 14:00:20.768661-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-08 14:00:20.768662-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe) [7 ][RSNVMeControllerrobe] fail.2022-10-08 14:00:20.768663-0400 0xf9 Default 0x0 0 0 kernel: (HighPointNVMe) 2022-10-30 18:30:13.720715-0400 0x1f7 Default 0x0 0 0 kernel: (HighPointNVMe) Registering service: pci1987,5012 ...2022-10-30 18:30:13.728370-0400 0x1f7 Default 0x0 0 0 kernel: (HighPointNVMe) Registering service: pci1987,5012 ...2022-10-30 18:30:13.729104-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) [ ][RSNVMeController:init]2022-10-30 18:30:13.729105-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.729109-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) [8 ][RSNVMeController:robe]2022-10-30 18:30:13.729109-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.729135-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) continue to judge 7103/71052022-10-30 18:30:13.729136-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.729164-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) MMIO: plx up bus:1, bridge func:82022-10-30 18:30:13.729164-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.729185-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) Val0x74 :416103, *Val0x78:10300002022-10-30 18:30:13.729185-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.729186-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) bus:8, is first member,CheckProtectMCU2022-10-30 18:30:13.729187-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.787475-0400 0x1f7 Default 0x0 0 0 kernel: (HighPointNVMe) Registering service: pci1987,5012 ...2022-10-30 18:30:13.788246-0400 0x93e Default 0x0 0 0 kernel: (HighPointNVMe) [ ][RSNVMeController:init]2022-10-30 18:30:13.788247-0400 0x93e Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.788250-0400 0x93e Default 0x0 0 0 kernel: (HighPointNVMe) [9 ][RSNVMeController:robe]2022-10-30 18:30:13.788251-0400 0x93e Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.810500-0400 0x1f7 Default 0x0 0 0 kernel: (HighPointNVMe) Registering service: pci1987,5012 ...2022-10-30 18:30:13.811228-0400 0x93f Default 0x0 0 0 kernel: (HighPointNVMe) [ ][RSNVMeController:init]2022-10-30 18:30:13.811229-0400 0x93f Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.811233-0400 0x93f Default 0x0 0 0 kernel: (HighPointNVMe) [a ][RSNVMeController:robe]2022-10-30 18:30:13.811234-0400 0x93f Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.834751-0400 0x940 Default 0x0 0 0 kernel: (HighPointNVMe) [ ][RSNVMeController:init]2022-10-30 18:30:13.835319-0400 0x940 Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.842541-0400 0x940 Default 0x0 0 0 kernel: (HighPointNVMe) [b ][RSNVMeController:robe]2022-10-30 18:30:13.843124-0400 0x940 Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.936458-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) 00000000 00000000 00000000 000000002022-10-30 18:30:13.937223-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)2022-10-30 18:30:13.944592-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe) Verify controller failed (retry:0).2022-10-30 18:30:13.945272-0400 0x93d Default 0x0 0 0 kernel: (HighPointNVMe)

As I have no issues dual booting Windows I don't think this will not help my problem because as I understand ACPI still gets patched for OSX loading non the less. Still feel my DSDT tables may be incorrect though considering the NVME errors I see in logs. Topic for another day. Thanks

Confused on what exactly is the OC mod version in that it doesnt use a dsdt? You also say the dsdt is a limitation? I thought you needed one. Right now having an issue getting a Highpoint 7204 card working and I suspect that its the dsdt at fault. I used generator apps to create it through the usual ways most guides out there tell you. Is this possible and perhaps will the mod version help me with my issue? thanks

Curious about how you guys got this all working on Opencore.