HCL -ASRock B560 Pro (NIC Intel I219-V unrecognised)
78 views
Skip to first unread message
te...@yvt.net.au
May 25, 2021, 7:00:40 AM5/25/21
to qubes...@googlegroups.com
Machine purpose built to run Qubes
ASRock-B560Pro, Intel i5-11500
500G NVMe x4, 16G RAM (might have needed more RAM)
so onboard graphics, NIC, single PS/2 port, planned to use splitter for
key/mouse, dual PS/2 only present too old tech
annoying problem with display resolution stated at 800x600, actually
appears as normal HD but top bar pushes Apply Cancel buttons off bottom
of screen in Qubes Settings, nigh impossible to click buttons while
chasing settings (took a while to realise there was buttons off-screen!)
The real problem!
No recognition of Intel i219-v NIC
Likely due to lack of recognition;
"Unable to reset PCI device... no FLR PM reset etc..." selected in the
exceptions which allowed sys-net to start
Altered sys-net from fedora-32 to debian-10 =same problem
BARE METAL
tested fedora-34 live CD on bare machine, works perfectly
likewise worked with bare metal garuda OS
but not with linuxmint 20.1 =same problem with nic
attempted via long process get files onto a VM, to install fed-34 as
HVM, which failed at 4%
gave up on installing other HVM's no exFAT support, no net to install
exFAT support
looks like a kernel problem? I don't know enough...
via usb phone tether updated entire qubes (dom0, fed32)
installed fedora-33 from repository
same problem, 20+hrs wasted, can't afford to continue flogging a dead
horse
there are no older kernels to test in a fresh install,
there appears to be one other in repository, but still recent, the NIC
is year's old apparently...
conclusion, so much for hardware requirements,
Intel integrated graphics, VT-d, even IO-SRV not that there's a graphics
card
Anyone with a single combo PS/2 port, (recent boards no longer have
dual) this board had a dual PS/2 via splitter option in UEFI,
but Qubes allowed installation of sys-usb with PS/2 keyboard only
attached, then worked with a USB mouse attached afterwards for multiple
boots.
I didn't get as far as buying a splitter cable, and there's wiring
diagrams about.
ASRock-B560Pro, Intel i5-11500
500G NVMe x4, 16G RAM (might have needed more RAM)
so onboard graphics, NIC, single PS/2 port, planned to use splitter for
key/mouse, dual PS/2 only present too old tech
annoying problem with display resolution stated at 800x600, actually
appears as normal HD but top bar pushes Apply Cancel buttons off bottom
of screen in Qubes Settings, nigh impossible to click buttons while
chasing settings (took a while to realise there was buttons off-screen!)
The real problem!
No recognition of Intel i219-v NIC
Likely due to lack of recognition;
"Unable to reset PCI device... no FLR PM reset etc..." selected in the
exceptions which allowed sys-net to start
Altered sys-net from fedora-32 to debian-10 =same problem
BARE METAL
tested fedora-34 live CD on bare machine, works perfectly
likewise worked with bare metal garuda OS
but not with linuxmint 20.1 =same problem with nic
attempted via long process get files onto a VM, to install fed-34 as
HVM, which failed at 4%
gave up on installing other HVM's no exFAT support, no net to install
exFAT support
looks like a kernel problem? I don't know enough...
via usb phone tether updated entire qubes (dom0, fed32)
installed fedora-33 from repository
same problem, 20+hrs wasted, can't afford to continue flogging a dead
horse
there are no older kernels to test in a fresh install,
there appears to be one other in repository, but still recent, the NIC
is year's old apparently...
conclusion, so much for hardware requirements,
Intel integrated graphics, VT-d, even IO-SRV not that there's a graphics
card
Anyone with a single combo PS/2 port, (recent boards no longer have
dual) this board had a dual PS/2 via splitter option in UEFI,
but Qubes allowed installation of sys-usb with PS/2 keyboard only
attached, then worked with a USB mouse attached afterwards for multiple
boots.
I didn't get as far as buying a splitter cable, and there's wiring
diagrams about.
Sven Semmler
May 25, 2021, 1:20:14 PM5/25/21
to qubes...@googlegroups.com
On 5/25/21 6:00 AM, te...@yvt.net.au wrote:
> "Unable to reset PCI device... no FLR PM reset etc..."
Have you tried https://www.qubes-os.org/doc/pci-devices/#no-strict-reset ?
> "Unable to reset PCI device... no FLR PM reset etc..."
If not, maybe I hold off adding your HCL to the next pull request until
you had a chance to try? Let me know.
/Sven
--
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6
Sven Semmler
May 25, 2021, 1:26:07 PM5/25/21
to qubes...@googlegroups.com
On 5/25/21 6:00 AM, te...@yvt.net.au wrote:
> No recognition of Intel i219-v NIC
That NIC shows up in 35 positive HCLs ... just checked.
Sven Semmler
May 27, 2021, 3:12:58 PM5/27/21
to qubes...@googlegroups.com
On 5/25/21 6:00 AM, te...@yvt.net.au wrote:
> Machine purpose built to run Qubes
> ASRock-B560Pro, Intel i5-11500
Thank you for your HCL report, which is now part of this pull request:
> ASRock-B560Pro, Intel i5-11500
https://github.com/QubesOS/qubes-hcl/pull/66
... and will be visible on the website soon!
Reply all
Reply to author
Forward
0 new messages