ufopinball

Members
  • Content count

    162
  • Joined

  • Last visited

Community Reputation

5 Neutral

1 Follower

About ufopinball

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • URL
    http://www.ufopinball.com/
  1. I may have, but it's been awhile. I originally ran Cinebench and Blender. Are there other benchmarks you suggest? Note that my GPU isn't a gaming model. As for "utilizing other resources" ... is there an easy way to do this? I can start a second VM, assign it all remaining CPU cores, and run Prime95 there. Does that cover what you are asking? - Bill
  2. Is there any downside to using the ACS override feature? Once enabled, my IOMMU groupings are very, very favorable for VM usage. I am currently passing through my GPU, and also a USB 3.0 port from the motherboard. ASUS Prime X370-PRO motherboard, and the Ryzen 1800X (you can probably do very well with a 1700 though!) - Bill
  3. I like the idea of building a wiki page. I bought my Ryzen on launch day (March 2nd), and put it in an unRAID box early on. The other thread is ~20 pages long, and while it has a lot of good information, it's likely a bit daunting. I'll see what I can do about making a wiki section, but you can start with the previous thread and see what you think. My build has been running for ~3 months now. There are a few gotchas, but the feeling is that those things will be sorted out eventually ... either by BIOS upgrades, or unRAID & Linux Kernel upgrades. Do you have a list of specs on what you have bought or plan to buy? My specs are in my signature line, if that helps. - Bill
  4. Last week, I had upgraded to the ASUS Prime X370-PRO beta BIOS 0803 with AGESA 1.0.0.6 ... so far, the server is running smoothly. Today, I tried a test run with unRAID 6.4-rc2 (sorry, it's what I had on the thumb drive), but the later Linux kernel didn't include any new support for the sensor chip on the ASUS Prime X370-PRO motherboard. Since I was only curious, I built a temp thumb drive to run the test. Afterwards, I booted back on my regular thumb drive that's running unRAID 6.3.5. If you're interested in using the Dynamix System Temp plugin on the ASUS Prime X370-PRO, check my previous post for details. Bill
  5. Okay, so I have loaded the ASUS Prime X370-PRO beta-test BIOS 0803 with AMD/Ryzen AGESA 1.0.0.6. I am still running unRAID 6.3.5, though. The BIOS upgrade seemed to take longer this time. As usual, I had to go in and redo all my preferred settings. The system accepted them and rebooted, then did nothing for like 10 minutes. I finally powered down, counted to 10, and started it up again and this time it worked. No idea what was up with the weird hang. I've rebooted about 3-4 times since then trying different things, and have not encountered it again. Just be-aware that this may occur, at least the first time after the BIOS upgrade. Otherwise, my system temperatures are a bit higher, but we're in the middle of a heat wave and that may have something to do with it. My memory is rated at 2133, so I'm not testing for the 3000-4000 speeds that others are looking for. I did turn off all the ACS override stuff, but the "new" IOMMU table doesn't look all that impressive: IOMMU group 0 [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 IOMMU group 1 [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453 IOMMU group 2 [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 IOMMU group 3 [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 IOMMU group 4 [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453 IOMMU group 5 [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 IOMMU group 6 [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454 [1022:145a] 29:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a [1022:1456] 29:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1456 [1022:145c] 29:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 145c IOMMU group 7 [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454 [1022:1455] 2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 [1022:7901] 2a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [1022:1457] 2a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457 IOMMU group 8 [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 9 [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1460 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1461 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1462 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1463 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1464 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1465 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1466 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1467 IOMMU group 10 [1022:43b9] 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 1d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) [1022:43b4] 1d:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) [1022:43b4] 1d:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) [1022:43b4] 1d:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) [1000:0072] 21:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) [1b21:1343] 25:00.0 USB controller: ASMedia Technology Inc. Device 1343 [8086:1539] 26:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 11 [1002:677b] 28:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:aa98] 28:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM] I ended up switching the ACS override back on, since my Windows 10 VM wouldn't start without it. Unfortunately, that's about all the time I have at the moment. I'd still like to switch from the USB audio to the onboard audio, and will hopefully find some time to poke at that soon. Dunno if anyone is monitoring the unRAID 6.4 board, but they're up to RC3 now. No idea how close they are to a final cut. That's still on my list, though. Anyone else give it a try? - Bill
  6. Some minor updates. A new "system stability" BIOS has been posted for the ASUS Prime X370-PRO motherboard, version 0612. I've been on it for about a week and have not encountered any issues. Likewise, I upgraded to unRAID 6.3.5 in a similar time frame, and things are going smoothly. I know there's an unRAID 6.4 pre-release RC available, but I haven't had a chance to load it yet. Might have better support for Ryzen, since it's based on a Linux 4.11.* kernel. Also there appears to be a ASUS Prime X370-PRO beta-test BIOS with the AMD/Ryzen AGESA 1.0.0.6. If I have time I may load that as well. Just throwing it out there for those who are looking for a weekend project. :-) - Bill
  7. For what it's worth, this has always been the behavior that I have experienced. Even when I was doing pre-testing with an Asus F2A85V-PRO motherboard and AMD A10-5800K Trinity 3.8GHz FM2 Quad CPU. The three GPUs I tested were the ASUS Radeon HD 3450, ASUS Radeon HD 4350 and Asus Radeon HD 6450. Dunno if it's something specific to AMD CPUs, ASUS motherboards or ASUS Radeon GPUs ... or even the Windows OS? Are others seeing this same sort of behavior where you shut down the Windows VM and it doesn't return you to the unRAID console? Or is this just how it's expected to work? Thanks... - Bill
  8. It's certainly worth trying out the other options, but failing that I would reboot and go into the BIOS and try to record nominal values for the CPU/MB temp and CPU fan. Then boot into unRAID and see which of the items in your "sensors" outputs comes closest and use those. Afterwards you can always run a Prime95 or similar test and see if the output values follow the expected progression. - Bill
  9. When you say "onboard audio", do you mean the audio off the motherboard, or off one of the GPUs? I'm presently using a USB audio device. Looking at my "System Devices", the only audio device is the HDMI audio output from my GPU. I'd love to reduce another device and work with the motherboard audio chip. Would you share the necessary details? Thanks! - Bill
  10. That's disappointing. With the ACS patch on unRAID, I am able to pass in one of three USB controllers built into the motherboard. I ended up returning my USB 3.0 PCIe card because it wasn't necessary anymore. It was less than $10, so I suppose it's no big deal either way. Still, it would be nice to be able to plug the USB 3.0 card into a PCIe x1 slot, than having to use one of the larger x16 slots ... that's just how the IOMMU groupings broke up. - Bill
  11. Good article on the Ryzen AGESA 1.0.0.6 firmware update, which includes much more flexibility (BIOS settings) when it comes to expanded memory support. Surprise, there are also some details on expanded IOMMU/ACS support! AMD must have listened when this was brought up in an earlier AMA meeting. Glad to see them stepping up items for virtualization, as this will become more important moving forward into Naples/Epyc. https://community.amd.com/community/gaming/blog/2017/05/25/community-update-4-lets-talk-dram All that said, it looks like it's not out yet, just in beta test. Actual finalized BIOS updates aren't expected till mid/late June. Wonder what else will be included? - Bill
  12. Okay, so I took another stab at this today. For the record, my board is the ASUS Prime X370-PRO. If I open a putty window and run "sensors-detect", here's what I get (skipping 'No" items): Trying family `ITE'... Yes Found unknown chip with ID 0x8665 (logical device 4 has address 0x290, could be sensors) Unfortunately, the ITE 0x8665 driver is not included in the unRAID 6.3.4 build ... however, this led me to this thread: https://github.com/groeck/it87/issues/10 Following their instructions, I tried this command: modprobe it87 force_id=0x8620 and then ran 'sensors', which now produced this output: it8620-isa-0290 Adapter: ISA adapter in0: +0.88 V (min = +2.22 V, max = +2.42 V) in1: +2.74 V (min = +0.97 V, max = +1.39 V) in2: +2.20 V (min = +2.06 V, max = +1.81 V) in3: +2.18 V (min = +1.34 V, max = +2.27 V) in4: +0.04 V (min = +1.57 V, max = +0.49 V) in5: +0.04 V (min = +1.46 V, max = +2.76 V) in6: +0.04 V (min = +2.11 V, max = +0.16 V) 3VSB: +3.60 V (min = +3.24 V, max = +4.51 V) Vbat: +3.46 V in11: +0.41 V Array Fan: 1053 RPM (min = 11 RPM) fan3: 795 RPM (min = 40 RPM) CPU Temp: +44.0°C (low = -31.0°C, high = +78.0°C) sensor = thermistor MB Temp: +32.0°C (low = +84.0°C, high = +13.0°C) sensor = thermistor temp3: +34.0°C (low = -13.0°C, high = -14.0°C) sensor = thermistor temp4: +34.0°C temp6: +34.0°C intrusion0: ALARM Since we don't have the proper driver, we're using a 'compatible' driver, so the above information has some issues. Notably the min/max values are incorrect ... however for my purposes, I am only interested in obtaining enough data to populate the Dynamix System Temperature plugin. This works as follows: To complete the setup, I added the command "modprobe it87 force_id=0x8620" to my 'go' file and rebooted. The system loads the drivers at boot time, and the plugin now displays the CPU/MB temperature and the CPU fan speed on the status line. Hopefully in unRAID 6.4, they'll include the necessary sensors packages to support the ITE 0x8665 chipset. If someone has one of the other ASUS motherboards and find that this also works for you, let us know? - Bill PS: I did not test this with an earlier version of unRAID, so I don't know if version 6.3.4 (or later) is required. You may wish to upgrade prior to attempting this.
  13. I've been checking every few days, but so far there's no new BIOS for the ASUS Prime X370-PRO motherboard. Last update was on April 10th. Otherwise, I was away for the weekend, but upgraded to unRAID 6.3.4 this morning. So far, no problems. Can't comment on stability, I'm leaving my Windows 10 VM because that was my original use case. This effectively prevents me from testing stability without a VM running. Again, the C-States setting doesn't appear to make a difference on this board, so it's currently at the default setting. - Bill
  14. Upgraded from 6.3.3 to 6.3.4, went smoothly with no issues. Thanks Limetech!
  15. Are you running any VMs? It might be worth setting one up. I have the ASUS Prime X370-PRO motherboard, and last I checked (albeit not recently), disabling C-States didn't actually do anything. My guess was that the BIOS setting exists, but the underlying feature was unimplemented. My system stays alive (16 days, 7 hours, 55 minutes) by virtue of having a Windows 10 VM running all the time. This keeps the processor busy enough to keep the sleep states from occurring, and thus it works around the crash issue. Since you have the ASUS Prime B350M-A board, I am guessing that the C-States setting may not be performing any action on your board, either. You can test power consumption with the C-States enabled/disabled and see if there is a difference. Not sure how you got a week of uptime, maybe you have a VM but it's not always running? Anyway, something to try out... - Bill
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.