- Joined
- Jan 6, 2012
- Messages
- 94
- Motherboard
- MSI Z77-G41
- CPU
- i5-2500
- Graphics
- AMD Radeon R7 250X
- Mobile Phone
Wanted to post this 2 days ago but got banned so..
Heya, I managed to get macOS High Sierra up and running on my newly bought XPS 13 Kaby - just for testing purposes for now because I'm waiting for my wifi card to arrive. However I noticed some minor issues with it. The major thing is that Retina scaling options are somehow buggy. That means the first two scale options are not working at all, the following ones are: 1280x720, 2278x1152 (or any weird value) and 1600x900. The first two options do not work at all. Of course the screen is detected as native QHD+ screen in "This Mac" tab. For now I went back to Windows. I'll install macOS again once I receive my Wi-Fi card.
I also installed newest 2.3.1 BIOS and noticed a troubling thing. It seems that DELL decided to ditch out some options to increase DVMT leaving only 64MB at most not only for Iris Plus 640 users but also for regular HD620 ones.
Not a cool move from them. But the UI is very snappy and after ignoring buggy scaling it can be be used as a daily driver.
The os booted just fine with DVMT set to 64MB and Total Gfx Mem set to MAX. I added proper IFR dump from the BIOS in The attachment. Can small DVMT value cause the resolutions bug? I'm not quite sure. It can be also related to CoreDisplayFixup I'm using. No idea. The system didn't panic at all and I do not use any patched framebuffer data for it.
Also noticed that using the files provided in the archive the MATH device is not loading (not present in Ioreg). As I read some info the _STA method from it needs to be removed for letting macOS initialize the device. I went the Hotpatch Method and made a DSDT patch that renames _STA to XSTA allowing it to load under macOS:
The Mutex values also seem to be non-zero So I went again the clover patch way and made patch for every non-zero mutex changing the value to Zero (hopefully new clover dsdt option FixMutex can be used to correct this. Thanks @RehabMan for this).
Heya, I managed to get macOS High Sierra up and running on my newly bought XPS 13 Kaby - just for testing purposes for now because I'm waiting for my wifi card to arrive. However I noticed some minor issues with it. The major thing is that Retina scaling options are somehow buggy. That means the first two scale options are not working at all, the following ones are: 1280x720, 2278x1152 (or any weird value) and 1600x900. The first two options do not work at all. Of course the screen is detected as native QHD+ screen in "This Mac" tab. For now I went back to Windows. I'll install macOS again once I receive my Wi-Fi card.
I also installed newest 2.3.1 BIOS and noticed a troubling thing. It seems that DELL decided to ditch out some options to increase DVMT leaving only 64MB at most not only for Iris Plus 640 users but also for regular HD620 ones.
Code:
Setting: DVMT Pre-Allocated, Variable: 0x785 {05 91 1C 05 2F 05 35 27 01 00 85 07 14 10 00 FE 00}
0x40CE5 Option: 0M, Value: 0x0 {09 07 1D 05 00 00 00}
0x40CEC Option: 32M, Value: 0x1 {09 07 1E 05 30 00 01}
0x40CF3 Option: 64M, Value: 0x2 {09 07 1F 05 00 00 02}
0x40CFA Option: 4M, Value: 0xF0 {09 07 20 05 00 00 F0}
0x40D01 Option: 8M, Value: 0xF1 {09 07 21 05 00 00 F1}
0x40D08 Option: 12M, Value: 0xF2 {09 07 22 05 00 00 F2}
0x40D0F Option: 16M, Value: 0xF3 {09 07 23 05 00 00 F3}
0x40D16 Option: 20M, Value: 0xF4 {09 07 24 05 00 00 F4}
0x40D1D Option: 24M, Value: 0xF5 {09 07 25 05 00 00 F5}
0x40D24 Option: 28M, Value: 0xF6 {09 07 26 05 00 00 F6}
0x40D2B Option: 32M/F7, Value: 0xF7 {09 07 27 05 00 00 F7}
0x40D32 Option: 36M, Value: 0xF8 {09 07 28 05 00 00 F8}
0x40D39 Option: 40M, Value: 0xF9 {09 07 29 05 00 00 F9}
0x40D40 Option: 44M, Value: 0xFA {09 07 2A 05 00 00 FA}
0x40D47 Option: 48M, Value: 0xFB {09 07 2B 05 00 00 FB}
0x40D4E Option: 52M, Value: 0xFC {09 07 2C 05 00 00 FC}
0x40D55 Option: 56M, Value: 0xFD {09 07 2D 05 00 00 FD}
0x40D5C Option: 60M, Value: 0xFE {09 07 2E 05 00 00 FE}
Not a cool move from them. But the UI is very snappy and after ignoring buggy scaling it can be be used as a daily driver.
The os booted just fine with DVMT set to 64MB and Total Gfx Mem set to MAX. I added proper IFR dump from the BIOS in The attachment. Can small DVMT value cause the resolutions bug? I'm not quite sure. It can be also related to CoreDisplayFixup I'm using. No idea. The system didn't panic at all and I do not use any patched framebuffer data for it.
Also noticed that using the files provided in the archive the MATH device is not loading (not present in Ioreg). As I read some info the _STA method from it needs to be removed for letting macOS initialize the device. I went the Hotpatch Method and made a DSDT patch that renames _STA to XSTA allowing it to load under macOS:
Code:
Comment: change Method _STA in MATH to XSTA
Find: 22002079 0014185f 53544100
Replace: 22002079 00141858 53544100
The Mutex values also seem to be non-zero So I went again the clover patch way and made patch for every non-zero mutex changing the value to Zero (hopefully new clover dsdt option FixMutex can be used to correct this. Thanks @RehabMan for this).