Bug 1124

Summary:	acerdhdf ok, but must be better
Product:	Mageia	Reporter:	y mun <muny>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	marja11, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	kernel	CVE:
Status comment:

Description y mun 2011-05-04 01:14:26 CEST

acerhdf, kernel module to manage fan on aspire one (and several other Acer Inc Computer), from Mr Feuerer, is ok on mageia kernel, as mainstream. But certainly distribution could gain to adopt other behaviour than default for this module :

Default is "turn everytime, and accelerate when have hot". 

Inclusion proposal :
options acerhdf verbose=0 fanon=67000 fanoff=55000 interval=10 kernelmode=1
As acerhdf options, (less than 50Â°C, fan stop, big ouffff. More than 67Â°C fan start (and accelerate automaticly if hotest)

Comment 1 y mun 2011-05-04 01:57:07 CEST

or fanon=60000 
?

Thierry Vignaud 2011-05-06 14:18:35 CEST

CC: (none) => thierry.vignaud
Source RPM: (none) => kernel

Ahmad Samir 2011-05-06 23:06:13 CEST

Assignee: bugsquad => tmb

Comment 2 Marja Van Waes 2011-10-12 19:30:45 CEST

any news on this request?

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-01-16 21:22:25 CET

Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.

@ Thomas
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

@ y mun

Is the problem still there in current kernel 
(updated cauldron or Mageia 2 alpha 3)

Comment 4 Marja Van Waes 2012-05-26 13:05:40 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Marja Van Waes 2012-06-16 19:08:18 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD