On 01/10/18 21:36, 'awokd' via qubes-users wrote:
Eric wrote on 10/1/18 10:29 AM:

When running Centos, does lspci -vvv give the same unusual output for that problem device? Don't know what else to suggest; I have a Realtek dual port RTL8111/8168/8411 PCI Express card in one of my systems and it works fine under Qubes 4.0.

No "lspci -vvv" outputs a complete description of both controllers as expected
and 01:00.0's first line ends with "(rev 07)" as it should.

Strange, sounds like Qubes is initializing just that one device wrong then. I had a similar issue with an old PCIe v1.1 wireless NIC. What version is your NIC? I never got mine working, but you might try adding "xen-pciback.hide=(01:00.0)" to your boot options in xen.cfg and seeing if it will let you assign it to sys-net then.

With boot option "xen-pciback.hide=(01:00.0)" (on the options= line in default config in /boot/efi/EFI/qubes/xen.cfg) everything comes up exactly the same. Getting the same error on PCI while booting and same error attempting to start sys-net with 01:00.0 attached. That option appears to be having no effect.

The hardware is new as mentioned previously - there are 3 PCI bridges (ports 3,4&5) same as:
"00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) (prog-if 00 [Normal decode])"

This is the bad lspci output for NIC 1:
"01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev ff) (prog-if ff)
    !!! Unknown header type 7f
    Kernel driver in use: pciback
    Kernel modules: r8169"

Compared to NIC 2:
"03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
    Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 16
    Region 0: I/O ports at d000 [size=256]
    Region 2: Memory at f7000000 (64-bit, non-prefetchable) [size=4K]
    Region 4: Memory at f0000000 (64-bit, prefetchable) [size=16K]"
...lots of capabilities...
   "Kernel driver in use: pciback
    Kernel modules: r8169"

Only other thing to note am getting "pcilib:sysfs_read_vpd: read failed: Input/output error" on stderr when running lspci for the above output in the good NIC capabilities section, however Centos gets two of these messages, one in the same place for each NIC so I am presuming it is not related to the problem I have with Qubes.

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/76709495-5485-dc0e-3b43-1394502d8c26%40asar.biz.
For more options, visit https://groups.google.com/d/optout.

Reply via email to