Anybody planning a Ryzen build?


Recommended Posts

Is Ryzen or Threadripper able to run unraid WITHOUT disabling C6 yet? 

My c state settings on 1920x/X399 Taichi is the default one. I didn’t touch it. I’ve not done any c state syslinux changes either.

Stable for over a week since last reboot and I do see it hovering at 1.8-2.2ghz as per lscpu


Sent from my iPhone using Tapatalk
Link to comment
  • 2 weeks later...
On 3/18/2018 at 8:43 AM, Greygoose said:

Possible Ryzen issues?

 

I have 2 VMs running, ryzen system with 32gb ram. all on stock settings...

 

Earlier i tried to backup a HDD in unassigned devices and one of my VMs just turned off and unraid wouldn't allow me to boot the VM. 

 

I have attached the diagnostics, i also have bad performance when i try to do anything with data. my VM stutters and feels laggy.,  I have the NVME as unassigned device and the VM on it so was expecting it to be smooth even when copying data to the array between a different unassigned device (not the NVME).

mediaserver-diagnostics-20180317-1746.zip

 

I'm also experiencing really horrible ssd performance in my windows vm. I'm gettin 250mb write which is OK but it feels like it's lagging as soon as it's doing any io. I have no clue as to how to debug this so any help would be appreciated 

Link to comment
On 4/22/2018 at 6:05 AM, jammsen said:
On 4/22/2018 at 4:35 AM, methanoid said:

Is Ryzen or Threadripper able to run unraid WITHOUT disabling C6 yet? 

It works fine for me, but beware that the mainboard, the bios and the CPU/APU plays a role in it too.

But if you want to go for ultra low wattage on standby, you wont get the same results as Intel does.

I recently bios flashed, and left global C-states enabled, been a few days now. I know of a few other Threadripper owners who never had-to, or bothered, to disable C-states.

 

My meter reports 170W as I'm writing this, from VM, system details in signature. 

Link to comment
20 hours ago, mikegg said:

'm also experiencing really horrible ssd performance in my windows vm. I'm gettin 250mb write which is OK but it feels like it's lagging as soon as it's doing any io. I have no clue as to how to debug this so any help would be appreciated 

I peaked at your diagnostics file. Is the VM in question running on the Samsung 850 drive?

If answer is yes, is the partition aligned?  If you're unsure how to check, like I was, here are the instructions I was given before:

SSH into the unraid, then run the command "parted /dev/sdx"  where x = the drive sdx is your drive's address.

once in there run "print" to see a list of the partitions, then run the following command

align-check opt n
 

Where n = the partition you want to check, will probably be 1.

 

It'll tell you if your alignment is right..  When you do the print, it'll tell you what sector you're starting on.

Even if you answered no, and it's on another SSD, would probably be a worth while thing to check on. 

 

As for, how to fix the issue, if you find partitions not aligned, I made and used a gparted-live disk; rebooted my system into that environment and moved the partition into alignment. 

Moving the partition took about 45 minutes to complete (500gb drive).

Link to comment
20 hours ago, Jcloud said:

I peaked at your diagnostics file. Is the VM in question running on the Samsung 850 drive?

If answer is yes, is the partition aligned?  If you're unsure how to check, like I was, here are the instructions I was given before:


SSH into the unraid, then run the command "parted /dev/sdx"  where x = the drive sdx is your drive's address.

once in there run "print" to see a list of the partitions, then run the following command

align-check opt n
 

Where n = the partition you want to check, will probably be 1.

 

It'll tell you if your alignment is right..  When you do the print, it'll tell you what sector you're starting on.

Even if you answered no, and it's on another SSD, would probably be a worth while thing to check on. 

 

As for, how to fix the issue, if you find partitions not aligned, I made and used a gparted-live disk; rebooted my system into that environment and moved the partition into alignment. 

Moving the partition took about 45 minutes to complete (500gb drive).

Thanks for trying to help, i tried checking the alignment of the partitions and it says that it's aligned.

Also, it's not my diagnostics file you've been loking at since i haven't posted any yet :D

 

16 hours ago, david279 said:

Ok try setting the xml for your vm like this. Set the cache part to none instead on writeback.

 


<driver name='qemu' type='raw' cache='none'/>

This seems to kill the stuttering for me. 

I've already set it like that but i don't think it's working as it's evident that my read speeds are RAM speeds ?

Here is my xml for the VM:

<domain type='kvm' id='1'>
  <name>Windows 10 Gaming</name>
  <uuid>a97e8d42-ddc6-a463-54d6-8a2b4918092a</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>16777216</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='8'/>
    <vcpupin vcpu='1' cpuset='9'/>
    <vcpupin vcpu='2' cpuset='10'/>
    <vcpupin vcpu='3' cpuset='11'/>
    <vcpupin vcpu='4' cpuset='12'/>
    <vcpupin vcpu='5' cpuset='13'/>
    <vcpupin vcpu='6' cpuset='14'/>
    <vcpupin vcpu='7' cpuset='15'/>
    <emulatorpin cpuset='6-7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/a97e8d42-ddc6-a463-54d6-8a2b4918092a_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/disk/by-id/ata-INTEL_SSDSC2BW240A4_PHDA428200RD2403GN'/>
      <backingStore/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Win10_1709_English_x64.iso'/>
      <backingStore/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <alias name='ide0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/>
      <backingStore/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <alias name='ide0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='sata0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:9d:30:39'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10 Gaming/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'>
      <alias name='input0'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input1'/>
    </input>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/user/isos/gtx1080.rom'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0b' slot='0x00' function='0x3'/>
      </source>
      <alias name='hostdev3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </hostdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

Link to comment

Here is the xml for my Win 10 VM, also Im using Q-2.11 for my VM. Try virtIO for the bus type.....

<domain type='kvm'>
  <name>Windows 10 HTPC</name>
  <uuid>7d5d103c-144f-1f5e-402a-825074ed2075</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows_teamgreen.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='5'/>
    <vcpupin vcpu='2' cpuset='6'/>
    <vcpupin vcpu='3' cpuset='7'/>
    <vcpupin vcpu='4' cpuset='8'/>
    <vcpupin vcpu='5' cpuset='9'/>
    <vcpupin vcpu='6' cpuset='10'/>
    <vcpupin vcpu='7' cpuset='11'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.11'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/7d5d103c-144f-1f5e-402a-825074ed2075_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/mnt/disks/500GBSSDStorage/Windows 10 HTPC/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.126-2.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='nec-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0xb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xc'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0xd'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0xe'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0xf'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:fc:43:3d'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/disks/500GBSSDStorage/Windows 10 HTPC/EVGAGTX1030.rom'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0a5c'/>
        <product id='0x21e8'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Edited by david279
Link to comment

@david279 Thanks for the help but no dice. I've tried;

* Changing the currrent VM to Q35 - still same issue

* Changing bus to VirtIO - won't even boot

* Reinstalled windows with Q35 and disabled cache - still same issue

* Reinstalled windows with i4 and disabled cache - still same issue

Link to comment
8 minutes ago, mikegg said:

9 Thanks for the help but no dice. I've tried;

* Changing the currrent VM to Q35 - still same issue

* Changing bus to VirtIO - won't even boot

* Reinstalled windows with Q35 and disabled cache - still same issue

* Reinstalled windows with i4 and disabled cache - still same issue

Not optimal, but trouble-shooting hardly is, have you tried setting up Windows on that drive and with this board as "bare metal" to see if it's hardware or combination of hardware causes the issue? Or was this your old gaming system, or similar, and hence you already have an idea of what the benchmark numbers should look like on bare metal? Perhaps it's failing hardware? I don't know the age of these components, so I'm just asking from perspective of general troublehooting - as my Linux Kungfu isn't as strong. 

 

What version of the Redhat VirtIO drivers are you running in Windows? That's the first time I've seen QEMU listed in windows (from my own vm dealing at least).

Edited by Jcloud
Link to comment
1 hour ago, Jcloud said:

Not optimal, but trouble-shooting hardly is, have you tried setting up Windows on that drive and with this board as "bare metal" to see if it's hardware or combination of hardware causes the issue? Or was this your old gaming system, or similar, and hence you already have an idea of what the benchmark numbers should look like on bare metal? Perhaps it's failing hardware? I don't know the age of these components, so I'm just asking from perspective of general troublehooting - as my Linux Kungfu isn't as strong. 

 

What version of the Redhat VirtIO drivers are you running in Windows? That's the first time I've seen QEMU listed in windows (from my own vm dealing at least).

Good shout, will likely try that tomorrow. I think i did this before and didn't see the issue then. But i don't think i looked at the average response time but went more on feeling. Passing the ssd through like i do makes it possible to also boot on the SSD directly. But don't want to disturb peoples plexing right now :)

Link to comment
1 hour ago, mikegg said:

Good shout, will likely try that tomorrow. I think i did this before and didn't see the issue then. But i don't think i looked at the average response time but went more on feeling. Passing the ssd through like i do makes it possible to also boot on the SSD directly. But don't want to disturb peoples plexing right now :)

For ultra-paranoid, and to make sure nothing happens with that array data, on the power-off you could physically disconnect the power for the drives in your array, just so Windows doesn't see it and nothing happens to data.

 

I would hate to rebuild my media library because of a drive mix-up. ;)

Link to comment

So looking at the new Zen+ CPUs, I'm really eyeing that 2700 with the 65 TDP, it seems to keep up with the + in all but gaming, and even there it is close enough.  I'm seeing benchmark results all over the place on encoding (which I use to compare between processors as few do "transcoding" testing).

 

It would be very cool to actually /drop/ my TDP from my 77 Xeon and get ~5k more passmarks and double the threads..but it almost seems too good to be true.  Anyone have any input here on what I might not be accounting for?

 

Details: Migrating from a E3-1275 v2 on an OLD Supermicro board, want to be able to have a windows VM as a desktop replacement (Desktop is an older i7) for light gaming while not over-taxing the server.

Link to comment

Is anyone here running ECC RAM on their Ryzen machines? I am considering Ryzen for my next server build, but ECC is a must. I have read so much confusing information online about Ryzen and ECC I am simple not sure what is what. If anyone does have an ECC setup, what MB, CPU, and RAM  combo are you using? What is your understanding/impression of the state of ECC and Ryzen?

 

Link to comment
15 hours ago, primeval_god said:

¿Hay alguien aquí corriendo ECC RAM en sus Ryzen máquinas? Estoy considerando Ryzen para mi próxima generación de servidor, pero ECC es una necesidad. He leído tanto confusa información en línea acerca de Ryzen y ECC No estoy seguro de lo sencillo es lo. Si alguien tiene una configuración de ECC, lo que MB, la CPU y la RAM combinado está usando? ¿Cuál es su comprensión / impresión del estado de ECC y Ryzen ?

 

para todos aquellos que estén interesados en el tema, les sugiero la "lectura completa" del siguiente artículo

 

"ECC Memory & AMD's Ryzen - A Deep Dive"
Author: MAC
Date: March 30, 2017

Link to comment

Hello all,

 

Recently i upgraded my intel i5 gen 4 platform to an ryzen platform:

AMD RYZEN 7 2700X sAM4 +Wraith
16GB 2x8GB CMK16GX4M2B3000C15
MSI X470 GAMING PRO Mobo

 

Ive been using unraid with my i5 gen 4 for more than 2 years now without any issue. And im very pleased that the upgrade was seamless. After connecting the new hardware to my 'old' cache ssd array and hhd storage array and using the same unraid pen drive image, everything booted without issues. I have running on top of the unraid os (v6.4.0):

 

krusader

netdata

pihole

2x tonido cloud server

2x windows 10 vm with dedicated gpu

bunch of user utilities

 

On the bios (latest version) did left it almost at default settings. XFR enable ( mem running @ 3GHz ) , AMD cool and quiet enable ... So all ryzen firmware oc features are enable and working well, the grep MHz command shows cpu core speed varying from 2.2GHz up to 4.25GHz :)

 

Relative to power consumption i have not noticed any relevant change.

The system is currently up and running for more than 3 days, no issues.

The only downside i have up to this moment is not knowing the system / core temperatures (x470 is still very recent), fan speed is looking good (not worried about it, great stock cooler ).

 

Here are some prints:

 

image.png.ee427267097907f18afa64854e3bc0c3.png

 

image.png.b5ae1b178468c0e2fcdb682e20f4d9ac.png

 

image.png.f4ff9094ec8a531b0075859074b795b2.png

 

 

Regards.

 

 

 

 

Edited by react
  • Like 1
Link to comment
6 hours ago, react said:

Hello all,

 

Recently i upgraded my intel i5 gen 4 platform to an ryzen platform:


AMD RYZEN 7 2700X sAM4 +Wraith

16GB 2x8GB CMK16GX4M2B3000C15

MSI X470 GAMING PRO Mobo

 

 

Thank you. That's the motherboard that I have purchased too, I'm just waiting for my RAM before setting up. If you spot any problems then please do share.

Link to comment
19 hours ago, react said:

On the bios (latest version) did left it almost at default settings. XFR enable ( mem running @ 3GHz ) , AMD cool and quiet enable ... So all ryzen firmware oc features are enable and working well, the grep MHz command shows cpu core speed varying from 2.2GHz up to 4.25GHz :)

 

image.png.b5ae1b178468c0e2fcdb682e20f4d9ac.png

 

 

I can't believe that there isn't more discussion on this, as it certainly caught my attention.

 

I have an 1800X, and my individual core's max out at 3.6GHz with unRAID, even when only a single core is loaded.

 

I always figured that this was just a limitation of Linux, as in earlier testing I saw 4.1GHz in Windows.

 

Now react comes along and shows boosting working perfectly on a 2700X, what's up with that?

 

While I know that the 2xxx series on the X470 motherboards adds Precision Boost 2 and XFR2, these simply permit more aggressive boosting when more cores are loaded, and shouldn't be required for boosting when only a single core was loaded.

 

I never see over 3.6GHz (I don't manually overclock).  Is this the same experience of other Ryzen 1 users?

 

Is there a change in Ryzen 2 or X470 that fixes this issue, or a system setting or BIOS setting I might have wrong?

 

Paul

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.