Dear Qubes community,

Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
wifi) by setting PCI permissive mode? (as described in:)

https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues

I successfully used this in Qubes R3.2 to get wifi working for dell xps
13 9350 (bcm4350) but am having no luck using this method in R4.0_rc3.

This situation seems identical (driver errors that persist but
nonetheless wifi works using permissive mode) resolved by in a previous
(R3.2) qubes-users thread by miaoski --
https://groups.google.com/forum/#!msg/qubes-users/m4GzpfOVBiQ/bf5XCEc-DQAJ

I'm hesitant to give up and go back to R3.2 on this machine, so I don't
have access to the R3.2 dom0 dmesg output for PCI spermissive mode, but
I recall before setting permissive mode dmesg suggested doing so.  This
is not the case in R4.0_rc3 however.

Some dmesg output, if this gives anyone any ideas:

[dom0 ~] lspci | grep -i network
3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
Network Adapter (rev 08)

Before setting permissive mode:
[dom0 ~]$ sudo dmesg | grep
[    7.222306] pci 0000:3a:00.0: [14e4:43a3] type 00 class 0x028000
[    7.222348] pci 0000:3a:00.0: reg 0x10: [mem 0xdc400000-0xdc407fff 64bit]
[    7.222379] pci 0000:3a:00.0: reg 0x18: [mem 0xdc000000-0xdc3fffff 64bit]
[    7.222618] pci 0000:3a:00.0: supports D1 D2
[    7.222619] pci 0000:3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    7.222766] pci 0000:3a:00.0: System wakeup disabled by ACPI
[    8.053279] pciback 0000:3a:00.0: seizing device
[   68.211970] xen_pciback: vpci: 0000:3a:00.0: assign to virtual slot 0
[   68.212362] pciback 0000:3a:00.0: registering for 4
[   68.217475] pciback 0000:3a:00.0: enabling device (0000 -> 0002)

After setting permissive mode (and rebooting):
[dom0 ~]$ sudo dmesg | grep 3a:00
[    7.256107] pci 0000:3a:00.0: [14e4:43a3] type 00 class 0x028000
[    7.256150] pci 0000:3a:00.0: reg 0x10: [mem 0xdc400000-0xdc407fff 64bit]
[    7.256181] pci 0000:3a:00.0: reg 0x18: [mem 0xdc000000-0xdc3fffff 64bit]
[    7.256419] pci 0000:3a:00.0: supports D1 D2
[    7.256421] pci 0000:3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    7.256568] pci 0000:3a:00.0: System wakeup disabled by ACPI
[    8.099473] pciback 0000:3a:00.0: seizing device
[   57.896166] pciback 0000:3a:00.0: enabling permissive mode
configuration space accesses!
[   57.896168] pciback 0000:3a:00.0: permissive mode is potentially unsafe!
[   72.466856] xen_pciback: vpci: 0000:3a:00.0: assign to virtual slot 0
[   72.467231] pciback 0000:3a:00.0: registering for 2
[   72.472685] pciback 0000:3a:00.0: enabling device (0000 -> 0002)

could it be anything to do with assign to virtual slot 0, or qvm-pci?

Many thanks for anyone's input,

-m0ssy

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8eebd8f1-4f78-b069-3354-9b6e22ebd752%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to