Updated Qubes 4.2 with a clean install Qubes 4.3 .. Wifi no longer works

User Support General
1

My wifi hardware is: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800]

In sys-net, this is listed along with the direct connect wired network that is always connected. It appears that the latest software didn’t install the wifi drivers … or encountered an error. Please advise as to how to update this.

Update: Using Fedora Template.

Thanks!

2

Fedora template?

3

yes

4

Maybe this could help:

5

I’m not familiar with that specific chipset, but if it worked in a previous Qubes version it should work in 4.3.0 now.

If the driver is anything like ath11k, it needs a big chunk of RAM to initialize and get off the ground. Try increasing “initial memory allocation” for sys-net to at least 600MB.

6

Thanks to all for the help. I’ve discovered that making a simple mistake in trying changes in qubes can be fatal, kills qubes :slight_smile: This is the second clean 4.3 installation for me :frowning:

I changed swiotlb=16384. Didn’t help.
I also changed the initial memory allocation for sys-net to 600MB. Didn’t help.
I tried updating dom0 to get latest drivers. I got the following …

firefox@dom0:~$ sudo qubes-dom0-update
Using sys-firewall as UpdateVM for Dom0
Downloading updates. This may take a while…
Fedora 41 - x86_64 256 kB/s | 19 MB 01:16
Fedora 41 - x86_64 - Updates 9.4 MB/s | 8.4 MB 00:00
Qubes Host Repository (updates) 0.0 B/s | 0 B 06:00
Errors during downloading metadata for repository ‘qubes-dom0-current’:

Again … thanks for your help!

Update Resolved … due to my firewall … see below. “This is weird. Firefox can connect to the internet without a problem. But I can’t ping a ip like 8.8.8.8 or 1.1.1.1 in any qube? How to start fixing this?”

7

How you able to make this card work in Qubes 4.2?
You have backup from your QubesOS 4.2 installation with relevant template?

After same google look like it doesn’t supported by Linux at all, there is no driver for this card.

8

Yes. When I initially loaded a clean Qubes 4.2, the hardwire networking and wifi worked. I then installed a clean Qubes 4.3 The hardwire networking worked, but wifi did not. I then discovered the wifi hardware was no longer displayed as being recognized by Qubes ?. Since I need wifi to be working soon … I tried the simple solution … I reloaded a clean Qubes 4.2. I then encountered the Fedora template was no longer supported “errors” … lots of problems to fix. So I then reinstalled a clean Qubes 4.3. I then noticed the wifi hardware was no longer recognized but hardwire networking worked. For your info: My motherboard is PRO Z790-A MAX WIFI with Crucial Pro 32GB DDRS RAM and Kingston KC3000 PCIe 4.0 NVMe M.2 1024 GB SSD. Booting/starting cubes takes only seconds. The only thing limiting me now is how fast I can type.

9

When pasting the yum timeout links into a firefox browser … it fails to connect. It almost looks like a dns problem?

10

This is weird. Firefox can connect to the internet without a problem. But I can’t ping a ip like 8.8.8.8 or 1.1.1.1 in any qube? How to start fixing this?

Update: I purchased a wifi extender to convert existing wifi to wired internet. This fixed my ping/update dom0 problem. Here’s why.

  1. I have ATT fiber. The modem provides wifi and a wired internet connect.
  2. The wired internet goes to my firewall which originally provided wired internet to my Qubes computer. This breaks Qubes preventing any ip connections, etc.
  3. Something about dns I’m guessing at this point. The firewall provides a secure dns. Qubes is probably not using it.
  4. The wifi extender bypassed the firewall exposing this problem :slight_smile:
  5. I was able to also download the latest firmware, etc. which would include any wifi driver problems … hopefully.
    Update
    My clean qubes 4.3 version was 6.12.59-1.qube.fc41.x86_64
    After reboot : 6.17.9–1.qubes.fc41.x86_64.
    Wifi hardware still not recognized.
11
  1. Boot into livecd of Fedora 38 (represent QubesOS 4.2), check your wifi card and if it works share driver information with us.
  2. Boot into livecd of Fedora 41 (represent qubes 4.3), do same.
  3. Last, boot into livecd of Fedora 42 or 43, to check last and most update to date driver.
12

Trying to load iso live. Tried two different iso’s, 43 & 41. Fedora 38 is no longer supported and it definitely didn’t even start right. All Sha256 verified for all. 43 & 41 start as they normally would (give you standard options) … but then abort to a black screen and leave the computer non responsive if selecting live.

Since my only disk space is a Kingston KC3000 PCIe 4.0 NVMe M.2 1024 GB SSD and currently totally encrypted by Qubes, can the live unix install? I just became aware that the bios must know it’s encrypted (tpm2) and saved me from it getting trashed? I have 32GB DDRS Ram it could use? This is all new to me, never tried to do this. For windows 11 … I’d just turn off the encryption to allow access. Please advise as to how to proceed. Thanks!

13

Update; live update only uses ram. I have 32 GB … that should be enough to run. Not sure why these iso’s won’t run at boot?

14

Update: For some reason, I could not get rufus to generate a bootable usb iso for my 8gb or 32gb drives. I used a 64gb usb with partition scheme MBR, Target system BIOS or UEFI, File system Large FAT32 (Default), Cluster size 32 kilobytes (Default). This worked for both Fedora 38 and Fedora 43. Bottom line was … the wifi adapter was not recognized in either 38 or 43. Looking at feedback on this motherboard … there are complaints that the wifi is not working. The wifi module appears to plug into the motherboard … but not easily accessible due to a heat sink above it. Taking this apart now is not an option. Since I have a workaround for the wifi, willing to live with reduced bandwidth of 95MB/sec versus 1000MB/sec. I’ll repost the final analysis when I get the time. Thanks for the help! Bottom line is that I love Qubes. I was forced to go to windows 11 on my other computer :frowning: and I only use windows 11 when I have to. Can’t trust Microsoft with my data!