Gymnae Posted June 15, 2017 Share Posted June 15, 2017 Hello, I just upgrade to .25 BIOS and now I am stuck at the slide value calculation. I tried to follow the guide, and I think I found a block of Available memory, but I just can't figure out how to calculate the right slide value. I attached pictures of the error and my memmap. Cheers Link to comment Share on other sites More sharing options...
Krim404 Posted June 15, 2017 Author Share Posted June 15, 2017 Hello, I just upgrade to .25 BIOS and now I am stuck at the slide value calculation. I tried to follow the guide, and I think I found a block of Available memory, but I just can't figure out how to calculate the right slide value. I attached pictures of the error and my memmap. Cheers slide=149 alking about automated installion. So my question is, anybody faced with this issue? How can I force to install to my SSD? Thank You Guys! no need for downgrade. see step7 with osxaptiofree200. However: seems like your boot media is defunc. Recreate it. 1 Link to comment Share on other sites More sharing options...
Gymnae Posted June 15, 2017 Share Posted June 15, 2017 slide=149 Tried that, didn't work, see photo of the result. So maybe it's me, but I don't know how to calculate based on the memory map. Link to comment Share on other sites More sharing options...
Krim404 Posted June 15, 2017 Author Share Posted June 15, 2017 Tried that, didn't work, see photo of the result. So maybe it's me, but I don't know how to calculate based on the memory map. thats strange, there is an offset in your memmap. slide 149 should be 0x12bdd000 but it is 0x169f9000, which normally should be 180. difference is 31. so try 118. Link to comment Share on other sites More sharing options...
Gymnae Posted June 15, 2017 Share Posted June 15, 2017 slide=118 gives a different error, and fewer pages remain to be sought and unavailable, but still no boot: "Couldn't allocate device tree" Link to comment Share on other sites More sharing options...
Krim404 Posted June 15, 2017 Author Share Posted June 15, 2017 slide=118 gives a different error, and fewer pages remain to be sought and unavailable, but still no boot: "Couldn't allocate device tree" thats pretty strange, because your memmap has free space at the exact location.... you can also try https://github.com/wmchris/DellXPS15-9550-OSX/blob/master/10.12/CLOVER/drivers64UEFI/Other/OsxAptioFix2Drv-free2000.efiinstead of osxaptio2, with slide=0. Link to comment Share on other sites More sharing options...
Gymnae Posted June 16, 2017 Share Posted June 16, 2017 Thanks With the OsxAptioFix2Drv-free2000 I was able to boot back into MacOS. I kept it at slide=121 which gave me the Kernel cache error, which sounded I was close to fixing it. So it works for me now. Link to comment Share on other sites More sharing options...
Mr.C Posted June 17, 2017 Share Posted June 17, 2017 no need for downgrade. see step7 with osxaptiofree200. However: seems like your boot media is defunc. Recreate it. Hi! Thank You for the support! I managed to install it with no problem! The system is working fine, I managed to install the nvidia webdriver but there is one frustrating thing: The internet connection via wifi is slow... I mean I could download with ~3-4-5 MB/s instead of 10-12 MB/s. Is this normal? I tried to fix it but the result was that I cannot turn on the wifi so I had to reinstall the OS. Any solution for that? Thank You Again! Link to comment Share on other sites More sharing options...
Krim404 Posted June 17, 2017 Author Share Posted June 17, 2017 Hi! Thank You for the support! I managed to install it with no problem! The system is working fine, I managed to install the nvidia webdriver but there is one frustrating thing: The internet connection via wifi is slow... I mean I could download with ~3-4-5 MB/s instead of 10-12 MB/s. Is this normal? I tried to fix it but the result was that I cannot turn on the wifi so I had to reinstall the OS. Any solution for that? Thank You Again! no thats not normal. you also dont need a nvidia driver (you cant use the card anyway) 1 Link to comment Share on other sites More sharing options...
Mr.C Posted June 17, 2017 Share Posted June 17, 2017 no thats not normal. you also dont need a nvidia driver (you cant use the card anyway) well, what do you think about this solution: - Turn off WI-Fi. For this purpose, click Wi-Fi menu bar and select Turn Wi-Fi Off. - Enter the following path into the new window: /Library/Preferences/SystemConfiguration/. com.apple.airport.preferences.plist com.apple.network.eapolclient.configuration.plist com.apple.wifi.message-tracer.plist NetworkInterfaces.plist preferences.plist - Remove those files - Once matching Wi-Fi configuration files are deleted, restart Mac. - When the system boots up, click on Wi-Fi menu bar, and select Turn Wi-Fi On. I dont want to reinstall the OS again Link to comment Share on other sites More sharing options...
Krim404 Posted June 17, 2017 Author Share Posted June 17, 2017 well, what do you think about this solution: - Turn off WI-Fi. For this purpose, click Wi-Fi menu bar and select Turn Wi-Fi Off. - Enter the following path into the new window: /Library/Preferences/SystemConfiguration/. com.apple.airport.preferences.plist com.apple.network.eapolclient.configuration.plist com.apple.wifi.message-tracer.plist NetworkInterfaces.plist preferences.plist - Remove those files - Once matching Wi-Fi configuration files are deleted, restart Mac. - When the system boots up, click on Wi-Fi menu bar, and select Turn Wi-Fi On. I dont want to reinstall the OS again dont think this will help, but dont ask, just give it a shot. 1 Link to comment Share on other sites More sharing options...
han8819 Posted June 18, 2017 Share Posted June 18, 2017 I stuck at this black screen. I don't have any mac, so I used vmware workstation for trial. I made bootable usb and I replaced Clover folder with git /10.12 / Clover folder. Also I changed config.plist ig-platform-id with 0x19160000(i5-6300hq model) and used https://github.com/wmchris/DellXPS15-9550-OSX/blob/master/10.12/CLOVER/drivers64UEFI/Other/OsxAptioFix2Drv-free2000.efi Can anyone help? Link to comment Share on other sites More sharing options...
vasvas10 Posted June 18, 2017 Share Posted June 18, 2017 Hi,I recently updated to BIOS 1.2.25, and everything was working as before (after changing to OsxAptioFix2Drv-64.efi and correctly calculating my slide), but when I checked the system.log there was a ton of repeating messages accusing `ACPI Error`, like this: 2017-06-18 14:29:54.222727-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222729-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222734-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.ECDV.KDRT] 2017-06-18 14:29:54.222735-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.ECDV.KDRT] 2017-06-18 14:29:54.222738-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_NOT_FOUND 2017-06-18 14:29:54.222739-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_NOT_FOUND 2017-06-18 14:29:54.222743-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psargs-1d1) 2017-06-18 14:29:54.222744-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psargs-1d1) 2017-06-18 14:29:54.222748-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222749-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222752-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-18 14:29:54.222753-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-18 14:29:54.222756-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.MON0.FAN0] (Node ffffff8048512f10) 2017-06-18 14:29:54.222758-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.MON0.FAN0] (Node ffffff8048512f10) 2017-06-18 14:29:54.222760-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-18 14:29:54.222762-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-18 14:29:54.222764-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) 2017-06-18 14:29:54.222766-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270)It seems to be related to SSDT-Fan.dsl, as the definitions of \_SB_.PCI0.LPCB.ECDV.KDRT and \_SB_.PCI0.LPCB.MON0.FAN0 are from there... Maybe Dell changed something and this patch is not compatible anymore?EDIT: After removing SSDT-Fan, the error disappeared, so it must be the culprit Link to comment Share on other sites More sharing options...
Krim404 Posted June 18, 2017 Author Share Posted June 18, 2017 I stuck at this black screen. I don't have any mac, so I used vmware workstation for trial. I made bootable usb and I replaced Clover folder with git /10.12 / Clover folder. Also I changed config.plist ig-platform-id with 0x19160000(i5-6300hq model) and used https://github.com/wmchris/DellXPS15-9550-OSX/blob/master/10.12/CLOVER/drivers64UEFI/Other/OsxAptioFix2Drv-free2000.efi Can anyone help? ehm no? this is for Dell XPS 15, direct install. Not emulation. So totally wrong thread, wrong files, wrong drivers, wrong everything. Link to comment Share on other sites More sharing options...
KNNSpeed Posted June 19, 2017 Share Posted June 19, 2017 Hi, I recently updated to BIOS 1.2.25, and everything was working as before (after changing to OsxAptioFix2Drv-64.efi and correctly calculating my slide), but when I checked the system.log there was a ton of repeating messages accusing `ACPI Error`, like this: 2017-06-18 14:29:54.222727-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222729-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222734-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.ECDV.KDRT] 2017-06-18 14:29:54.222735-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.ECDV.KDRT] 2017-06-18 14:29:54.222738-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_NOT_FOUND 2017-06-18 14:29:54.222739-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_NOT_FOUND 2017-06-18 14:29:54.222743-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psargs-1d1) 2017-06-18 14:29:54.222744-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psargs-1d1) 2017-06-18 14:29:54.222748-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222749-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-18 14:29:54.222752-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-18 14:29:54.222753-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-18 14:29:54.222756-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.MON0.FAN0] (Node ffffff8048512f10) 2017-06-18 14:29:54.222758-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.MON0.FAN0] (Node ffffff8048512f10) 2017-06-18 14:29:54.222760-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-18 14:29:54.222762-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-18 14:29:54.222764-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) 2017-06-18 14:29:54.222766-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) It seems to be related to SSDT-Fan.dsl, as the definitions of \_SB_.PCI0.LPCB.ECDV.KDRT and \_SB_.PCI0.LPCB.MON0.FAN0 are from there... Maybe Dell changed something and this patch is not compatible anymore? EDIT: After removing SSDT-Fan, the error disappeared, so it must be the culprit ECDV -> EC__ if using "rename ECDV to EC" patch. But that SSDT-Fan doesn't give you correct readings, anyways (the math is just wrong). You can't get the fan RPMs through ACPI on the XPS line, only the temperature the fan controller measures because Dell does some proprietary stuff in its Windows drivers (CFSP is the ACPI fan speed for one of the fans, but it's not defined anywhere). Link to comment Share on other sites More sharing options...
vasvas10 Posted June 19, 2017 Share Posted June 19, 2017 ECDV -> EC__ if using "rename ECDV to EC" patch. But that SSDT-Fan doesn't give you correct readings, anyways (the math is just wrong). You can't get the fan RPMs through ACPI on the XPS line, only the temperature the fan controller measures because Dell does some proprietary stuff in its Windows drivers (CFSP is the ACPI fan speed for one of the fans, but it's not defined anywhere). This is weird.... I applied the "rename ECDV to EC" patch. This one: <key>Comment</key> <string>change ECDV to EC</string> <key>Disabled</key> <false/> <key>Find</key> <data>RUNEVg==</data> <key>Replace</key> <data>RUNfXw==</data> However the error continues to show up. EDIT: Sorry, I missunderstood. You meant to change ECDV to EC__ inside the SSDT-Fan. Now everything is working, thanks mate. Another thing, can I use the SSDT-Fan from your XPS 9560 build, or is it indifferent/incompatible for the 9550? 1 Link to comment Share on other sites More sharing options...
KNNSpeed Posted June 19, 2017 Share Posted June 19, 2017 The one from my build should work fine. You'll want the modified ACPISensors kext to go with it (especially if you use hwmonitor). Be aware that this is because I listed all the temperatures that can be queried through the EC as fans (due to hwmonitor bugs and what I think is a FakeSMC bug regarding temp sensor querying). So "RPM" is actually displaying "degrees C" Link to comment Share on other sites More sharing options...
Krim404 Posted June 19, 2017 Author Share Posted June 19, 2017 ECDV -> EC__ if using "rename ECDV to EC" patch. But that SSDT-Fan doesn't give you correct readings, anyways (the math is just wrong). You can't get the fan RPMs through ACPI on the XPS line, only the temperature the fan controller measures because Dell does some proprietary stuff in its Windows drivers (CFSP is the ACPI fan speed for one of the fans, but it's not defined anywhere). are you sure the RPMs are wrong? This ssdt was created a while ago and tbh the values looked fine for me. Also which calculation do you mean are wrong? Also i dont get the ACPI error, which is strange. Link to comment Share on other sites More sharing options...
KNNSpeed Posted June 19, 2017 Share Posted June 19, 2017 The SSDT adds "2000" (0x7D0) to the temperature (which is multiplied by 10) to get "RPM." That's, quite simply, not an accurate calculation of RPM. They're probably using a PID loop (from electronic control theory) to control the RPM in hardware. The fans also do turn off if the CPU temps are low enough; they don't hang out at some value above 2000 RPM. I saw the original post in which the SSDT was created, and the "2000" number looks to have been arbitrarily picked to give a convincing-looking number. Are you properly renaming ECDV to EC? If you're not seeing that error then you haven't renamed ECDV to EC and MacOS doesn't know you have an EmbeddedController. Link to comment Share on other sites More sharing options...
Krim404 Posted June 19, 2017 Author Share Posted June 19, 2017 The SSDT adds "2000" (0x7D0) to the temperature (which is multiplied by 10) to get "RPM." That's, quite simply, not an accurate calculation of RPM. They're probably using a PID loop (from electronic control theory) to control the RPM in hardware. The fans also do turn off if the CPU temps are low enough; they don't hang out at some value above 2000 RPM. I saw the original post in which the SSDT was created, and the "2000" number looks to have been arbitrarily picked to give a convincing-looking number. Are you properly renaming ECDV to EC? If you're not seeing that error then you haven't renamed ECDV to EC and MacOS doesn't know you have an EmbeddedController. You're right, a fan value based on multiplication of a temperature value is just too unreliable for usage. Link to comment Share on other sites More sharing options...
KNNSpeed Posted June 19, 2017 Share Posted June 19, 2017 You wouldn't get an error if you didn't rename ECDV to EC in the first place. But if you don't do that, you may not be correctly limiting max current (amperage) out of the USB ports, or you might have devices that aren't loading correctly, or you have to use more than just ACPIbatterymanager for battery status. Link to comment Share on other sites More sharing options...
Krim404 Posted June 19, 2017 Author Share Posted June 19, 2017 You wouldn't get an error if you didn't rename ECDV to EC in the first place. But if you don't do that, you may not be correctly limiting max current (amperage) out of the USB ports, or you might have devices that aren't loading correctly, or you have to use more than just ACPIbatterymanager for battery status. never had problems with it, but it seems like its something which should be added to the repository. thank you. Link to comment Share on other sites More sharing options...
Diep Pham Posted June 19, 2017 Share Posted June 19, 2017 The tutorial works perfectly, first time trying and I can manage to install successfully within an hour. Mine is a Dell Precision 5510, which is nearly identical as Dell XPS 9550 AFAIK. The only problem I have is the touchpad 2 finger scrolling doesn't work well, it is like 2-3 of 10 times I scroll with 2 fingers it just didn't move. I suspect that it might incorrectly recognizes as 2 finger taps or something else. How can I disable all actions/gestures except click/right click/2 finger scrolling? I try to edit the Info.plist inside VoodooPS2Trackpad.kext, but there are millions of options that I can't figure out from their names. Link to comment Share on other sites More sharing options...
Mr.C Posted June 19, 2017 Share Posted June 19, 2017 Hi! Thank You for the support! I managed to install it with no problem! The system is working fine, I managed to install the nvidia webdriver but there is one frustrating thing: The internet connection via wifi is slow... I mean I could download with ~3-4-5 MB/s instead of 10-12 MB/s. Is this normal? I tried to fix it but the result was that I cannot turn on the wifi so I had to reinstall the OS. Any solution for that? Thank You Again! well, a little update about my macOS behaviour: - in another location connected to another wifi internet speed is normal (100 mbps) so my router is my problem, trying to fix it - battery usage is not good, drains a lot, with full brightness ~3h governed by the OS not the Intel Speed Step. Although I disabled the SD-card in BIOS, it wont work. - screen is always turn off after a while no matter what i set in the settings but sleeps works normally well, the other issues related to the OS itself so I have to learn how to use is but it is still awesome Thanks for the Guide! Link to comment Share on other sites More sharing options...
th3_v0ice Posted June 19, 2017 Share Posted June 19, 2017 Hello everyone, I followed the guide but i am not able to get into the OS environment after installing the kexts. System goes into a boot loop. I have Dell XPS 15 9550 with 4K screen and Samsung SSD. While in the boot loop text is garbled and "still waiting for root device" is being printed, although barely readable. What can I do to fix this? I installed the NVMe Hackr. I assume that this has something to do with the SSD? I tried to add new boot entry which will load cloverx64.efi from EFI, but that didn't help. ( Doing this and removing the rest of the boot options actually fires up Support Assistant and complains that OS is missing ) I don't know what else to try. Any help would be appreciated. Kind regards, S. Link to comment Share on other sites More sharing options...
Recommended Posts