Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Installation problems with Qubes 4.0.2 final #5553
Qubes OS version
Affected component(s) or functionality
The laptop (Acer Aspire V) is fine. I have the latest BIOS firmware. I checked the memory and SSD. I have been using it with Qubes 3.1 until 4.0.1 without problems. I installed in BIOS Legacy mode.
Solutions you've tried
I also tried adding the options mapbs=1 and noexitboot=1 to the xen.cfg without success:
Similar problem here with threadripper on x399 mobo. I installed in UEFI mode, had to comment out mapbs and noexitboot in the USB installer boot cfg but I didn't in the installed system. I tried to do the post-install finalization procedure 2 times, and two times I got a sudden reboot. Third time I just ticked "do not configure anything" and continued to the installed system, but without the default VMs is hard for me to figure out what to do to manually configure them.
EDIT1: I repeated the install process from the beginning (wipefs and reboot to the installer), and on reboot I got a random reboot during the x11 initialization (before the post-install finalization prompt).
EDIT2: I repeated (again) the install process from the beginning. This time I added "efi=attr=uc" option in xen.cfg as stated in the UEFI troubleshooting page and don't know if it worked because the debian templatevm install bar stopped moving, so after a couple of minutes I tried to switch to a console (alt+ctrl+Fx) and as soon as I arrived to F7... I had been able to read the first line only (something about "kernel BUG"), it looked like a kernel panic and xen triggered the watchdog to reboot dom0.
EDIT3: After a new fresh install, I tried to disable SMT in BIOS (because I noticed it is disable in xen.cfg) and reduce mem_max to 2048M (because it did the trick for xcp-next install). But no luck. Same behaviour.
EDIT4: I tried adding the mapbs and noexitboot options, one at a time, with no luck. Mapbs simply hangs the computer with black screen (same of the installer, I had to remove those in order to see the installer welcome screen). Noexitboot makes no difference at all. At this point I'm short of options. The numa arch of this machine might be the issue, but I've no idea how to troubleshoot it.
EDIT5: After adding noreboot boot option I've been able to read the kernel panic message. The first line asserts some kind of kernel bug in blk-core.c:1779. The second line complaints about invalid opcode 0000 SMP NOPTI. I also tried to disable memory interleaving (NUMA) in the mobo BIOS, in order to have a more traditional UMA topology, but didn't change anything. Still: it may be a NUMA related issue, as the mobo connects the network devices to one numa node and the nvme block devices to the other node; but I don't know if I can disable numa for I/O as well, as I did with memory. It looks like it fails on "blk put" function... block device write issue? The first stage of the install process is massive on block device and have no bug! I also run badblocks to check for block device problems and ... the block device is fully functional.
I can confirm 4.0.2-rc3 works and ... is awesome!!! I've been testing QubesOS about once per year since the first public release and ... this is the first time I've the feeling I can replace my current distro with QubesOS. All the operations I tried went smooth, flawless. Even glxgears works! Probably steam games (proton) won't be so easy to run but ... it's a start.
Congratulation guys, it's really a good job. PLEASE, keep going.
@marmarek: Thx a lot for bringing back back the 4.0.2 RC version. I will try to install the RC version on the weekend.
Maybe the news section of the homepage should also be updated ASAP, so users are not confused and look for the final version 0f 4.0.2.
Thx for the great work. I love Qubes. It is the best OS ever!
I just wanted to note that in the news section of the web site it still says that the new version 4.0.2 is out. I think it would be better to also remove that so not to confuse anybody.
Thx for the great work. I love Qubes OS.
Yes, I'm aware. That's because the News page contains a list of all the News posts, and the original 4.0.2 announcement post has not been taken down. We never take down a post after publishing it (we only add updates within the body of the post), because links to the post are immediately shared on mailing lists, social media websites, and elsewhere across the Web immediately after publication. Taking down the post would break all of those links, which would prevent people from seeing the update in the body of the post to learn what is going on. How about this: I'll add
_posts: gpg: Good signature from "Andrew David Wong (Qubes Documentation Signing Key)" [ultimate] object 018cea3924c0b77de4a4a067a8c9ff2555b3a702 type commit tag adw_018cea39 tagger Andrew David Wong <email@example.com> 1578871693 -0600 Tag for commit 018cea3924c0b77de4a4a067a8c9ff2555b3a702 018cea3 Add "[Delayed]" to 4.0.2 post title (QubesOS/qubes-issues#5553)
Updated installation image, soon to be published as R4.0.3-rc1: