Search results

Linux (Ubuntu) with kvm/qemu. So Proxmox should be okay as it's just Debian based thing.

https://www.aliexpress.com/item/1005005588272165.html worked just fine on Linux w/ vfio/kvm/qemu for me. 4 x Renesas USB3.0, 4 ports in the back and 2 headers with 2 ports internally. Bridge chip is made by Asmedia.

BMC information generally won't update until there's successful boot. I'd try different RAM if possible.

Did the board work just fine before the BIOS flash? I got that too, but I got it resolved by using different RAM. Kingston Fury didn't work, but regular ValueRAM did.

Do you have one of those flimsy M.2 SATA cards without metallic bracing? You might've just cracked the PCB because they're super thin and fragile. If you look at Silverstone ECS07 you can tell that it's much more robust adapter and get something like that from Ali's mysterious hardware emporium.

For open ended / more than 8x or higher slot they'd be required to run traces for 75W of power instead of 25W by the spec, which 1) costs money b) costs money

I've never had this work on 2 different sets of Supermicro boards. Inventory never updates, but system runs fine so I'm not bothered about it. I'm sure there has to be some BIOS or IPMI option that's just blocking it.

For mac stuff just get 2nd hand M1 Mac mini. It's so much easier than dealing with the janky hackintosh stuff.

Another recommendation for M393A8G40AB2-CWE

If you use Linux you can just unbind the driver, raise up the BAR and it should be enabled; here's how my system does it with NVIDIA card on VM (/etc/libvirt/hooks/qemu.d/virt-instance/prepare/begin/bar.sh): echo 0000:01:00.0 > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind echo 0000:01:00.1...

Even if you disable the JMB585 in the BIOS and enable C-states, they're bugged and won't function. I got freezes after few days of uptime constantly. Disabling the higher C-states made it solid, but at the cost of power consumption.

Have you tried mixing 2 of the old and 2 of the new? Maybe it's some weird memory controller limitation re LRDIMMs

Looking at the part-# those look like to be LRDIMMs. I'll check what my RAM was, but the numbers look same-ish and I couldn't get them to work either on my Epyc system. E: mine were M386A4K40BB0, so 2400T speed and wouldn't boot with them. E2: yeah disregard my post anyway, just stupid rambling.

Do you have 1044 days of uptime? AMD's EPYC Rome Chips Crash After 1,044 Days of Uptime. E: nvm read wrong :D

Yeah I bought local retail board because they were getting close in price, at the moment they're actually cheapr. 550 euro for fully warrantied and European consumer protected item vs. something the SM support will not help due to dubious origins is not that deal atm.

Got tall bracket in the mail (twice expensive eBay one) and did upgrade to SM firmware and seems solid enough now. FW: https://kikkel.it/aoc-stg-i4s-fw-v9.00.zip

Got the firmware files from SM support so I should be good to go as soon as I find some spare time, thanks for the heads up.

Got one last weekend installed for a while but got tons of connectivity issues, rolled back to working Mellanox card, due to time pressure have had to shelf the card for now and will investigate later. E: card came with this FW: Num Description Ver.(hex) DevId S:B...

Seeing you're in Euros you could take a look at https://forums.servethehome.com/index.php?threads/eur-40-super-micro-4-port-10gbe-sfp-nic.43340/

With deeper C-states than 3 and JMB585 disabled?