[18:34] <vilius> Hi. I have realtek 8811cu wifi dongle attached to my laptop. It worked fine until the last restart of my laptop. Now it is not on for some reason. Any ideas why or solutions?
[18:40] <tomreyn> vilius: does "rfkill" (a terminal command) list it as blocked?
[18:40] <tomreyn> (either "soft" or "hard")
[18:41] <vilius> both unblocked
[18:41] <tomreyn> vilius: which xubuntu version are you running, which kernel version?
[18:42] <tomreyn> (lsb_release -ds; cat /proc/{version,cmdline}) |& nc termbin.com 9999
[18:43] <vilius> Ubuntu 22.04.2 LTS
[18:44] <vilius> Ubuntu 22.04.2 LTS
[18:44] <vilius> Linux version 5.15.0-67-generic (buildd@lcy02-amd64-116) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023
[18:44] <vilius> BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=764d7856-bc58-4e15-a5ea-7697c16e87be ro quiet splash vt.handoff=7
[18:44] <tomreyn> !paste | vilius 
[18:45] <vilius> !pastebinit Ubuntu 22.04.2 LTS
[18:45] <vilius> Linux version 5.15.0-67-generic (buildd@lcy02-amd64-116) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023
[18:45] <vilius> BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=764d7856-bc58-4e15-a5ea-7697c16e87be ro quiet splash vt.handoff=7
[18:46] <tomreyn> that's also wrong ;) but i got the info now, thanks. give me a minute to read up.
[18:46] <tomreyn> note that you can also get help with not xubuntu specific questions such as hardware support (like here) in #ubuntu - which is often more active
[18:48] <tomreyn> can you run this command, which will gather kernel warnings and errors and post the output online? you should only post the http address that is returned:
[18:49] <tomreyn> journalctl -kb0 -pwarning |& nc termbin.com 9999
[18:49] <vilius> https://termbin.com/sezfw
[18:50] <tomreyn> oh i see you asked the same question in #ubuntu, too
[18:51] <tomreyn> so the company developing the wifi chipset you have there, 8821cu, has unfortunately provided very bad driver support for linux
[18:52] <tomreyn> as a result you already have  been using a so-called "out-of-tree" kernel module, one which is of so bad quality or incompatible license (or both) that it was not added to linux itself
[18:53] <tomreyn> usually, these out of (kernel) tree drivers (or "modules") are only compatible to a certain kernel version, or a couple versions
[18:53] <tomreyn> i assume you are now running a newer kernel verison than you used to, or one with slightly changed "ABIs"
[18:53] <tomreyn> making the old driver you still have installed no longer compatible
[18:54] <vilius> OK; I did apt update and apt-get update; there was some update with kernel (if I remember correctly), so maybe that forced it to stop working
[18:54] <tomreyn> if you look at what you posted at https://termbin.com/sezfw you'll see several lines about "8821cu"
[18:55] <tomreyn> yes, probably, you got a kernel update, which is good. but the wireless driver is not part of the kernel so you still ru the old one there
[18:55] <tomreyn> now we need to look for a newer version of the 8821cu which soemone patched to become compatible to the newer kernel version / ABI you have there
[18:59] <tomreyn> you can bookmark this - which may also link to the latest version in the future: https://github.com/morrownr/8821cu
[19:00] <tomreyn> then start here https://github.com/morrownr/8821cu-20210916#installation-information
[19:02] <vilius> I see there are at least three different users producing drivers for the same dongle? Any idea why?
[19:02] <tomreyn> anything up to "Installation Steps" is background information, which you should read and try to understand (and maybe come back to later), but the actual installation steps are further down
 so the company developing the wifi chipset you have there, 8821cu, has unfortunately provided very bad driver support for linux
[19:03] <tomreyn> ^^that's the answer to your question
[19:12] <vilius> Sorted! Thank you, tomreyn
[19:12] <vilius> I was not aware of the fact that there are various drivers available for the same unit of hardware - migrating from windows for the last three weeks...
[19:15] <tomreyn> vilius: glad you worked it out! that's not usually so, but when people have a piece of badly supported hardware and they don't want to just trash it and have the capability (or think they do) they'll try to patch existing drivers to make them compatible to newer kernel versions
[19:16] <tomreyn> "that"-> various drivers available for the same unit of hardware