For Wifi, in sys-net keep 02:00.0, but remove (03:00.0 and) 03:00.1. If you need Ethernet, good luck. I have been unable to get the Realtek Ethernet devices to function reliably -- barely at all -- on my Lemur, but Wifi works great.
For the error that you're getting, you need to add 03:00.0 to sys-net. However, even with that change, I was only sometimes able to get Ethernet connectivity. Similar: https://groups.google.com/forum/#!topic/qubes-users/Fs94QAc3vQI https://github.com/QubesOS/qubes-issues/issues/1393 I played around with permissive settings but ultimately it is unneeded for Wifi and did not seem to impact the reliability of the Ethernet. My experience: Sometimes Ethernet would work only to not work upon reboot, regardless of the kernel version or configurations I attempted; although, my Linux troubleshooting skills are minimal so maybe I missed something in the kernel/xen and other logs. Yet, it seemed strange that it would work during one session but not after a VM and/or system reboot. Something about the 03:00.0/1 device does not play well with Xen/Qubes. So, unless you really need Ethernet, I recommend only connecting your Wifi device to sys-net. The 8260 works great when on its own. On Monday, January 2, 2017 at 10:27:27 PM UTC-8, pixel fairy wrote: > used a working desktop to install and update to qubes-unstable. this time the > lemur was able to boot, but sys-net could not run. heres an hcl-report > followed by a typescript session showing pci devices and the error. adding > pci devices to sys-net in the qubes-manager gave the same result. > > --- > layout: > 'hcl' > type: > 'notebook' > hvm: > 'yes' > iommu: > 'yes' > slat: > 'yes' > tpm: > 'unknown' > brand: | > System76, Inc > model: | > Lemur > bios: | > 5.12 > cpu: | > Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz > cpu-short: | > FIXME > chipset: | > Intel Corporation Device [8086:5904] (rev 02) > chipset-short: | > FIXME > gpu: | > Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) > gpu-short: | > FIXME > network: | > Intel Corporation Wireless 8260 (rev 3a) > Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit > Ethernet Controller (rev 12) > memory: | > 32655 > scsi: | > Samsung SSD 850 Rev: 1B6Q > CT750MX300SSD1 Rev: 0100 > > versions: > > - works: > 'FIXME:yes|no|partial' > qubes: | > R3.2 > xen: | > 4.6.3 > kernel: | > 4.8.12-12 > remark: | > FIXME > credit: | > FIXAUTHOR > link: | > FIXLINK > > --- > > Script started on Mon 02 Jan 2017 09:33:34 PM PST > ]0;user@dom0:~ [user@dom0 ~]$ lspci > 00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02) > 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) > 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model > 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI > Controller (rev 21) > 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP > Thermal subsystem (rev 21) > 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME > HECI #1 (rev 21) > 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller > [AHCI mode] (rev 21) > 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) > 00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1) > 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port > #6 (rev f1) > 00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21) > 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) > 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) > 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) > 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) > 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI > Express Card Reader (rev 01) > 03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) > ]0;user@dom0:~ [user@dom0 ~]$ qvm-start sys-net > --> Creating volatile image: /var/lib/qubes/servicevms/sys-net/volatile.img... > --> Loading the VM (type = NetVM)... > Traceback (most recent call last): > File "/usr/bin/qvm-start", line 136, in <module> > main() > File "/usr/bin/qvm-start", line 120, in main > xid = vm.start(verbose=options.verbose, > preparing_dvm=options.preparing_dvm, start_guid=not options.noguid, > notify_function=tray_notify_generic if options.tray else None) > File "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py", > line 122, in start > xid=super(QubesNetVm, self).start(**kwargs) > File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line > 1966, in start > self.libvirt_domain.createWithFlags(libvirt.VIR_DOMAIN_START_PAUSED) > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1059, in > createWithFlags > if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', > dom=self) > libvirt.libvirtError: internal error: Unable to reset PCI device > 0000:03:00.1: internal error: Active 0000:03:00.0 devices on bus with > 0000:03:00.1, not doing bus reset > ]0;user@dom0:~ [user@dom0 ~]$ ip a > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > ]0;user@dom0:~ [user@dom0 ~]$ ip l > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode > DEFAULT group default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > ]0;user@dom0:~ [user@dom0 ~]$ exit > exit > > Script done on Mon 02 Jan 2017 09:34:09 PM PST -- 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/b8351064-5f00-45e2-9814-d8c8fb30ee5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.