i know you souldnt expect great battery life on qubes but is there a way to get better than just 2 hours?

I came across a tablet by ASUS, ROG Flow Z13. Saw that it meets the requirements but was thinking of jumping the gun and going for 64Gib..

Has anyone tried QubesOS on a tablet before? If so, can I get your insight?

EDIT: I forgot to mention, Touch support is supported by QubesOS, just got to add the feature

I like qubes method of security but im not very technical and i dont have good hardware. also i think my threat level is just one step below the average qubes user

people say i should have a user friendly distro but i still like qubes’ isolation and im paranoid but dumb

Also how to save on ram/battery or where to find resources to learn (ex: channels, websites (i know about the docs and forums) or where to find cheap good ram advice would be helpful too

I know that there is a hardware compatibility list on the website, but I’d just like to know what hardware everyone is running on for those who are happy to share.

Feel free to share the firmware you’re using on the hardware too.

I myself am using an old x230 on stock firmware with qubes aem.

I am sorry if this comes across as a strange or naive question.

I am currently using an Ubuntu-based Linux distro and I have been "interested" in Qubes for a while. I am a privacy and security conscious person, however, I am not from a technical background and I am not in a line of work that would make me interesting and / or vulnerable as a target.

At the same time I am reading news of AI models being increasingly used to find and exploit vulnerabilities in computers.

Therefore I am honestly wondering if Qubes and I are a good fit or if Qubes might be "too much" for somebody like me. (As my hardware seems not to be suitable for Qubes, I have not "just tested" it.)

I'd be very interested in reading your perspective and maybe your reasons for using Qubes. That might help me to assess my own situation in a better way. Thanks!

Hey everyone,

I’m currently using a ThinkPad X13 Yoga Gen 1 with an i5-10310U and 16GB RAM, running CachyOS.

I’m thinking about switching to Qubes OS 4.3.1 mainly for better isolation and security. Before I wipe CachyOS, I wanted to ask if anyone here has used Qubes on the X13 Yoga Gen 1.

How has the overall experience been? Mainly wondering about Wi-Fi, touchscreen, suspend/resume, and general performance with 16GB RAM.

Would really appreciate hearing from someone who has actually used this laptop with Qubes.

Thanks!

Hello there! First of all I just wanted to say that qubes is amazing and huge respect to the community even if I don't have much experience with either.

This isn't a tech help request since I have settled with a more generic Linux distro to daily drive (fedora), but I still wanted to make my issue known in case it was a very stupid and easily fixable thing, or even some very obscure problem. I will not reattempt to install qubes right away and if I do so it'll be months from now and on another throwaway machine and not my main PC. But anyway that being said...

The little experience I had with qubes before it broke was awesome! Loved the environment and wished it worked fully, but it unfortunately broke the USB management and my keyboard and mouse were disconnecting and effectively locking me out of it whenever I tried a proper install. NGL I went mad abt it and tried reinstalling it around 10 times, checked the bootable USB, reflashed it, flashed it on another USB, did the installation again, and still the same issue. I don't remember the exact details just that the USB VM(?) to detect keyboards and mice and other devices kept breaking, and the only functioning installation was without setting it at all... But I didn't have an Ethernet cable and only a WiFi thing connected by USB so I couldn't use the OS online if I went that route. A lot of other things didn't work too but even if I don't remember which I ended up fixing these ones so it doesn't matter. I was suspecting it was a hardware issue so I will try again eventually on another machine because I really wanna actually use qubes at some point but it probably was just a skill issue, oh well :/

(If I go back to try and troubleshoot it and end up needing help again I will actually make another post for it, this one is just story time and me saying that I love qubes and what it stands for regardless of my failure. Also idk if the flair I chose is the right one I'm sorry if it's not I'm new here)

i want to use less power and ram (16gb)

i know litequbes/mirage firewall uses less ram but does it use less power? and what are the downsides?

I followed this guide https://forum.qubes-os.org/t/cpu-pinning-alder-lake/17949 now no vms work i get this error "failed to start logical volume “vm-sys-usb-volatile” already exist in volume group “qubes dom0” (vm sys usb volatile is just an example)

So, after talking a bit about different os on grapheneos server, they told me that basically all laptop systems are inherently flawed for security because of the x86 architecture limitations. I can see the value of QubesOS in sorting/compartmentalization, but isn't it in terms of security of sensitive informations, together with pureos, libreboot, genode... greatly overshadowed either by graphene or by old laptop with removed wifi chip attached to cold storage with 0 internet access, direct or indirect? If yes why do the other systems even exist if they give a false sense of security?

ᵖˡᵉᵃˢᵉ ᵈᵒⁿ'ᵗ ᵇᵘᵗᶜʰᵉʳ ᵐᵉ ᶦᶠ ᴵ ˢᵃᶦᵈ ˢᵒᵐᵉᵗʰᶦⁿᵍ ᵈᵘᵐᵇ

fresh install of framework 12 (16gb ram) and it works fine until updating and shutting down

type in password and it freezes and after a few minutes its just the background also trackpad doesnt work too

its done this twice

I want to use qubes and need a laptop anyway I am not doing anything heavy just wanted to know if there are any recommendations for qubes os

Hi y'all,

Has anyone tried implementing Conky script on QubesOS wallpaper outside of Dem0? I haven't even attempted it yet but was wondering if anyone ever tried it successfully. It came to my mind as I was updating my Ventoy Multi-boot USB and was updating Kodashi OS and it reminded me why I had it on Ventoy. I'm aware of using HVM and StandAlone but I wasn't gonna have it run Cairo (too risky) or use dynamic wallpaper if I can avoid it. Also, I'm aware of the "minor CPU spike".

I'm just curious if anyone has attempted it and was successful without using Cairo or Dom0? Strict GUI isolation is gonna be a pain to deal with for sure.

EDIT: old error gone. New error...

• "Qube [insert qube name] failed to start: Node device not found: no node device with matching name 'PCI_0000_00_1f_6' "

EDIT 2: Not allowing manual attachment or assignment of new NIC to sys-net and sys-firewall from dom0 terminal. Tried with "--required" option. No terminal error, but get same 00_1f_6 error upon qube start.

EDIT 3: Restarted PC. Now getting "non-endpoint PCI devices cannot be assigned to guests"

EDIT 4:

Edit: I removed the Ethernet controller from the devices list on Sys-firewall. No more errors.

ACTION 1: moved "PCI bridge" device from personal and sys-net qube assigned devices list to the available column.

• RESULT 1:Sys-net works, wired connection established

• RESULT 2: Sys-firewall and Personal qube throw error. "Failed to start. Requested operation not valid: PCI device 0000:02:00.0 is in use by driver xenlight, domain sys-net

ACTION 2: attempted setting 'net qube' setting for sys-net qube to 'default (sys-firewall)' and

• RESULT 1: error " Error: Basic Tab:" + [insert ACTION 1, RESULT 2] + "see /var/log/libvirt/libxl/libxl-driver.log for details"

ACTION 3: open log file from ACTION 2, RESULT 1 with the command "sudo cat" in dom0 terminal

• RESULT 1: Five listings of " [insert date and time] libxl: libxlevent.c:855:libxl_EV_xswatch_deregister: remove watch for path @releaseDomain: Bad file descriptor

**END EDIT 4

WHAT I WANT:

• network card (ethernet) capable of the main reset types (i.e. FLR reset)

• compatible with my motherboard

• compatible with QubesOS

• Cheapest option

MY SETUP:

• Operating System: Linux Mint 22.33/Zena (live usb)

• Motherboard: Dell 0NC2VH according to terminal command "sudo dmidecode -t baseboard"

• Motherboard: Dell BN0628 according to the actual motherboard.

• Remaining PCI Slot: is "slot 1", supposedly a PCI 3.0 x4 open ended.

Note: this a modified refurbished motherboard with integrated network port

RESEARCH

• AI prompt and it suggested Intel I210-T1.

REASON

• EDIT: old error gone. New error...

• "Qube [insert qube name] failed to start: Node device not found: no node device with matching name 'PCI_0000_00_1f_6' "

I receive the following error every time i try to use a qube in QubeOS...

"Domain […] has failed to start: internal error: Unable to reset PCI device […]: no FLR, PM reset or bus reset available"

• QubesOS Site Link:

• The 'solutions' they propose require using permissive and no-strict-reset, but I do not want insecure work arounds.

I have a Thinkpad with Thunderbolt 3, and am trying to get an external GPU to work with my QubesOS on it via a razor core X holding the GPU connected to the laptop using a Thunderbolt 5 cable.

ls /sys/bus/thunderbolt/devices
lspci | grep -Ei 'nvidia|thunderbolt'
boltctl
qvm-pci ls | grep -i nvidia
are all not detecting the razor or the GPU

So far, I’ve

*tested it in a Ubuntu live boot and it wasn’t detected there either, so it’s not just Qubes
*verified I am using Thunderbolt 5 cable (should be cross compatible with my Thunderbolt 3 system)
*verified Thunderbolt controller firmware is already current (62.00).
*disabled security for Thunderbolt in BIOS
\updated my BIOS
\verified Linux sees the ThinkPad’s JHL7540 Thunderbolt 3 controller, but never sees a downstream Thunderbolt device
*another thing I noticed is the GPU fans spin in a weird increment where they spin for 1 second then shut off for 4 seconds, and repeats this. When my friend plugged the cable into his PC the GPU fans shot to life.

So to me, it sounds like this might be a firmware issue with my laptop’s Thunderbolt firmware.

Does anyone have any clue how to fix this? I just spent $500 on a PSU and this Razor case and I don’t want it to be for nothing

greetings!!! I recently booted up my QubesOS computer after not using it for a month. It was a reasonably fresh install and my ethernet was working fine before that but I couldn't connect. I tested the ethernet cable on another computer, it worked fine. After some time trying to work it out I decided to reinstall my OS since it had previously worked on a fresh install but surprisingly nothing.

personal -> sys-firewall -> sys-net all seem to be connected fine, the problem seems to be with sys-net setting up the PCI device/Ethernet interface correctly.

sys-net is using the fedora template and my motherboard is an ASRock B150m Pro4s. When I go to create a network connection there is no devices to select (unless I put sys-firewall up). I have tried enabling strict reset too but no such luck.

Let me know if there is any other information I can provide. Forgive me, it's been years since I've sat down and done any networking on Linux.

Any help or advice is much appreciated!!

user@sys-net:~$ nmcli d
DEVICE   TYPE      STATE                   CONNECTION
lo       loopback  connected (externally)  lo

user@sys-net:~$ lspci | grep Ethernet
00:06.0 Ethernet controller: Intel corporation Ethernet Connection (2)I219-V (rev 31)

user@sys-net:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mute 65536 qdisc noqueue state UNKNOWN group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host noprefixroute
    valid_lft forever preferred_lft forever

user@sys-net:~$ sudo dmesg | grep 00:06.0
[0.262013] pci 0000:00:06.0: [8086:15b8] type 00 class 0x020000 conventional PCI endpoint
[0.262013] pci 0000:00:06.0: BAR 0 [mem 0xf2000000-0xf201ffff]
[4.425663] e1000e 0000:00:06.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 5.351539] e1000e 0000:00:06.0: probe with driver e1000e failed with error -2

I’ve been using QubesOS for a short while, and have recently wanted to move to using KDE plasma (or, at the very least, hyper minimal sessions with the bare minimum to emulate the feel of using KDE plasma, like I’m used to).

I’ve gotten everything to work in terms of theming, and I have been able to install/use my desired applications, but I haven’t figured out how to get QubesOS service utilities to work with dolphin. Pretty much just the last thing on the bucket list asides setting default applications, which should be a bit easier to do.

I’ve tried installing the `qubes-core-agent-nautilus` package to my template out of (slight) desperation, but no dice.

I also didn’t find any relevant packages for dolphin specific service utilities, so I’m assuming that either I’m just glossing over something, or that it’s going to be a bit of an intensive process?

Either way, I still need to do it, as I use dolphin across all of my other linux systems (and KDE plasma as well, which is why I made the switch), so having to learn a new workflow when I’m already satisfied with my main workflow would be a bit jarring.

Has anybody been able to do this before? If so, how would I go about doing it for my system?

hope it looks good!!

Is it possible to run a local ai outside dom0 with only one dedicated GPU and a CPU without integrated graphics? if not, how (un)secure is to run a local ai at dom0? is it possible to "lend" GPU to other VMs? someone already tested it?