Mine is essentially "in the mail" (see above) This is the only one from newegg $650 or lessCounter offer: get the 8 RAM slot one from Newegg. Boot your Turin. Rejoice.
Move the CPU to 12 slot one when it arrives. Find a decent cheaper Turin for me within my price range. I'll pay you $650 for the mobo minimum. Rest we can see.
So?
I was only offering to buy it from you in case it helped us see your Turin come to life earlier.Please advise
I suppose you have worked this out in the mean time...Question though, I think you have the same motherboard as me, the supermicro. I can't figure out how to get it to boot from the sata hard disk. I get the boot order to UEFI hard disk, and the option for disks to use legacy and (the other choice) and it sees the drive, but keeps wanting to boot from something else, some network drive,
If the disk is brand new, it should work either way, or at least from a USB windows install disk. The fix is simple. A brand new NVME drive. But that seems silly.I suppose you have worked this out in the mean time...
I never tried booting from SATA myself — not Genoa/H13SSL-N, and I think not even Rome/H11DSi. Obviously, the first item to set suitably is the Boot Mode right at the top of the Boot tab of the BIOS — UEFI boot mode needs to be set for GPT formatted disks, and Legacy boot mode for MBR formatted disks. Then, the Boot Option #1(and #2…#9 if desired) need to be set to either UEFI Hard Disk or, I don't know, Legacy Hard Disk?
It does not work for Turin. I loaded the most recent bios (1.9 at the time) and it would not even start up the fans ANY fans.Why not just use the h13ssl rev 1.01?
It should work with BIOS 3. Turin patch is not present in BIOS 1.9It does not work for Turin. I loaded the most recent bios (1.9 at the time) and it would not even start up the fans ANY fans.
right. But supermicro says that it ALSO requires version 2.0 of the motherboard.It should work with BIOS 3. Turin patch is not present in BIOS 1.9
check the Turin build thread in CPUs, motherboard, case and second cpu all but guaranteed to be here tomorrow !! Probably be up thursday to compete in PG. This should be interesting.Well, my second Turin CPU is supposed to be delivered Tuesday, and the motherboard is supposed to be shipped tomorrow. And I had to get a new case. shipping tomorrow.
Stay tuned.
In PrimeGrid, I am playing it safe on my own dual socket AMD Zen systems and run two BOINC instances: One tied to all logical CPUs of socket 0, the other tied to all logical CPUs of socket 1. The PrimeGrid tasks which are launched by these instances inherit this affinity. All memory which they allocate, they therefore allocate locally at their home socket.Probably be up thursday to compete in PG.
I use lasso, and with windows it appears to work fine on dual 64 cores boxes with lasso. I tried the duzal Milan, and while slow, it appeared to work. Obviously I will let you and everyone know.PS,
my dual-socket precautions may be overcautious. After all, once a PrimeGrid task is lasso'd to a CCX, all the really intense data accesses happen in cache. But as I said, I haven't done proper experiments to find out the actual impact of cross-socket transitions of tasks.
But version 1.01 works. Here is another data point: https://openbenchmarking.org/result/2411165-NE-EPYCTURIN10right. But supermicro says that it ALSO requires version 2.0 of the motherboard.
One BIG difference. That is a retail, I have ES chips.But version 1.01 works. Here is another data point: https://openbenchmarking.org/result/2411165-NE-EPYCTURIN10