Linux 101 stuff. Questions are encouraged, noobs are welcome! @lemmy.world RAM @discuss.tchncs.de 3 mo. ago

[SOLVED] Wifi adapter suddenly stopped working after 1 year

//Solution:

I installed this driver (https://github.com/morrownr/8821au-20210708).

The driver however, did not work until I ran a script called remove-driver.sh from the driver that I used to use (https://github.com/morrownr/8821cu-20210916). Then the wifi adapter started working again :)

Thanks a lot for the help - I am still not really sure what the problem actually was, but I'm very thankful for having my internet connection back :)

//Original post below:

Hey :)

I've been using a wifi adapter for my computer for about a year. A few days ago, it suddenly stopped working. It no longer shows up when I run 'nmcli device' in the terminal. When running 'lsusb' it still shows up as 'Realtek Semiconductor Corp. 802.11ac NIC'.

To my knowledge I hadn't updated anything before it stopped working. After it had stopped working, I used usb-tethering from my phone to do a system update, hoping it would fix the problem. I think one of the updates was a linux firmware update. Anyways, it didn't fix anything.

The adapter didn't work out of the box. It arrived with a driver called 'RTL88x2BU' and a document stating that it was compatible with the following chip drivers for linux: RTL8811AU RTL8811CU RTL8812BU RTL8814AU

I couldn't get the driver it arrived with to work, so instead I downloaded this driver and have been using it until it stopped working. https://github.com/morrownr/8821cu-20210916

this driver only states that it supports some linux kernel version. I'm using '6.8.0-40-generic', which it does not claim to suppport. I download this driver, which should support my kernel, but it didn̈́'t work either. https://github.com/morrownr/8821au-20210708

I've tried running lsmod on my system, and it seems to be, that no wifi driver even starts. The only thing I can remember doing just prior to my internet not working, was running 'systemctl disable jellyfin.service'. I doubt that has anything to do with this, but I'm not sure what else it could be. My only other theory is, maybe the usb wifi adapter hardware just gave up.

Any help is appreciated ^^

16 comments

Do you even dmesg bro?
- dmesg gives me 942 lines - is there anything specific I should be looking for or share here ?
  
  If it's an usb device, you can remove it and plug it in again and look at the 'new' lines at the end of the dmesg output.

A few things to start. We need to know more about how things are currently.

lspci -vv

That will give us what modules are being used by what devices along with a bunch of other information.

lsusb -v

That will give us some info about your USB layout, drivers, and so on.

We also need to know what distro you are using, kernel version, and for the distro what exact version, so if Ubuntu is it LTS, current, 23.04, etc.

That should be a good start, after that we can see where we are at and what next steps are.

I'm running Ubuntu 22.04.4 LTS, thanks for helping me :)

lspci -vv gives information about the following results, I don't think the wifi adapter is among them

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation IvyBridge GT2 [HD Graphics 4000] (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Desktop SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

lsusb -v gives

Bus 002 Device 004: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0xc811 
  bcdDevice            2.00
  iManufacturer           1 Realtek
  iProduct                2 802.11ac NIC
  iSerial                 3 123456
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0035
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           5
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 802.11ac NIC
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               3
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

I know the issue has be fixed but this is something you (or others) might want to consider.

If you have a desktop computer you can get a "wireless access point" which you can connect to your desktop using an ethernet cable then connect the AP to your WiFi network.

This negates the need to find an adapter that supports Linux and having to install drivers to make an adapter work.

With an AP the computer only sees an ethernet connection and as the AP is separate to your computer you can position it where it gets the best reception (there are even access points from the likes of TP-Link and others that can use POE (power over ethernet) so you can run just one cable).
- that's a good idea - it certainly would have saved me from a lot of work :)
  
  Wireless access points are really versatile and can be used is a number of ways.
  
  I recently upgraded from an all in one WiFi router to a wired only router (I have fibre) which is then connected to my desktop using ethernet and I have a UFO style access point on the ceiling connected using ethernet and powered by POE.
  
  If I need to upgrade the WiFi at a later date I don't have to redo my entire network setup.
Are the networking service and network manager up and running?
systemctl status networking
systemctl status network-manager
What does rfkill list wifi show?
- 'systemctl status networking' gives
  
  Unit networking.service could not be found.
  
  'systemctl status network-manager' gives
  
  Unit network-manager.service could not be found.
  
  'rfkill list wifi' gives nothing
  
  //edit:
  
  'systemctl status NetworkManager' gives
  
  ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; v> Active: active (running) since Mon 2024-08-19 08:12:34 CEST; 1h 54min > Docs: man:NetworkManager(8) Main PID: 770 (NetworkManager) Tasks: 3 (limit: 9251) Memory: 11.1M CPU: 5.564s CGroup: /system.slice/NetworkManager.service └─770 /usr/sbin/NetworkManager --no-daemon
  
  ip link show should list all available interfaces. If the wifi card isn't there, then it's not initialised after all.

You've viewed 16 comments.