This appears to be a hardware issue rather than a software bug.
This appears to be a hardware issue rather than a software bug.
Hello everyone, I'm reaching out for advice and ideas. Right now I have an MSI B-450 A motherboard. The newest AMD chipset drivers are installed, along with the latest UEFI version. Windows 10 1909 is currently running. I plan to update soon to fix this problem. On the board, PCI-e slots contain: an NVMe drive, a GTX 1070, and a newly added Cisco VIC 1225 Fiber Channel card. The latter works fine in my R2 server as well. The newest drives come from Cisco (version 4.2). The card operates correctly when I adjust PCIe settings in UEFI, but changing the lane size to 4x4x4x4 and then booting into Windows 10 causes driver errors—no card appears in Device Manager. I've experimented with various settings without success. I also found a post from Cisco mentioning a bug, though I don't think it relates to my case since I'm still using the same steps. Other options I considered are updating Windows to 21H2 or rearranging the card positions. I tried modifying registry flags, but that didn't resolve the issue. The key question is what's actually causing this problem—Cisco, MSI, AMD, Windows, or something else? Thanks for any help.
The clear way is to try another slot, place the card at the bottom. Do you own an NVMe card or just an M.2 drive? If it's an M.2 in an expansion card, can you relocate it to the internal slot during testing? You should have your GPU in the top 16x slot, with expansion cards below that. I recommend skipping any changes to PCIe settings—restore the factory defaults and see if your configuration functions properly. The bifurcation exists mainly to allocate dedicated bandwidth; don’t stress over fine-tuning until it operates correctly. You might be mistaken by tweaking settings unnecessarily.
I just rearranged the cards in the slots to check for improvements. The GPU was in the lower 16x slot while the NIC was in the top one. No changes appeared in the Windows Device Manager. Everything seems to have been reset back to its default position. I don’t have a NVM expansion card, so it might be using the standard slot. I considered that recent adjustments could be causing the problem, so I reverted everything to “Auto.” Looking at the Cisco card shows a UART Port, which I’m wondering about and how it might affect things. My goal is to make this work on Windows 10, but I’ll try booting into Linux to see if it behaves differently.
I’ve moved to Windows Server 2019 and still face the same problem. On Linux, the card isn’t recognized until I adjust the UEFI settings. There’s no clear guidance on the UART port, though it functions but gives unclear output. It seems fixing it might be impossible without the right configuration.