Jump to content

[GUIDE] Dell XPS 15 (9550) High Sierra 10.13.1 Quick Installation

* * * * * 9 votes Hackintosh dell xps full working perfect clone easy

  • Please log in to reply
1084 replies to this topic

#241
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

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...



#242
tsmo

tsmo

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

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



#243
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

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

already did.



#244
dpassmor

dpassmor

    InsanelyMac Protégé

  • Members
  • Pip
  • 23 posts

(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



#245
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

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)

Attached Files



#246
dpassmor

dpassmor

    InsanelyMac Protégé

  • Members
  • Pip
  • 23 posts

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)

 

Weird, I remember attaching it... thanks  :)



#247
hackedWifi

hackedWifi

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

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

Attached Files



#248
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

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

Attached Files



#249
gujiangjiang

gujiangjiang

    An Orthopedic Graduate Student In Medical University.

  • Members
  • PipPipPipPipPip
  • 293 posts
  • Gender:Male
  • Location:Changzhou,China

Weird, I remember attaching it... thanks   :)

 

Hello Tiphareth.

 

What about native nvram worked?This is a common bug of 6th intel motherboard when install osx.

 

I hope this can be fix but I have no idea.



#250
hackedWifi

hackedWifi

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

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

I will do it. Thank you. I report back later.

Sent from my Pixel XL using Tapatalk

#251
KYBOSH

KYBOSH

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

Good evening folks.

Quick question.

Wanted to know if there was a way to check and see if the NVMe drive I had in my system was a hynix or not.

Unfortunately the XPS did not come with an OS and i dont have another machine I can run lspci  with it on.

Anyway to tell from looking at the ssd itself?

 

I believe i have installed the NVMe patches correctly but still don't see the SSD as an install target during installation.

Best to be sure before laying out $$$ for a new SSD.

 

Thanks!



#252
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

Good evening folks.

Quick question.

Wanted to know if there was a way to check and see if the NVMe drive I had in my system was a hynix or not.

Unfortunately the XPS did not come with an OS and i dont have another machine I can run lspci  with it on.

Anyway to tell from looking at the ssd itself?

 

I believe i have installed the NVMe patches correctly but still don't see the SSD as an install target during installation.

Best to be sure before laying out $$$ for a new SSD.

 

Thanks!

use a live linux enviroment. less risk.



#253
KYBOSH

KYBOSH

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

use a live linux enviroment. less risk.

 

 

Thanks for that!

Not sure why that didnt occur to me.

I actually had an elementary OS dumb drive on my desk.

 

So my Device says its a 1179:0115 rev 01.

Assuming hynix only has 1 vendor ID (1c5c) Im good on that front.

I'll do some rereading and try to figure this one out.

Starting with the BIOS settings again.

 

If anyone can suggest anything for me to check or try I'd appreciate it.

Again, my issue ATM is the SSD isnt showing up as a installation target of Sierra.

 

TIA



#254
hackedWifi

hackedWifi

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

Thanks for that!
Not sure why that didnt occur to me.
I actually had an elementary OS dumb drive on my desk.

So my Device says its a 1179:0115 rev 01.
Assuming hynix only has 1 vendor ID (1c5c) Im good on that front.
I'll do some rereading and try to figure this one out.
Starting with the BIOS settings again.

If anyone can suggest anything for me to check or try I'd appreciate it.
Again, my issue ATM is the SSD isnt showing up as a installation target of Sierra.

TIA

Well what steps are you taking?

Sent from my Pixel XL using Tapatalk

#255
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

Thanks for that!

Not sure why that didnt occur to me.

I actually had an elementary OS dumb drive on my desk.

 

So my Device says its a 1179:0115 rev 01.

Assuming hynix only has 1 vendor ID (1c5c) Im good on that front.

I'll do some rereading and try to figure this one out.

Starting with the BIOS settings again.

 

If anyone can suggest anything for me to check or try I'd appreciate it.

Again, my issue ATM is the SSD isnt showing up as a installation target of Sierra.

 

TIA

 

thats a toshiba.



#256
KYBOSH

KYBOSH

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

thats a toshiba.

 
Yes Sir it is.
Its the same drive Mikolatero and others mentioned upthread (the TOSHIBA THNSN5512GPUK NVMe)
 
 
4:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:0115] (rev 01) (prog-if 02 [NVM Express])
	Subsystem: Toshiba America Info Systems Device [1179:0001]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at dde00000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
		DevCtl:	Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L0s unlimited, L1 <4us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Not Supported
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [b0] MSI-X: Enable+ Count=8 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00003000
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr+ BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [168 v1] Alternative Routing-ID Interpretation (ARI)
		ARICap:	MFVC- ACS-, Next Function: 0
		ARICtl:	MFVC- ACS-, Function Group: 0
	Capabilities: [178 v1] #19
	Capabilities: [198 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [1a0 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1- ASPM_L1.2+ ASPM_L1.1- L1_PM_Substates+
			  PortCommonModeRestoreTime=255us PortTPowerOnTime=1200us
	Kernel driver in use: nvme
	Kernel modules: nvme
Only thing is I still cant make it visible to the OSX installer.
I've undated the clover config.plist file with he hynix patch code you mentioned on page 9 but still no joy.
I've reread this thread and others linked to it but am not getting very far as most ppl are having post installation issues.


Well what steps are you taking?

Sent from my Pixel XL using Tapatalk


Honestly just going over things one by one to ensure that I didnt do something glaringly newbish and obvious.
But it seems to be my Hynix SSD for sure. Just not sure why the Hynix SSD patch isn't doing the trick....

#257
KYBOSH

KYBOSH

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

thats a toshiba.


I've been through it all again and I still can't see what (if anything I have missed). My BIOS firmware is the latest and all the settings are toggled properly for the install.
Hynix Ssd patch is inserted in the clover config.plist and formatted properly. Really don't know...

#258
hackedWifi

hackedWifi

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

I've been through it all again and I still can't see what (if anything I have missed). My BIOS firmware is the latest and all the settings are toggled properly for the install.
Hynix Ssd patch is inserted in the clover config.plist and formatted properly. Really don't know...

Have you tried using the unsupported Sata text on this guide. What if you have an u supported one.
https://www.tonymacx...-clover.148093/

Sent from my Pixel XL using Tapatalk

#259
wmchris

wmchris

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 281 posts

I've been through it all again and I still can't see what (if anything I have missed). My BIOS firmware is the latest and all the settings are toggled properly for the install.
Hynix Ssd patch is inserted in the clover config.plist and formatted properly. Really don't know...

toshiba normally works out of the box, but it seems like you have a new revision (THNSN5512GPUK, normally in dell is a THNSN5512GPU7) but still this device is known as working. so i really doubt this is the reason.

 

you've just used the installation config.plist w/o modification, right?

 

You can only try this: http://www.insanelym...12#entry2361551 with different values. You can also try to reformat and repartition it from your linux thumb drive - pikers patches are a lil bit picky with some partition tables.



#260
KYBOSH

KYBOSH

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

toshiba normally works out of the box, but it seems like you have a new revision (THNSN5512GPUK, normally in dell is a THNSN5512GPU7) but still this device is known as working. so i really doubt this is the reason.

New revision... hummm not sure if that that's a good thing or a bad thing.
But we will power through it.

you've just used the installation config.plist w/o modification, right?


My initial run was with the clover installation as prescribed in post #1.
Using the "git/" folder and overwriting everything on the USB's EFIs Clover folder with the contents of 10.12.
Are you referring the the original config.plist file Pandora made?

You can only try this: http://www.insanelym...12#entry2361551 with different values. You can also try to reformat and repartition it from your linux thumb drive - pikers patches are a lil bit picky with some partition tables.


I have this on my list of To-Dos but wanted to make sure my issue wasn't something simple first.





Also tagged with one or more of these keywords: Hackintosh, dell, xps, full working, perfect clone, easy


2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy