Burned R4.0.4 (xfce) ISO to 8GB stick from linux Mint Ulyssa; booted ISO stick, installed to 64GB USB3.0 stick for 10-day evaluation; successful.
Performed dual-boot install next to linux Mint Ulyssa, (just in case).
Installed R4.0.4 to 256GB primary partition next to multiple (critical) logical partitions. No insurmountable obstacles not covered by Qubes Documentation or Forum.
[Original (Mint) partition moot; eliminating w/ no change to Qubes bootloader.]
Can I install Qubes OS together with other operating system (dual-boot/multi-boot)?
You shouldn’t do that, because it poses a security risk for your Qubes OS installation. But if you understand the risk and accept it, read documentation on multibooting. It begins with an explanation of the risks with such a setup.
From the practical perspective what I would suggest is installing it instead in an external SSD and that way you avoid all the multiple partitions / multiboot issues. Just remember to install it without sys-usb if the SSD is a USB device.
Perfect. Spending some afternoons in the docs is really key to not getting frustrated on Qubes. So many users (including myself) have struggled a lot because they didn’t do that first.
Good luck!
p.s. Also, if you’re ok with it, could you attach the .yml file of the HCL report? If you need any help on that just reply.
During 4.1.1 installation, I used a custom disk configuration, wherein I set / and /home as separate slices. No need to set mount points for keeper (no destroy) ext4 partitions, as was necessary in R4.0.1. After install, sys-net failed to launch: ERROR: Unable to reset pci device 0000:02:00.1
I had to disable the onboard NIC to get wireless networking to work. In dom0: terminal: qvm-shutdown --wait --all (Highly suggested) qvm-pci detach sys-net dom0:02_00.1 qvm-pci attach --persistent --option no-strict-reset=true dom0:02_00.1 Also, increase Fedora36 Initial Memory to 1000MB or initial upgrade will fail.
Thanks Sven, it’s good to be back.
I’ve got one more that is in work: an R.4.1.1 install on my Dell Optiplex 9020 studio tower. Looking to fat-thumb an AV-MX linux qube to handle my PreSonus AudioBox 1818VSL USB 2.0 recording interface.
Regards,
An extraordinary O/S on an outstanding laptop!
I installed an aftermarket 2TB SSDD a few years back. During R4.2 installation, I opted for a custom disk configuration, wherein I set / and /home as individual partitions of 300GB and 32GB each, more than enough acreage for most interests.
I decided to go for a debian-12 system configuration over the fedora-38 system I used with R4.1.2.
I use WiFi exclusively.
As with R4.1.x, sys-net fails to start on first boot:
In dom0: terminal, disable the onboard NIC to get wireless networking to work.: qvm-shutdown --wait --all (Highly suggested) qvm-pci detach sys-net dom0:02_00.1 qvm-pci attach --persistent --option no-strict-reset=true dom0:02_00.1
Restart: sys-firewall & sys-net should take off…
In dom0 terminal: vi /etc/qubes-rpc/policy/qubes.InputMouse
Add the following line: sys-usb dom0 allow
Save and restart.
I’ve maintained separate extended disk partitions for dedicated file categories on all my systems for over 20 years, originally FAT32 and now steadfastly ext4: Data: Anything non-graphical derived from the Internet, which can be replaced if necessary:
EXEs, ISOs, PDFs, ZIPs, TARs, etc. Files: Any and all content I originate, without exception. Grafx: Graphical Internet content: wallpapers, bitmaps, etc.
I leave them untouched during disk configuration (no mount point set), then mount them persistent according to function-specific qubes.
