Sys-net does not start with RTL8821CE

[ghost]

Release used : I first used the stable ver 4.1.2 then the 4.2 rc1and even rc2

New installation of Qubes on an ASUS laptop that only have wifi network chip (RTL8821CE).

Issue and actual behaviour : Sys-net do not start then there is no Network Manager in the systray.

To reproduce : As explaned on the forum where people friendly helped me I was able to start sys-net when kernel set in PV mode just the time enough to try running the dkms-install recommanded script. Then putting back the kernel in HVM but I never saw the "Enabling wifi" menu item in the Network Manager.

Then I bought this new laptop for nothing.

Expert behaviour : Please integrate RTL8821CE in the new rc3 and final 4.2 release. I really have to, and want because I like it so much, stay using qubesos.

Sincerely thank you and have a nice day.

[andrewdavidwong]

Is this a duplicate of #8452?

[andrewdavidwong]

Oh, if it also affects 4.1, then maybe not.

[ghost]

Dear Mr Wong,

it is not a duplicate but in fact it is the same situation I have.

I received an error when it try to start sys-net and then it close it without having a Network Manager in the systray (and it is of course normal because sys-net did not started).

I have this problem in both vesions 4.1.2 and 4.2 rc1 and rc2.

Thank you to take this problem on your todo list please because I know I as not alone having this issue and I am still now stopped in the process of having a functional QubesOS connected to internet. All other is all right except this sys-net that does not want to start and give me a "Enabling WiFi" menu item in the Network Manager (systray icon).

I just reinstalled 4.1.2 and will try again what others explained to me by setting sy-net kernel to provided by qubes then running the dkms-install.sh in the sys-net template and finally blacklist the rtw88_8821ce (in the modprobe.d/blacklist.conf) then I finally hope I could establish a wireless connection with this new ASUS laptop.

Have a good night and with pleasure to read you soon :-)

L.M.

2023-08-31 20:08 UTC, Andrew David Wong @.***>:

Oh, if it also affects 4.1, then maybe not.

-- Reply to this email directly or view it on GitHub: https://github.com/QubesOS/qubes-issues/issues/8472#issuecomment-1701712467 You are receiving this because you authored the thread.

Message ID: @.***>

--

---

米革耳 - Mig ;-)

---

[ghost]

Dear all,

I tried this morning to do what we recommended to me but I encounter this issue : "dkms" command line is not available by default. Let me explain.

1) I put sys-net kernel as "provided by qube" then I started it (in dom0 "qvm-start sys-net") and got a Network Manager in the systray (without having an "Enabling WiFi" menu item)

2) with another computer I downloaded the recommended "dkms-install.sh" (on an USB key) but I am not able to run it because it contents "dkms" command line that is not available in the 4.1.2 image. Then I tried to put my smartphone as tethering (connection) process but when I tried to assign my smartphone device to the sys-net it returns the error : "Attaching to sys-net failer. Error: QubesException - Device attach failed : /usr/lib/qubes/usb-import: line 46: /sys/devices/platform/vhci_hcd/status: No such file or directoryNo unused port found! VM: "sys-net" File: "/usr/lib/qubes/usb-import" Version Control: https://github/Qubes/qubes-app-linux-usb-proxy/blob/master/src/usb-import/usr/lib/qubes/usb-import: line 81: /sys/dev..."

Then I was not able to make a "dnf update" then a "dnf install dkms" to allow me installing the recommended "dkms-install.sh"

Thank you for your investigation and update of this rtl8821ce problem that some of us have on laptop that does not have (anymore) an ethernet port.

Have a nice day.

[ghost]

Dear all,

I just tried the RC3 to see if my RTL8821CE problem was solved but unfortunatly not.

1) after the reboot when it says "Setup networking" (just before it asks the user password) I received this popup message with Dom0 error Windows titre :

['/usr/bin/qvm-start','sys-firewall'] failed: stout : " " stderr : "qrexec-daemon statut failed: 2023-09-09 17:24:01.798 qrexec-daemon[14383]: qrexec-daemon.c:144:sigchld_parent_handler: Connection to VM failed

2) it asks the user password and when logged in I saw there was no NetworkManager then

3) I changed the sys-net kernel to "provided by qubes" then ran the "qvm-start sys-net" that showed me the NetworkManager in the systray (still without an "Enabling WiFi" menu item)

4) Devices tabulation in sys-net settings is always disabled (greyed)

5) I goes to Fedora template (which is the sys-net template) to check if dkms is available by default because I is required to run the "dkms-install.sh" that could perhaps allowing us getting à WiFi connection but dkms is not available in terminal command line in this template.

Then the situation is not available for my case. I am trying since two months but I can not having qubesos working on my new bought ASUS (X415E model) laptop.

Sincerely thank you for your hard work trying to help us in this situation.

Have a nice day.

[hyperron]

I think I've seen the solution about this particular wifi chip or similar RTL wifi. Not sure if it was GitHub or reddit. Apparently, in order to work, sys-net initial memory needs to be set above 600MB. I can't confirm this as I don't have RTL based wifi. Please let us know if this has worked in your case.

[stoufa06]

I have asus laptop, i have tried 4.1.2 and 4.2.0 and 4.2.1 and nothing worked for me. Basically i was unable to have internet at all. The more i try, the more it becomes impossible to solve. It's like made on purpose not to have this driver working. I was trying to test this distribution to see if it's worthy. I wish i can help here.

[ProGamer2508-0]

I have the same problem. This issue has been going on for years and I had the bad luck of having had 2 laptops with this network card. in the post-installation of Qubes OS I had also set that it would create a sys-usb qube, but this problem avoids the creation of that qube

[ProGamer2508-0]

I have the same problem. This issue has been going on for years and I had the bad luck of having had 2 laptops with this network card. in the post-installation of Qubes OS I had also set that it would create a sys-usb qube, but this problem avoids the creation of that qube

It did so in both laptops

[marmarek]

Apparently, in order to work, sys-net initial memory needs to be set above 600MB.

Does this help?

[ProGamer2508-0]

It returns the same error even though I gave it more memory (I can't show the screenshots I took because I don't remember how to transfer the dom0 data to another qube to put them in the SD card. Now I'll see how to do it)

[ProGamer2508-0]

[stoufa06]

Apparently, in order to work, sys-net initial memory needs to be set above 600MB.

Does this help?

I have tried on 4.2.0 and set to 1000MB but didn't work. The problem if you don't have internet you can get nothing. Even solutions that i have found in different threads and websites are blocked, whether the package or release was removed, anything that can give you handle to fix the issue is completely wiped out. I have tried different ways and get internet working but no luck. Tried to connect with cable. Tried to download wifi packages and all its dependencies to install it manually but nothing worked. Missed or removed documentation. The more i try, the more it's blocked. Even the patch is there for wifi but not added to the release. Very weird. It looked like something or someone doesn't want it to work.

[ProGamer2508-0]

I also confirm. every time I reinstalled Qubes OS to see if I could fix it, it all went into a dead end. in other operating systems the card goes beyond 5Mb of download and even supports the monitoring mode

[ProGamer2508-0]

in the post-installation of Qubes OS I had also set that it would create a sys-usb qube, but this problem avoids the creation of that qube

It also causes this problem so to use the mouse I have to start sys-net or create a clone (although I have never cloned sys-net for something like that)

[ProGamer2508-0]

(To start sys-net and enable the USB ports I have to remove the network card from the PCI devices used)

[ProGamer2508-0]

The problem if you don't have internet you can get nothing. Even solutions that i have found in different threads and websites are blocked, whether the package or release was removed, anything that can give you handle to fix the issue is completely wiped out.

Removing the network card from the devices used by sys-net should work. If you're using Ethernet, enable the Ethernet card. Usually that one is detached. If you can't, do with the USB connection using a smartphone or a USB for mobile data (I don't have an Ethernet port on my laptop, so I have to do these two options. Currently my smartphone is... Uh... differently functional at the moment and I don't have a USB for mobile data, so I have to swich with the dual boot)

[stoufa06]

(To start sys-net and enable the USB ports I have to remove the network card from the PCI devices used)

What did you do to remove the network card?

[ProGamer2508-0]

use the arrows that are in the middle when you have selected the PCI device. This issue can only be understood by experts in order to be solved

[ProGamer2508-0]

Select the Networ Controller and disable it with the arrow pointing to the left (do not click the double arrow: disable all devices from sys-net)

[ProGamer2508-0]

remember to turn on USB tethering in your smartphone when you have started sys-net and connected your smartphone with a USB cable

[stoufa06]

I don't have ethernet port but i have 4g modem that have usb port. I have removed the pci card from list of devices and the sys-net started. I have connected the modem with laptop and connected the usb device to sys-net but didn't work. The device keeps disconnecting with some gibberish logs.

[2024-04-21 12:58:53] [
366.482858] audit: type=1130 audit (1713700734.446:227): pid=1 uid=0 auid-4294967295 ses=4294967;
msg-'unit-qubes-update-check comm-"systemd" exe-"/usr/lib/systemd/systemd* hostname=? addr=? terminal=? res=success'
[2024-04-21 12:58:53] [
306.483228] audit: type=1131 audit (1713700734.447:228): pid-1 uid=0 auid=4294967295 ses=42949672
msg-'unit-qubes-update-check comm-"systemd" exe-"/usr/lib/systemd/systemd* hostname-? addr=? terminal-? res-success'
[2024-04-21 12:58:56]
308.860661] hci hcd: unlink->seqnum 337
{2024-04-21
12:58:56]
308.868708] vhci hcd: urb->status
104
[2024-04-21
12:58:56]
308.974518] usb 2-1: device descriptor read/64, error -110
[2024-04-21
12:58:56]
309. 196573]
usb 2-1: reset high-speed USB device number 3 using hei_hcd
[2024-04-21
12:58:56]
309.196672]
usb 2-1: SetAddress Request (3) to port o
[2024-04-21 12:59:01]
314.492439] vhci hcd: unlink->seqnum 339
[2024-04-21
12:59:01]
314.492494]
hei_hed: urb->status
-104
[2024-04-21
12:59:011
314.492550]
usb 2-1: device descriptor read/8, error -110
[2024-04-21 12:59:071
319.611654]
vhci hcd: unlink->seqnum 341
[2024-04-21 12:59:073 [
319.611702]
vhci hcd: urb->status
-104
[2024-04-21 12:59:12] [
324.733785]
hei_hcd: unlink->seqnum 343
[2024-04-21 12:59:12]
324.733839]
vhci hcd: urb->status -104
[2024-04-21 12:59:171 L
329.854084] vhci hcd: unlink->seqnum 345
[2024-04-21 12:59:171 [
329.854140] vhci hcd: urb-›status
- 104
[2024-04-21 12:59:171 [
329.854224] usb 2-1: device descriptor read/8, error -110
[2024-04-21 12:59:17][
330.076266] usb 2-1: reset high-speed USB device number 3 using hei hcd
[2024-04-21 12:59:171 [
330.076359] usb 2-1: SetAddress Request (3) to port 0
(2024-04-21 12:59:22] [
335.486395] hci hcd: unlink->seqnum 347
[2024-04-21 12:59:22] [
335.486472] vhci_hcd: urb-›status -104
(2024-04-21 12:59:221 [
335.486549] usb 2-1: device descriptor read/8, error -110
(2024-04-21 12:59:28] [
341.116307] vhci hcd: unlink->seqnum 349
[2024-04-21 12:59:281 [
341. 116355] vhci hcd: urb->status - 104
(2024-04-21 12:59:331 [
346.235746] vhci_hcd: unlink->seqnum 351
[2024-04-21 12:59:331 [
346.235795] vhci hcd: urb-›status - 104
[2024-04-21 12:59:38] [
351.355659] hoi hcd: unlink->seqnum 353
[2024-04-21 12:59:381 [
351.355707] vhci hcd: urb-›status - 104
(2024-04-21 12:59:38] 0
(2024-04-21 12:59:38] [
351.355793] usb 2-1: device descriptor read/8, error -110
351.458909] usb 2-1: USB disconnect, device number 3
[2024-04-21 12:59:391 [
[2024-04-21 12:59:39]
351.594109] usb 2-1: new high-speed USB device number 4 using vhci_hcd
352.007498] hoi hcd: connection closed
[2024-04-21 12:59:391 [
352. 007712] vhci hcd: stop threads

[2024-04-21
12:59:39]
352.0077121 vhci
hcd: stop threads
[2024-04-21
12:59:391
352.0077871 vhci hcd: release socket
[2024-04-21
12:59:391
352.0078391
vhci hcd: disconnect device
[2024-04-21
12:59:44]
357.048512] vhci_hcd: vhci_device speed not set
[2024-04-21
13:00:013
374.266333]
audit: type=1334 audit (1713700802.230:229): prog-id=77 op=LOAD
[2024-04-21
13:00:011
374.2664871
audit: type=1334 audit (1713700802.230:230): prog-id=78 op=LOAD
[2024-04-21
13:00:011
374.266688]
[2024-04-21
13:00:011
374.266719]
[2024-04-21
13:00:011
374.266745] audit:
[2024-04-21 13:00:011
374.323700]
msg='unit=systemd-hostnamed
comm="systemd"
[2024-04-21 13:00:011
374.3620251
[2024-04-21 13:00:01]
し
374.362039]
[2024-04-21 13:00:011 L
374.362073] WARNING: CPU: 1 PID: 1574 at drivers/xen/evtchn.c: 167 evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[2024-04-21 13:00:01] [ 374.362095] Modules linked in: cdc_ether uas usbnet usb storage mii hei_hed usbip_core snd
snd_timer snd soundcore fkill artr nft_ reject ipvo nf_reject ipv6 nft_reject_ipva nf_reject _ipv4 nft_reject nft
nf_defrag_ipv6 nf_defrag_ipv4 nf_
tables nfnetlink
polyval generic ghash clmulni intel sha512 ssse sla256 ssse shal
serio_raw xen_scsiback target_core_mod xen _netback xen_prived fuse xen gntdev xen gntallo xen_blkback xen evtchn loop overlay xen _blkfront
[2024-04-21 13:00:01] [
374.362221] CPU: 1 PID: 1574 Comm: qrexec-fork-ser Tainted: G
[2024-04-21 13:00:01]
374.362240] Hardware name: Xen HVM domU, BIOS 4.17.3 03/12/2024
[2024-04-21 13:00:01]
374.362250] RIP: 0010:evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[2024-04-21 13:00:01] [
374.362265] Code: ba 01 00 00 00 be 1d 00 00 00 48 8d bb 88 00 00 00 e8 3e a3 b7 cf
<Of> Ob eg 61 ff ff ff Of 1f
00 90 90 90 90 90 90 90 90 90 90 90 90
[2024-04-21 13:00:01] [
374.362294] RSP: 0018:ffffadf3c1b87d70. EFLAGS: 00010086
[2024-04-21 13:00:01]
374.362304]
type-1334 audit (1713700802.230:231): prog-id=79 op=LOAD
type=1334 audit (1713700802.230:232): prog-id=75 op=UNLOAD
type=1334 audit (1713700802.230:233): prog-id=76 op=UNLOAD
type=1130 audit (1713700802.286:234): pid=1 uid=0 auid=4294967295
seS=4294967295 subj=system_u:system_r: init_t: s0
exe="/us/lib/systemd/systemd" hostname=? addr=? 'terminal=? res=success'
apparently not enabled; per-user 00000000398a6cb
snd hrtimer snd_seq snd seq devi
rapl msr intel rapl common intel_pc_core crctl0dif_pelmul cre32_pclmul crc32c.
ssse3 drm_vram_helper drm
ct nft_masq nft_chain nat nf_nat nf_ conntrack
intel polyval_clm
ttm helper ttm ehci_pci ehci hed pospr i2c piix ata generic pata
W
6.6.21-1 qubes. fc37x86_64 #1
eb b4 8b 76 20 48 89 da 48 c7 c7 70 02 51 cO e8 f:
RAX: 0000000000000000 RBX: ffff951e94c3aa80 RCX: 0000000000000027
[2024-04-21 13:00:01]
374.3623171
RDX: ffff951ebbf21588 RSI: 0000000000000001 RDI: ffff951ebbf21580
[2024-04-21 13:00:01]
374.3623301
RBP: ffff951e89f73040 R08: 0000000000000000 R09: ffffadf3c1b87c08
[2024-04-21 13:00:01]
374.362342]
R10: 0000000000000003 R11: ffffffff91946248 R12: ffff951e82b2e4a4
[2024-04-21 13:00:01]
374. 362355] R13: ffff95182b2e560 R14: ffff951e89f73040 R15: ffff951e82b2e400
[2024-04-21
13:00:011
374.362368]
FS:
000071b8ada06d80 (0000) GS:ffff951ebbf00000(0000) knGS:0000000000000000
[2024-04-21 13:00:011
374.3627221
CS:
0010 DS: 0000 ES: 0000 CRO: 0000000080050033
[2024-04-21
13:00:011
374.362734]
CR2: 0000718ada30080 CR: 0000000024ea4005 CR4: 00000000003706е0

[2024-04-21 13:00:01]
374.362748]
Call Trace:
[2024-04-21 13:00:01]
374.362755]
<TASK>
(2024-04-21 13:00:01]
374.362761] ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[2024-04-21 13:00:01]
[2024-04-21 13:00:01]
374.3627 F1
warn+0x81/0x130
374.362785] ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[2024-04-21 13:00:01].
[2024-04-21 13:00:01]
374.362798] ? report_bug+0x171/0x1a0
374.362806] ? prb_read_valid+0x1b/0x30
[2024-04-21
13:00:01]
374.362816] ? handle_bug+0x41/0x70
[2024-04-21
13:00:01]
374.362824] ? exc_invalid_op+0x17/0x70
[2024-04-21 13:00:01]
374.362832] ? asm_exc_invalid_op+0x1a/0x20
[2024-04-21 13:00:01] [
374.362841] ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[2024-04-21 13:00:01] [
374.362852]
free irq+0x111/0x330,
[2024-04-21 13:00:01]
374.362862]
free_irq+0x32/0x70
[2024-04-21 13:00:01] [
374.362869]
unbind_ from irqhandler+0x31/0xbe
[2024-04-21 13:00:011 [
374.362880]
evtchn release+0x2b/0xa0 (xen _evtchn]
12024-04-21 13:00:011 [
374.362892]
fput+0xf2/0x290
2024-04-21 13:00:01]
374.362902]
x64_sys_close+0x3d/0x80
[2024-04-21 13:00:011 [
374.3629101
do syscall_64+0x5c/0x90
[2024-04-21 13:00:01]
374.362919]
count_memcg_events+0x4d/0x90
[2024-04-21 13:00:01] L
374.362929] ? count_memcg_events.constprop.0+0x1a/0x30|
[2024-04-21 13:00:01]
374.362940] ? handle_mm_fault+0xa2/0x370
[2024-04-21 13:00:011
374.362949]
? do user_addr_fault+0x323/0x660
(2024-04-21 13:00:01] L
374.362959] ? exc_page_fault+0x77/0x170
(2024-04-21 13:00:01]
374.362968]
entry_SYSCALL_64_after_hwframe+0x6e/0xd8
(2024-04-21 13:00:011 [
374.362978] RIP: 0033:0x71b8adb995dc
[2024-04-21 13:00:011 U
374.362986] Code: 0f 05
48 3d 00 fO ff ff 77 3c c3 of
1f 00 55 48 89 e5 48 83
ec 10 89 7d fc e8 40 74 f8 ff 8b 7d fc 89 c2 b8 03 00 00 00 ef 05
<48> 3d 00 f0 ff ff
77 2c 89 d7 89 45 fc e8 a2 74 f8 ff 8b 45 fc c9
[2024-04-21 13:00:011 [
374.3630181 RSP:
:00007++8&+0 LS:09RG R:00000000003
[2024-04-21 13:00:01] [
374.363033] RAX:
ffffffffffffffda RBX：
0000604a49062ad0 RCX: 000071b8adb995dc
(2024-04-21 13:00:01] L
374.363046]
RDX:
ỒA. ĐĐĐĐ0- RS: 00000000000000 RDI: 000000000000000
(2024-04-21 13:00:010 1
374.363058] RBP:
00007fff8dfda3be R08:
0000000000000 R09: 0000000000000000
[2024-04-21 13:00:011 0
374.363072]
R10:
000071b8adaa8300 R11: 0000000000000293 R12: 0000000000000000

[stoufa06]

I have tried also to connect with my fruit smartphone. Dead end ugh😖

[ProGamer2508-0]

I have connected the modem with laptop and connected the usb device to sys-net but didn't work. The device keeps disconnecting with some gibberish logs.

My modem does not support USB connection. Maybe yours does the same

I have tried also to connect with my fruit smartphone. Dead end ugh😖

enable the USB controller. You've probably disabled it or the system hasn't enabled it automatically

[ProGamer2508-0]

see the screenshot to see what I mean by USB controller (it's one of the sys-net enabled devices)

[stoufa06]

Seams that device assignments are exclusive here. Means usb controller is meant to be used only with that particular qubes. I had to shutdown sys-usb before proceeding. An error appeared when tried to start the sys-net

[ProGamer2508-0]

I don't know how you got sys-usb, but disable the setting that starts on startup, restart your pc and put the USB controller to sys-net. If it crashes, I don't know what to do

[stoufa06]

[ProGamer2508-0]

Ok. I know what causes it and how to fix it. Give me a moment to see how to explain

[ProGamer2508-0]

go into PCI devices: there should be a button underneath that fixes the problem. click it and click the USB controller once, then confirm. Then try restarting sys-net

[stoufa06]

Finally, the sys-net qubes doesn't connect sys-usb!? So weird there is problem somewhere it hangs. I wish i could debug this to find out.

[stoufa06]

@ProGamer2508-0 thanks for the tip. Trying to update but looks like it is not doing anything

[ProGamer2508-0]

Updating won't fix the problem, but you can now browse the internet on Qubes OS

[stoufa06]

I want to test and use this system on daily basis. Not sure if i can count on it. Doesn't look reliable.

[stoufa06]

The simple update stuck there forever and doesn't want to cancel

[ProGamer2508-0]

Let it update. It always takes a long time

[ProGamer2508-0]

I want to test and use this system on daily basis. Not sure if i can count on it. Doesn't look reliable.

making me think... Is this network card more common in the market? if it is, most likely those who tried to use Qubes OS with this card ended up buying an external network card or uninstalling Qubes OS. I see 4 issues that have been opened that relate to this tab (including this one), but none of them have been closed

[ProGamer2508-0]

In addition... This network card also handles Bluetooth, so it is not possible to do Bluetooth tethering

[stoufa06]

Most of the time when i start using new OS, it doesn't take much time to troubleshoot an issue even if it's a complex problem. This time was different, i have invested few days in it. Even though it is not really fixed, 4G modem attached with short usb cable is not really solution. I have to invest some money to get new hardware to use this OS and i am not sure if it will work for all my apps.

[ProGamer2508-0]

when I used Qubes OS for the first time... it didn't work because the pc didn't have virtualization technology, so Qubes OS didn't work properly. the second time I used it... I unintentionally destroyed the installation and had to do it all over again because there was no qube. On the third time, I had this problem and it took me hours to figure out what it was

[ProGamer2508-0]

making me think... Is this network card more common in the market? if it is, most likely those who tried to use Qubes OS with this card ended up buying an external network card or uninstalling Qubes OS. I see 4 issues that have been opened that relate to this tab (including this one), but none of them have been closed

I think I'm right. There are a lot of forums regarding this driver with Qubes OS and all attempts to fix them have failed after a certain period of time. I found something that seemed to fix the problem before Qubes OS was updated to an unspecified version (a driver put on github that didn't allow WPA3 and monitor mode: https://github.com/tomaspinho/rtl8821ce), but now nothing allows this PCI device to work with sys-net

[ProGamer2508-0]

I also found this forum that explains the problem a little better: https://forum.qubes-os.org/t/cant-access-the-internet/19523?page=2

[ProGamer2508-0]

I also found this forum that explains the problem a little better: https://forum.qubes-os.org/t/cant-access-the-internet/19523?page=2

It also shows why I can't get sys-usb

[ProGamer2508-0]

Also this issue with this PCI device has been there since 2021 (and this is just a function request, so it's probably been there since 2020 or earlier): #6713

[stoufa06]

I have tried all sorts of solutions i found on forums, all are dead end. I spent few days fallowing this issue, every time i say this it the solution it ends with disappointment. I have just stopped looking and waiting for new release this includes the patch for this driver. This driver seems to be used for many network cards from Realtek

[ProGamer2508-0]

Don't use this: https://github.com/lwfinger/rtw88. When I built it, it broke my Fedora template and now I have to reinstall it

[ProGamer2508-0]

I confirm the fact that it completely breaks Fedora if installed. I redid it with a clone by performing all the steps written in the README, but when the Fedora 39 clone was rebooted, dom0 gave a cube connection error

[ProGamer2508-0]

log-console.txt quest-sys-net-clone-1.log quid.sys-net-clone-1.log

These are my logs (I put them because I haven't seen any developers write in a while and no useful comments from developers)

[ProGamer2508-0]

The first one shows my attempts to create sys-usb (the first command is the first attempt, the second is to try to solve the problem and the third is the second attempt). the second one shows the data from the log file "quest-sys-net-clone-1.log" (clone of the sys-net qube. I use it to do the tests with the drivers without endangering sys-net. Clearly shows a kernel panic at the end of the log). the third one shows the data of the log file "quid.sys-net-clone-1.log" (the log is different from the other times. now it says that the window manager had a problem)

[ProGamer2508-0]

@andrewdavidwong, I'll give you a summary on this issue: this issue is in *no way" connected to a problem like issue #8452 (I think). the problem is specifically found in the driver used by QubesOS to make it work: it is not a hardware compatibility issue, but a corrupted driver issue due to the behavior of sys-net and other qubes with which the device is connected. the problem does not appear in the template, but in the file systems of QubesOS itself (but obviously it is only a hypothesis analyzing the situation from as I remember it. I don't currently have the PC in hand to see, but this problem won't be solved with normal updates I'm pretty sure).

in addition... other linux operating systems support this network card

I forgot to mention one thing: it's not a "there's not enough RAM" issue. all tests have shown that the hardware doesn't care if it has more than 400Mb. it is useless to say to put 600, 1000 or even 4000Mb if the same error occurs every time