On Thursday, March 8, 2018 at 9:25:12 AM UTC+1, sevas wrote: > Been looking through the files and google trying to find out how to make my > USB wireless card work. I didnt try no-strict-reset or permissive mode > because it said something something SECURITY something and so I skipped over > it without a second thought. > > After hours and hours of troubleshooting, I realize that that was my problem. > I needed no-strict-reset because of FLR. I have no idea what FLR is. > > Bus 001 Device 006: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 > Wireless Adapter > > I guess thats my card. One of those RT numbers. > > Anyway. I have a few questions. > > Question 1: Should I fix my wireless card with a car or a hammer? > > Question 2: What kind of wireless card should I buy or what should I be on > the lookout for to make sure its compatible with qubes? (long range for bonus > pts!) > > Question 3: What kind of security am I forfeiting when I use this frothy > no-strict-reset card? > > Question 4: Is there anything I can do for my card? Heres the error output: > > I think one of these 1st two sections is the output when the VM is already > started and I attach the device and the other is when I start it with the > device already attached. Or maybe not. It could the the before and after of > dom0$ qvm-prefs -s netvm kernelopts "iommu=soft swiotlb=16384" Who knows.... > Not me, I mean. > > dom0 lvm[923]: Monitoring thin pool qubes_dom0-pool00-tpool. > dom0 qubesd[9781]: b' WARNING: Sum of all thin volume sizes (328.68 GiB) > exceeds the size of thin pool qubes_dom0/pool00 and the size of whole volume > group (166.68 GiB)!\n' > dom0 dmeventd[923]: No longer monitoring thin pool qubes_dom0-pool00-tpool. > dom0 lvm[923]: Monitoring thin pool qubes_dom0-pool00-tpool. > dom0 qubesd[9781]: b' WARNING: Sum of all thin volume sizes (338.68 GiB) > exceeds the size of thin pool qubes_dom0/pool00 and the size of whole volume > group (166.68 GiB)!\n' > dom0 libvirtd[9825]: 2018-03-08 05:27:18.209+0000: 9861: error : > virPCIDeviceReset:1002 : internal error: Unable to reset PCI device > 0000:00:14.0: no FLR, PM reset or bus reset available > dom0 qubesd[9781]: Start failed: internal error: Unable to reset PCI device > 0000:00:14.0: no FLR, PM reset or bus reset available > dom0 dmeventd[923]: No longer monitoring thin pool qubes_dom0-pool00-tpool. > > dom0 lvm[923]: Monitoring thin pool qubes_dom0-pool00-tpool. > dom0 qubesd[9781]: b' WARNING: Sum of all thin volume sizes (328.68 GiB) > exceeds the size of thin pool qubes_dom0/pool00 and the size of whole volume > group (166.68 GiB)!\n' > dom0 dmeventd[923]: No longer monitoring thin pool qubes_dom0-pool00-tpool. > dom0 lvm[923]: Monitoring thin pool qubes_dom0-pool00-tpool. > dom0 qubesd[9781]: b' WARNING: Sum of all thin volume sizes (338.68 GiB) > exceeds the size of thin pool qubes_dom0/pool00 and the size of whole volume > group (166.68 GiB)!\n' > dom0 libvirtd[9825]: 2018-03-08 05:27:18.209+0000: 9861: error : > virPCIDeviceReset:1002 : internal error: Unable to reset PCI device > 0000:00:14.0: no FLR, PM reset or bus reset available > dom0 qubesd[9781]: Start failed: internal error: Unable to reset PCI device > 0000:00:14.0: no FLR, PM reset or bus reset available > dom0 dmeventd[923]: No longer monitoring thin pool qubes_dom0-pool00-tpool. > > > This was definitely during attach while VM running: > ERROR: Devices tab: Got empty response from qubesd. see journalctl in dom0 > for details. > followed by: > dmesg: > [ 122.885838] xhci_hcd 0000:00:14.0: USB bus 2 deregistered > [ 122.889909] xhci_hcd 0000:00:14.0: remove, state 1 > [ 122.889917] usb usb1: USB disconnect, device number 1 > [ 122.889918] usb 1-5: USB disconnect, device number 2 > [ 122.982262] usb 1-6: USB disconnect, device number 3 > [ 122.982600] usb 1-7: USB disconnect, device number 4 > [ 122.984305] xhci_hcd 0000:00:14.0: USB bus 1 deregistered > [ 122.984842] kauditd_printk_skb: 5 callbacks suppressed > [ 122.984843] audit: type=1130 audit(1520492985.409:136): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 122.989660] pciback 0000:00:14.0: seizing device
Definitely never try get usb-modems working if your USB controller is still in dom0 though, if you get that working, then you're exposing all of dom0 to the internet directly. -- 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/bf63c398-ec59-4692-9d96-c45606390bd4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
