Quote from: zipiju on November 09, 2013, 11:11:03 PM

Quote from: LiveJay on November 09, 2013, 09:32:52 PM

I just submitted a pull request at GitHub for a fix I made to the klondike driver in cgminer. It was incorrectly reporting the target fan speed on the status line (always 0% due to a math error). Here is the diff if any of you adventurous souls out there want to try it out:

https://github.com/LiveJay/cgminer/commit/0124217db80cd4506d4fe1c921a6fd49bba59efb

Now it looks like this (it's capped at 99% because there isn't room for a fourth character):

https://photos-3.dropbox.com/t/0/AABLHwHkiYxSag3F8H6E3NUiyuUxGv8kqWewpDi4MHqkDA/12/44288815/png/1024x768/3/1384027200/0/2/Screenshot%202013-11-09%2010.25.55.png/eip0CZO0no5uOh5M9nwMA62GLBvLG4MNn1qJHuyykIE

My question is this: The firmware aways seems to be returning 255 or 100% for the fan target speed, even when the fan is obviously running slower. Is there any current activity around this in the firmware? Is the firmware source available for review? And where are the firmware devs hanging out. I wouldn't mind listening in or helping out.

Thanks,

-Jay

Fantarget was dropped in latest firmware and cgm driver, since there is a temptarget. Because of compatibility with older firmware, the fantarget is set by cgm driver to 255.
If you want to monitor an actual fan speed (or current pwm level, since fan rpm measurement is not implemented in firmware yet), you have to take a look at klninfo->status[dev].kline.ws.fanspeed variable.
You can review K16 firmware at github.com/zipiju/k16-firmware.

Thanks! I'll make that change in my branch.

-Jay

LiveJay

Posts

Merits