Bug 10394 - New version LM_sensor which supporting AMD family 16h power sensors (Trinity)
Summary: New version LM_sensor which supporting AMD family 16h power sensors (Trinity)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Damien Lallement
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-02 13:01 CEST by Dušan Pavlík
Modified: 2015-03-31 16:03 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dušan Pavlík 2013-06-02 13:01:46 CEST 
Description of problem:
I have AMD Triniti A10-5800 procesor but sensor in GKrelM indicant no relevant information.

As you see in LM-sensor changelog  http://lm-sensors.org/browser/lm-sensors/tags/V3-3-4/CHANGES new version add support for this chips. 

Version-Release number of selected component (if applicable):
lm_sensor 3.3.3-3.mga3

change to 

lm_sensor 3.3.4-mga3

Source:

http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.4.tar.bz2


Reproducible: 

Steps to Reproduce:
Comment 1 Damien Lallement 2013-06-04 01:08:52 CEST 
3.3.4 now in cauldron.
Will work on a backport.

Status: NEW => ASSIGNED
CC: (none) => mageia
Assignee: bugsquad => mageia

Comment 2 Marja Van Waes 2015-03-31 16:03:22 CEST 
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.