11:37 <eintopf> anybody know the special technical word for small fan molex connectors?

17:59 <DocScrutinizer05> look it up in datasheet of small fan ;-)

18:09 <whitequark> JST connector maybe?

18:26 <eintopf> yea looks like such...

18:27 <eintopf> but I read another forum thread

18:27 <eintopf> the idea was... I have second fan on my notebook and I want to connect it to the main fan - just for the sensing, that I don't get FAN ERROR at booting

18:28 <eintopf> now in forum thread, somebody flashed the EEPROM with another notebook which don't have such second fan...

18:28 <eintopf> and it worked

18:28 <eintopf> I suppose now - in eeprom, there exists a magic bit where I can turn off the FAN ERROR check for the second fan

18:28 <eintopf> but don't know which bit :-)

18:29 <eintopf> sadly the guy didn't compare both hexdumps of eeprom

18:30 <eintopf> I don't care about manipulating eeprom if the tool sets the correct CRC afterwards - but I care about that my system has no password afterwards set

18:30 <eintopf> and I need to access i2c

18:30 <eintopf> I think it's impossible to find that bit :(

18:30 <eintopf> without having two eeproms

18:30 <eintopf> dumps

18:31 <eintopf> maybe... I could lookup in BIOS flashing tool

18:31 <eintopf> and search for the eeprom default settings

18:31 <eintopf> and then compare them, but... then I need to figure out which eeprom do the second fan check setting and which not

18:31 <eintopf> this is real hacking :(

18:32 <eintopf> another option in forum thread is to remove some circuits on the board :-)

18:33 <eintopf> I really don't need the second fan, it's so loud

18:33 <eintopf> sadly the bios has also no setting to disable the check... it's just some hidden config bit

18:37 <eintopf> anybody ideas?

19:00 <eintopf> I should maybe simple ask on the mailinglist for thinkpad_acpi - there is maybe one person which knows that bit :-)

19:48 <DocScrutinizer05> eintopf: sorry you lost me. When you got NO fan connected then the sensing (actually ALARM) for that connector evidently is already disabled, since otherwise a missing signal from fan sensor is same effect like blocked fan

19:49 <DocScrutinizer05> you CANNOT connect two fan sense signals to one jack

19:52 <DocScrutinizer05> if your plan is to *remove* the 2nd fan and you can't disable the alarm in BIOS (usually that's pretty simple by either dedicated flag or by setting lower threshold to 0) then you simply could connect the sense input of FAN2_JACK to an arbitrary other fan's sense output, i.e connect sense pin of fan jack1 and jack2

19:53 <DocScrutinizer05> also see linux "sensors"

19:54 <DocScrutinizer05> http://paste.opensuse.org/37187916 --set

19:56 <eintopf> DocScrutinizer05: I want to remove the fan but with no warning message from bios afterwards - so yes

19:56 <eintopf> that's my plan

19:57 <DocScrutinizer05> sensors --set

19:57 <DocScrutinizer05> is your friend

19:57 <eintopf> I can't control the second fan

19:57 <DocScrutinizer05> man sensors

19:57 <eintopf> I mean I can control it but then the main fan is also disable -> big design failure

19:58 <DocScrutinizer05> -s, --set

19:58 <DocScrutinizer05> Evaluate all `set' statements in the configuration file and exit. You must be `root' to do this. If this parameter is not specified, no `set' statement is evaluated.

19:59 <DocScrutinizer05> man sensors.conf

20:00 <DocScrutinizer05> http://paste.opensuse.org/44418830

20:04 <DocScrutinizer05> http://paste.opensuse.org/72607829

20:06 <eintopf> that doesn't work

20:06 <eintopf> the board is build that the embedded control (external mcu) readout eeprom setting and control the fans

20:07 <eintopf> and the embedded control firmware has no possibility to control both fans independend from each other

20:07 <eintopf> it's a big design failure

20:07 <DocScrutinizer05> i'm not talking about fan control

20:07 <eintopf> or somebody didn't found the right bits :-)

20:08 <eintopf> ah ok.

20:08 <DocScrutinizer05> the name is SENSORS

20:09 <DocScrutinizer05> as mentioned above: when nothing else helps, simply connect the sense input of fan2 jack to same pin of fan1

20:11 <eintopf> yea, that was the idea

20:11 <eintopf> I just need such tiny connect to build such cable connection

20:11 <eintopf> if it's not threshhold...

20:12 <eintopf> I think with such 555 "pulse" generator, I can generate a similar wave e.g. second fan

20:12 <eintopf> but...

20:12 <eintopf> it's a dummy which consumes power :-)

20:16 <DocScrutinizer05> set alarm min RPM to 0 in BIOS

20:17 <DocScrutinizer05> if there's no such setting in BIOS, you're SOL

20:18 <eintopf> it's not there...

20:18 <DocScrutinizer05> I wouldn't recommend flashing a wrong firmware to the controller

20:18 <eintopf> but i believe it's a hidden config. I can access the bios config eeprom from linux :-)

20:19 <DocScrutinizer05> then otoh I wonder if your notebook would not overheat without that 2nd fan

20:19 <eintopf> only models with wwan cards has that fan

20:19 <DocScrutinizer05> oh

20:20 <eintopf> i don't use this card anymore

20:20 <eintopf> i think my best choice is to ask on thinkpad acpi mailinglist if somebody knows that hidden bit

20:20 <eintopf> that would be a software solutiom

20:22 <DocScrutinizer05> arrrgh thinkpad

20:23 <DocScrutinizer05> had fun with swapping blue and ctrl key, also involved flashing a new/patched controller MCU firmware

20:24 <DocScrutinizer05> somebody RE'ed it but didn't punlish the findings, only the results

20:24 <DocScrutinizer05> publish*

20:24 <eintopf> yes, same here

20:24 <eintopf> but middleton bios has versions for ctrl/fn swap

20:25 <eintopf> don't know if your model is supported by middleton

20:25 <DocScrutinizer05> my model is cursed by defect fan

20:26 <DocScrutinizer05> actually defect controller driver FET for fan

20:26 <eintopf> oh

20:26 <DocScrutinizer05> I blocked the fan with some plastic stick when cleaning heatsink with pressurized air, but that stick bent and glitched ---> BORKED

20:27 <DocScrutinizer05> you can kill the mobo of a laptop with a simple vacuum cleaner

20:28 <DocScrutinizer05> without disassembling the laptop

20:30 <eintopf> :-/

20:31 <eintopf> new thinkpads are worse

20:31 <eintopf> we need to build a qi hardware notebook

20:31 <eintopf> based on retro thinkpads but opener and better

20:32 <eintopf> not a nanonote, i mean x86 hardware

20:35 <DocScrutinizer05> do you know of any service manuals for thinkpad (T510) ?

20:35 <eintopf> search for hmm

20:35 <DocScrutinizer05> nm, aunt google helps

20:35 <eintopf> hmm is the usual thinkpad bible

20:36 <eintopf> but we do more infos there

20:36 <eintopf> and the embedded controller will be open source

20:36 <eintopf> yes... we will create the better thinkpads

20:37 <eintopf> if we have a embedded controller...

20:37 <eintopf> sorry, i am dreaming

20:42 <DocScrutinizer05> that dang service manual has not even a component placement diagram of mobo :-( of course no schematics

20:43 <DocScrutinizer05> seems this will be a true EE revocery job for when I'm terribly bored

20:51 <eintopf> :-D

20:52 <eintopf> thats why we need to do an open retro thinkpad

20:52 <eintopf> we need another name

20:52 <eintopf> hackpad

20:52 <eintopf> brainpad

20:52 <eintopf> sounds like brainbug

20:52 <eintopf> qipad

20:53 <eintopf> thats too ipad like

20:55 <DocScrutinizer05> sidenote: byebye avalanche! we won't miss you

20:55 <DocScrutinizer05> :-D

20:56 <DocScrutinizer05> alas I'm pretty sure somebody else will take over in not time

20:57 <DocScrutinizer05> https://www.heise.de/newsticker/meldung/Ermittlern-gelingt-Schlag-gegen-Botnet-Schwergewicht-Avalanche-3530277.html

21:02 <DocScrutinizer05> http://bioshddpassword.com/?tag=thinkpad&paged=10 GRRR

21:12 <DocScrutinizer05> HAH! http://kythuatphancung.vn/download/lenovo-thinkpad-t510-w510-wistron-kendo1-ws-laptop-schematics.html

21:14 <DocScrutinizer05> http://wstaw.org/m/2016/12/01/plasma-desktopuF2244.png