But Windows does work, and Linux should, too. It looks like there's plenty of available space for 00:1f.5 BAR 0. Can you try a current version of Linux, e.g., v5.8-rc1 with the command line argument 'dyndbg="file drivers/pci/* +p"'? There were some significant resource assignment changes in v5.5.
AIDA64 (https://www.aida64.com/) has a free trial version that should show the PCI address map under Windows. I assume it probably moved 00:1f.5 BAR 0 to somewhere inside the PCI host bridge window.
It looks like a BIOS bug to me.
But Windows does work, and Linux should, too. It looks like there's plenty of available space for 00:1f.5 BAR 0. Can you try a current version of Linux, e.g., v5.8-rc1 with the command line argument 'dyndbg="file drivers/pci/* +p"'? There were some significant resource assignment changes in v5.5.
AIDA64 (https:/ /www.aida64. com/) has a free trial version that should show the PCI address map under Windows. I assume it probably moved 00:1f.5 BAR 0 to somewhere inside the PCI host bridge window.