Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal
pchitech

Lenovo ThinkBook 13s-IML Stock at EB # LOG:Exitbs: Start

    Recommended Posts

    Hi all,

    I bought a new Lenovo ThinkBook 13s-IML laptop and these are the specs:

    Cpu
    Intel Core i5-10210U processor (1.60GHz 6MB)

    Display
    13.3 "FHD IPS AntiGlare WLED backlight 1,920 x 1,080

    Ram
    8.0 GB DDR4-2666 DDR4 SODIMM 2666 MHz

    SSD
    512 GB M.2 PCIe NVMe SSD

    Graphics
    Intel UHD

    I've tried all the methods I know with both clover and opencore, but whatever I do I get Stock at

    EB # LOG:Exitbs: Start

    +++++++++++++++++++++++++++++++++++++++++++++++++

    and I can't do the installation.

    Please help me.

    spacer.png

    Share this post


    Link to post
    Share on other sites

    Hi all,

    i followed the guide but rest stuck on exitbs

    I Can't disable Cfg Lock in bios so i've enable AppleCpuPmCfgLock e AppleXcpmCfgLock

    I've  try  SetupVirtualMap e RebuildAppleMemoryMap n/n n/y y/y e y/n nothing

    Then i've try with DevirtualiseMmio and AppleXcpmExtraMsrs but rest Stuck at EB # LOG:Exitbs: Start

    Please help me

     
     

    Share this post


    Link to post
    Share on other sites

    use a fakecpuid

     

    Share this post


    Link to post
    Share on other sites

    I've tried with this your efi that has the fakecpuid but rest Stuck at EB # LOG:Exitbs: Start

     

    Share this post


    Link to post
    Share on other sites

    These are the more technical specifications of my notebook :

     

    Codename    Kaby Lake-U/Y
    Specification    Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
     
    Chipset     
    Northbridge    Intel Comet Lake rev. 0C
    Southbridge    Intel Comet Lake PCH rev. 00
     
    Memory SPD     
    Memory type    DDR4
    Module format    SO-DIMM
    Module Manufacturer(ID)    Samsung (CE00000000000000000000)
    SDRAM Manufacturer (ID)    Samsung (CE00000000000000000000)
    Size    8192 MBytes
    Max bandwidth    DDR4-2666 (1333 MHz)
     
    Mainboard Model    LNVNB161216 (0x000002B1 - 0x9FAA9BE0)
     
    Display Adapters     
    Name    Intel(R) UHD Graphics
    Board Manufacturer    Lenovo
    Codename    Comet Lake GT2
    Technology    14 nm
    PCI device    bus 0 (0x0), device 2 (0x2), function 0 (0x0)
    Vendor ID    0x8086 (0x17AA)
    Model ID    0x9B41 (0x3F15)
    Revision ID    0x2

     

    Share this post


    Link to post
    Share on other sites

    check booter quirks

    Share this post


    Link to post
    Share on other sites
    On 6/30/2020 at 4:23 PM, MaLd0n said:

    check booter quirks

    I have tried many combinations of booter quirks but none make me bypass exitbs

    Share this post


    Link to post
    Share on other sites

    It seems to be a fairly common problem on some Lenovo notebooks from the comet lake series. In particular it seems that nobody who has a lenovo from the thinkpad X1 or X2 series with the comet lake processor has managed to overcome this Exitbs, maybe my thinkbook 13s-IML is part of the same family boh?

     

    Anyway I don't give up, but a hand is always welcome 😉

    • Like 1

    Share this post


    Link to post
    Share on other sites

    Update ..... I tried to change RAM and use OpenCore 0.6.0, but the result doesn't change.

    Share this post


    Link to post
    Share on other sites

    u try change some booter quirks?

    Share this post


    Link to post
    Share on other sites
    23 hours ago, MaLd0n said:

    u try change some booter quirks?

    Obviously I tried but I don't know which combination to try anymore.

    I came to a bitter conclusion no one was able to install catalina on a lenovo x1 carbon with comet lake the 20r1 series. My thinkbook derives from this notebook the project is identified as 20rr and we all have the same problem 😭😭😭😭EB # LOG: Exitbs: Start https://github.com/bomdurup/x1c7_2020_hacintosh

    The bios, however, is locked for writing, therefore the various methods of modifying the cfg lock do not work.

    At this point I believe that only opencore developers can do something.

    Attached you will find the log of opencore if someone wants to help me thank you in advance.

    opencore-2020-07-04-182439.7z

    Share this post


    Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    ×
    ×
    • Create New...