SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is still kinda a niche area for home users. I doubt many will encode video or use Blender.
I used Blender to model my new home's kitchen design. I was able to get something that was photo realistic enough for my wife to make a decision.
It does have a learning curve and it used to have a weird mouse binding. Tons of videos out there that show you what it can do and how you make it do that.
I used Blender to model my new home's kitchen design. I was able to get something that was photo realistic enough for my wife to make a decision.
It does have a learning curve and it used to have a weird mouse binding. Tons of videos out there that show you what it can do and how you make it do that.
I'm not saying nobody will use those in a home environment, just that it isn't common for most home users to be encoding videos and doing 3D modeling.
For those interested, I built a mini-ITX box, primarily for games and science applications. Pretty good and fast on day-to-day computing activities. I don't have any Radeon GPUs that fit the ITX form factor, but do have a XFX Radeon RX590 Fatboy connected with a PCI-E riser (what could go wrong?). I'm using the Phoronix Test Suite (via Slackbuilds.org) to stress test. Attached are some benchmarks for the Unigine Valley GPU test. So far everything is on default settings. 'HIGH' indcates a run with high power profile instead of auto.
Quote:
Slackware64 Current kernel 5.4.6.
GIGABYTE X570 I AORUS PRO WIFI Mini-ITX Motherboard
AMD RYZEN 7 3800X CPU
Patriot Viper Steel 16GB DDR4 4400 (PC4 35200)
Coolermaster Elite 110 case
SilverStone SST-KR01 low profile cooler
Rosewill HIVE 650S 650W ATX power supply
The only glitch so far is support for ITE 8688 sensor chip for fan speeds. CPU and GPU temperatures are available, as is GPU fan speed. No CPU or case fan data.
Last edited by kingbeowulf; 12-22-2019 at 06:49 PM.
Reason: added information;correction
I think I posted on this before on another thread.
The Ryzen 7 afaik, does this on the chip, which is far better than anything lm_sensors can do. A semiconductor junction can be used as a temperature sensor, allowing them to sense heat in very design sensitive locations.
They have this neat little video which dumbs this down. It shows a triangle, representing cpu temperature, voltage, & frequency. The points of this triangle represent design limits. A smaller triangle inside represents the SOA (Safe Operating Area). AMD automatically control the frequency & core voltage on the chip, to keep the heat within the SOA. This is far faster/better than metal sensors a couple of layers away from the core. You know the score - Junction blows at 150ºC, but if you see 80ºC it's too hot, and it does an emergency shutdown at 105ºC, which approximates 150ºC at the core. That's passé with AMD. The only user variable is how fast the fans are run, which controls your available boost speed.
business_kid, interesting but not really applicable to my post, as CPU and other temperatures are available without requiring lm-sensors. Also, you do not set the fan speed to govern CPU (or GPU) clock and boost clock speeds; you set the power management (or clock and/or voltage) which will adjust the fan speed as needed.
The CPU and case fan speeds are governed by the motherboard, not cpu. As I said, for the Ryzen 7 on this Gigabyte motherboard, I have the CPU and other temperatures, as well GPU fan speed, via kernel hwmon (k10temp, amdgpu, i2c, ACPI thermal etc). The only thing missing, is the can and CPU fan speeds - available in BIOS but not enumerated when the kernel boots. I can fiddle with various CPU/GPU power settings, which will adjust fan speed as needed, but no direct read-out of RPM. /sys/class/hwmon/... has a lot of info, but only the temperatures, some voltages, and GPU fan speed.
As far as I have been able to determine, motherboard fan speeds are enumerated via, in this case, an ITE chip, and the it87 kernel module. Unfortunately, ITE does not publicly provide data sheets and so kernel support is lacking for this particular ship (ITE ID=0x8688).
Not here to argue. My point was that the Ryzen 7 adapts itself to the circumstances in which it finds itself. Given that it's on chip, nobody's bothered writing driversfor external control.
Throttling core voltage and frequency as a safety measure to prevent overheating (bad fan, wrong cooler or improperly installed cooler) has been around for ages, not "new" with the Ryzen series. Back in the day, a thermal diode (or fuse) would 'pop' to shut down the CPU. You would save the expensive CPU but brick the motherboard, which was considerably cheaper. AMD still provides the CPU temperature data outputs so that motherboard manufacturers' can incorporate that data in the BIOS via a sensor chip. It is STILL the motherboard circuitry that sets the fan speed based on the CPU temperature data. The issue with some new motherboards (actually this has always been an issue), is that the linux kernel doesn't get any love for the technical documentation of these sensor chips. I have boxes here that have NCT chips and I can access all sorts of CPU data and fan settings. ITE is another matter: lm-sensors still needs a kernel module to be loaded and then just reads back stuff in /sys/class/hwmon. I can run this same Ryzen mini-ITX setup with Windows10 and have all the BIOS data in a software utility from the Gigabyte utility DVD. My son has a Ryzen box (can't think of the motherbaord atm) that uses a sensor ship supported in the linux kernel (slackware-current) and can pull up all the fancy sensor data from the CPU.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.