Anybody else have any problems with the new dom0 update

General Discussion
1

Wifi does not work with the new dom0 update. Anybody else have this problem?

1 Like
2

I changed the linux kernel in global config to the previous and it works again this is a kernel problem

3 Likes
3

I have. Intel Corporation Wi-Fi 6 AX201 (rev 20) on Intel NUC 11th does not work. I downgraded to kernel 6.6.77-1.fc37 for sys-net

1 Like
4

Thanks for the awnser. This has to be reported to the team

1 Like
5

For curiosity, are you using Fedora-40 template anywhere ?

Probably not related, but after a lot of attempts to troubleshoot, I have just done a full reinstall of an old system (Hardware compatibility list (HCL) | Qubes OS), which suddenly started crashing on sys-usb startup.
The only obvious change I can see is that the newly installed 4.2.4 install has fedora-41 template for everything, vs 40 on the crashing setup… Annoyingly, I only tested an older kernel on Dom0, I don’t have a very useful set of logs from previous boots, and time is against restoring a dom0 backup for testing.

6

It is not my default template if that is what you are asking, currently using debian 12. Not using it anywhere else. However i did have a problem long ago with debian on pc and could not scan my wifi card and not connect. I did a reinstall with default template fedora and it worked.

1 Like
7

Important clarification, my sys-net using debian-12-minimal with installed qubes-core-agent-networking, qubes-core-agent-dom0-updates, qubes-core-agent-network-manager, firmware-iwlwifi, wpasupplicant

1 Like
8

Yes, I was wondering exactly that … I think my problem must be unrelated.

1 Like
9

Thanks very much for sharing. Cheers

1 Like
10

Did this change fix your problem?

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

11

sys-usb broke for me after update.

12

The same problem after updating dom0. It seems that it only updated the dom0 kernel, but many Qubes VMs broke and can no longer be launched (nested call or something). I tried to launch the old kernel version via grub, dom0 works, but many cubes do not work, although they use the kernel version provided by the cube. Maybe something is broken in the modules?
Use Qubes OS now is inposible

13

Having the exact same problem. Updated dom0, rebooted, no more wifi options in sys-net. Network controller exists, but VMs have no wifi device.

Edit: Swapped out the sys-net template from debian 12 to fedora 40. Works now.

14

For me swapping previous kernel worked well.

15

Did you try updating to previous throught the qubes manager → global config?

16

This is most likely a problem with too old firmware packages in Debian template. Updater (either the GUI one or qubes-vm-update command) should take care of it, but manual apt-get upgrade call doesn’t.

2 Likes
17

I also have the error that I have no wifi anymore, with the kernel 6.12.18-1.fc37.
With the kernel 6.6.77-1 the wifi works.
I also used a minimal deb 12 template for it.

I have run qubes-vm-update but have not seen any firmware installed.
I also use an apt cacher.

How can I get the firmware in the template?

18

If that’s minimal template, check if you have firmware-linux-nonfree package installed, I think it isn’t there by default.

1 Like
19

Thank you, that helped.
I was missing the package.

20

New problem again with kernel 6.12.21 changed it to 6.6.77 and it worked. Issue is still ongoing.

1 Like