Jump to content
2,144 posts in this topic

Recommended Posts

Maybe this is off topic but I need to ask: is there anyone here successfully using opencore on Big Sur with fakesmc kext? It causes kernel panic with "You shutdown your computer because of a problem ..." message. Tried reading logs but found nothing useful. I need fakesmc with radeon monitor plugin as it's the only way to read temperature from my 5700 gpu.

opencore-2020-12-18-192820.txt

2 hours ago, Paksman said:

Maybe this is off topic but I need to ask: is there anyone here successfully using opencore on Big Sur with fakesmc kext? It causes kernel panic with "You shutdown your computer because of a problem ..." message. Tried reading logs but found nothing useful. I need fakesmc with radeon monitor plugin as it's the only way to read temperature from my 5700 gpu.

opencore-2020-12-18-192820.txt

This is the SMC key MSSD

MSSD
si8
1
Stores the last known Shut-down cause.
STOP_CAUSE_SHUTDOWN_GOOD_CODE 5
STOP_CAUSE_SLEEP_GOOD_CODE 5
STOP_CAUSE_POWERKEY_GOOD_CODE 3
SLEEP_CAUSE_SLEEP_LOWBATT_CODE 2 // Deprecated. Use STOP_CAUSE_LOWBATT
SLEEP_CAUSE_SLEEP_OVERTEMP_CODE 1 // Deprecated. Use appropriate STOP_CAUSE_TEMP*
STOP_CAUSE_INIT_CODE 0 // Initial code
STOP_CAUSE_HEALTHCHECK_CODE -1 // 0xFF
STOP_CAUSE_PS_CODE -2 // 0xFE
STOP_CAUSE_TEMP_MULTISLEEP_CODE -3 // 0xFD
STOP_CAUSE_SENSORFAN_CODE -4 // 0xFC
STOP_CAUSE_TEMP_OVERLIMITTO_CODE -30 // 0xE2
STOP_CAUSE_PSWRSMRST_CODE -40 // 0xD8
STOP_CAUSE_UNMAPPED_CODE -50 // 0xCE Deprecated because it should never occur
STOP_CAUSE_LOWBATT_CODE -60 // 0xC4
STOP_CAUSE_NINJA_SHUTDOWN_CODE -61 // 0xFF
STOP_CAUSE_NINJA_RESTART_CODE -62 // 0xC2
STOP_CAUSE_TEMP_PALM_CODE -70 // 0xBA
STOP_CAUSE_TEMP_SODIMM_CODE -71 // 0xB9
STOP_CAUSE_TEMP_HEATPIPE_CODE -72 // 0xB8
STOP_CAUSE_TEMP_BATT_CODE -74 // 0xB6
STOP_CAUSE_ADAPTERTO_CODE -75 // 0xB5
STOP_CAUSE_TEMP_MANUAL_CODE -77 // 0xB3 Not currently used.
STOP_CAUSE_CURRENT_ADAPTER_CODE -78 // 0xB2
STOP_CAUSE_CURRENT_BATT_CODE -79 // 0xB1
STOP_CAUSE_TEMP_SKIN_CODE -82 // 0xAE
STOP_CAUSE_TEMP_BACKUP_CODE -84 // 0xAC
STOP_CAUSE_TEMP_SKIN_BOTHBAD_CODE -83 // 0xAB Will die with M57, M59, M75, M76
STOP_CAUSE_TEMP_CPUPROX_CODE -86 // 0xAA
STOP_CAUSE_TEMP_CPU_CODE -95 // 0xA1
STOP_CAUSE_TEMP_PS_CODE -100 // 0x9C
STOP_CAUSE_TEMP_LCD_CODE -101 // 0x9B
STOP_CAUSE_RSM_POWER_FAIL_CODE -102 // 0x9A
STOP_CAUSE_BATT_CUV_CODE -103 // 0x99
STOP_CAUSE_UNKNOWN_CODE -128 // 0x80 for unknown shutdown cause

With Clover you will have correct key.

With OpenCore you have to exclude MSSD from FakeSMC.info.plist

  • Thanks 1
9 hours ago, Streets said:

Goodnight.
Merry Christmas.
Is there any solution for the fans of the Nuvoton NTC5887D-M?

Should be checked in system.log and provide a datasheet.

  • 4 weeks later...
On 12/9/2020 at 11:56 PM, unixb0y said:

Today, I updated my OC installation and created a completely new EFI. I chose VirtualSMC and no W836 Kext and now I have sensor readings for my fans :D

I use now:


AppleALC.kext
IntelMausi.kext
Lilu.kext
SMCProcessor.kext
SMCSuperIO.kext
VirtualSMC.kext
WhateverGreen.kext

And I have all this good stuff. iStats also works with these Kexts!

 

Screenshot 2020-12-09 at 23.55.15.png

Screenshot 2020-12-09 at 23.55.54.png

 

Only issue with that solution: fan control is not working :/

Do you work on SMCSuperIO / VirtualSMC as well? This is all from team Acidanthera, right?

  • 2 weeks later...
On 12/30/2020 at 8:15 AM, Paksman said:

is there anyone here successfully using opencore on Big Sur with fakesmc kext?

 

My rig running fine with OC0.6.6, FakeSMC.kext and BS11.2.

 

@Paksman This is interesting.

Edited by tonyx86
Added link to updated FakeSMC for OC
  • Like 1
  • 2 weeks later...
4 hours ago, tonyx86 said:

I posted a note about this in the OC Discussion thread and am 'double-posting' this here.  I ask for Moderator forgiveness as I think this issue is relevant to both discussions.  I am now testing this updated FakeSMC.kext with OC 0.6.6.  After I updated my rig's BIOS, I started to experience random reboots and I experienced an unexpected system restart during my upgrade from BS 11.2 to BS 11.2.1.  I suspect that these reboots/restarts were caused by incompatibility between the 'old' FakeSMC.kext and OC.  If you use XCode to edit your OC config.plist (part of the migration to the new FakeSMC), see my post here.

But you are confusing FakeSMC 6.x and 3.x. They are not different versions. They are different projects and this particular thread is about FakeSMC 3.x.

FakeSMC 3.x with plugins works fine in BigSur 11.3.1b1. No crashes etc.

I want to announce new release 243.

IntelCPUMonitor

- added IceLake and TigerLake CPUs

RadeonMonitor

--added RX5500-5900 cards temperature monitoring

Added new plugin IntelMCHMonitor

for Kabylake and up. Testing will be in separate thread.

  • Like 5
  • Thanks 1

@Slice

Thanks. :)

There are changes for FakeSMC 3.5.3 since 2019 ? or not. I only use this kext from the bundle. So I want to know, if updating is necessary. Please.

2 hours ago, Matgen84 said:

@Slice

Thanks. :)

There are changes for FakeSMC 3.5.3 since 2019 ? or not. I only use this kext from the bundle. So I want to know, if updating is necessary. Please.

Not necessary.

I may recommend to edit his info.plist

The key MSSD will be better to be 05

Снимок экрана 2021-02-16 в 19.01.38.png

  • Thanks 1
18 hours ago, Slice said:

Not necessary.

I may recommend to edit his info.plist

The key MSSD will be better to be 05

 

 

Hi @Slice

I've panic after change MSSD data to 05 (FakeSMC 3.5.3) on my Ivybridge config (Mojave). See screenshot. Several searches, replace by data 03 and clear NVRAM, I can boot again.

Very strange. I misunderstood something, i don't know where I mistaken

 

Spoiler

1.thumb.jpg.3c98e21880ad03c6f0e993fac341dff3.jpg


 

SOLVED: it's a problem with PDEditPlus: the tool don't save correctly data changes. I use Plist Edit Pro instead: the issue is solved. I can boot without panic.

Edited by Matgen84
  • Like 2
4 minutes ago, Slice said:

I also have panics after info.plist editing. Strange...


I posted a comment to the developer on their thread to report the issue.

OK now works well

hack Z370 --> BS11.3 FakeSMC.kext + IntelCPUMonitor.kext + IntelMCHMonitor.kext

2021-2-18_17-41-56_CLOVERX64-5130.efi.log

all that remains is that on restart before arriving at the desktop the writing appears: you turned off the computer due to a problem.
Of course there is no problem, which is not the case with virtualsmc

  • Sad 2
×
×
  • Create New...