[qubes-users] HCL -
Hi I'm here to report how Qubes works on my 6-year-old laptop after 1-month of installation. In short, it can take longer time to start-up VMs (inevitable for my 8Gb RAM), but once a VM is on, softwares within it run smoothly. I once received a warning like "not enough memory to start a new VM", but that was when I had 6 other VMs running. Pre-installation check: This model has Intel VT-d available (checked on intel official specs: https://ark.intel.com/content/www/us/en/ark/products/85212/intel-core-i5-5200u-processor-3m-cache-up-to-2-70-ghz.html). But I wanted to make sure if it was on, as this aspect is not visible on the very restricted factory BIOS. I downloaded the Intel Processor Identification Utility to scan my hardware, and it appears that Intel VT-d is turned off. I could not find a way to turn this feature on without replacing my BIOS, so I figured I'd try the installation anyway. I installed Qubes-R4.0.4-x86_64 through a bootable USB made with Rufus on Windows 10. Booting with UEFI: (didn't work for me) I chose to wipe the disk and did a full install. It all went fine and it said "Installation complete". But then I was unable to boot into Qubes. My BIOS(?) thought its windows OS is corrupted and offered to reinstall/ repair windows, and both options returned error. Booting with legacy: (worked) I then force-close the laptop and try install Qubes in legacy mode, and it went smoothly. Did not meet error with Intel VT-d feature. Qubes management: I chose to install the additional Debian TemplateVM, sys-net, sys-firewall, sys-whonix. They all worked fine. I was unable to update TemplateVMs with the GUI Qubes updater, but with command prompts it worked fine. Other functionalities: 1. wifi connection: OK -a minor bug: when I wake laptop from sleep and wifi network reconnects, system message displayed "Network disconnected", even though I was connected to the wifi) - the time display wasn't accurate at first, but once I got the system on the internet it synchronised automatically 2. i-bus Pinyin input: OK (I installed on TemplateVMs, so when I turned on both fedora and debian VMs, there're two input method icons displayed) 3. fn keyboard shortcuts: OK - no problem to adjust volumn, screen brightness and logout/hibernate options with original keyboard shortcuts 4. USB ports: partial OK - USB 2.0 port, but not USB 3.0 port is usable. The USB 2.0 can be isolated in a VM and then attach to another workspace VM (e.g. personal) 5. Software installation: OK Apart from command prompts, I used Synaptic Package manager for Debian and Software Manager that comes with Fedora. Both worked fine. And yeah, that's all. I am practically a newbie in Linux and there were other bloopers when I tried install Qubes, but the detailed documentation solved most of my problems. Thanks for the teams great work! -- Sent with Tutanota, the secure & ad-free mailbox: https://tutanota.com -- 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/MYYVlb2--3-2%40tutanota.com. Qubes-HCL-Acer-Aspire_V3_371.yml Description: application/yaml
Re: [qubes-users] HCL - HP Spectre x360 15-BL152NR
Hi Ben, thank you for this HCL report. It is now part of this pull request: https://github.com/QubesOS/qubes-hcl/pull/59 ... and will be visible on the website soon! /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- 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/c2ce4d84-b1b4-86df-c904-143e3fff1097%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] HCL - Dell Precision 5520
Hi Ben, you wrote: Installed in legacy mode - will try another install at some point to see if I can get UEFI working. Thank you for your HCL report! Are you aware that there was a thread about this machine in 2019? https://groups.google.com/g/qubes-users/c/WMc88pfT-hM/m/4r7sS6d7BQAJ Yassine Ilmi reported the (almost) identical machine. They have an additional Nvidia card as well as a different network card, but the rest of the HCL is identical to yours. That's why I've added your report as an additional line to the previous one and it's now part of this pull request: https://github.com/QubesOS/qubes-hcl/pull/59 It will be visible on the website soon! /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- 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/5a98ef03-2692-840a-4cc7-96017329be07%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
[qubes-users] HCL - HP Spectre x360 15-BL152NR
Set the following kernel options on the installer usb media: Comment out noexitboot=1 and mapbs=1 (https://www.qubes-os.org/doc/uefi-troubleshooting/) Blacklisted nouveau (https://www.qubes-os.org/doc/uefi-troubleshooting/) Set i915.force_probe=* (https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.md) Works perfectly out of the box. Touchpad isn't very good on this laptop (nothing to do with qubes). It's an older synaptics unit and has weird acceleration behaviour. I tried playing around with the config but would definitely say Lenovos and Dells have much better thinkpads. I've been testing qubes on a few older workstation laptops - all have 4K screens. I haven't found dealing with that particularly difficult even with i3. Follow the instructions here off the bat: https://github.com/Qubes-Community/Contents/blob/master/docs/troubleshooting/intel-igfx-troubleshooting.md. I use an ultrawide monitor at my desk, but have the laptop display switched off when it's connected, so I don't have to deal with multiple displays at different DPIs. I just wrote a script that checks the screen resolution then rewrites the dom0 xft.resources dpi setting, passes the gsettings commands to all running vms via qvm-run and restarts lightdm, and bound it to a key in my i3 config. I then have another script that autostarts in each VM to check what the screen resolution is and sets the scaling for the VM appropriately. A little bit fiddly initially but works fine, and given I only have to use it when I'm docking or undocking the machine (which is not that often), restarting lightdm isn't a particularly big deal. I'll post my configs elsewhere, but I wouldn't let that deter you from running Qubes on a 4k laptop, it's really nowhere near as annoying as some of the threads you get from a google search suggest. -- 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/a60608b2-f0bf-fb47-df15-abfddd801916%40protonmail.com. --- layout: 'hcl' type: 'convertible' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | HP model: | HP Spectre x360 Convertible 15-bl1XX bios: | F.42 cpu: | Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Device [8086:5914] (rev 08) chipset-short: | FIXME gpu: | Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21) gpu-short: | FIXME network: | Intel Corporation Wireless 8265 / 8275 (rev 78) memory: | 16260 scsi: | usb: | 1 versions: - works: 'yes' qubes: | R4.0 xen: | 4.8.5-29.fc25 kernel: | 5.4.90-1 remark: | FIXME credit: | Ben link: | FIXLINK ---
[qubes-users] HCL - Dell Precision 5520
Set the following kernel options on the installer usb media: Comment out noexitboot=1 and mapbs=1 (https://www.qubes-os.org/doc/uefi-troubleshooting/) Blacklisted nouveau (https://www.qubes-os.org/doc/uefi-troubleshooting/) Set i915.force_probe=* (https://www.qubes-os.org/doc/uefi-troubleshooting/) Installed in legacy mode - will try another install at some point to see if I can get UEFI working. Otherwise - install is perfect. Everything works out of the box, no issues. -- 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/bcc471f9-3d43-cf3a-6046-86718bd7ec53%40protonmail.com. --- layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | Dell Inc. model: | Precision 5520 bios: | 1.22.1 cpu: | Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz cpu-short: | FIXME chipset: | Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) chipset-short: | FIXME gpu: | Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Wireless 8265 / 8275 (rev 78) memory: | 32291 scsi: | usb: | 2 versions: - works: 'FIXME:yes|no|partial' qubes: | R4.0 xen: | 4.8.5-30.fc25 kernel: | 5.4.107-1 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK ---
[qubes-users] Recover data from 'private-cow.img'
Hello everyone,
I lost a somewhat important file from a software crash in an appvm.
Within the VM, I couldn't find a way to recover it. I copied the appvm
filesystem containers ('private.img', 'private-cow.img',
'private-cow.img.old').
As I understand it, 'private-cow.img' contains the old version of files
that were changed since last appvm startup.
However, '-cow.img' files contain no filesystem, but "binary patch"
data, thus can't be mounted or read directly or without their
corresponding'.img' files.
I found only little info online. Qubes documentation [1] says about
reverting template 'root-cow.img' changes:
> 1. Ensure that no other VMs uses this template.
> 2. Prepare snapshot device with root-cow.img.old instead of root-cow.img
> (/etc/xen/scripts/block-snapshot prepare).
> 3. Replace snapshot device-mapper target with snapshot-merge, other
> parameters (chunk size etc) remains untouched. Now kernel starts merging
> changes stored in root-cow.img.old into root.img. d-m device can be used
> normally (if needed).
> 4. Waits for merge completed: dmsetup status shows used snapshot blocks –
> it should be equal to metadata size when completed.
> 5. Replace snapshot-merge d-m target back to snapshot.
> 6. Cleanup snapshot device (if nobody uses it at the moment).
> 7. Move root-cow.img.old to root-cow.img (overriding existing file).
I tried to apply these steps to 'private.img' and 'private-cow.img', but
already failed with the second step, where I couldn't really figure out
how to use the '/etc/xen/scripts/block-snapshot' script.
Is there any hope to recover an older version of a changed/deleted file
from 'private-cow.img'?
Can anyone give me a pointer how to access its content, aka "apply its
content as a patch to 'private.ig'"?
Thank you in advance,
Stickstoff
[1] https://www.qubes-os.org/doc/template-implementation/
--
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/8bbce168-ea9c-6ef9-b6b0-a39e037e1ba8%40posteo.de.
[qubes-users] Re: Unable to connect to saved WiFi
Maybe examine a previously working connection's WiFi tab & the Device line for uniqueness. The trouble is variability of reference, I think. Say you see wlan0 or wifi0 plus a MAC? Try changing that to simply the device's MAC (no snappy name, this is part of what I suspect the problem is), just the MAC for the device & save then attempt to activate the connection. On Friday, April 16, 2021 at 11:51:52 PM UTC-5 Ben Tilford wrote: > Once I connect to a wifi network I'm unable to ever re-use that connection > again. If I select the SSID it creates a 2nd (or Nth) connection to that > network. It looks like network settings in xfe/gnome also don't allow any > way to connect to a network, only configure it. > > I'm used to KDE is there something I'm just missing in how xfe/qube > manages connections? > -- 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/840d1e7f-0986-417d-a43e-8f2209abc320n%40googlegroups.com.
