I have a Ryzen 5 1600AF (Zen+) and 2x 8 GB DDR4 3600 HyperX. when I select XMP1, it says 1.35V in the profile. however, when I boot Strelec WinPE USB (I’m on Fedora, I really don’t want to install windows just so I can run HWINFO), install all drivers and launch HWINFO64 it says 1.2V. so I enter BIOS again, go to Voltages and enter 1.35 manually instead of auto. no change, still reads 1.2V. the BIOS side screen shows 1.35 after reboot.

I’ve found an unresolved thread somewhere with the same problem for my board. I’m on latest BIOS.

am I missing something, is there some additional setting I need to switch so it registers? the BIOS setup is hella confusing and borderline stupid, e.g. enabling virtualization required turning on SMP (how am I supposed to guess what that is?!) that’s located in the “Frequency” subsection (wtf?!).

  • SteveTech@programming.devEnglish
    2·
    1 year ago

    If you open the sensors part of HWINFO there should be a DIMM voltage from the motherboard, that’s a live reading, what does that say?

    I’m on Fedora

    Here’s a few alternatives to HWINFO I’ve used:

    • CPU-X (has a GUI, and is probably the most like HWINFO but still different)
    • lm-sensors (might require a custom profile for your motherboard, but can provide live temp/fan/voltage sensor readings)
    • dmidecode (built in, can read the data off the dimm, but doesn’t read sensors directly)

    Edit: Just realised I have that motherboard, and it’s probably why XMP stopped being stable. I’ll look into it on Monday.

    Edit 2: From memory to use lm-sensors you need to use an updated it87 driver for both chips to appear, I can provide a sensors profile on Monday.

    • dingdongitsabear@lemmy.mlOPEnglish
      2·
      1 year ago

      CPU-X doesn’t list RAM voltages. sensors lists a buncha stuff (none labeled as DDR voltage) but all at 1.2V. dmidecode also lists 1.2V for all items, but I’ve read that its data is unreliable. I’ve tried already all the listed options (and then some) and that’s why I tried WinPE, as HWINFO64 is supposed to have methods to reliably determine RAM voltage.

  • dingdongitsabear@lemmy.mlOPEnglish
    2·
    1 year ago
    Diagnostics

    dmidecode output:

    Memory Device
	Array Handle: 0x000B
	Error Information Handle: 0x0011
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8 GB
	Form Factor: DIMM
	Set: None
	Locator: DIMM 0
	Bank Locator: P0 CHANNEL A
	Type: DDR4
	Type Detail: Synchronous Unbuffered (Unregistered)
	Speed: 3000 MT/s
	Manufacturer: Kingston
	Serial Number: 0B0672F9
	Asset Tag: Not Specified
	Part Number: KHX3600C17D4/8GX    
	Rank: 1
	Configured Memory Speed: 3000 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V
	Memory Technology: DRAM
	Memory Operating Mode Capability: Volatile memory
	Firmware Version: Unknown
	Module Manufacturer ID: Bank 2, Hex 0x98
	Module Product ID: Unknown
	Memory Subsystem Controller Manufacturer ID: Unknown
	Memory Subsystem Controller Product ID: Unknown
	Non-Volatile Size: None
	Volatile Size: 8 GB
	Cache Size: None
	Logical Size: None

    sensors:

    it8792-isa-0a60
Adapter: ISA adapter
in0:           1.79 V  (min =  +0.00 V, max =  +2.78 V)
in1:           1.18 V  (min =  +0.00 V, max =  +2.78 V)
in2:           1.02 V  (min =  +0.00 V, max =  +2.78 V)
+3.3V:         3.38 V  (min =  +0.00 V, max =  +5.56 V)
in4:           1.20 V  (min =  +0.00 V, max =  +2.78 V)
in5:           1.04 V  (min =  +0.00 V, max =  +2.78 V)
in6:           2.78 V  (min =  +0.00 V, max =  +2.78 V)  ALARM
3VSB:          3.36 V  (min =  +0.00 V, max =  +5.56 V)
Vbat:          3.33 V

    bios:

    dmidecode and sensors output are from XMP2 (3000 MT/s, also 1.35V) as I can’t boot the OS at XMP1, but when I could the output was the same.

      • dingdongitsabear@lemmy.mlOPEnglish
        2·
        1 year ago

        correct, HWINFO64 lists two. thanks for the link, but seems way too cumbersome to install it so I’ll use WinPE from my Ventoy USB drive if I need to check if the detected voltage changes.

        • SteveTech@programming.devEnglish
          2·
          1 year ago

          Yeah it does need a sensors config for your motherboard too, if you want the proper names, but I won’t be able to get mine until maybe Sunday.

          • dingdongitsabear@lemmy.mlOPEnglish
            2·
            1 year ago

            I’m mainly checking if there’s something else to switch in BIOS or that’s all there is to it and my setup is just incompatible; I’m waiting to snag a used 5600 when they drop a bit more in price, since they’re supposed to work better with faster RAM. but sure, if you get around to it I’d appreciate any config you can share.

              • dingdongitsabear@lemmy.mlOPEnglish
                1·
                1 year ago

                my original reply vanished, so here I go again: thank you very much for your efforts and for following up. I couldn’t get the driver to compile on my system but that wasn’t my primary goal, guess my setup is just incompatible. hopefully I’ll get a used 5600 by year’s end and check then. thanks again.

                • SteveTech@programming.devEnglish
                  1·
                  1 year ago

                  No worries!

                  I believe for the driver you need to install build-essential @development-tools (forgot about fedora) and then run sudo make dkms.

  • Lojcs@lemm.eeEnglish
    0·
    1 year ago

    If it’s running stable at the correct speed, does it matter what voltage it runs on?

    • dingdongitsabear@lemmy.mlOPEnglish
      2·
      1 year ago

      it is not, presently it runs at 2400. setting it to 3600 causes it to fail to boot. occasionally it boots fine, but various apps don’t work (Firefox can’t open, Geekbench crashes, etc.). also, there’s the known issue of freezing after waking from sleep, for which the fixed voltage is supposedly the fix.