Contribute
Register

Laptop Compatibility Lenovo ideapad 320s 13IKBR

Status
Not open for further replies.
Joined
Jun 17, 2010
Messages
10
Motherboard
ASUS UX303LB
CPU
Core i7 2.4GHz Broadwell
Graphics
Intel HD Graphics 5500
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Has anyone explored installing High Sierra on this laptop?
Intel Core i5 8250u quadcore
8GB RAM
Intel 620 graphics + Nvidia MX120 2GB
256GB Intel NVME
13.3 slim bezel Full HD Screen.

It really performs well on Win 10 but would love to check if it's good with high sierra. thanks
 
Has anyone explored installing High Sierra on this laptop?
Intel Core i5 8250u quadcore
8GB RAM
Intel 620 graphics + Nvidia MX120 2GB
256GB Intel NVME
13.3 slim bezel Full HD Screen.

It really performs well on Win 10 but would love to check if it's good with high sierra. thanks

Follow the Clover guide linked from the FAQ.
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html

Although you should read the FAQ for an overview of issues, the Clover guide is linked from the first question: "Q. Where do I start?", just after the bold face "Clover Guide".
Here is a direct link, just to be clear:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

Also, your profile must be filled out with complete details as requested in the FAQ, again under "Q. Where do I start?". All seven details requested are equally important.

And if you have an issue (after following the guide), or on any other problem, you must provide a detailed description of the problem including information that helps us understand what you're doing. Always attach "Problem Reporting" files as per FAQ.
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html
The required files and data are fully detailed in the last question in the FAQ:
"Q. What are typical "Problem Reporting" files?"
 
I had the same thoughts - I got KP though. I used High Sierra and assumed kext: EMU, Voodoo, Intel graphics; disable nVidia graphics; NVMe class spoof (on RP09 as per example); APFS with HPFS+. Have yet to check whether the Wifi needs to be replaced.
 

Attachments

  • CLOVER.zip
    1.8 MB · Views: 210
I had the same thoughts - I got KP though. I used High Sierra and assumed kext: EMU, Voodoo, Intel graphics; disable nVidia graphics; NVMe class spoof (on RP09 as per example); APFS with HPFS+. Have yet to check whether the Wifi needs to be replaced.

Probably DVMT-prealloc related.
Read the guide carefully regarding DVMT-prealloc.
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

Note that for kexts/Other, FakeSMC sensor kexts not recommended, and SATA-100-series-unsupported.kext is missing.
The Lilu.kext you are using is also too old for 10.13.2.
 
Thanks for that. I have cleaned it up and then tried to use ig-platform-id 0x123456789 and then set it back to 0x19160000. Still stuck at boot.
IMG_4099.jpg

Maybe I'm missing a step - not sure what though.
 

Attachments

  • CLOVER.zip
    1.9 MB · Views: 168
Thanks for that. I have cleaned it up and then tried to use ig-platform-id 0x123456789 and then set it back to 0x19160000. Still stuck at boot.
View attachment 301236

Maybe I'm missing a step - not sure what though.

Boot using invalid ig-platform-id, then provide all "problem reporting" files, as per FAQ.
(because I have no idea which kexts are installed to the system volume without kextcache output)

Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the tool mentioned in the FAQ, that way it is less likely you'll omit something.

Note also that your graphics device (8086:5917) requires FakePCIID.kext + FakePCIID_Intel_HD_Graphics.kext
 
OK. So changed the ig-platform-d and added the two kext. This time I booted with kext debug.

With that it seems to be waiting to respawn. Unable to boot the installer.
 

Attachments

  • CLOVER.zip
    1.9 MB · Views: 132
  • IMG_1778.jpg
    IMG_1778.jpg
    3 MB · Views: 320
  • IMG_1779.jpg
    IMG_1779.jpg
    3.9 MB · Views: 324
  • IMG_1780.jpg
    IMG_1780.jpg
    4 MB · Views: 327
  • IMG_1781.jpg
    IMG_1781.jpg
    2.2 MB · Views: 319

OK after the disassembly the grep shows: SDDT-20-CB and SDDT-6-CB.
$ grep -l Method.*_OFF *.dsl
DSDT.dsl
SSDT-20-CB-01 .dsl
SSDT-6-CB-01 .dsl

How do you tell which one is the real path? Both are under PowerResource()

For SDDT-20-CB, it is under SSDT->\_SB.PCI0.RP01->_ON->_OFF
PowerResource (PC01, 0x00, 0x0000)
{
Name (_STA, One) // _STA: Status
Name (MSD3, Zero)
Method (_ON, 0, Serialized) // _ON_: Power On
Method (_OFF, 0, Serialized) // _OFF: Power Off
}

For SDDT-6-CB, it is under SSDT->\_TZ->STA->_OFF
PowerResource (FN00, 0x00, 0x0000)
{
Method (_STA, 0, Serialized) // _STA: Status
Method (_ON, 0, Serialized) // _ON_: Power On
Method (_OFF, 0, Serialized) // _OFF: Power Off
}

However, the _INI matches SSDT-20-CB and the path is \_SB.PCI0.RP01.PXSX.
Is this the one to use?

I also used Xcode to set DSDT Patches for _DSM to XDSM Disable to NO.
 

Attachments

  • CLOVER.zip
    1.9 MB · Views: 151
OK after the disassembly the grep shows: SDDT-20-CB and SDDT-6-CB.
$ grep -l Method.*_OFF *.dsl
DSDT.dsl
SSDT-20-CB-01 .dsl
SSDT-6-CB-01 .dsl

How do you tell which one is the real path? Both are under PowerResource()

For SDDT-20-CB, it is under SSDT->\_SB.PCI0.RP01->_ON->_OFF
PowerResource (PC01, 0x00, 0x0000)
{
Name (_STA, One) // _STA: Status
Name (MSD3, Zero)
Method (_ON, 0, Serialized) // _ON_: Power On
Method (_OFF, 0, Serialized) // _OFF: Power Off
}

For SDDT-6-CB, it is under SSDT->\_TZ->STA->_OFF
PowerResource (FN00, 0x00, 0x0000)
{
Method (_STA, 0, Serialized) // _STA: Status
Method (_ON, 0, Serialized) // _ON_: Power On
Method (_OFF, 0, Serialized) // _OFF: Power Off
}

However, the _INI matches SSDT-20-CB and the path is \_SB.PCI0.RP01.PXSX.
Is this the one to use?

I also used Xcode to set DSDT Patches for _DSM to XDSM Disable to NO.

As per code in SSDT-20, _OFF is at path _SB.PCI0.RP01.PXSX.
 
Status
Not open for further replies.
Back
Top