mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #334] Creating config for Sony VAIO VPCSE1X1R #300
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#300
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bananakid on GitHub (Sep 17, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/334
Hello everyone!
I'm trying to figure out how to create a config for Sony VAIO VPCSE1X1R. So far I have disassembled (and later reassembled) my notebook following Marco Krüger's guide (quite an adventure to be honest) to find out EC name as FAQ suggests. I've figured out the name of EC (Super I/O) which happened to be SMSC MEC1609 (that's it at Microchip's website). I've found a 530-page datasheet at manufacturer's website and a smaller 13-page annotation.
However I'm stuck since FAQ suggests using datasheet but FAQ doesn't specify what I'm supposed to look for (I've read through fan-related pages briefly and haven't noticed something worthy). Following chapters of FAQ speak about using different tools to find out by testing. But I've got the datasheet and I'd like to use it's information. I'm also worried the datasheet dates to 2017 but my laptop has been manufactured 11/2011. Would somebody please help me out?
– bananakid
@bananakid commented on GitHub (Sep 17, 2017):
P.S. Maybe it's a nice idea to include EC (Super I/O) model in the config description when possible. Thus enthusiasts like myself could look into already known EC datasheets and have better understanding what numbers too look for.
@github-actions[bot] commented on GitHub (Dec 9, 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