Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Fonz,
1. According to your documentation,
dns323-leds 0x10 and 0x20 make the "top LED" blink (I assume you mean the big blue LED??)
When I issue these commands, I don't notice any changes to any of the LEDs.
Note that using 0x02 and 0x04, I can get the orange LEDs to blink
2. I notice that any fan speed that I give to "dns323-fan s" is dropped and reset every 5 minutes (coincident with when /tmp/fan is rewritten). Is 'fancontrol' responsible for that?
Similarly, temper, temper_F and temper_C seem to be written every 30 minutes. But not sure by what process and I don't see anything in the crontab.
3. What is the meaning of the 3rd "status" output of dns323-fan -v?
I would guess that it is indicating whether actual_speed is within "range" of program_speed. But I don't know what tolerances you are using (seems to be maybe 20% or so?)
4. Also, it seems like you can't set the fan exactly - but that it jumps to the nearest of a certain number of fixed speeds. Is that right?
5. Does dns323-fan differ significantly from the built-in fanspeed command?
Similoarly, does dns323-temper differ significantly from dns323-temp?
Offline
1. B1 hardware might work a little different.
2. Yes, fancontrol.
3. No idea, it's what the kernel returns. Maybe the kernel source has a description.
4. Yes, there're some restrictions on the fan speed granularity, but I don't know the exact rules.
5. It's using the same kernel interface. Afaict, temperature prints F on some, and C on other boxes, while dns323-temp always prints the same.
Offline
Thanks Fonz.
Re #3, it does seem that status is 0 if the actual speed is locked within a range of the set frequency and 1 otherwise.
Offline