Originally posted by InsideJob
View Post
Announcement
Collapse
No announcement yet.
AMD Confirms Linux Performance Marginality Problem Affecting Some, Doesn't Affect Epyc / TR
Collapse
X
-
Originally posted by Beherit View PostIs there a bug in the ignore list function? I just added duby229 and sdack to mine, but still suffer having to filter their noise.Last edited by sdack; 08 August 2017, 12:24 PM.
Comment
-
Originally posted by pjssilva View Post
Actually you can do this kind of stuff by suing a configuration file in /etc/sensors ou /etc/sensors.d but I do not remember the details. In this case the formula is no easy that I do it in my head. Note that the -20 C is only necessary for the X processors, like 1700X and 1800X. For a regular processor, like 1700, the temperature will be already correct. I forgot to mention that. Sorry.
First check your chip and sensor you want to adjust:
sensors -u
Code:nct6779-isa-0290 ... SMBUSMASTER 0: temp7_input: 48.000
Code:chip "nct6779-isa-0290" compute temp7 @-20,@+20
sensors
Code:... SMBUSMASTER 0: +28.0°C
For me the problem is that KDE thermal monitor plasmoid is ignoring these offsets.Last edited by shmerl; 08 August 2017, 12:55 PM.
- Likes 1
Comment
-
I would think twice about believing a company that has taken from May until now to even own up
to the fact there was something wrong with their Ryzen chip, I read 39 pages on the AMD forum
of complaints, and endless examples of how to re create the problem.
I will wait until Phoronix tests the Threadripper, and the community subject it to the same tests
that showed the Ryzen for what it is, until then, I for One do not believe AMD, as I think it is no coincidence
that they only owned up right before the release of their Threadripper, and in doing so got sell the amazing
piece of news to us all that Threadripper is not sick like the Ryzen.
- Likes 2
Comment
-
Originally posted by sdack View Post*lol* I'm no hypocrite, but you're a fear-mongerer. First you want AMD to confirm your worst fears, and when it's not happening, but they rather tell you it doesn't affect Windows and it's only a rare case found only under Linux, which we knew all along, do you choose not to believe AMD, but want to hold on to your fears. Very smooth of you ... *lol*
If I'm the one sitting in a cave then it sure isn't as dark as yours.
- Likes 4
Comment
-
Originally posted by Windingroads View PostI would think twice about believing a company that has taken from May until now to even own up
to the fact there was something wrong with their Ryzen chip, I read 39 pages on the AMD forum
of complaints, and endless examples of how to re create the problem.
I will wait until Phoronix tests the Threadripper, and the community subject it to the same tests
that showed the Ryzen for what it is, until then, I for One do not believe AMD, as I think it is no coincidence
that they only owned up right before the release of their Threadripper, and in doing so got sell the amazing
piece of news to us all that Threadripper is not sick like the Ryzen.
This kind of behaviour is par for the course in this particular game I'm afraid.
- Likes 2
Comment
Comment