Contribute
Register

<< Solved >> OpenCore Big Sur Installation stuck on OC : Watchdog status is 0

Status
Not open for further replies.
RizkiAA

RizkiAA

Joined
Nov 18, 2018
Messages
53
Motherboard
Lenovo Legion 7i - 15IMH05
CPU
i7-10750H
Graphics
UHD 630 / RTX 2070
Mobile Phone
  1. Android
Hello everybody...

This is the second time for me to install a Hackintosh on a laptop, here is the specifications :


Laptop : Lenovo legion 7i-15IMH


Processor : Intel Core i7-10750H
Memory : 16GB DDR4
iGPU : Intel UHD 630 for 10th Gen Comet Lake-H GT2
dGPU : Nvidia RTX 2070 Max-Q 8GB GDDR6 VRAM
Wi-Fi : Intel Wi-Fi 6 AX201
Ethernet : Realtek RTL8168 Gigabit Ethernet
Audio : Realtek ALC 287
Storage : 1x Samsung MZVLB1T0HBLR-000L2 NVME SSD 1TB
Keyboard : PS2 Keyboard
Touchpad : MSFT0001 I2C Touchpad
Thunderbolt : Available(Thunderbolt 3)
Keyboard backlight : Available (Corsair)
Display : Full HD (1920x1080p) 144Hz
Bootloader : OpenCore 0.8.8
Destination OS : macOS Big Sur

I have followed the installation guides from Dortania. However, I still encounter this issue when booting Opencore from my USB stick:

View attachment IMG_20230129_160256.jpg

At first, it was able to pass the "Watchdog Status is 0" then selecting Big Sur installation and go to the above stage showed, then restarts... But now it stuck on " Watchdog status is 0" showed below:

IMG_20230130_123941.jpg


what I have done :
  • Change NVRAM WriteFlash to NO
  • Delete NVRAM/ADD "4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"
on my config.plist, reading solved issue from another forum, but nothing success.

I attach my EFI Partition zipped below...any help would be appreciated. :)

N.B.
  • I used the Debug version of OpenCore (for easy debugging) but the release version of kext as Dortania not "explicitly" told me to do so, correct me if I'm wrong.
  • I am also currently using the prebuilt SSDT, which I'll be making them manually once I've done installing.
 

Attachments

  • EFI.zip
    7.7 MB · Views: 92
RizkiAA said:
Hello everybody...

This is the second time for me to install a Hackintosh on a laptop, here is the specifications :


Laptop : Lenovo legion 7i-15IMH


Processor : Intel Core i7-10750H
Memory : 16GB DDR4
iGPU : Intel UHD 630 for 10th Gen Comet Lake-H GT2
dGPU : Nvidia RTX 2070 Max-Q 8GB GDDR6 VRAM
Wi-Fi : Intel Wi-Fi 6 AX201
Ethernet : Realtek RTL8168 Gigabit Ethernet
Audio : Realtek ALC 287
Storage : 1x Samsung MZVLB1T0HBLR-000L2 NVME SSD 1TB
Keyboard : PS2 Keyboard
Touchpad : MSFT0001 I2C Touchpad
Thunderbolt : Available(Thunderbolt 3)
Keyboard backlight : Available (Corsair)
Display : Full HD (1920x1080p) 144Hz
Bootloader : OpenCore 0.8.8
Destination OS : macOS Big Sur

I have followed the installation guides from Dortania. However, I still encounter this issue when booting Opencore from my USB stick:

View attachment 562784

At first, it was able to pass the "Watchdog Status is 0" then selecting Big Sur installation and go to the above stage showed, then restarts... But now it stuck on " Watchdog status is 0" showed below:

View attachment 562785

what I have done :
  • Change NVRAM WriteFlash to NO
  • Delete NVRAM/ADD "4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"
on my config.plist, reading solved issue from another forum, but nothing success.

I attach my EFI Partition zipped below...any help would be appreciated. :)

N.B.
  • I used the Debug version of OpenCore (for easy debugging) but the release version of kext as Dortania not "explicitly" told me to do so, correct me if I'm wrong.
  • I am also currently using the prebuilt SSDT, which I'll be making them manually once I've done installing.
Click to expand...
PM981 cause issues, you will need to replace it
 
Feartech said:
PM981 cause issues, you will need to replace it
Click to expand...
ohh... i see, been searching about it now..

some people said that newer version of NVMeFix support PM981, does that mean there is a possibility to use PM981 with NVMeFix without changing the SSD?
 
Feartech said:
Click to expand...
Thanks for the info, i've just seen it

Guess for now i'll be installing it on an external SSD Drive, then buy a new supported NVMe drive or tweak it to make it work

i just want to disable it from SSDT so that it won't cause issue, this is my Storage Controller path as seen from Windows :
1675164154787.png


its address is "\SB.PCI0.RP09.PXSX"
and below is the code that ChatGPT tells me to disable my NVMe Drive

Code: 
DefinitionBlock ("", "SSDT", 2, "Hack", "SSDT-DISABLE-SSD", 0x00000000)
{
    External (_SB.PCI0.RP09.PXSX, DeviceObj)

    Scope (_SB.PCI0.RP09.PXSX)
    {
        Device (SSD)
        {
            Name (_ADR, Zero)
            Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x02)
                {
                    "disable-ssd",
                    Buffer (One)
                    {
                        0x01
                    }
                }, Local0)

                Return (Local0)
            }
        }
    }
}
is it correct? are there something wrong? thank you :)
 
RizkiAA said:
Thanks for the info, i've just seen it

Guess for now i'll be installing it on an external SSD Drive, then buy a new supported NVMe drive or tweak it to make it work

i just want to disable it from SSDT so that it won't cause issue, this is my Storage Controller path as seen from Windows :
View attachment 562840

its address is "\SB.PCI0.RP09.PXSX"
and below is the code that ChatGPT tells me to disable my NVMe Drive

Code: 
DefinitionBlock ("", "SSDT", 2, "Hack", "SSDT-NVM", 0x00000000)
{
    External (_SB.PCI0.RP09.PXSX, DeviceObj)

    Scope (_SB.PCI0.RP09.PXSX)
    {
        Device (SSD)
        {
            Name (_ADR, Zero)
            Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x02)
                {
                    "disable-ssd",
                    Buffer (One)
                    {
                        0x01
                    }
                }, Local0)

                Return (Local0)
            }
        }
    }
}
is it correct? are there something wrong? thank you :)
Click to expand...
edit, here is the corrected one. Previously the identifier was to long
 
Solved by changing DevitualiseMMIO to False, and used the -igfxmlr boot args
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top