On Thursday, March 8, 2018 at 11:17:14 AM UTC+1, awokd wrote: > On Thu, March 8, 2018 9:02 am, Yuraeitha wrote: > > On Thursday, March 8, 2018 at 9:25:12 AM UTC+1, sevas wrote: > > >> 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 > > >> > >> Question 1: Should I fix my wireless card with a car or a hammer? > > Go ahead and try the no-strict-reset option. > > >> 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!) > > Try looking through the HCL for known good ones, or picking one and > searching the mailing list for reported problems. There's no HCL for PCI > devices, but I'm wondering if it might be good to have one. > > >> Question 3: What kind of security am I forfeiting when I use this > >> frothy no-strict-reset card? > > See the link in the same doc. > > >> Question 4: Is there anything I can do for my card? Heres the error > >> output: > > #1 > > > I think what you need to do here is merge the sys-net with your sys-usb. > > That might also resolve the issue if both controllers are reported as > being under the same device, but in this case I think trying > no-strict-reset first is probably worthwhile.
@awokd Agreed, it's not clear what is causing the issue, trying these suggestions definitely could work too. @sevas I definitely agree with awokd that you can put the no pci reset, he makes a good point here. If you came from a more unsecure OS anyway before you went Qubes, and you're not putting your life or well-being on the line, then you can probably take bit bigger risks like this one. The exploits through firmware is more exotic attacks in this day and age, but that might change in the future if they become more commonplace, i.e. by A.I's automatically finding exploits in the many, many different firmwares, and turns this from an exotic attack into a common and everyday type of attack. Generally though, if you're not putting something on the line here, you can afford to make mistakes and learn a bit, mistakes are the best learners after all, just as long as you can afford the consequences of course. Just keep in mind that it's important that you improve these things over time and never just settle, small stepes, rom wasn't build in a single day, so too is your Qubes usage going to improve over time as well if you keep learning small bits every day. Lax a bit down now on these issues, and try find out why and how they work, so you can increase your knowledge of security. Try identify the biggest threats first, and keep the lower ones for later, prioritizing to maximize your IT security understanding as time goes on. -- 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/2a746980-fce6-41e5-948d-a6dd90df00f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
