ubuntu Install

Message boards : Number crunching : ubuntu Install
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4

AuthorMessage
Profile Keith Myers
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 2428
Credit: 183,946,152
RAC: 355,090
United States
Message 1899240 - Posted: 5 Nov 2017, 5:41:29 UTC - in response to Message 1899238.  

Hi Grant, sorry for mis- appellation. Yes, I concur the AVX app is most definitely faster under Windows. Not sure that is the case under Linux. So far, Rick's tests have put the AVX way down on the bottom in performance compared to everything else other than SSE2 on his 1950X system. I have to assume that a Ryzen system would perform similarly since the 1950X is just two 1800X dies with some special sauce thrown on it. I found the SSE4.1 app faster than the AVX app under Linux on the FX processor. As I stated, I am going to get a week's baseline performance with the SSE4.1 app then switch back to the AVX app. I have my suspicions that the AVX app WILL be faster on the Ryzen system under Linux too. But I want to test anyway instead of just taking a leap of faith.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1899240 · Report as offensive     Reply Quote
Profile MikeProject Donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 30592
Credit: 57,579,242
RAC: 30,259
Germany
Message 1899264 - Posted: 5 Nov 2017, 9:11:21 UTC

The SSE 4.1 version is faster on Linux with a Ryzen.
I`m running it myself since i installed Mint 18.2.
With each crime and every kindness we birth our future.
ID: 1899264 · Report as offensive     Reply Quote
Profile RueiKeProject Donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 270
Credit: 103,969,172
RAC: 234,506
Taiwan
Message 1899274 - Posted: 5 Nov 2017, 11:22:41 UTC - in response to Message 1899236.  

Thanks for the continued testing Rick. I have just now brought the Linux machine back online after the Ryzen 1800X upgrade. The hardware upgrade went fairly smoothly other than putting in a duff AIO that I had my suspicions about anyway. It never worked correctly in Windows but I thought the issue was a Windows thing. Turned out Windows had nothing to do with the problem, it was the hardware. Pump to be more specific. Fell back on the original AIO that was in place when it was a FX system. That is working fine now. Have to RMA the H110i on Monday.

The software turned out to be the real wrench in the works. I could not get my desktop to load forever. I had read that putting new hardware under a Linux installation was supposed to be easy compared to Windows. In my case, that wasn't true. And I have learned that there just isn't any way to monitor the CPU temps. I have not had any success in compiling a module that is supposed to pick up the chip and motherboard sensors but I can't get it to compile yet. Missing resources that I can't figure out how to solve yet. Been putting the system through Prime95 stress test and stress-ng stress tests for a day. So far, no hardware issues but I really don't like not knowing what the Vcpu voltage is or what the CPU temp is. I have been resorting to shooting components under stress with a IR temp gun as the only way to get some idea of where I am at. I basically set the system up as a carbon copy of the 1700X system with regard to frequency and settings.

One mystery for me is that when I ran the BOINC benchmarks on the system, it came out much lower than the Windows system. I had always thought that the benchmarks are always higher when run under Linux. Should have been either identical or higher theoretically. Will have to look at other Ryzen hosts at SETI and see if I am normal.

For now, I am just continuing with the SSE4.1 app that I switched to last week when Jeff, Grant and Brent said it was faster than the AVX app I was previously running. I hear though and have the experience in Windows, that Ryzen does especially well with the AVX app because it has much better AVX topology compared to the old FX processors. I will run the SSE4.1 app for a week to get a baseline and then switch back over to the AVX app and then compare performance. It will interesting to find out if the same is true under Linux.


Hi Keith, I also had to work through a cooling problem over the weekend. I found my Windows 1950X system throttled at 1.5GHz @68.5C. Inspection found the coolant lines out of the CPU block had almost no coolant flowing. Ended up being gummed up coolant in the CPU block. Looks like the green Mayhems dye that I added to PrimoChill True coolant wasn't compatible. No problems in Mayhems coolant. I posted some photos on instagram. It just took me the evening to get the system back up, but temps look great now. 53C when fully loaded.

I agree with the concern on system monitoring software in Linux. I am using lm-sensors. Reports back good GPU temps, but CPU temps and Vcore don't look right. So far have not found a good solution. I am setting a Vcore (not offset) in BIOS, so there should be no issue with it running at some other voltage, but it would be great to have software confirmation.

I have switched Eos over to sse4.1 based on initial data. The 14 WU experiment is still running. Should be done tomorrow. I will post the results when complete.
YouTube Channel: Rick's Performance Computing
ID: 1899274 · Report as offensive     Reply Quote
Profile MikeProject Donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 30592
Credit: 57,579,242
RAC: 30,259
Germany
Message 1899275 - Posted: 5 Nov 2017, 11:27:02 UTC

I agree with the concern on system monitoring software in Linux. I am using lm-sensors. Reports back good GPU temps, but CPU temps and Vcore don't look right. So far have not found a good solution. I am setting a Vcore (not offset) in BIOS, so there should be no issue with it running at some other voltage, but it would be great to have software confirmation.


I don`t get temps for my CPU with lm-sensors ?
With each crime and every kindness we birth our future.
ID: 1899275 · Report as offensive     Reply Quote
Profile RueiKeProject Donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 270
Credit: 103,969,172
RAC: 234,506
Taiwan
Message 1899277 - Posted: 5 Nov 2017, 11:56:03 UTC - in response to Message 1899275.  

I agree with the concern on system monitoring software in Linux. I am using lm-sensors. Reports back good GPU temps, but CPU temps and Vcore don't look right. So far have not found a good solution. I am setting a Vcore (not offset) in BIOS, so there should be no issue with it running at some other voltage, but it would be great to have software confirmation.


I don`t get temps for my CPU with lm-sensors ?

Here is my output of sensors command of lm-sensors:
amdgpu-pci-4700
Adapter: PCI adapter
fan1:             N/A
temp1:        +48.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

amdgpu-pci-4300
Adapter: PCI adapter
fan1:             N/A
temp1:        +44.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

amdgpu-pci-0b00
Adapter: PCI adapter
fan1:             N/A
temp1:        +46.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

amdgpu-pci-4800
Adapter: PCI adapter
fan1:             N/A
temp1:        +48.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

amdgpu-pci-4400
Adapter: PCI adapter
fan1:             N/A
temp1:        +46.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

amdgpu-pci-0c00
Adapter: PCI adapter
fan1:             N/A
temp1:        +48.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

nct6779-isa-0290
Adapter: ISA adapter
Vcore:                  +0.57 V  (min =  +0.00 V, max =  +1.74 V)
in1:                    +1.09 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:                   +3.28 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:                  +3.28 V  (min =  +2.98 V, max =  +3.63 V)
in4:                    +1.80 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                    +0.93 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                    +1.21 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:                   +3.46 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:                   +3.28 V  (min =  +2.70 V, max =  +3.63 V)
in9:                    +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in10:                   +0.81 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                   +0.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                   +1.65 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                   +0.92 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                   +0.86 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                  1953 RPM  (min =    0 RPM)
fan2:                     0 RPM  (min =    0 RPM)
fan3:                  1890 RPM  (min =    0 RPM)
fan4:                  1896 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
SYSTIN:                 +31.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:                 +43.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                +15.0°C    sensor = thermistor
AUXTIN1:                +36.0°C    sensor = thermistor
AUXTIN2:                +34.0°C    sensor = thermistor
AUXTIN3:                +33.0°C    sensor = thermistor
SMBUSMASTER 0:          +84.5°C  
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

YouTube Channel: Rick's Performance Computing
ID: 1899277 · Report as offensive     Reply Quote
Profile Keith Myers
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 2428
Credit: 183,946,152
RAC: 355,090
United States
Message 1899343 - Posted: 5 Nov 2017, 16:47:30 UTC - in response to Message 1899274.  


I agree with the concern on system monitoring software in Linux. I am using lm-sensors. Reports back good GPU temps, but CPU temps and Vcore don't look right. So far have not found a good solution. I am setting a Vcore (not offset) in BIOS, so there should be no issue with it running at some other voltage, but it would be great to have software confirmation.

I have switched Eos over to sse4.1 based on initial data. The 14 WU experiment is still running. Should be done tomorrow. I will post the results when complete.

Rick, so you know what your SIO chip is on your motherboard? Lm-sensors does not recognize my ITE 8665 chip at all. It supposedly can if you recompile the lm-sensors module with a configuration file for the IT87 and should then pick up the motherboard sensors on my ASUS Prime X370 Pro motherboard. But I have not been able to compile the code so far.

Did you find a version of LM-sensors that worked with your motherboard at first shot? Or did you compile a new module like I am trying to do?
This is the resource I am trying to use. monitor-amd-ryzen-temperatures-in-linux-with-latest-kernel-modules#h10-build-lm-sensors
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1899343 · Report as offensive     Reply Quote
Profile Keith Myers
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 2428
Credit: 183,946,152
RAC: 355,090
United States
Message 1899346 - Posted: 5 Nov 2017, 16:53:17 UTC

Thanks for the post Rick. Looks like you have the NCT6779 SIO chip. I am assuming you built a new lm-sensors module to incorporate that chip by the process in my link. Was that so? If so, did you run into any issues compiling the module and how did you resolve them?
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1899346 · Report as offensive     Reply Quote
Profile RueiKeProject Donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 270
Credit: 103,969,172
RAC: 234,506
Taiwan
Message 1899418 - Posted: 5 Nov 2017, 22:41:24 UTC - in response to Message 1899346.  

Thanks for the post Rick. Looks like you have the NCT6779 SIO chip. I am assuming you built a new lm-sensors module to incorporate that chip by the process in my link. Was that so? If so, did you run into any issues compiling the module and how did you resolve them?


Hi Keith, No, I did not do a custom build. Just the standard download and answered all questions "Y" when doing the detection. I have the ASRock X399 Professional MB.
ID: 1899418 · Report as offensive     Reply Quote
Profile Keith Myers
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 2428
Credit: 183,946,152
RAC: 355,090
United States
Message 1899439 - Posted: 6 Nov 2017, 0:29:59 UTC - in response to Message 1899418.  

Hi Rick, thanks for the reply. I guess you got lucky with lm-sensors already having your SIO chip configured and I am unlucky in that it doesn't have support for my ITE8665 chip. If I can't figure out how to compile the lm-sensor module for my chip, I guess I will have to do without or until the lm-sensors maintainers do the work for me in future releases.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1899439 · Report as offensive     Reply Quote
Profile RueiKeProject Donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 270
Credit: 103,969,172
RAC: 234,506
Taiwan
Message 1899623 - Posted: 6 Nov 2017, 22:42:10 UTC

It took 40 hours to run, but finally have AVX vs SSE4.1 results on 14 WU running in Linux. Same as before, my setup is a Linux VM on my Win10 machine Nemesis. The VM is setup with 1 core and 8GB of RAM. The main machine is fully loaded (93%) with SETI CPU/GPU work. The VM runs the benchmarks while the main machine continues to run SETI. This way I can achieve a consistently loaded environment during the test. Here are my results:
ID: 1899623 · Report as offensive     Reply Quote
Profile Keith Myers
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 2428
Credit: 183,946,152
RAC: 355,090
United States
Message 1899629 - Posted: 6 Nov 2017, 23:14:45 UTC
Last modified: 6 Nov 2017, 23:17:19 UTC

Thanks for the update Rick. The results are trending along with your previous tests it seems. A general consensus is that the AVX app is faster on BLC tasks and the SSE4.1 app is faster on Arecibo tasks. The question now should be ...... for how long are we going to receive Arecibo tasks and is it worthwhile to stay on SSE4.1 until they are no more and we only receive BLC tasks. And further out is the question, if and when we start getting Parkes data, what app is fastest for them.

Back to other news. I have been successful in getting the ASUS Prime X370 Pro motherboard sensors to show up. I now have the CPU and VRM temps showing in GKrellm. I also have the CPU Fan, Fan1 and Fan2 showing. There are some voltages showing but they are nonsense until I can figure out how to scale them. VBat and 3VSB are showing correctly though.

Turns out sensors-detect does not detect the SIO chip. And I also found out the chip is NOT the ITE-8665E as far as any software is concerned. The system identifies the chip as the ITE-8620.
Once I did a modprobe at the correct address, sensors in terminal shows the chip output. I then added the module to my boot modules and now I have permanent sensor readout.
modprobe it87 force_id=0x8620

keith@Darksider:~$ sensors
asus-isa-0000
Adapter: ISA adapter
cpu_fan:        0 RPM

it8620-isa-0290
Adapter: ISA adapter
in0:          +1.48 V  (min =  +1.61 V, max =  +2.29 V)
in1:          +2.75 V  (min =  +1.44 V, max =  +0.66 V)
in2:          +2.15 V  (min =  +1.32 V, max =  +1.42 V)
in3:          +2.18 V  (min =  +2.65 V, max =  +2.84 V)
in4:          +0.04 V  (min =  +1.48 V, max =  +0.68 V)
in5:          +0.04 V  (min =  +2.96 V, max =  +3.02 V)
in6:          +0.04 V  (min =  +0.52 V, max =  +2.87 V)
3VSB:         +3.62 V  (min =  +0.31 V, max =  +0.65 V)
Vbat:         +3.50 V  
fan1:        1430 RPM  (min =   15 RPM)
fan3:         873 RPM  (min =   10 RPM)
fan5:         726 RPM  (min =   -1 RPM)  ALARM
temp1:        +40.0°C  (low  = -86.0°C, high = -51.0°C)  sensor = thermistor
temp2:        +35.0°C  (low  = +58.0°C, high = -25.0°C)  sensor = thermistor
temp3:        +30.0°C  (low  = +127.0°C, high = +126.0°C)  sensor = thermistor
temp4:        +30.0°C  
temp5:        +30.0°C  
intrusion0:  ALARM

keith@Darksider:~$ 


So for Mike and anyone else running the Crosshair VI or Prime X370 motherboard, try to modprobe the it87 module and see if you can find yours. If that doesn't produce any output you will have to probe some other alternate addresses such as 0x8622, 0x8607, 0x8628 and 0x8632.
It looks like the ROG Crosshair VI Hero is at 0x8665.
The driver is it87.ko and is in the:

/lib/modules/4.10.0-38-generic/kernel/drivers/gpio/gpio-it87.ko
/lib/modules/4.10.0-38-generic/kernel/drivers/hwmon/it87.ko

directories or your equivalent distributions. Hope this helps others running a Ryzen under Linux.
[Edit] A quick check with lsmod will print out all your current loaded modules. Look for the it87 module.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1899629 · Report as offensive     Reply Quote
Previous · 1 · 2 · 3 · 4

Message boards : Number crunching : ubuntu Install


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.