MS does have a driver for the card, it installed by default on my rampage 5
extreme - didn't have to do a thing.. that also doesn't explain the lack of
PXE boot message and I have all the bios options for startup messages set
to UEFI an legacy reports.
Both these machines are basically identical barring a few things.
The R5E10 is running
a samsung 1TB PCIx4 SSD vs a WD 512GB PCIx4 SSD on the X399
an Intel 6900K vs AMD TR 1900x
the 6900x is running a few Sata II drives as well
Broadcom wireless Vs ASUS Intel wireless.
Barring odds and sods for differences in USB ports etc both machines are
Gigabyte Aorus 1080 Ti's
Avago ( broadcom ) 9361 Raid Controller running 8 HGST 4Tb drives with
cachevault and supercap.
32 Gb 3000Mhz Corsair DDR4 4 Sticks at 8 Gig same model
Silverstone Strider ST1500 1500W power supplies
Windows 10 64 Bit pro.
Everything just works with no intervention on the R5E10 but seems to fail
on the X399
Either your motherboard (X399a) is defective or it doesn't support the cards or there is a conflict with another component installed on your motherboard.
If your motherboard doesn't detect the cards, no drivers will be able to install since they don't see a compatible component installed.
falloutboy, I am very lost here, so my questions may be redundant. What OS are you running (if Windows, command prompt - winver) and post the screenshot here. Where did it come from? If it is not a fresh install, please do one which may be a good idea anyway. Can you see the card in the UEFI? Are you running the latest UEFI for your MB? Is CSM enabled? Can you see the card in the Device Manager and if so does it have a yellow bang? This is all weird. Thanks and enjoy, John.
Windows 10 Professional Version 1803 Build 17134.81, it is a fresh install.
Where did it come from?? Microsoft. For reference the card is also not
shown under Ubuntu on my X399 but is shown on my R5E10. When the machine
boots and I go into bios there is no UEFI entry for the card, nor do I get
any PXE boot messages which I do on the R5E10. I have tried both with and
without CSM and Fastboot. The card showed in device manager the very first
time it was put in with a code 43 and then was never shown again after the
driver was deleted and the system rebooted to allow it to detect it again.
The card does not show up at all under windows 10 now and will not show at
all under Ubuntu on the X399.
It is very odd, either card in the R5E10 just works without me doing
anything but place them in the X399 - Zip, Nothing Nada.
Thanks, falloutboy. You have shown remarkable patience with me. What OS is running in the R5E10? Have you tried one Mellenox card in the PCIex16_4 slot with the slot set to X8 in the UEFI? If not, please do. Is the connector on the Mellenox card a physical x8 size? I assume you have done multiple Clear CMOS operations? If not, please do, and always after changing HW (cards, etc). I would like to see a complete list of your HW. Here is mine, if you are curious:
ASRock Fatal1ty X399 Pro Gaming, Threadripper 1950X, 2xSamsung SSD 960 EVO RAID, 1TB & 500GB WD Black, G.SKILL [Flare X (for AMD)] F4-3200C14Q-32GFX, Windows 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.0
Do you have a Support Ticket open with your MB vendor? Thanks and enjoy, John.
EDIT: I tried code tags around my HW but they did not work. Anyone help me here?
Windows 10 Professional 64 bit same rev and build - yes have tried that on
the X399 - no change, physically the card has an x8 connector. Yup have
done cmos resets, even went as far as battery removal. Yes I just sent asus
all the specs this morning and told them not to come back until it's fixed.
Those Asus 10GBASE-T cards usually work fine, I have a few of them on more mundane rigs and they work with a Cisco box I use.
If you LAN is sick this telling me your windows setup is mangled so use reset windows and see if that works with the gear you have
I use 1803 with clean installs and it works fine
The funny thing is though if I use the internal 1gb nics built into the
motherboards they work fine too... I would argue that that it's not
installed os or installation and I have done a full network reset on both.
There is some sort of board/bios/Chipset issue here
I've thought about this issue very logically.
It's not the OS, I have created identical Bootable Ubuntu USB keys for my
two systems and get the same results I get from Windows 10 ( can't blame
Microsoft this time ).
If I boot up on the X399 using Ubuntu the Mellenox card is not seen and
there is nothing mentioning it the startup logs - so it's not a windows
If I boot up on the R5E10 using Ubuntu and have either of the two Mellenox
cards in that PC they show up under Ubuntu and the logs are full of
information about the configuration.
I can boot off either key on either machine and get the same result, the
R5E10 sees the card no mater which card or key I use, the X399 does not.
I also note that the R5E10 brings up PXE boot messages from the card - and
the X399 does not do this so this is either an:
X399 chipset issue
A BIOS issue
faulty motherboard ( I'm steered away from faulty motherboard simply by the
fact that I can put my 9361 Raid controller or a wireless network card in
any slot in any combination and they work, this points more toward Bios or
Thanks for trying though but installing Windows 10 on a separate drive I
think you'll agree logically would be a waste of time.
On Sat, Jun 9, 2018 at 2:45 AM, hardcoregames™ <email@example.com>