Thanks, falloutboy. I agree with you - this is not an OS issue. This is a board/UEFI issue. If your UEFI does not see the Mellenox card, you are dead meat, no matter the OS. I looked at Newegg and Mellenox products are expensive except for a few from $20 - 50$. Please take a look and see if any of the cheap ones would have a chance to duplicate your problem. We could both purchase one each and compare results. Thanks and enjoy, John.
Amazon sells them cheaper I got mine here in nz for 70nzd each but the
answer I feel is not to throw money at more nics when the ones ive got are
obviously fine, it's for the chipset/bios issue to be sorted.
OK, falloutboy. I will give up on that path. It looks like US Amazon has two cards for 41USD. Please post your equivalent screenshot:
Requires CPU-Z 1.85 or above. Thanks and enjoy, John.
Thanks, falloutboy. WOW, that AGESA is way down level! Are you sure you are running the latest UEFI? Please look and point me to what you are running. As you probably know AGESA comes from AMD and we all should be running close to the same version. ASRock has released a Beta UEFI with AGESA 220.127.116.11 (AGESA!V9.ThreadRipperPI-SP3r2-18.104.22.168) and you have 0.0.6.0 - sounds like an initial release. This is a good candidate for your problem. Let me hear. Thanks and enjoy, John.
EDIT: Please look on your R5E10 and see what is there.
EDIT AGAIN: I think this is it. On the ASUS BIOS page version 0601 talks about AGESA 22.214.171.124 but contains 0.0.6.0. BTW your board is an Extreme not Rampage.
EDIT#3: All the old UEFI files also show the AGESA as 0.0.6.0, I talked to ASUS and they said they would look into it, but you could flash 0503. You will need to use the FlaskBack (ASRock name) but it is a special USB socket on the back.
Latest version of the BIOS as per whats available on the ASUS website.
AGESA 126.96.36.199 ; however my understanding is that AGESA only deals with
of the processor cores, memory, and the HyperTransport controller - I have
not seen any reference to AGESA dealing with PCIe initialization but am
continuing to look.
Well it does look like it has something to do with PCI in the early stages
here is hoping that applying the squeeky wheel gets the grease treatment to
ASUS gets it sorted, I.E contacting them every 5 mins until its fixed.
falloutboy, I agree with elstaci - please give ASUS holy dickens! Even if the AGESA version number just failed to get updated, this is an egregious error! It shows extreme lack of attention to detail. If anything needs careful attention it is the UEFI. I hope I have not over hyped this, but it needs to be corrected and the underlying sloth needs to be corrected. Running unknown code is unacceptable. Have you considered going back to 0503? Good hunting and enjoy, John.
I don't think it would help, I was running 0503 when I ran up their own
XGC-100Cs and while they detected they simply wouldn't work.