[qubes-users] Re: How to attach a Yubikey as a normal, extra usb keyboard only to specific AppVMs?
I was able to get my yubikey to work in this personal vm but for the life of me I wasn't able to use it to authenticate with my gmail on this login. I followed the instruction where you add the info to the qubes.InputKeyboard file then it worked. You'll know you've configured that file correctly if you get the popup. I'm still not able to get my smart card reader to work even though I think i've followed all the instructions. I'm gonna use all these same tricks and see if I can get it to work in the Win7 HVM...FML B4U2D0 -- 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/68ff7e9e-7bf1-454c-8c33-7a026e529e34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Wifi Issues Atheros QCA9377
OMG I got it... The issue is that the Kernel Module wasn't loading during boot, thats why I wasn't seeing any error messages or anything in the dmesg output. What led me down the road to my answer was the fact that when I ran the lspci -k command the "Kernel module in use:" line was missing. I noticed that is was a potential issue in my original post but I didn't know how to go about fixing it... After trying I found out that the "ath10k_core" was being loaded at startup but not the "ath10k_pci" Kernel Module. In an attempt to load that module I noticed that the /usr/lib/modules/`uname -r`/modules.networking file was absent "ath10k_pci". I decided to modify the file located at /etc/sysconfig/modules/qubes-u2mfn.modules and add the line "modprobe ath10k_pci.ko" and BAM BANG POW after a reboot the wifi starts working!!! Well... I can at least see the wifi networks now but I'm sure they work... -- 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/e96547da-4d54-4289-bf02-3b8da54956a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Wifi Issues Atheros QCA9377
It is Qubes 3.2. Kernel is 4.4.31-11.pvops.qubes.x86_64. I've been to that link before but I haven't tried any of the steps to dom0 so im going to give it a try now qubes-hcl-report on dom0 shows my wireless adapter under the Net: listing. I'm sure it's supposed to work just wondering what it is that I'm missing...gotta be something easy I just suck... Dmesg on dom0 shows this... [85068.905503] audit: type=1123 audit(1483579070.490:139): pid=10524 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D6620514341393958302F terminal=pts/4 res=success' [85076.346626] audit: type=1123 audit(1483579077.917:144): pid=10528 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D6620514341393938342F terminal=pts/4 res=success' [85082.446595] audit: type=1123 audit(1483579084.006:149): pid=10537 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D6620514341393938582F terminal=pts/4 res=success' [85094.044343] audit: type=1123 audit(1483579095.580:154): pid=10539 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D662051434139383838 terminal=pts/4 res=success' [85110.305439] audit: type=1123 audit(1483579111.810:159): pid=10542 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D662051434139383858 terminal=pts/4 res=success' [85114.181940] audit: type=1123 audit(1483579115.678:164): pid=10544 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D662051434139383837 terminal=pts/4 res=success' [85122.442339] audit: type=1123 audit(1483579123.923:169): pid=10546 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D662051434136313734 terminal=pts/4 res=success' [85128.582364] audit: type=1123 audit(1483579130.051:174): pid=10548 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k" cmd=726D202D72202D662051434134303139 terminal=pts/4 res=success' [85459.730731] audit: type=1123 audit(1483579460.551:179): pid=10593 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k/QCA9377/hw1.0" cmd="dmidecode" terminal=pts/4 res=success' [86069.245761] audit: type=1123 audit(1483580068.874:184): pid=10759 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k/QCA9377/hw1.0" cmd="dmesg" terminal=pts/4 res=success' [86091.606143] audit: type=1123 audit(1483580091.191:189): pid=10764 uid=1000 auid=1000 ses=1 msg='cwd="/usr/lib/firmware/ath10k/QCA9377/hw1.0" cmd="dmesg" terminal=pts/4 res=success' Still troubleshooting. -- 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/ad0c53cd-5ff5-4c06-8acf-2ccb2dd9be27%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to attach a Yubikey as a normal, extra usb keyboard only to specific AppVMs?
Good Luck @LeeteqXV I haven't yet tried to get my yubikey to work but that is on my to-do list. I hope you are able to deduce the problem and get it working. Still troubleshooting my wifi problems. Ugh...fml -- 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/bd1e090b-c892-4717-8057-59032b5ecc37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Glitch: sys-net and sys-firewall start without "Start VM automatically on boot" setting enabled
@marc You are right, unchecking the box "should" make them not startup. I'm sure you've already figured it out but for anyone else that finds this page I'll post the answer. Go to /etc/systemd/system/ and comment out the line in "qubes_netvm.service" that tells the default netvm to start. Bam... This must be done for me because everytime I restart the box I have no connection in sysnet which requires me to do various steps in order to have sysnet actually connect to the internet...very annoying. Searched for that fix but haven't figured it out yet. B4U2DO -- 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/4e44-4551-4518-a22d-8784fdcc2fff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
