Contribute
Register

[Guide] Dell XPS 13 9343 Sierra

Joined
Sep 13, 2011
Messages
73
Motherboard
Dell XPS 13 9343 QHD
CPU
i7-5500U
Graphics
HD 5500
Mobile Phone
  1. Other
Has anyone gotten iMessage to work? I followed the workaround guides and it worked just a few hours ago, but now it doesn't and it seems they have detected the Hackintosh. Slight warning to those trying it out themselves.
 
Last edited:
Joined
Oct 9, 2018
Messages
10
Motherboard
Dell XPS 13 9343
CPU
i7
Graphics
HD 5500
Has anyone gotten iMessage to work? I followed the workaround guides and it worked just a few hours ago, but now it doesn't and it seems they have detected the Hackintosh. Slight warning to those trying it out themselves.
I have no problems with iMessage. Maybe try a different id in Smbios and make sure your active network card is set to en0
 
Joined
Sep 13, 2011
Messages
73
Motherboard
Dell XPS 13 9343 QHD
CPU
i7-5500U
Graphics
HD 5500
Mobile Phone
  1. Other
I have no problems with iMessage. Maybe try a different id in Smbios and make sure your active network card is set to en0
Tried that. iMessage worked just now but after quitting the app and restarting it doesn't again.
 
Joined
Sep 13, 2011
Messages
73
Motherboard
Dell XPS 13 9343 QHD
CPU
i7-5500U
Graphics
HD 5500
Mobile Phone
  1. Other
Has anybody found a solution to the Webcam only working once after each boot/sleep cycle?
 
Joined
Jan 20, 2019
Messages
31
Motherboard
XPS 13 9343-Clover
CPU
i7-5500U
Graphics
HD 5500 (3200x1800)
I bought a new ssd and Mojave is working flawless... (except few minor things).
So the LiteOn CX1 is not compatible with osx...
 
Joined
Jan 26, 2016
Messages
55
So I did recently make a clean install and I've just discovered something, by disabling PTT, I cannot use VoodooI2C with its satelite (VoodooI2CHID), These 2 Voodoos are actually a life changing discovery, those are super awesome. What i did is that, i enabled the PTT security again. Using da_beidl's trick by manually loading the apfs will do the job.
I really want to avoid the crazybird's patch do as vanilla as possible.

By the way, to Install VoodooI2C: (guide is in process)
1. Patch DSDT with either OS FixWindows 8 or 8.1 (need to check, be back in few hours) it's 8.1
2. Download / get a new VoodooPS2Controller.kext, right click and Show Package Content, click Contents/PlugIns/ there will be 3 files, delete everything except VoodooPS2Keyboard.kext this is mandatory in order to avoid conflict between this and VoodooI2C
3. Get newest release of VoodooI2C from here https://github.com/alexandred/VoodooI2C
4. After extracting, you need 2 files from VoodooI2C, these are VoodooI2C.kext and VoodooI2CHID.kext
5. Install those 2 files and your newly configured VoodooPS2Controller.kext in /Library/Extension, mind if you already have VoodooPS2Controller.kext in your L/E, uninstall it first then proceed to install this.
6. Done


Completely different thing,
If your IOREG shows MacBookAir7(no good) instead of MacBookAir7,2 (although you have changed it in your config.plist), make sure to check the following config.plist/KernelAndKextPatches/DellSMBIOSPatch set to true
I had set USBInjectall and didn't take any effect (the IORegistryExplorer shows everything under XHC very wrong) and after set it to true, everything goes back into normal and proceed with SSDT-UIAC.aml and everything's fine
 
Last edited:
Joined
Sep 13, 2011
Messages
73
Motherboard
Dell XPS 13 9343 QHD
CPU
i7-5500U
Graphics
HD 5500
Mobile Phone
  1. Other
So I did recently make a clean install and I've just discovered something, by disabling PTT, I cannot use VoodooI2C with its satelite (VoodooI2CHID), These 2 Voodoos are actually a life changing discovery, those are super awesome. What i did is that, i enabled the PTT security again. Using da_beidl's trick by manually loading the apfs will do the job.
I really want to avoid the crazybird's patch do as vanilla as possible.

By the way, to Install VoodooI2C: (guide is in process)
1. Patch DSDT with either OS FixWindows 8 or 8.1 (need to check, be back in few hours) it's 8.1
2. Download / get a new VoodooPS2Controller.kext, right click and Show Package Content, click Contents/PlugIns/ there will be 3 files, delete everything except VoodooPS2Keyboard.kext this is mandatory in order to avoid conflict between this and VoodooI2C
3. Get newest release of VoodooI2C from here https://github.com/alexandred/VoodooI2C
4. After extracting, you need 2 files from VoodooI2C, these are VoodooI2C.kext and VoodooI2CHID.kext
5. Install those 2 files and your newly configured VoodooPS2Controller.kext in /Library/Extension, mind if you already have VoodooPS2Controller.kext in your L/E, uninstall it first then proceed to install this.
6. Done


Completely different thing,
If your IOREG shows MacBookAir7(no good) instead of MacBookAir7,2 (although you have changed it in your config.plist), make sure to check the following config.plist/KernelAndKextPatches/DellSMBIOSPatch set to true
I had set USBInjectall and didn't take any effect (the IORegistryExplorer shows everything under XHC very wrong) and after set it to true, everything goes back into normal and proceed with SSDT-UIAC.aml and everything's fine

When I try to compile my DSDT I run into the following error: (attachment)
How would you go about fixing that? I'm not a DSDT specialist.
 

Attachments

  • Bildschirmfoto 2019-08-10 um 10.29.40.png
    Bildschirmfoto 2019-08-10 um 10.29.40.png
    156.4 KB · Views: 91
Joined
Jan 26, 2016
Messages
55
When I try to compile my DSDT I run into the following error: (attachment)
How would you go about fixing that? I'm not a DSDT specialist.
pretty common error, however easy solution is to replace some of the codes with these:
to begin with, click the error and you'll be directed into the corresponding line, then proceed to replace with "patched"

Code:
native:
                If (LEqual (PM6H, One))
                {
                    CreateBitField (BUF0, \_SB.PCI0._Y0C._RW, ECRW)  // _RW_: Read-Write Status
                    Store (Zero, ECRW (If (PM0H)
                            {
                                CreateDWordField (BUF0, \_SB.PCI0._Y0D._LEN, F0LN)  // _LEN: Length
                                Store (Zero, F0LN)
                            }))
                }

patched (replace with):
                If (LEqual (PM6H, One))
                {
                    CreateBitField (BUF0, \_SB.PCI0._Y0C._RW, ECRW)  // _RW_: Read-Write Status
                    Store (Zero, ECRW)
                }
If (PM0H)
                            {
                                CreateDWordField (BUF0, \_SB.PCI0._Y0D._LEN, F0LN)  // _LEN: Length
                                Store (Zero, F0LN)
                            }


then try to compile again, and you'll get another error, this time

Code:
native:
    Method (ADBG, 1, Serialized)
    {
        If (CondRefOf (MDBG))
        {
            Return (MDBG)
            Arg0
        }


        Return (Zero)
    }


patched:
    Method (ADBG, 1, Serialized)
    {
        If (CondRefOf (MDBG))
        {
            Store (Arg0, MDBG)       
            Return
        }
        Return (Zero)
    }
 
Joined
Sep 13, 2011
Messages
73
Motherboard
Dell XPS 13 9343 QHD
CPU
i7-5500U
Graphics
HD 5500
Mobile Phone
  1. Other
Thanks @avatecer, it's compiling now.
Which patch corresponds to Windows 8.1? I can only find Windows 8 and Windows 10 (wouldn't apply/no diff) in the list of DSDT patches in MaciASL. I could also change the condition to Windows 10 OR Darwin manually but I'm not sure if the Windows 10 _OSI would activate I2C.
 
Joined
Jan 26, 2016
Messages
55
Thanks @avatecer, it's compiling now.
Which patch corresponds to Windows 8.1? I can only find Windows 8 and Windows 10 (wouldn't apply/no diff) in the list of DSDT patches in MaciASL. I could also change the condition to Windows 10 OR Darwin manually but I'm not sure if the Windows 10 _OSI would activate I2C.
hmm are you really sure? from the list here, I chose [Windows] Windows 8.1 Patch. what it does is actually changing
Code:
        Method (_INI, 0, Serialized)  // _INI: Initialize
        {
            Store (0x07D9, OSYS)
            If (CondRefOf (\_OSI, Local0))
            {
                If (_OSI ("Windows 2009"))
                {
                    Store (0x07D9, OSYS)
                }

                If (_OSI ("Windows 2012"))
                {
                    Store (0x07DC, OSYS)
                }

                If (_OSI ("Windows 2013"))
                {
                    Store (0x07DD, OSYS)
                }
            }


to

        Method (_INI, 0, Serialized)  // _INI: Initialize
        {
            Store (0x07D9, OSYS)
            If (CondRefOf (\_OSI, Local0))
            {
                If (_OSI ("Windows 2009"))
                {
                    Store (0x07D9, OSYS)
                }

                If (_OSI ("Windows 2012"))
                {
                    Store (0x07DC, OSYS)
                }

                If(LOr(_OSI("Darwin"),_OSI("Windows 2013")))
                {
                    Store (0x07DD, OSYS)
                }
            }

So, patching with win 10 patch wouldn't be possible because there aren't any Windows 2015.
by the way OS Fix is actually just the same with this one.
 

Attachments

  • Screenshot 2019-08-10 at 14.39.18.png
    Screenshot 2019-08-10 at 14.39.18.png
    86.8 KB · Views: 130
Top