Jump to content

RehabMan

RehabMan

Member Since 25 Jun 2012
Offline Last Active Today, 03:57 AM
*****

Posts I've Made

In Topic: Patch for using NVMe under macOS Sierra is ready.

28 July 2016 - 10:01 PM

Yes, I realise that but the _SUN is in the middle of it's own lump of code, or so it seems.
 
So I've found this in my DSDT:
 
               Device (H000)
                {
                    Name (_ADR, 0x00)
                    Method (_SUN, 0, NotSerialized)
                    {
                        Return (SNUM ())
                    }
                }
 
and that's the section which I think you suggest I remove (perhaps I've misunderstood).
 
I am looking further into DSDT and it is obvious that I have a lot to learn so I guess I should be patient. It is frustrating, however. Many references are to do with DSDT Editor and not MaciASL. The former seems to require Java which I refuse to install. I try to disassemble my DSDT.aml and things just go wrong from there so like I said, I guess I'm just going to need to be patient.
 
Amongst other problems that I'm trying to sort out with my X99 system is Turbo boost. Last night I switched off turbo on the BIOS but switched off EIST. This made some difference so when I run AppleIntelInfo, I now get the last state as being 34' and not '33'. My GeekBench score has gone up above 20000, now but I do not think that things are correct. With turbo boost, I should have processor speeds up to 3.7 GHz but I can only get things up to 3.4 GHz.
 
Of course any help / ideas would be appreciated.

Yes, I realise that but the _SUN is in the middle of it's own lump of code, or so it seems.
 
So I've found this in my DSDT:
 
               Device (H000)
                {
                    Name (_ADR, 0x00)
                    Method (_SUN, 0, NotSerialized)
                    {
                        Return (SNUM ())
                    }
                }
 
and that's the section which I think you suggest I remove (perhaps I've misunderstood).
 
I am looking further into DSDT and it is obvious that I have a lot to learn so I guess I should be patient. It is frustrating, however. Many references are to do with DSDT Editor and not MaciASL. The former seems to require Java which I refuse to install. I try to disassemble my DSDT.aml and things just go wrong from there so like I said, I guess I'm just going to need to be patient.
 
Amongst other problems that I'm trying to sort out with my X99 system is Turbo boost. Last night I switched off turbo on the BIOS but switched off EIST. This made some difference so when I run AppleIntelInfo, I now get the last state as being 34' and not '33'. My GeekBench score has gone up above 20000, now but I do not think that things are correct. With turbo boost, I should have processor speeds up to 3.7 GHz but I can only get things up to 3.4 GHz.
 
Of course any help / ideas would be appreciated.


Try removing just the _SUN method. It would leave you with:
               Device (H000)
                {
                    Name (_ADR, 0x00)
                }
 
If you're going to do much ACPI coding, recommend you read the ACPI spec.

In Topic: Patch for using NVMe under macOS Sierra is ready.

28 July 2016 - 02:04 PM

Thanks, Rehab. I'm not sure how to inject _DSM so I guess removing _SUN would be easier for me. Will I have to remove that whole section?

Okay, so I tried removing the section H000 with _SUN but when I compiled, I got two errors:
 
17195, 4007, Field offset is in bits, but a byte offset is required
 
55141, 4064, Object does not exist (\_SB.PCI0.BR1A.H000)
 
So I tried just saving without any changes and I still got the first error.
 
Not sure where to go from here.


My suggestion was to remove only the _SUN, not the entire H000 device.

In Topic: Patch for using NVMe under macOS Sierra is ready.

27 July 2016 - 02:24 PM

I got there in the end, I think. Thanks again joevt for the heads-up on the F4 thing at the Clover boot screen.


Your DSDT already defines an ACPI identity at _SB.PCI0.BR1B.H000, but it also defines _SUN. Might help to remove it, or you can inject "built-in" with a _DSM.

In Topic: Patch for using NVMe under macOS Sierra is ready.

26 July 2016 - 08:29 PM

Sorry for the delay, Rehab.
 
I don't have anything in ACPI/origin but here are the other files...


The ioreg is corrupt. Probably not captured with IORegistryExplorer v2.1 as requested.

In Topic: Patch for using NVMe under macOS Sierra is ready.

26 July 2016 - 03:28 PM

Anyway, RehabMan, can you tell me what part of your add-in pertains to the identification of your NVMe? I can get a device ID from whatever but I don't recognise anything in your add-in that looks like a device ID... or am I barking up the wrong tree?


Attach ioreg collected with IORegistryExplorer v2.1.
Also might be helpful if you attach native DSDT/SSDT files (from ACPI/origin). And if you have patched ACPI, ACPI/patched.
© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy