Was that necessary to be able to boot (after install)?
Right, see UEFI troubleshooting | Qubes OS
Yes, it is the only way to boot after install.
After some research it seems that my system rebooted without finishing installation. So, I do not think that troubleshooting guide could help me.
I reinstalled Qubes and after Template installation, Executing qubes configuration and while Setting up networking my system rebooted again.
This time it booted to installer once again, but without templates being enabled.
After trying to install once more I got error.
Then login page was shown.
It seems to work, but I did not test it enough.
I read that booting to grub command line could be due to fail to unmount flash drive during installation in some linuxes. So, maybe I could try some other flash drive.
The same happened to me (P14s AMD G2), some times it hang up at ānetwork configurationā instead of a reboot, so I thought its related to the wifi problems I have. But every time the installer started again and looked as shown on your picture and also showing this error. Anyway, qubes seems to work ā¦ at least I couldnt find any issues related to this.
1 Like
When I installed I did not select create default qubes. And did not use USB qube sinice it would lock me from USB keyboard.
But when starting qubes(sometimes manually) and trying to do meaningful(update and compile WiFi driver) things i got often rcu_sched errors. I tried to add flags like idle=mnowait since that was somewhere recommended for this problem.
You can install all default qubes except sys-usb. I had the same problem on Desktop and used USB keyboard with USB to PS/2 adapter. Of course, it is not an option when you have a laptop.
Just in case you did not find the way how to use sys-usb with LUKS, read this.
Sounds like a pain. The best way to deal with all Qubes WiFi troubles is to use LAN to WiFi setup, if your laptop has LAN output. You can try your old router in bridge mode for this.
I used USB WiFi dongle attached to sys-net. With every update there is a risk that you will not have internet access, so
update Qubes OS only on Fridays
this way you will have time to repair it.
There are three reasons why USB dongle fails:
- sys-net or sys-usb is not using Fedora template;
- sys-net and sys-usb do not use the same kernel version;
- a bug in new kernel, try to use the older one in VM options.
I hope this will help someone.
If someone will find this topic to install Qubes on Xiaomi Mi Notebook Pro 15.6 with 4K OLED display, then you should know that Xfce desktop environment does not support such displays.
The only option for you is to install KDE. As of Augest 2021, Qubes 4.1 does not fully support KDE and you should use those workarounds.
What do you mean? 4K? I just changed resolution (to FHD) because I was not happy with result on UHD with dpi-correction and stuff. So KDE is worth trying?
As I wrote earlier, I could not install Qubes, so I tried Kubuntu. I did not use KDE for around 10 years and was amazed how good the UX is.
The best result was using scaling option (and rebooting the OS). Everything looked just fine (except x buttons on windows), but my FHD display was looking too zoomed. Then I logged using Wayland and the second display looked just perfect, but programs were blurred. The problem with Wayland is that programs should be modified to support it. Firefox works nice, but LibreOffice looks blurred and nothing you can do about that.
I switched back to X and scaled it again. I decided that every time I attach FHD display I can change the scaling option.
So, yes, KDE worked acceptable with my UHD on Ubuntu. I am confident that KDE is the only way to go for QubesOS.
Have you or anyone been able to build 4.1 with xen 4.15?
I just got the 2021 Asus G14 (r9 5900hs + 3060) and Iāve tried everything in this thread to get the installer to boot on this machine with no luck. When I keep the vga console, I see that Iām getting CPU#X stuck for X seconds shortly after the Releasing VGA console message from Xen.
Does anyone have suggestions besides the dom0_max_vcpus=1 or i915.force_probe=* to try out on this machine? Iāve tried both OCT 2 alpha builds and the beta build, but have had no luck with either.
Did you try to use latest Qubes ISO build with kernel-latest from here?
https://qubes.notset.fr/iso/
Posted in wrong tab.
I am facing the same issue with Legion 7 gen 6 (5900hx and 3080). Iāve tried all of these suggestions and the furthest I get is the CPU stuck for X seconds. Iāve been using the latest Qubes builds from https://qubes.notset.fr/iso/ for the past couple weeks with no luck.
I, also, have a laptop with 5900hx (Vega APU) and NV 3080 in an Asus Studiobook ProArt, running Qubes 4.1 on kernel 6.2. Booted with vanilla Debian 11.7, it suspends and resumes fine.
It suspends apparently OK (slow blinking LED) but fails to resume from suspend (black screen, unresponsive, must power-cycle). I have nouveau blacklisted, although I probably should load it just long enough to power down the 3080 first. I have already added āmem_sleep_default=deepā to the boot line, and ādom0_max_cpus=1 dom0_vcpus_pinā to the Xen startup line, with no success. Regular Debian 11.7 resume fails, too, when started in Xen mode.
I suspect that the amdgpu kernel module might be at fault, but find no docs on how to evict it from the dom0 kernel before suspend. There is lots about listing modules to evict from other VMsā kernels before suspension, but not from dom0. Clue?