Jump to content

[GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation


Krim404
1,809 posts in this topic

Recommended Posts

@whchris For some weird reason HDMI (built-in laptop & at dell dock) doesn't work when I'm using MBP 13,3 but it's working while I'm on the MB 9,1 smbios. Well the problem is that the VGA & Display port (built-in dock) seems to be inactive while I'm using MacOS (i'm now on 10.12.4 beta - rumors states that it should contains usb-c & thunderbolt fixes). DP -> VGA also is not recognized bu OS and results in black screen.

 

It doesn't matter if I left the mouse/keyboard plugged in before starting OS or if I plug it in after boot up - still no response. Keyboard and mouse works fine when they are plugged into laptop's usb though.

 

Under Windows 10 dock seems to behave at it should be, so I can exclude any hardware faults (Dock, cables, monitors etc.)

 

Answering your question regarding charging through usb-c - yes it is charging the laptop and all peripherals attached to the dock. The battery is charging/remains on the same charge level even under heavy load. Right now I've attached external drive, smartphone & laptop to the dock and smartphone and laptop is charging.

 

I'll do couple more test because it's getting late in UK and maybe i'll sort those problems out.

Link to comment
Share on other sites

@whchris For some weird reason HDMI (built-in laptop & at dell dock) doesn't work when I'm using MBP 13,3 but it's working while I'm on the MB 9,1 smbios. Well the problem is that the VGA & Display port (built-in dock) seems to be inactive while I'm using MacOS (i'm now on 10.12.4 beta - rumors states that it should contains usb-c & thunderbolt fixes). DP -> VGA also is not recognized bu OS and results in black screen.

 

It doesn't matter if I left the mouse/keyboard plugged in before starting OS or if I plug it in after boot up - still no response. Keyboard and mouse works fine when they are plugged into laptop's usb though.

 

Under Windows 10 dock seems to behave at it should be, so I can exclude any hardware faults (Dock, cables, monitors etc.)

 

Answering your question regarding charging through usb-c - yes it is charging the laptop and all peripherals attached to the dock. The battery is charging/remains on the same charge level even under heavy load. Right now I've attached external drive, smartphone & laptop to the dock and smartphone and laptop is charging.

 

I'll do couple more test because it's getting late in UK and maybe i'll sort those problems out.

the DP connection is directly wired to the GPU. this should work every time, even from within the EFI. Dell used an USB-GPU on such docks in the past, which will not work on OSX.

If the keyboard is not detected, but other USB devices work i've no idea what could lead to this behaviour. Maybe a security feature against "bad-usb devices" (see http://null-byte.wonderhowto.com/how-to/make-your-own-bad-usb-0165419/)?

it's pretty hard to debug such a device without physical access to it :(

  • Like 1
Link to comment
Share on other sites

Little update - I managed to hook up both monitors to the laptops and in fact they are detected by MacOS as separate displays. First display is hooked to HDMI at laptop, second to the HDMI at dock, still for some reason VGA & display port seems to be not recognised by MacOS.

 

It turns out that you can only plug in single monitor through udb-c/thunderbolt output (Source) at MacOS - that's a little bit disappointing. No changes regarding plug-in peripherals such as mouse/keyboard - only way to make them to work it is to plug them directly into laptop not the docking station. 

 

@whchris could you do a favour (ofc  if this is not a problem for you) for me and PM me links/etc to any tutorials you may know about debugging such a devices? I'm first year IT student so I'm not afraid to try it. It actually may help me with passing some of the LO during studies. In mean time I'll ask my lecturer about it, he's unix/linux enthusiast so he may have some useful information too. 

 

Thank you in advance :)

 

 

post-1631985-0-62243800-1485920811_thumb.jpg

Link to comment
Share on other sites

Yes. Here's the IOKitPersonality key:

<key>IOKitPersonalities</key>	<dict>		<key>Platform SMBIOS Match</key>		<dict>			<key>CFBundleIdentifier</key>			<string>org.syscl.FakeSMBIOS</string>			<key>FakeProperties</key>			<dict>				<key>compatible</key>				<string>MacBookPro13,3</string>				<key>model</key>				<string>MacBookPro13,3</string>				<key>product-name</key>				<string>MacBookPro13,3</string>			</dict>			<key>IOClass</key>			<string>FakeSMBIOS</string>			<key>IOMatchCategory</key>			<string>FakeSMBIOS</string>			<key>IOProviderClass</key>			<string>IOPlatformExpertDevice</string>			<key>IOResourceMatch</key>			<string>SMBIOS</string>		</dict>	</dict>
On a different note -- has anyone else had some strange behavior with the SSDT/CodecCommander pair? I've had many boots where the audio device isn't recognized at all, others where everything works, and others still where the internal speakers work fine, but the headphone output is distorted.

 

While I have had these hit-or-miss boots since the beginning, this new issue with the headphone jack has me stumped.

I does not work at all. I can get to boot by generating MacBookPro13 SMBIOs

 

Sent from my Pixel XL using Tapatalk

I got my SMBIOS to work by deleting the SSDT.aml in Clover/patched

Link to comment
Share on other sites

Little update - I managed to hook up both monitors to the laptops and in fact they are detected by MacOS as separate displays. First display is hooked to HDMI at laptop, second to the HDMI at dock, still for some reason VGA & display port seems to be not recognised by MacOS.

 

It turns out that you can only plug in single monitor through udb-c/thunderbolt output (Source) at MacOS - that's a little bit disappointing. No changes regarding plug-in peripherals such as mouse/keyboard - only way to make them to work it is to plug them directly into laptop not the docking station. 

 

@whchris could you do a favour (ofc  if this is not a problem for you) for me and PM me links/etc to any tutorials you may know about debugging such a devices? I'm first year IT student so I'm not afraid to try it. It actually may help me with passing some of the LO during studies. In mean time I'll ask my lecturer about it, he's unix/linux enthusiast so he may have some useful information too. 

 

Thank you in advance :)

 

your source only states that the MBP doesnt support daisy chaining monitors (Multi Stream Output), which is false. OSX does support this from 10.9.x and higher. Also the dell is capable of this. But it's possible that apple blocked it somehow if you dont use apple hardware.

 

One idea regarding the USB: osx didnt implement all required usb profiles, yet. It often doesnt switch in alternate usage modes and displays a billboard device (http://www.cypress.com/knowledge-base-article/need-usb-billboard-device-type-c-solutions-kba97146) and sometimes it doesnt unlock additional required power on multi purpose devices. Please take a look at your system profiler (especially USB) in osx and upload a screen here, check lsusb on a linux instalation and debug the USB handshake.

  • Like 1
Link to comment
Share on other sites

I generated a dummy config.plist out of Clover Configurator and stripped the SMBIOS section from it, but here's the rundown:

<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>11/30/16</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>MBP133.88Z.0226.B08.1611301700</string>
		<key>Board-ID</key>
		<string>Mac-A5C67F76ED83108C</string>
		<key>BoardManufacturer</key>
		<string>Apple Inc.</string>
		<key>BoardSerialNumber</key>
		<string></string>
		<key>BoardType</key>
		<integer>10</integer>
		<key>ChassisAssetTag</key>
		<string>MacBook-Aluminum</string>
		<key>ChassisManufacturer</key>
		<string>Apple Inc.</string>
		<key>ChassisType</key>
		<string>08</string>
		<key>Family</key>
		<string>MacBook Pro</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>Mobile</key>
		<true/>
		<key>ProductName</key>
		<string>MacBookPro13,3</string>
		<key>SerialNumber</key>
		<string></string>
		<key>SmUUID</key>
		<string></string>
		<key>Trust</key>
		<false/>
		<key>Version</key>
		<string>1.0</string>
	</dict>
</key>

Did you make sure to update FakeSMBIOS's Info.plist to reflect MBP13,3?

I didn't do it manually because I thought clover configurator did it automatically. Thank you for your help! I'll compare mine and make sure the info is all correct.

Link to comment
Share on other sites

I didn't do it manually because I thought clover configurator did it automatically. Thank you for your help! I'll compare mine and make sure the info is all correct.

I got SMBIOS working with MacBookPro13 by deleting the SSDT.aml in Clover/patched.

 

Sent from my Pixel XL using Tapatalk

Link to comment
Share on other sites

Hi I just installed Sierra on my 4K XPS 9550 by following the tutorial and everything work fine, but the system info has show the Vram of Intel HD 530 is only 31 MB. It's makes Lunchpad and Dock effect too slowly.

I try to clean install several times and follow the tutorial carefully. I also change SMBios profile from iMac 5K to MPB 13.3, but the problem is still the same.

Can anyone tell me what should I do?

28aluf5.png

Link to comment
Share on other sites

I have run into some issues. I have a Samsung 960 Evo nvme m2. I cannot for the life of me get it to be viewed by this installer. I have checked all the options, but it should be viewable by the config.plist.

 

If there's anything you can suggest, I'd be very appreciative. 

 

Thanks so much for your work!

Link to comment
Share on other sites

I have run into some issues. I have a Samsung 960 Evo nvme m2. I cannot for the life of me get it to be viewed by this installer. I have checked all the options, but it should be viewable by the config.plist.

 

If there's anything you can suggest, I'd be very appreciative. 

 

Thanks so much for your work!

 

try the following patch on the installation clover config.plist:

<key>Comment</key>
<string>IONVMeFamily Pike R. Alpha SSD patch</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>9sEQD4UcAQAA</data>
<key>Name</key>
<string>IONVMeFamily</string>
<key>Replace</key>
<data>9sECD4UcAQAA</data>

You can also try to replace 9sECD4UcAQAA with 9sEBD4UcAQAA, 9sEED4UcAQAA or 9sEID4UcAQAA. There are even more, but these are the most common. This patch changes the lba sector metadata handling on pikes hackr which fixed multiple devices in the past, but each device requires a different one. If one of these works you'll have to create your own NVMeHackr for the post-install with the supplied patch, see: https://github.com/RehabMan/patch-nvme . I also recommend to read this thread for more support: http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready

 

You can also try to remove the 4k blocksize SSD patch to revert it to 512.

 

The supplied files in my git repository are only for the stock SSDs dell supplies. However: please share if you were successful :-)

  • Like 2
Link to comment
Share on other sites

try the following patch on the installation clover config.plist:

<key>Comment</key>
<string>IONVMeFamily Pike R. Alpha Hynix SSD patch</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>9sEQD4UcAQAA</data>
<key>Name</key>
<string>IONVMeFamily</string>
<key>Replace</key>
<data>9sECD4UcAQAA</data>

You can also try to replace 9sECD4UcAQAA with 9sEBD4UcAQAA, 9sEED4UcAQAA or 9sEID4UcAQAA. There are even more, but these are the most common. This patch changes the lba sector metadata handling on pikes hackr which fixed multiple devices in the past, but each device requires a different one. If one of these works you'll have to create your own NVMeHackr for the post-install with the supplied patch, see: https://github.com/RehabMan/patch-nvme . I also recommend to read this thread for more support: http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready

 

You can also try to remove the 4k blocksize SSD patch to revert it to 512. The supplied files in my git repository are only for the stock SSDs dell supplies.

 

Still: please share if you were successful :-)

 

 

Thank you for such a quick reply. I will try now and report back!

Link to comment
Share on other sites

Okay, I think it is the 4k blocksize patch. I have been doing research for the last bit and have not been able to find how to easily revert the patch so it goes back to 512. If you could offer advice on that, I think it'll work!

 

Thanks

Link to comment
Share on other sites

Hi I just installed Sierra on my 4K XPS 9550 by following the tutorial and everything work fine, but the system info has show the Vram of Intel HD 530 is only 31 MB. It's makes Lunchpad and Dock effect too slowly.

I try to clean install several times and follow the tutorial carefully. I also change SMBios profile from iMac 5K to MPB 13.3, but the problem is still the same.

Can anyone tell me what should I do?

 

you didnt switch the config.plist. you're still using the fakeid one or something removed the minsizestolen patch from the config.plist.

 

Okay, I think it is the 4k blocksize patch. I have been doing research for the last bit and have not been able to find how to easily revert the patch so it goes back to 512. If you could offer advice on that, I think it'll work!

 

Thanks

because this has nothing to do with the XPS15 i suggest asking in the corresponding thread.

Link to comment
Share on other sites

I got SMBIOS working with MacBookPro13 by deleting the SSDT.aml in Clover/patched.

 

Sent from my Pixel XL using Tapatalk

Alright I'll give that a try and see how it goes.

 

Hi I just installed Sierra on my 4K XPS 9550 by following the tutorial and everything work fine, but the system info has show the Vram of Intel HD 530 is only 31 MB. It's makes Lunchpad and Dock effect too slowly.

I try to clean install several times and follow the tutorial carefully. I also change SMBios profile from iMac 5K to MPB 13.3, but the problem is still the same.

Can anyone tell me what should I do?

 

I used a tool from a website not endorsed by insanelymac to install ONLY the HD530 graphics and that got everything working for me. I can't say the name of it here or it gets censored but I used it only for graphics and deleted it

Link to comment
Share on other sites

Alright I'll give that a try and see how it goes.

 

I used a tool from a website not endorsed by insanelymac to install ONLY the HD530 graphics and that got everything working for me. I can't say the name of it here or it gets censored but I used it only for graphics and deleted it

why? it's only one element in the config.plist...

Link to comment
Share on other sites

because this has nothing to do with the XPS15 i suggest asking in the corresponding thread.

 

Okay, I will. Would you be able to link me? I apologize, I had done a lot of looking but could not find the correct thread. Much appreciated.

 

T

Link to comment
Share on other sites

(Crossposted)

 

I'm on a Dell XPS 15 9550, but I believe this affects most, if not all Dell laptops.

After a lot of source code reading, patching, hex editing, and trial and error... it looks like the truncation of the model identifier is happening in the EFI firmware. It's not NULL-truncating the identifier, which would corrupt the SMBIOS, but it is overwriting everything past 11 characters with spaces. It does the same thing to the system SKU# field, which isn't even used in OS X as far as I can tell-- so I suspect it is a firmware issue. It's definitely not happening in Clover, the kernel, AppleACPIPlatform, or AppleSMBIOS kexts. I've not been able to discover *why* this is happening, and it's likely not possible since source is not available for boot.efi or Dell's firmware, but there is a workaround.

If Clover adds the SMBIOS table to the EFI system table with a non-standard GUID, and you hotpatch AppleACPIPlatform.kext and AppleSMBIOS.kext to use that non-standard GUID instead of the normal one (thus hiding it from the firmware and boot.efi), AppleACPIPlatform will set the model and compatible properties on the root nub correctly, and AppleSMBIOS will set the product-name property correctly. The SMBIOS resource published by AppleSMBIOS.kext will have correct info as well. During the boot process boot.efi tries to add a SMBIOS table to the EFI system table with the OEM SMBIOS, but it won't be used. This should be a complete solution, unlike kexts that later try to write correct properties to the root nub, since the system will have the correct model identifier from the time the platform expert starts.

I think this would work best as a single Clover fix that injects the SMBIOS with the non-standard GUID and hotpatches the kexts. Maybe 'DELL SMBIOS'? I'll try to work up a patch to Clover for that and submit it when I can; in the meantime I've attached my modified CLOVERX64.efi based on revision 3994. Mount your EFI partition and copy it to /Volumes/EFI/EFI/CLOVER. Also, apply the following kext patches to the 'KextsToPatch' section of your config.plist:

                        <dict>
                                <key>Comment</key>
                                <string>SMBios</string>
                                <key>Disabled</key>
                                <false/>
                                <key>Find</key>
                                <data>
                                RUI5RDJEMzE=
                                </data>
                                <key>Name</key>
                                <string>AppleACPIPlatform</string>
                                <key>Replace</key>
                                <data>
                                RUI5RDJEMzU=
                                </data>
                        </dict>
                        <dict>
                                <key>Comment</key>
                                <string>SMBios</string>
                                <key>Disabled</key>
                                <false/>
                                <key>Find</key>
                                <data>
                                RUI5RDJEMzE=
                                </data>
                                <key>Name</key>
                                <string>AppleSMBIOS</string>
                                <key>Replace</key>
                                <data>
                                RUI5RDJEMzU=
                                </data>
                        </dict>

fEDHKP.png

  • Like 4
Link to comment
Share on other sites

Just tested your patch, works well. Added the smbios truncation workaround in the git repro. thank you very much! :-)

 

(PS: you forgot to add the file here, thats why i attached it in this post)

Good late evening. I just added the cloverx64.efi to the /Volumes/EFI/EFI/CLOVER/ . I also added the Patch to my config.plist under kextToPatch. I am getting a Model Name: Apple device, and Serial Number: not Available

post-1879596-0-79853200-1486182824_thumb.png

Link to comment
Share on other sites

Good late evening. I just added the cloverx64.efi to the /Volumes/EFI/EFI/CLOVER/ . I also added the Patch to my config.plist under kextToPatch. I am getting a Model Name: Apple device, and Serial Number: not Available

on some installations the XPS EFI will boot from /EFI/BOOT/BOOTX64.efi. You have to edit your Bootloader in EFI to boot from /EFI/CLOVER/cloverx64.efi

post-19619-0-58835000-1486193491_thumb.jpg

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...