If manual reboot is necessary, then it is possible that the installer did not finish. It can happen if the installation iso is not correctly written.
For getting more help, it is necessary to answer some questions, and to explain which steps you have done.
Did you verify the iso file you downloaded?
What method did you use? Did it use the DIGESTS file you got with the iso?
After making the installation usb , when it booted, did you choose the option “Test the installation media…”? This is important. A bad USB key gives many different problems with installation.
Did you see any message about the testing of the media?
These verifications are necessary before installing qubes.
When you install, write down or make a photo of every stage and every choice you make. Write down also the things you leave as default. We do not want to see the photos, but some of the choices affect the problems you can see. If you see problems again, the photos will help you toexplain exactly when you see the problem.
I looked again at your messages. I do not understand what is the WiFi icon problem, and I do not understand when you did manual forced reboot. If you give more details, then maybe we can give more help.
This was a known issue that wifi problems happened with an update. Connect via ethernet and update your templates and dom0 or download the latest version and do a fresh reinstall and hope it’s been updated in the iso (and check the version notes if you’re unsure). Many said using an older linux kernel resolved this and you can just go to your boot options to do that.
Why QubesOS is not have the current Linux kernel and I do wish color theme of QubesOS can dracular color theme/Matte color theme for good for the eyes sights. White color theme is too bright for my eyes; it is making staring longer time is painful for the users.
ignore everything i wrote in this reply: there are two great replies below that should make this much clearer, including from the actual lead developer of qubes! which is like… incredible
(ignore all of my post below)
people posted on here about how the current kernel included with the install resulted in some problems with wifi. there should be an older kernel included. select that one or use an ethernet connection at first. (ignore this, it’s wrong, listen to marmarek below who is actually the lead developer! that’s wild he responded!)
you’re also not even including the error that is listed so i don’t even know what’s going on, nor do other people
is it always stopping at the same point? if so TELL US, don’t just post a picture of it stopping, say you tried X # of times and it always stops on X.
There are also hardware reports. Qubes is very particular. It often will not run on certain hardware and so there is a list of what computers work with Qubes and what don’t.
i don’t know if you are just complaining about no WiFi icon (and not noticing that this was a problem, as already stated, and not selecting another kernel or using an ethernet connection) or if it’s not booting.
people here will not guess the problem if you are not clear
@erickonix I am running Qubes on the Framework 13 Intel Core Ultra 7 165H and all hardware works. I also had to try installing a couple times. This is from memory but I think this is what finally worked to install Qubes 4.2.3 (note this is not exactly the 4.2.4 you’re trying).
Disable Secure Boot in BIOS
Set the date/time in the BIOS to the correct time in UTC. The install will fail mysteriously if the time is too off and the laptop comes out of the box with the time incorrect.
Install by choosing the kernel-latest (last) option from the grub boot menu
All other default options
Will reboot into initial setup
Chose debian as the default template and everything else left as default
Wifi won’t work properly
Open the Qube Manager, go to sys-net settings, under Advanced, set Kernel to (provided by qube) and restart sys-net
Wifi will work and system can be set up
For a better fix for the wifi issue, add the bookworm-backports debian repo (non-free-firmware) to sys-net and install the package firmware-iwlwifi from the backports repo. You can then set sys-net back to the default system kernel.
This sounds like an issue I encountered with my fw 13, where the keyboard/mouse didn’t work because they are connected via usb and subsequently blocked. The fix for me was to add a whitelist arg for untrusted usb devices in grub.
No idea which resource I followed, it’s been a few months.
Though the issue seems to have been fixed.
I can confirm that updating to latest (kernel version 1.13.7-1) fixes the issue for me on my fw 13.
If this doesn’t work, I can also confirm that downgrading to kernel version 1.11.10-1 worked for me for the past few months.
@marmarek glad it’s fixed. If I have to give feedback it would be that the issue was quite obscure to find, with the known issues page not helping at all since it didn’t list it.
I eventually stumbled onto the gh issue (if I remember right it was #7053?) after debugging a bit and searching for my network card name, at which point subsequent help threads were easy to find. All in all it was quite a challenge since I’m really not experienced in debugging os issues
