Contribute
Register

NO USB at all SuperMicro X9DAi motherboard, sierra install

Status
Not open for further replies.
Credits to fearandleb over at insanelymac for the X9DAi DSDT. EFI archive attached.
 

Attachments

  • EFI-folder-contents-2.zip
    1.7 MB · Views: 105
vulgo said:
Credits to fearandleb over at insanelymac for the X9DAi DSDT. EFI archive attached.
Click to expand...

Hello, The EFI folder I uploaded was much larger, I thought was around 82mb. This one is 4.9b mb. Is there something missing or do I just copy these folders contents into my EFI folder and the matching subfolders?

So MACOSX/Boot(yours) contents to MACOSX/Boot(mine)
So MACOSX/Clover(yours) contents to MACOSX/Clover(mine)
So MACOSX/Boot(yours) contents to MACOSX/Boot(mine)

Boot/Bootx64.efi(yours) contacts to Boot/Bootx64.efi(mine)

Clover/subfolders(yours) contents to Clover/subfolders(mine)

Thank You, Nick
 
misterphoton said:
The EFI folder I uploaded was much larger,
Click to expand...
I think that is part of your problem. Clover will boot using your mobo's native EFI and hand everything over to boot.efi - chameleon works differently. Read the FM AKA the Clover wiki.
 
misterphoton said:
Hello, The EFI folder I uploaded was much larger, I thought was around 82mb. This one is 4.9b mb. Is there something missing or do I just copy these folders contents into my EFI folder and the matching subfolders?

So MACOSX/Boot(yours) contents to MACOSX/Boot(mine)
So MACOSX/Clover(yours) contents to MACOSX/Clover(mine)
So MACOSX/Boot(yours) contents to MACOSX/Boot(mine)

Boot/Bootx64.efi(yours) contacts to Boot/Bootx64.efi(mine)

Clover/subfolders(yours) contents to Clover/subfolders(mine)

Thank You, Nick
Click to expand...


I copied the folders contents. I did not see any change in hardware recognition. Thank You, Nick
 
misterphoton said:
I copied the folders contents. I did not see any change in hardware recognition. Thank You, Nick
Click to expand...
Sorry i didn't understand what you meant before. The folder i uploaded was supposed to be a "complete" EFI folder. Basically same method as here with memory definition in SMBIOS for your RAM. What hardware are you expecting to be recognised that currently is not recognised?
 
vulgo said:
Sorry i didn't understand what you meant before. The folder i uploaded was supposed to be a "complete" EFI folder. Basically same method as here with memory definition in SMBIOS for your RAM. What hardware are you expecting to be recognised that currently is not recognised?
Click to expand...

DSDT isn't patched correctly. USB 2.0 is coming under EHC1, EHC2. Rename EHC1 to EH01, EHC2 to EH02 to bypass 15 port limit. SATA is coming under SAT0 which should be coming under SATA.

Code: 
Device (SATA)
            {
                Name (_ADR, 0x001F0002)  // _ADR: Address
                Name (^NATA, Package (0x01)
                {
                    0x001F0002
                })
                Name (\FZTF, Buffer (0x07)
                {
                     0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xF5      
                })
                Name (REGF, One)
                Method (_REG, 2, NotSerialized)  // _REG: Region Availability
                {
                    If (LEqual (Arg0, 0x02))
                    {
                        Store (Arg1, REGF)
                    }
                }

Code: 
Device (EH01)
            {
                Name (_ADR, 0x001D0000)  // _ADR: Address
                Name (_S4D, 0x02)  // _S4D: S4 Device State
                Name (_S3D, 0x02)  // _S3D: S3 Device State
                Name (_S2D, 0x02)  // _S2D: S2 Device State
                Name (_S1D, 0x02)  // _S1D: S1 Device State
                Device (HUBN)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Device (PR10)
                    {
                        Name (_ADR, One)  // _ADR: Address
                        Name (_UPC, Package (0x04)  // _UPC: USB Port Capabilities
                        {
                            Zero,
                            0xFF,
                            Zero,
                            Zero
                        })
                        Name (_PLD, Package (0x01)  // _PLD: Physical Location of Device
                        {
                            Buffer (0x14)
                            {
                                /* 0000 */  0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0008 */  0x30, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0010 */  0x00, 0x00, 0x00, 0x00                        
                            }
                        })
                        Device (PR30)
                        {
                            Name (_ADR, One)  // _ADR: Address
                            Name (_UPC, Package (0x04)  // _UPC: USB Port Capabilities
                            {
                                0xFF,
                                0xFF,
                                Zero,
                                Zero
                            })
                            Name (_PLD, Package (0x01)  // _PLD: Physical Location of Device
                            {
                                Buffer (0x14)
                                {
                                    /* 0000 */  0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                    /* 0008 */  0x21, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                    /* 0010 */  0x00, 0x00, 0x00, 0x00                        
                                }
                            })
                        }

Code: 
Device (EH02)
            {
                Name (_ADR, 0x001A0000)  // _ADR: Address
                Name (_S4D, 0x02)  // _S4D: S4 Device State
                Name (_S3D, 0x02)  // _S3D: S3 Device State
                Name (_S2D, 0x02)  // _S2D: S2 Device State
                Name (_S1D, 0x02)  // _S1D: S1 Device State
                Device (HUBN)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Device (PR10)
                    {
                        Name (_ADR, One)  // _ADR: Address
                        Name (_UPC, Package (0x04)  // _UPC: USB Port Capabilities
                        {
                            Zero,
                            0xFF,
                            Zero,
                            Zero
                        })
                        Name (_PLD, Package (0x01)  // _PLD: Physical Location of Device
                        {
                            Buffer (0x14)
                            {
                                /* 0000 */  0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0008 */  0x30, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0010 */  0x00, 0x00, 0x00, 0x00                        
                            }
                        })
 
I was able to get all of the RAM recognized by booting with an older version of Clover. I am uncertain about how to make the USB work on this based on the code that is above. Do I copy & paste this code into a text file on my HDD somewhere? I also see reference in the code above about SATA.

I have these problems in order:

1) The OS identifies the CPU's as Unknown, but they are XEON processors. It see the number of cores and sees both CPU"S but not as XEON.

2) I also was wondering in the system profiler it sees the motherboard bus speed at 400mhz. That seems incorrect.. I see in the BIOS the processor interconnect speed is 8.0 GT/s. So it would seem as though the bus speed should be much faster.

3) Can anyone clarify where I would put the above code on what file on the HDD to get all the USB going? I Only have the front USB 3.0 ports working. (everything else is not on the USB)

I had to use the iMac14,2 to get the machine to boot in Clover, with my NvIDIA card. Otherwise it's the black screen as it does not like any other system definition. I am also using the default OS X Nvidia graphics driver. The software web driver updates (f01 on the NVIDIA's website) black the machine out. I can get CUDA and OPEN CL to be recognized on the bright side.

I wish I could get this machine to boot with Chameleon in Sierra. It seems to see all the hardware would be recognized based on my experience when I boot to Chameleon to my Mavericks partition there are no problems. Thanks for your help. I tried my USB bootloader I made to boot my Mavericks partition that can boot 10.9.5 to see everything, but it won't boot Sierra.. I guess if we can get everything working in Clover, that's OK, and again thanks a lot for everyone's help!
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top