[GH-ISSUE #382] Help with config for Sony Vaio VPCEB4C5E #340

New issue

Closed

opened 2026-02-26 00:32:23 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 00:32:23 +03:00

Owner

Originally created by @alexvaio on GitHub (Nov 17, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/382

After having great success adapting an NBFC config for an Acer notebook I am struggling to develop one for my Sony Vaio VPCEB4C5E and was hoping someone could help me out please.

Trying out existing Sony configs, none seem to work. I tried a config for an SVF14N1C5E which led me to discover when 'Register write configuration' has the following settings, the fan revs up to a high speed and eventually settles down:

Write occasion: OnWriteFanSpeed or OnInitialization
Write mode: Set
Register: 94
Value: 32

When Read Register is set to 92 [0x5C] with a Min Speed of 0 and Max speed of 7 it does seem to respond with the fan speed change however a Write Register of 94 [0x5E] doesn't control the fan. Also, enabling the config with the above 'Register write configuration' settings can sometimes make the keyboard stop working.

I have run the EC Probe tool with Prime95 and I've attached my results below with a low - high - low fan speed. Register 175 [0xAF] seemed very responsive to the fan changes but I can't get it to control the fan either.

I have uploaded the DSDT here if it would help: https://pastebin.com/U91YW53B

If anyone can point me in the right direction I would very much appreciate it.

Originally created by @alexvaio on GitHub (Nov 17, 2017). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/382 After having great success adapting an NBFC config for an Acer notebook I am struggling to develop one for my Sony Vaio VPCEB4C5E and was hoping someone could help me out please. Trying out existing Sony configs, none seem to work. I tried a config for an SVF14N1C5E which led me to discover when 'Register write configuration' has the following settings, the fan revs up to a high speed and eventually settles down: Write occasion: OnWriteFanSpeed or OnInitialization Write mode: Set Register: 94 Value: 32 When Read Register is set to 92 [0x5C] with a Min Speed of 0 and Max speed of 7 it does seem to respond with the fan speed change however a Write Register of 94 [0x5E] doesn't control the fan. Also, enabling the config with the above 'Register write configuration' settings can sometimes make the keyboard stop working. I have run the EC Probe tool with Prime95 and I've attached my results below with a low - high - low fan speed. Register 175 [0xAF] seemed very responsive to the fan changes but I can't get it to control the fan either. I have uploaded the DSDT here if it would help: https://pastebin.com/U91YW53B If anyone can point me in the right direction I would very much appreciate it. ![ecprobe](https://user-images.githubusercontent.com/33764275/32967616-264d342c-cbd6-11e7-8f4f-45eea33bf69d.jpg)

kerem

2026-02-26 00:32:23 +03:00

closed this issue
added the
Stale
label

kerem commented

2026-02-26 00:32:23 +03:00

Author

Owner

@alexvaio commented on GitHub (Mar 13, 2018):

I manually stopped the fan and the registers that went to zero were 70 [0x46] and 71 [0x47] so I assume these are the fan control registers. Unfortunately NBFC does not seem to work with these registers even with the poll interval reduced so I guess the Embedded Controller needs to be put into manual mode. Can anyone give any advice as to how to find the correct register that puts the EC into manual mode?

@alexvaio commented on GitHub (Mar 13, 2018): I manually stopped the fan and the registers that went to zero were 70 [0x46] and 71 [0x47] so I assume these are the fan control registers. Unfortunately NBFC does not seem to work with these registers even with the poll interval reduced so I guess the Embedded Controller needs to be put into manual mode. Can anyone give any advice as to how to find the correct register that puts the EC into manual mode?

kerem commented

2026-02-26 00:32:23 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 7, 2019):

This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed

@github-actions[bot] commented on GitHub (Dec 7, 2019): This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed