On March 4, 2021 3:50:21 PM UTC, gregor herrmann wrote:
>On Tue, 02 Mar 2021 22:44:24 +, Thorsten Glaser wrote:
>
>> and the new one doesn’t work, and I don’t even
>> know what I’m supposed to put where. Perhaps upstream has some kind
>> of list what model needs which settings? Also, YAML i
On Tue, 02 Mar 2021 22:44:24 +, Thorsten Glaser wrote:
> and the new one doesn’t work, and I don’t even
> know what I’m supposed to put where. Perhaps upstream has some kind
> of list what model needs which settings? Also, YAML is such a weird
> format unfriendly to human editing…
What "works
Evgeni Golov dixit:
>>>, exactly because neither the old nor the new configuration is in a
>>>state where it's supposed to work out of the box.
>>
>>But why? The pre-YAML thing *did* work out of the box, very finely
>>so, and I only changed the config one hot summer to have a little
>>more quiet.
On March 2, 2021 9:01:28 PM UTC, Thorsten Glaser wrote:
>Evgeni Golov dixit:
>
>>>… without that it’ll also fail, which means it’ll fail package
>>>installation, which is a serious (RC) bug.
>>
>>No, the daemon is not started on install
>
>Did that change recently? Because when I reported this
Evgeni Golov dixit:
>>… without that it’ll also fail, which means it’ll fail package
>>installation, which is a serious (RC) bug.
>
>No, the daemon is not started on install
Did that change recently? Because when I reported this bug first
it was precisely because it was started on install…
>, ex
On March 2, 2021 8:26:12 PM UTC, Thorsten Glaser wrote:
>Evgeni Golov dixit:
>
>>> No, this is about the *vanilla* config shipped by the package.
>>> It used to work (my adjustment later was only regarding the levels
>>> of temperature as I’ve got an SSD, not HDD, so it can become a bit
>>> hig
Evgeni Golov dixit:
>> No, this is about the *vanilla* config shipped by the package.
>> It used to work (my adjustment later was only regarding the levels
>> of temperature as I’ve got an SSD, not HDD, so it can become a bit
>> higher for quietness) and now the package doesn’t work at all.
>
>Yea
On Tue, Mar 02, 2021 at 07:28:11PM +, Thorsten Glaser wrote:
> Evgeni Golov dixit:
>
> >> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
> >> Starting fan control tool: thinkfan
> >> ERROR: Error scanning
> >> /sys/devices/pci:00/:00:03.1/:27:00.0/hwmon: No such f
Evgeni Golov dixit:
>> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
>> Starting fan control tool: thinkfan
>> ERROR: Error scanning
>> /sys/devices/pci:00/:00:03.1/:27:00.0/hwmon: No such file or
>> directory
>> failed!
>
>-3 has a NEWS.Debian explaining the chang
Hey,
On Tue, Mar 02, 2021 at 04:13:01PM +0100, Thorsten Glaser wrote:
> Unfortunately, thinkfan still fails to work:
>
> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan stop
> Stopping fan control tool: thinkfan.
> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
> Starti
10 matches
Mail list logo
