[qubes-users] Include ath11k in kernel 5.10
So, I have a XPS13. Unfortunately it comes with an horrid killer AX500 wireless card that is moreover soldered on the motherboard, so no hope to replace it. The drivers for this wireless card should be shipped with kernel version 5.10.8. So I followed https://www.qubes-os.org/doc/managing-vm-kernel/ and gave: `sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel-latest-qubes-vm` ...Which installed kernel 5.10.8. Unfortunately, it appears that the ath11k drivers are still missing. Indeed, `modprobe ath11k_pci` says it can't find the module. At the moment, `lspci` in `sys-net` detect my wireless card as `Unassigned class [ff00]: Qualcomm Device 1101` I've spent the whole day trying to understand what to do with scarce success, and nearly all solutions involve kernel recompilation. I've never attempted that, so any help, or equivalently an idiot-proof guide about how to proceed would be super appreciated. :) Fab -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e63b6b82-f34a-4fe1-b122-d862ceabf8f5n%40googlegroups.com.
[qubes-users] kernel version mismatches
Kernel version numbers seem off, way off in some VMs and templates. Mainly, that /boot/initramfs does not does not match uname -r. uname -r vs ls /boot/initramfs* vs cat /proc/version vs cat /etc/os-release OK dom0: 5.4.88-1.qubes, 5.4.88-1.qubes, 5.4.88-1.qubes, 4.0 BAD vm: 5.4.88-1.qubes, 5.10.11-100.fc32, 5.4.88-1.qubes, 32 BAD vmTemplate: 5.4.88-1.qubes, 5.10.11-100.fc32, 5.4.88-1.qubes, 32 All of these machines were restarted to rule out updates that require a reboot. p.s. I had to send this from my phone so formatting mis not what i would like. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CA%2BVdTb8fS%3Dbo5YHT72Mghf5%2Bm08Tvb6czoOd%2BTD13CEpkkt3Aw%40mail.gmail.com.
[qubes-users] HCL - HP EliteDesk 800 G2 SFF
Hello, video NVIDIA Quadro P400 working fine networking: OpenVPN working fine sleep working running Debian 10 as well only issue so far is auto updating fedora 32 but updating via Qubes Manager works Regards, Peter -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/537143518.67929275.1612300664365.JavaMail.zimbra%40telenet.be. --- layout: 'hcl' type: 'low profile desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | HP model: | HP EliteDesk 800 G2 SFF bios: | N01 Ver. 02.17 cpu: | Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz cpu-short: | i7-6700 chipset: | Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) chipset-short: | FIXME gpu: | Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) gpu-short: | NVIDIA Quadro P400 network: | Intel Corporation Ethernet Connection (2) I219-LM (rev 31) memory: | 65416 scsi: | SAMSUNG MZ7LN256 Rev: 2H0Q SAMSUNG MZ7LN256 Rev: 100Q DVDROM DU8RESH Rev: 3HS2 ASM1153E Rev: 0 usb: | 1 versions: - works: 'yes' qubes: | R4.0 xen: | 4.8.5-29.fc25 kernel: | 5.4.88-1 remark: | everything is working fine credit: | Peter De Wolf link: | FIXLINK ---
Re: [qubes-users] How to forward UPnP/1900 multicast to AppVM?
On Sun, Jan 31, 2021 at 02:25:19PM -0800, Josefa Hays wrote: > I have a service on LAN multicasting UPnP, port 1900. Other devices on > LAN discover the service without problems. My AppVM does not detect it. > > Packets from the server looks like "protocol: UDP, port: 1900, source > ip: $SERVER_LAN-IP, destination ip: 239.255.255.250" > > How do I make the UPnP multicast reach an AppVM, i.e. how do I forward > the traffic on port 1900 to the relevant VM? > > I have played around with > https://www.qubes-os.org/doc/firewall/#port-forwarding-to-a-qube-from-the-outside-world > but without success. I am not completely new to IPTABLES, but somehow I > lost a point somewhere. When should I use 239.255.255.250 as destination > in iptables commands and should I use the IP of sys-firewall/app-vm. > > (this is quite a replica of > https://groups.google.com/g/qubes-users/c/BrbVe6s0aqE/m/ZsGKsMruCAAJ > that didn't receive a follow-up answer) > > > Best regards, > Jo > It would be helpful if you were to post the commands that you used (*showing where you ran them*), and what "without success" means. I'm working blind here. I'm assuming that the netvm has an address on the 239.255.255.250 network. You don't use this as the destination address for anything. On the netvm : a rule to forward packets from $SERVER_LAN-IP, udp:1900 to sys-firewall. On sys-firewall: a rule to forward packets from $SERVER_LAN-IP, udp:1900 to the target qube. On the qube: a rule to ACCEPT INCOMING packets from $SERVER_LAN-IP, udp:1900 What template are you using for the sys-net, sys-firewall? If you provide the IP addresses for sys-net, sys-firewall and qube, I can walk you through the detail. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210202163646.GC12097%40thirdeyesecurity.org.
Re: [EXT] [qubes-users] Updating a new installation
On Mon, Feb 01, 2021 at 11:34:30PM +0100, Ulrich Windl wrote: > On 1/27/21 7:44 AM, Shawn Creighton wrote: > > What is the quickest and most secure way to update the entire system > > including Dom0 on the first boot of a new install? I've noticed that it > > takes awhile for the updates to populate to the qubes updater when first > > connected to the net even though there are obviously updates available. > > Is there a way to expedite the process? > > I think you can always run the dom0 updater to get the updates, and for the > VMs it seems that starting one reduces the time until updates for the > corresponding template are found. > Still I'd like an explicit "check for updates"... > It's also worth checking to see what templates were installed with the new install. Depending on what installer you used you may find you have outdated templates - rather than upgrading these in place it''s almost always better to install a clean new template: e.g. sudo qubes-dom0-update template-qubes-debian-10 As Ulrich says, starting a qube will (by default) check for updates and report back to the system - you may or may not want this to happen automatically - it's a service that can be disabled across the system. You need not wait for this to happen if you use the gui updater tool - just open the tool, select "Enable updates for qubes without known available updates", and go ahead. N.B Install any new templates *before* you do this. unman -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210202152644.GA11744%40thirdeyesecurity.org.
Re: [qubes-users] Problems setting /etc/hosts
> On 2 Feb 2021, at 13:03, donoban wrote: > > On 2/2/21 1:55 PM, Martin Gladdish wrote: >> >> >>> On 2 Feb 2021, at 12:48, Ludovic wrote: >>> >>> >>> Le 02/02/2021 à 12:45, mgla...@gmail.com a écrit : # several lines of comment docker --data-root /home/user/docker || true echo '1.2.3.4 my-domain.example' >> /etc/hosts echo '1.2.3.4 another-domain.example' >> /etc/hosts Yes, when I run the script myself with sudo ./rc.local then it works fine. Argh. I think I've found the issue. It's the command to start docker that's causing the rest of the file to be ignored :( > > Do you mean that it runs docker in the foreground? try: > 'docker --data-root /home/user/docker &’ > Yep, that’s the “fix” that got everything working as expected. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CFA23FD1-96C2-4843-BE2C-0FB78E26C75C%40gmail.com.
Re: [qubes-users] Problems setting /etc/hosts
On 2/2/21 1:55 PM, Martin Gladdish wrote: > > >> On 2 Feb 2021, at 12:48, Ludovic wrote: >> >> >> Le 02/02/2021 à 12:45, mgla...@gmail.com a écrit : >>> >>> >>> # several lines of comment >>> >>> docker --data-root /home/user/docker || true >>> >>> echo '1.2.3.4 my-domain.example' >> /etc/hosts >>> echo '1.2.3.4 another-domain.example' >> /etc/hosts >>> >>> Yes, when I run the script myself with sudo ./rc.local then it works fine. >>> >>> Argh. I think I've found the issue. It's the command to start docker that's >>> causing the rest of the file to be ignored :( Do you mean that it runs docker in the foreground? try: 'docker --data-root /home/user/docker &' -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/931b2223-483f-0b55-69a5-5977391242f4%40riseup.net. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] Problems setting /etc/hosts
> On 2 Feb 2021, at 12:48, Ludovic wrote: > > > Le 02/02/2021 à 12:45, mgla...@gmail.com a écrit : >> >> >> # several lines of comment >> >> docker --data-root /home/user/docker || true >> >> echo '1.2.3.4 my-domain.example' >> /etc/hosts >> echo '1.2.3.4 another-domain.example' >> /etc/hosts >> >> Yes, when I run the script myself with sudo ./rc.local then it works fine. >> >> Argh. I think I've found the issue. It's the command to start docker that's >> causing the rest of the file to be ignored :( >> > Hi, > > note that '--data-root' is an option of the *dockerd* command, not *docker*… > > Ludovic > Yes. Sorry, that was autocorrect being too aggressive. It is indeed dockerd in my file. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6D9EA18D-5728-43B5-97A5-4BD557CF907E%40gmail.com.
Re: [qubes-users] Problems setting /etc/hosts
Le 02/02/2021 à 12:45, mgla...@gmail.com a écrit : # several lines of comment docker --data-root /home/user/docker || true echo '1.2.3.4 my-domain.example' >> /etc/hosts echo '1.2.3.4 another-domain.example' >> /etc/hosts Yes, when I run the script myself with sudo ./rc.local then it works fine. Argh. I think I've found the issue. It's the command to start docker that's causing the rest of the file to be ignored :( Hi, note that '--data-root' is an option of the *dockerd* command, not *docker*... Ludovic -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bb3201f3-1c40-7976-fc34-bad57c814bf3%40zyrianes.net.
Re: [qubes-users] Problems setting /etc/hosts
On Wednesday, 20 January 2021 at 22:34:31 UTC awokd wrote: > mgla...@gmail.com: > > Hi, > > > > Hopefully I'm doing something silly here. > > > > I want to add a couple of entries into my /etc/hosts file in a specific > VM. > > The instructions here are nice and > > clear: https://www.qubes-os.org/doc/config-files/ except... that > doesn't > > work. > > > > I've added the following to my /rw/config/rc.local : > > echo '127.0.0.1 example.com' >> /etc/hosts > > And after a VM restart my /etc/hosts is unchanged. > > Might have to add "sudo" in front of that echo. Also, double-check that > rc.local is set as executable and in proper script format. Does it work > if you run it yourself from the command line? > > ... Thanks. It's literally #!/bin/sh # several lines of comment docker --data-root /home/user/docker || true echo '1.2.3.4 my-domain.example' >> /etc/hosts echo '1.2.3.4 another-domain.example' >> /etc/hosts Yes, when I run the script myself with sudo ./rc.local then it works fine. Argh. I think I've found the issue. It's the command to start docker that's causing the rest of the file to be ignored :( I had presumed it was erroring, so appending || true would get me around that. But didn't think that the dockerd command could be running in the foreground. So, not for the first time, user error instead of an issue with the setup of Qubes itself! Any ideas where I could find the output when this file is run? That may help me track down similar issues next time around. Thanks for your help. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8d1cd8b2-7b37-41db-bfda-4934f6ab8c71n%40googlegroups.com.
[qubes-users] Re: HCL - Lenovo Yoga 720-13IKB
Hello, I wanted to knife if you could make my device also compatible. Below you can find with all of my hardware info. https://jpst.it/2psKG -AP Le jeudi 12 octobre 2017 à 18:58:29 UTC, Paul Mosier a écrit : > Hello, > > I'm happy to report that Lenovo 720 will run Qubes. HCL report is > attached. > > Some notes about getting the machine running: > > * The SATA controller must be set to AHCI in the BIOS to enable legacy > boot. Qubes 3.2 comes with Xen 4.6.6, which doesn't play nice with a pure > UEFI boot. > > * Also because of the above, after install you will need to adjust the > default EFI configuration with the instructions here: > https://www.qubes-os.org/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing > > * Change dom0 to use the 4.9 kernel to get all the hotkeys & touchscreen > working. Drop the kernel & initrd files into /boot/efi/EFI/BOOT and change > the top entry of BOOTX64.cfg to use this kernel instead. > > * The kernel appears to recognize the camera & Bluetooth, but I haven't > been able to get them to work yet. Probably some configuration issue on my > part. > > * Screen rotation does not appear to work. The ideapad_laptop kernel > module raises an uncaught event when the screen is folded all the way back > (ie. for tablet mode). So there's the possibility this will work in the > future, but not right now. > > * No TPM chip for AEM. > > Everything else works great. > > - Paul M > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f047960e-ec8a-4ea9-afdb-23e56756c923n%40googlegroups.com.
