mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Hardware

Reply
 
Thread Tools
Old 2021-07-25, 02:58   #221
paulunderwood
 
paulunderwood's Avatar
 
Sep 2002
Database er0rr

7·19·31 Posts
Default

Quote:
Originally Posted by paulunderwood View Post
Debian 10 (Buster) installed. The chip is running at 1.4GHz even though it says powersave. HyperThreading is off. 32 workers in 56 days for 113M bit candidates With some runtime tuning I expect this to lower.

Edit: After some runtime tuning by mprime at 2% done the ETA is now 55 days.
After another auto-benchmarking by mprime the ETA is now 47 days (with 4% done)

This is about 66% of the speed of a Radeon VII. Not bad for a cheap low-end chip.

Last fiddled with by paulunderwood on 2021-07-25 at 03:08
paulunderwood is online now   Reply With Quote
Old 2021-07-25, 16:06   #222
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

6,469 Posts
Default

Quote:
Originally Posted by paulunderwood View Post
After another auto-benchmarking by mprime the ETA is now 47 days (with 4% done)

This is about 66% of the speed of a Radeon VII. Not bad for a cheap low-end chip.
Radeon VII list was $699 new. Xeon Phi systems were considerably higher, ~$5k new as I recall.
The 7210 alone was ~$2036. https://ark.intel.com/content/www/us...z-64-core.html
kriesel is online now   Reply With Quote
Old 2021-11-02, 21:12   #223
ewmayer
2ω=0
 
ewmayer's Avatar
 
Sep 2002
República de California

32×1,303 Posts
Default

I have some very interesting p-1 stage 2 timings to report, related to the issue of running big-memory-footprint tasks in a mix of the 16GB fast onboard MCDRAM and any regular dimm-based RAM the owner has installed.

I just posted over in Software re. the release of Mlucas v20.1.1. On of the bugfixes in that patch-release is to permit p-1 stage 2 runs for moduli which need the currently-largest FFT length supported by the program, 512M. (I tested said fix on M(p) with p = 8589934693, which has 2 prime factors q = 2.k.p+1 < 2^68, with k1 = 1866092580 = 2^2.3^4.5.11.23.29.157 and k2 = 2291914028 = 2^2.23.727.34267. So b1 = 1000 and b2 = 35000 should catch them both.)

Once I had tested the 512M fix on the above, I started a run of a first p-1 stage 2 interval (from B1=10^7 to B2=10^8) on F33 using the stage 1 residue I spent August to mid-October crunching, which computation used only the MCDRAM. Will announce the distributed stage 2 initiative and upload the Stage 1 residue file needed for that soon. Now to the timings: Stage 1 was pinned to the MCDRAM using "numactl -m 1" - in low-memory build mode (which disallows both PRP+Gerbicz-check and p-1 stage 2 work), the resulting memory footprint fits easily into 16GB, with the actual main residue doubles-array occupying 4GB. Running on 64 of the 68 physical cores, 2 threads per core, gives a stage 1 timing around 470 ms/iter, stage 1 to B1 = 10^7 needed ~14.5 million of those.

Running exclusively in the MCDRAM is not an option for stage 2: The minimum stage 2 prime-pairing-related buffer count supported by the code is 24, which along with 4 auxiliary residue arrays and other stuff means a memory footprint of ~120GB. So using the new bugfixed v20.1.1 code I switched off the above numactl run-prefix. Note that the key stage 2 FFT-mul operation if of the form A *= (B - C[i]), where A is the stage 2 accumulator, B is update-recomputed just once for each bigstep-sized loop (frequency of perhaps once for every 10 of above SUBMULs, or less for larger bigstep values), and C[i] is one of our precomputed stage 2 prime-pairing buffers. When on a typical PC both stages are running of of the same pool of dimm-RAM, each stage 2 iteration runs 10-15% slower than a stage 1 one, since the former is doing a 3-input SUBMUL, whereas the latter is just doing LL/PRP-style FFT-autosquarings. So if the KNL had enough MCDRAM to run stage 2 in it, I would expect a timing of around 540 ms/iter.

I figured running out of RAM might be around 2x slower, but hoped that the OS would still be smart enough to keep the A and B-arrays (4GB each) in the MCDRAM, treating it as a huge L3 cache, and only stream the various C[i] in from the RAM. I specified 40 stage 2 buffers (total footprint ~180GB), the largest supported value which fits into the 208GB = (16GB MCDRAM + 192GB dimm-RAM) of the machine; the next-larger value of 48 buffers needs ~206GB, but in practice system tasks and such reduce the available RAM to ~200GB. My initial timings did not appear to reflect good usage of the MCDRAM, they are around 2.5x slower than the above using-only-MCDRAM estimate:
Code:
Using complex FFT radices       256        32        32        32        32
Using Bigstep 330, pairing-window multiplicity M = 1: Init M*40 = 40 [base^(A^(b^2)) % n] buffers for Stage 2...
Buffer-init done; clocks = 00:08:47.608, MaxErr = 0.066406250.
Small-prime[7] relocation: will start Stage 2 at bound 14285714
Stage 2 q0 = 14285700, k0 = 43290
Computing Stage 2 loop-multipliers...
Stage 2 loop-multipliers: clocks = 00:03:12.325, MaxErr = 0.070312500.
[2021-10-31 01:14:45] F33 S2 at q = 14454660 [ 0.20% complete] clocks = 03:43:54.623 [1342.1202 msec/iter] Res64: 375C751C2193C084. AvgMaxErr = 0.060365977. MaxErr = 0.078125000.
[2021-10-31 04:58:40] F33 S2 at q = 14624610 [ 0.39% complete] clocks = 03:43:54.280 [1341.1481 msec/iter] Res64: 8FA26CABD8066355. AvgMaxErr = 0.060372666. MaxErr = 0.078125000.
Now since stage 2 seemed to be using only/mostly the dimm-RAM, I figured I might as well restart my long-running on-again/off-again DC-run of F30 @64M FFT, using the same 64 physical cores and pinning it to the MCDRAM, to see what happens - the above F33 stage 2 timings barely budged, perhaps 1% slower than before; the F30 (Pépin-test, i.e. a base-3 PRP-style iteration sequence) timing was ~10x slower than the 60 ms/iter it gets when it has exclusive use of those physical cores and the MCDRAM. I've converted the F30 timings to sec/iter here to make it easier to keep them and the F33 timings straight:
Code:
[Oct 31 14:53:29] F30 Iter# = 1014050000 [94.44% complete] clocks = 01:52:37.270 [  0.6757 sec/iter] Res64: 61D461B8BE5AA6EC. AvgMaxErr = 0.020537182. MaxErr = 0.025390625.
[Oct 31 16:28:20] F30 Iter# = 1014060000 [94.44% complete] clocks = 01:34:11.211 [  0.5651 sec/iter] Res64: 0FAB072D0630B7AD. AvgMaxErr = 0.020541896. MaxErr = 0.027343750.
[Oct 31 18:21:34] F30 Iter# = 1014070000 [94.44% complete] clocks = 01:52:35.246 [  0.6755 sec/iter] Res64: 8E2F615B63261E5E. AvgMaxErr = 0.020547897. MaxErr = 0.027343750.
[Oct 31 20:00:07] F30 Iter# = 1014080000 [94.44% complete] clocks = 01:38:08.717 [  0.5889 sec/iter] Res64: 9FE2EFD72D198020. AvgMaxErr = 0.020539502. MaxErr = 0.025390625.
So time to peruse the numactl manpage for possible flags related to this - that turned up:
Code:
--preferred=node
	Preferably allocate memory on node, but if memory cannot be allocated there fall back to other nodes. This option
	takes only a single node number. Relative notation may be used.
So replaced the stage 1 "numactl -m 1" with "--preferred=1" ... the result was rather dramatic:
Code:
[2021-11-01 19:42:10] F33 S2 at q = 16323450 [ 2.38% complete] clocks = 01:53:30.824 [680.5380 msec/iter] Res64: AC7ADAF3890D3E2B. AvgMaxErr = 0.060386060. MaxErr = 0.078125000.
[2021-11-01 21:35:46] F33 S2 at q = 16494060 [ 2.58% complete] clocks = 01:53:36.272 [680.6743 msec/iter] Res64: A8F72B08FE0ED8ED. AvgMaxErr = 0.060396971. MaxErr = 0.078125000.
[2021-11-01 23:29:21] F33 S2 at q = 16665330 [ 2.78% complete] clocks = 01:53:34.381 [681.0976 msec/iter] Res64: EF5013CB5B044A5F. AvgMaxErr = 0.060309100. MaxErr = 0.078125000.
[2021-11-02 01:22:51] F33 S2 at q = 16835610 [ 2.97% complete] clocks = 01:53:30.290 [680.2808 msec/iter] Res64: AAC4601E2A662B3D. AvgMaxErr = 0.060352525. MaxErr = 0.078125000.
[2021-11-02 03:16:19] F33 S2 at q = 17005230 [ 3.17% complete] clocks = 01:53:28.145 [679.6591 msec/iter] Res64: BDCBEF62E1DCBA41. AvgMaxErr = 0.060377368. MaxErr = 0.078125000.
That cut the per-iter time in half. That was great, but I figured the F33 run now properly using the MCDRAM as an L3 cache would hammer the timings of the F30 run. Another surprise:
Code:
[Nov 02 09:23:01] F30 Iter# = 1014450000 [94.48% complete] clocks = 00:47:54.481 [  0.2874 sec/iter] Res64: DB4B350821A5186C. AvgMaxErr = 0.020541790. MaxErr = 0.027343750.
[Nov 02 10:19:12] F30 Iter# = 1014460000 [94.48% complete] clocks = 00:55:39.301 [  0.3339 sec/iter] Res64: C5BA6F080DB6978A. AvgMaxErr = 0.020556644. MaxErr = 0.027343750.
[Nov 02 11:07:43] F30 Iter# = 1014470000 [94.48% complete] clocks = 00:47:58.540 [  0.2879 sec/iter] Res64: 79736A5FEF2A69B3. AvgMaxErr = 0.020545662. MaxErr = 0.027343750.
[Nov 02 12:03:56] F30 Iter# = 1014480000 [94.48% complete] clocks = 00:55:42.774 [  0.3343 sec/iter] Res64: 6C83CE991294FBD3. AvgMaxErr = 0.020542251. MaxErr = 0.027343750.
[Nov 02 12:52:24] F30 Iter# = 1014490000 [94.48% complete] clocks = 00:47:56.019 [  0.2876 sec/iter] Res64: D6C2F91C87683142. AvgMaxErr = 0.020544057. MaxErr = 0.027343750.
So the timings for that secondary run also dropped by around 2x.
ewmayer is online now   Reply With Quote
Old 2021-11-27, 18:52   #224
ewmayer
2ω=0
 
ewmayer's Avatar
 
Sep 2002
República de California

2DCF16 Posts
Default

Mike/Xyzzy fwded the following link to a used-gear-4-sale Reddit page, asked if the Xeon Phi gear there was a good deal, presumably w.r.to GIMPS crunching:

https://www.reddit.com/r/hardwareswa...us_256_thread/

Went to the Intel page for the HNS7200AP compute module - looks like that is a host for the 7200-series CPUs, i.e. KNL; 6 dimm slots up to 384 GB RAM sounds just like my barebones workstation system, but mobo seems different. I see he has 2 w/CPU and 2 w/o. No idea how much stuff/work beyond the obvious (chassis, psu, water cooler) this needs to build into a working system - discussion welcome.
ewmayer is online now   Reply With Quote
Old 2021-11-27, 21:34   #225
paulunderwood
 
paulunderwood's Avatar
 
Sep 2002
Database er0rr

7·19·31 Posts
Thumbs up

Quote:
Originally Posted by ewmayer View Post
Quote:
complete running server with 4 cpus| 256 cores, 1024 threads, 48gb mcdram, dual 2100w psu (2 es 8gb chips and 2 es 16gb chips) |$2000 + shipping
Formidable power. I had toyed with getting such a system. The potential noise put me off. It would draw about 1400w running flat out. One would need a garage or basement to house it. I think it is like 4 machines in one i.e. it needs 4 kernels running. Still not a bad offer by the seller.

I guess one could run 16 mprime workers (4 cores each) on each of the two 8GB ES chips and likewise 32 workers (2 cores) on each of the 16GB chips.

Last fiddled with by paulunderwood on 2021-11-27 at 22:39
paulunderwood is online now   Reply With Quote
Old 2022-01-25, 18:53   #226
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

6,469 Posts
Default Identifying graphics hardware in the K1SPE Supermicro motherboard

In Windows 10 Pro, Device Manager says simply Microsoft Basic Display Adapter.
GPU-Z V2.44.0 detects no video type at all for a system booted with only the onboard graphics, or only the discrete GPU on a system booted with one installed.
CPU-Z V1.99 detects Aspeed AST1000/2000 which is vague and shows no details, and the Aspeed website includes numerous vga and SOC chips in the 1xxx and 2xxx families but no 1000 or 2000.
HWinfo64 v7.16-4560 spins through enumerating 272 logical processors of the Xeon Phi 7250, and some other items, and crashes too early to provide useful information or gain access to its settings to record debug information.

In Ubuntu/WSL1/Win10, what could be tried? Installed hwinfo, but its output doesn't contain anything about graphics or video; the only occurrence of the string "monitor" is in cpu flags.
What does native Linux report for onboard video hardware?
Attached Thumbnails
Click image for larger version

Name:	7250 MB graphics id.png
Views:	31
Size:	68.4 KB
ID:	26459  
kriesel is online now   Reply With Quote
Old 2022-01-25, 20:06   #227
chalsall
If I May
 
chalsall's Avatar
 
"Chris Halsall"
Sep 2002
Barbados

101000110011102 Posts
Default

Quote:
Originally Posted by kriesel View Post
What does native Linux report for onboard video hardware?
Code:
chalsall@hobbit:~$ lspci -v

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd 8th Gen Core Processor Host Bridge/DRAM Registers
        Flags: bus master, fast devsel, latency 0
        Capabilities: <access denied>
        Kernel driver in use: skl_uncore
        Kernel modules: ie31200_edac

00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 122
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000e000-0000efff [size=4K]
        Memory behind bridge: f6000000-f70fffff [size=17M]
        Prefetchable memory behind bridge: 00000000e0000000-00000000f1ffffff [size=288M]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:02.0 Display controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630]
        DeviceName: Onboard - Video
        Subsystem: Gigabyte Technology Co., Ltd CometLake-S GT2 [UHD Graphics 630]
        Flags: bus master, fast devsel, latency 0, IRQ 144
        Memory at f5000000 (64-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at f732e000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: <access denied>

00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI])
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
        Flags: bus master, medium devsel, latency 0, IRQ 134
        Memory at f7310000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH CSME HECI
        Flags: bus master, fast devsel, latency 0, IRQ 145
        Memory at f732d000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: <access denied>
        Kernel driver in use: mei_me
        Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] (prog-if 01 [AHCI 1.0])
        DeviceName: Onboard - SATA
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH SATA controller [AHCI mode]
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 133
        Memory at f7328000 (32-bit, non-prefetchable) [size=8K]
        Memory at f732c000 (32-bit, non-prefetchable) [size=256]
        I/O ports at f090 [size=8]
        I/O ports at f080 [size=4]
        I/O ports at f060 [size=32]
        Memory at f732b000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: <access denied>
        Kernel driver in use: ahci
        Kernel modules: ahci

00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #19 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 123
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1b.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #20 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 124
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 125
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 126
        Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #4 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 127
        Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 128
        Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
        I/O behind bridge: 0000d000-0000dfff [size=4K]
        Memory behind bridge: f7200000-f72fffff [size=1M]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #6 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 129
        Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 130
        Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.7 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #8 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 131
        Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: [disabled]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 132
        Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
        I/O behind bridge: [disabled]
        Memory behind bridge: f7100000-f71fffff [size=1M]
        Prefetchable memory behind bridge: [disabled]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1f.0 ISA bridge: Intel Corporation Device a2cc
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd Device 5001
        Flags: bus master, medium devsel, latency 0

00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset Family Power Management Controller
        Flags: bus master, fast devsel, latency 0
        Memory at f7324000 (32-bit, non-prefetchable) [size=16K]

00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
        DeviceName: Onboard - Sound
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH HD Audio
        Flags: bus master, fast devsel, latency 32, IRQ 146
        Memory at f7320000 (64-bit, non-prefetchable) [size=16K]
        Memory at f7300000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
        DeviceName: Onboard - Other
        Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset Family SMBus Controller
        Flags: medium devsel, IRQ 16
        Memory at f732a000 (64-bit, non-prefetchable) [size=256]
        I/O ports at f040 [size=32]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801

01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050]
        Flags: bus master, fast devsel, latency 0, IRQ 143
        Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
        Kernel modules: nvidiafb, nouveau

01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1)
        Subsystem: ASUSTeK Computer Inc. GP107GL High Definition Audio Controller
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at f7080000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at d000 [size=256]
        Memory at f7204000 (64-bit, non-prefetchable) [size=4K]
        Memory at f7200000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8169
        Kernel modules: r8169

b:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) (prog-if 02 [NVM Express])
        Subsystem: Phison Electronics Corporation E12 NVMe Controller
        Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
        Memory at f7100000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: nvme
        Kernel modules: nvme
Your results are almost 100% likely to be different than this. But this is what serious people see when they ask the correct questions from their supporting kit and OS.
chalsall is online now   Reply With Quote
Old 2022-01-25, 20:07   #228
ewmayer
2ω=0
 
ewmayer's Avatar
 
Sep 2002
República de California

32·1,303 Posts
Default

Quote:
Originally Posted by kriesel View Post
In Windows 10 Pro, Device Manager says simply Microsoft Basic Display Adapter.
GPU-Z V2.44.0 detects no video type at all for a system booted with only the onboard graphics, or only the discrete GPU on a system booted with one installed.
CPU-Z V1.99 detects Aspeed AST1000/2000 which is vague and shows no details, and the Aspeed website includes numerous vga and SOC chips in the 1xxx and 2xxx families but no 1000 or 2000.
HWinfo64 v7.16-4560 spins through enumerating 272 logical processors of the Xeon Phi 7250, and some other items, and crashes too early to provide useful information or gain access to its settings to record debug information.

In Ubuntu/WSL1/Win10, what could be tried? Installed hwinfo, but its output doesn't contain anything about graphics or video; the only occurrence of the string "monitor" is in cpu flags.
What does native Linux report for onboard video hardware?
Don't know about Ubuntu on KNL ... under CentOS you want to use the 'lshw' command. On my KNL, truncating a bunch of similar 'generic' items after the interesting part:

Code:
[ewmayer@localhost ~]$ sudo lshw -short
[sudo] password for ewmayer: 
H/W path             Device      Class          Description
===========================================================
                                 system         Super Server (To be filled by O.E.M.)
/0                               bus            K1SPE
/0/0                             memory         64KiB BIOS
/0/2c                            memory         208GiB System Memory
/0/2c/0                          memory         32GiB DIMM DDR4 Synchronous Registered (Buffered) 2400 MHz (0.4 ns)
/0/2c/1                          memory         32GiB DIMM DDR4 Synchronous Registered (Buffered) 2400 MHz (0.4 ns)
/0/2c/2                          memory         32GiB DIMM DDR4 Synchronous Registered (Buffered) 2400 MHz (0.4 ns)
/0/2c/3                          memory         32GiB DIMM DDR4 Synchronous Registered (Buffered) 2400 MHz (0.4 ns)
/0/2c/4                          memory         32GiB DIMM DDR4 Synchronous Registered (Buffered) 2400 MHz (0.4 ns)
/0/2c/5                          memory         32GiB DIMM DDR4 Synchronous Registered (Buffered) 2400 MHz (0.4 ns)
/0/2c/6                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/7                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/8                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/9                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/a                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/b                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/c                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/2c/d                          memory         2GiB Chip DRAM Synchronous 7200 MHz (0.1 ns)
/0/53                            memory         4352KiB L1 cache
/0/54                            memory         34MiB L2 cache
/0/55                            processor      Intel(R) Xeon Phi(TM) CPU 7250 @ 1.40GHz
/0/100                           bridge         Intel Corporation
/0/100/5                         generic        Intel Corporation
/0/100/5.2                       generic        Intel Corporation
/0/100/5.4                       generic        Intel Corporation
/0/100/5.6                       generic        Intel Corporation
/0/100/8                         generic        Intel Corporation
/0/100/8.1                       generic        Intel Corporation
/0/100/8.2                       generic        Intel Corporation
/0/100/11                        generic        C610/X99 series chipset SPSR
/0/100/11.4          scsi2       storage        C610/X99 series chipset sSATA Controller [AHCI mode]
/0/100/11.4/0.0.0    /dev/sda    disk           1TB PNY CS900 1TB SS
/0/100/11.4/0.0.0/1              volume         599MiB Windows FAT volume
/0/100/11.4/0.0.0/2  /dev/sda2   volume         1GiB EXT4 volume
/0/100/11.4/0.0.0/3  /dev/sda3   volume         929GiB LVM Physical Volume
/0/100/14                        bus            C610/X99 series chipset USB xHCI Host Controller
/0/100/14/0          usb3        bus            xHCI Host Controller
/0/100/14/0/1        wlp0s20u1   network        802.11 n WLAN
/0/100/14/0/e                    bus            Hub
/0/100/14/0/e/1                  input          Keyboard
/0/100/14/1          usb4        bus            xHCI Host Controller
/0/100/16                        communication  C610/X99 series chipset MEI Controller #1
/0/100/16.1                      communication  C610/X99 series chipset MEI Controller #2
/0/100/1a                        bus            C610/X99 series chipset USB Enhanced Host Controller #2
/0/100/1a/1          usb1        bus            EHCI Host Controller
/0/100/1a/1/1                    bus            USB hub
/0/100/1c                        bridge         C610/X99 series chipset PCI Express Root Port #1
/0/100/1c.3                      bridge         C610/X99 series chipset PCI Express Root Port #4
/0/100/1c.3/0                    bridge         AST1150 PCI-to-PCI Bridge
/0/100/1c.3/0/0                  display        ASPEED Graphics Family
/0/100/1c.4                      bridge         C610/X99 series chipset PCI Express Root Port #5
/0/100/1c.4/0        enp4s0f0    network        I350 Gigabit Network Connection
/0/100/1c.4/0.1      enp4s0f1    network        I350 Gigabit Network Connection
/0/100/1d                        bus            C610/X99 series chipset USB Enhanced Host Controller #1
/0/100/1d/1          usb2        bus            EHCI Host Controller
/0/100/1d/1/1                    bus            USB hub
/0/100/1f                        bridge         C610/X99 series chipset LPC Controller
/0/100/1f.3                      bus            C610/X99 series chipset SMBus Controller
/0/100/1f.6                      generic        C610/X99 series chipset Thermal Subsystem
/0/1                             generic        Intel Corporation
...
/0/1f.2                          generic        Intel Corporation
/0/85                            system         PnP device PNP0b00
/0/86                            system         PnP device PNP0c02
/0/87                            system         PnP device PNP0c02
/0/88                            communication  PnP device PNP0501
/0/89                            communication  PnP device PNP0501
/1                   virbr0-nic  network        Ethernet interface
/2                   virbr0      network        Ethernet interface

Last fiddled with by ewmayer on 2022-01-25 at 20:08
ewmayer is online now   Reply With Quote
Old 2022-01-25, 21:55   #229
ewmayer
2ω=0
 
ewmayer's Avatar
 
Sep 2002
República de California

267178 Posts
Default

Heads-up: the several brands of 32GB DIMM4 ECC server RAM modules I listed in post #168 of this thread are now all ~$100 each. (I paid $150 each for 6 such at Nemix last May, been keeping those busy with F33 stage 2 work since last Fall.) The 64GB modules have dropped by a mere 10% in the interim; I did find at least one such offering on eBay for closer to $200 but it was listed "out of stock".
ewmayer is online now   Reply With Quote
Old 2022-01-25, 23:01   #230
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

6,469 Posts
Default

Thanks for the real-Linux responses. WSL really gets in the way for things that want to reach out to read the hardware. And its provision for some guest OS capabilities is simply absent. Following are from Supermicro K1SPE motherboard, Xeon Phi 7250, Ubuntu 18.04/WSL1/Win10 Pro. I know there's a spinning HD in the box too since I put it there.
Code:
$ sudo lshw
hydra
    description: Computer
    width: 64 bits
    capabilities: smp
  *-core
       description: Motherboard
       physical id: 0
     *-memory
          description: System memory
          physical id: 0
          size: 15GiB
     *-cpu
          product: Intel(R) Xeon Phi(TM) CPU 7250 @ 1.40GHz
          vendor: Intel Corp.
          physical id: 1
          bus info: cpu@0
          capacity: 1401MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave osxsave avx f16c rdrand lahf_lm abm 3dnowprefetch fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms avx512f rdseed adx avx512pf avx512er avx512cd ibrs ibpb cpufreq
  *-network:0
       description: Ethernet interface
       physical id: 1
       logical name: eth0
       serial: 0c:c4:(redacted)
       capabilities: ethernet physical
       configuration: broadcast=yes ip=(redacted) multicast=yes
  *-network:1 DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: eth1
       serial: 0c:c4:(redacted)
       capabilities: ethernet physical
       configuration: ip=169.254.(redacted)

$ sudo lshw -short
H/W path  Device  Class      Description
========================================
                  system     Computer
/0                bus        Motherboard
/0/0              memory     15GiB System memory
/0/1              processor  Intel(R) Xeon Phi(TM) CPU 7250 @ 1.40GHz
/1        eth0    network    Ethernet interface
/2        eth1    network    Ethernet interface
Code:
$ lspci -v
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
$ sudo lspci -v
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
Since neither Windows & its utilities nor native CentOS have much to say about the onboard video circuitry, and the K1SPE was designed as a server motherboard, I think it's safe to now assume there will be no IGP GIMPS cycles to eke out of whatever the ASpeed video hardware is. I should probably be glad it has any video capability on the motherboard. Many workstation designs did not.

Last fiddled with by kriesel on 2022-01-25 at 23:05
kriesel is online now   Reply With Quote
Old 2022-01-25, 23:50   #231
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

6,469 Posts
Default

Quote:
Originally Posted by ewmayer View Post
Heads-up: the several brands of 32GB DIMM4 ECC server RAM modules I listed in post #168 of this thread are now all ~$100 each. (I paid $150 each for 6 such at Nemix last May, been keeping those busy with F33 stage 2 work since last Fall.) The 64GB modules have dropped by a mere 10% in the interim; I did find at least one such offering on eBay for closer to $200 but it was listed "out of stock".
Just bought out the remaining stock from the (eBay) vendor I got my first (~$123) sample from; 5 more at $77.40 per 2133Mhz 32GiB ECC RDIMM, which should work with either 7250 or 7210 Xeon Phi on the K1SPE MB, and fill a board.
A used modular power supply is also reportedly on its way.
Micron MTA72ASS8G72LZ-2G3B2 (64GiB ECC LRDIMM) are US$265 and up @ eBay; Samsung M386A8K40BM1-CRC4Q $222 & up with lowest priced vendors only q1 or 2 stock.

Last fiddled with by kriesel on 2022-01-26 at 00:01
kriesel is online now   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
AMD vs Intel dtripp Software 3 2013-02-19 20:20
Intel NUC nucleon Hardware 2 2012-05-10 23:53
Intel RNG API? R.D. Silverman Programming 19 2011-09-17 01:43
AMD or Intel mack Information & Answers 7 2009-09-13 01:48
Intel Mac? penguain NFSNET Discussion 0 2006-06-12 01:31

All times are UTC. The time now is 21:45.


Thu May 19 21:45:28 UTC 2022 up 35 days, 19:46, 1 user, load averages: 1.87, 1.87, 1.73

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.

≠ ± ∓ ÷ × · − √ ‰ ⊗ ⊕ ⊖ ⊘ ⊙ ≤ ≥ ≦ ≧ ≨ ≩ ≺ ≻ ≼ ≽ ⊏ ⊐ ⊑ ⊒ ² ³ °
∠ ∟ ° ≅ ~ ‖ ⟂ ⫛
≡ ≜ ≈ ∝ ∞ ≪ ≫ ⌊⌋ ⌈⌉ ∘ ∏ ∐ ∑ ∧ ∨ ∩ ∪ ⨀ ⊕ ⊗ 𝖕 𝖖 𝖗 ⊲ ⊳
∅ ∖ ∁ ↦ ↣ ∩ ∪ ⊆ ⊂ ⊄ ⊊ ⊇ ⊃ ⊅ ⊋ ⊖ ∈ ∉ ∋ ∌ ℕ ℤ ℚ ℝ ℂ ℵ ℶ ℷ ℸ 𝓟
¬ ∨ ∧ ⊕ → ← ⇒ ⇐ ⇔ ∀ ∃ ∄ ∴ ∵ ⊤ ⊥ ⊢ ⊨ ⫤ ⊣ … ⋯ ⋮ ⋰ ⋱
∫ ∬ ∭ ∮ ∯ ∰ ∇ ∆ δ ∂ ℱ ℒ ℓ
𝛢𝛼 𝛣𝛽 𝛤𝛾 𝛥𝛿 𝛦𝜀𝜖 𝛧𝜁 𝛨𝜂 𝛩𝜃𝜗 𝛪𝜄 𝛫𝜅 𝛬𝜆 𝛭𝜇 𝛮𝜈 𝛯𝜉 𝛰𝜊 𝛱𝜋 𝛲𝜌 𝛴𝜎𝜍 𝛵𝜏 𝛶𝜐 𝛷𝜙𝜑 𝛸𝜒 𝛹𝜓 𝛺𝜔