Lid sensor flooding log with clamshellStateChanged

[mclovin5]

Hi,

(Mojave 10.14.3)

I'm noticing my CPU quickly ramps up to max.
Looking on Console I see endless messages from loginWindow.logging:

clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=0

I'm guessing it is a problem with the lid sensor.
I don't really need sleep / wakeup to work for my hackintosh, but would like to find an option to stop the log flooding.
(Killing some service / process or a patch would all be fine for me)

Does anyone have a suggestion on how I may fix this?

Thanks!

 

[mclovin5]

If any future Surface Book 2 traveler comes along:

I fixed this by commenting out all "LID" code in DSDT.

(So extract DSDT via the @RehabMan instructions via Clover F4. Then convert it to a DSL. Edit the DSL and search for the code block involving the LID (there's a whole bunch in the SurfaceBook DSDT). Then comment it out by putting // in front)

There might be more elegant solutions, such as making the lid actually work, but I'm ok with this patch for now.

 

[MattMcHackit83]

Appear to be having a similar problem... see my thread here.

I get this flooding the Console/logs:

clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2

 

[mclovin5]

@MattMcHackit83

Ah. Very interesting! Thanks for letting me know.
I thought I was alone in the issue.

I've attached my patched up DSL if that is helpful.
(You cannot use it directly, but you could repeat similar steps in your own DSDT)

Also interesting your machine specs are somewhat similar to mine.
So I will go dig around in your thread to see if you solved any internal monitor issues

 

[MattMcHackit83]

@MattMcHackit83

Ah. Very interesting! Thanks for letting me know.
I thought I was alone in the issue.

I've attached my patched up DSL if that is helpful.
(You cannot use it directly, but you could repeat similar steps in your own DSDT)

Also interesting your machine specs are somewhat similar to mine.
So I will go dig around in your thread to see if you solved any internal monitor issues

Hi! Thanks for the late reply! I'll give it a try!

 

[Hugotai]

If any future Surface Book 2 traveler comes along:

I fixed this by commenting out all "LID" code in DSDT.

(So extract DSDT via the @RehabMan instructions via Clover F4. Then convert it to a DSL. Edit the DSL and search for the code block involving the LID (there's a whole bunch in the SurfaceBook DSDT). Then comment it out by putting // in front)

There might be more elegant solutions, such as making the lid actually work, but I'm ok with this patch for now.

This fixed my log flood too, thank you.