Announcement

Collapse
No announcement yet.

Kubuntu 22.04 - using Realtek wireless adapter

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Kubuntu 22.04 - using Realtek wireless adapter

    I have been struggling with setting this up for the past few days. I've trawled through many help articles and attempted to install the drivers and uninstall unused ones. The other day, I thought I had got it - it was working well for a few days. Then I rebooted today and it no longer works on reboot. I'm using Linux again after a while away as my HDD that is attached to Windows is starting to fail.

    PC info:
    Release: 22.04
    Version of KDE: Unsure
    Version of Grub: Unsure

    lscpu: Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz x64
    GPU: NVidia GTX 1080ti
    RAM: 8 GB
    HDs: SSD attached to Kubuntu

    Output from lsusb:
    Code:
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1038:1710 SteelSeries ApS SteelSeries Rival 300 Gaming Mouse
Bus 001 Device 003: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 007: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano]
Bus 001 Device 005: ID 1038:1612 SteelSeries ApS SteelSeries Apex 7
Bus 001 Device 002: ID 1038:1260 SteelSeries ApS Arctis 7 wireless adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Output from DKMS Status:

    Code:
    tl88x2bu/5.13.1, 5.15.0-41-generic, x86_64: installed
    I followed the steps outlined in morrownr/88x2bu-20210702. I did not have any issues following the installation but the adapter does not connect.

    Any advice is appreciated.
    Tags: kubuntu, network
    • Top
    • Bottom
    #2
    I don't think the 88x2bu is the correct driver for your card, the device ID is not on the list of devices:
    https://github.com/morrownr/88x2bu-2...ted-device-IDs

    I think this one is the proper git repo
    https://github.com/morrownr/8821au
    Which leads to the current repo, and your device ID IS listed
    https://github.com/morrownr/8821au-2...ted-device-IDs

    This one might also work
    https://ostechnix.com/install-tp-lin...pter-in-linux/

    I'd uninstall what you have, and try one of these, preferably the morrownr, not the aircrack one in the ostechnix link.
    • Top
    • Bottom

    Comment

      #3
      I tried using both of those repos, first the morrownr then aircrack, both were successful, neither resulted in the adapter coming online. Is there another step I'm supposed to take after installing the drivers and then reboot-unplug and replug USB?
      • Top
      • Bottom

      Comment

        #4
        No, I don't think so.
        Realtek can be a big PITA

        You did uninstall the previous drivers you installed when testing different ones?
        • Top
        • Bottom

        Comment

          #5
          Yes, as far as I'm aware of I tried to ensure I used dkms remove --all as well as deleting the directories. For sure every time I tried to install a driver I made sure nothing came up under dkms status. Maybe I'll try using a different adapter, I think I have one around here somewhere.
          • Top
          • Bottom

          Comment

            #6
            Unfortunately the other adapter I have is ALSO realtek, that uses the 88x2bu: Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey]

            If no one has any ideas, are there recommendations for WiFi adapters that DO work reliably?

            Edit: I saw someone using modprobe and running dmesg to see the output. I think this is the pertinent part of that output, if this can be of assistance.

            Code:
            [   46.837952] 88x2bu: Unknown symbol __cfg80211_alloc_event_skb (err -2)
[   46.837964] 88x2bu: Unknown symbol wiphy_register (err -2)
[   46.837973] 88x2bu: Unknown symbol cfg80211_remain_on_channel_expired (err -2)
[   46.837991] 88x2bu: Unknown symbol cfg80211_vendor_cmd_reply (err -2)
[   46.838001] 88x2bu: Unknown symbol cfg80211_del_sta_sinfo (err -2)
[   46.838010] 88x2bu: Unknown symbol wiphy_unregister (err -2)
[   46.838037] 88x2bu: Unknown symbol cfg80211_ch_switch_notify (err -2)
[   46.838046] 88x2bu: Unknown symbol cfg80211_ch_switch_started_notify (err -2)
[   46.838053] 88x2bu: Unknown symbol ieee80211_get_channel_khz (err -2)
[   46.838063] 88x2bu: Unknown symbol cfg80211_ready_on_channel (err -2)
[   46.838088] 88x2bu: Unknown symbol wiphy_free (err -2)
[   46.838094] 88x2bu: Unknown symbol wiphy_new_nm (err -2)
[   46.838100] 88x2bu: Unknown symbol cfg80211_get_bss (err -2)
[   46.838113] 88x2bu: Unknown symbol ieee80211_freq_khz_to_channel (err -2)
[   46.838121] 88x2bu: Unknown symbol __cfg80211_send_event_skb (err -2)
[   46.838135] 88x2bu: Unknown symbol cfg80211_disconnected (err -2)
[   46.838142] 88x2bu: Unknown symbol cfg80211_michael_mic_failure (err -2)
[   46.838151] 88x2bu: Unknown symbol cfg80211_ibss_joined (err -2)
[   46.838176] 88x2bu: Unknown symbol cfg80211_scan_done (err -2)
[   46.838186] 88x2bu: Unknown symbol cfg80211_roamed (err -2)
[   46.838191] 88x2bu: Unknown symbol cfg80211_put_bss (err -2)
[   46.838202] 88x2bu: Unknown symbol cfg80211_connect_done (err -2)
[   46.838216] 88x2bu: Unknown symbol cfg80211_unlink_bss (err -2)
[   46.838228] 88x2bu: Unknown symbol cfg80211_inform_bss_frame_data (err -2)
[   46.838236] 88x2bu: Unknown symbol cfg80211_new_sta (err -2)
[   46.838249] 88x2bu: Unknown symbol __cfg80211_alloc_reply_skb (err -2)
[   46.838261] 88x2bu: Unknown symbol cfg80211_mgmt_tx_status (err -2)
[   46.838267] 88x2bu: Unknown symbol cfg80211_rx_mgmt_khz (err -2)
[   46.838276] 88x2bu: Unknown symbol cfg80211_external_auth_request (err -2)
[  137.369007] 88x2bu: Unknown symbol __cfg80211_alloc_event_skb (err -2)
[  137.369019] 88x2bu: Unknown symbol wiphy_register (err -2)
[  137.369028] 88x2bu: Unknown symbol cfg80211_remain_on_channel_expired (err -2)
[  137.369046] 88x2bu: Unknown symbol cfg80211_vendor_cmd_reply (err -2)
[  137.369056] 88x2bu: Unknown symbol cfg80211_del_sta_sinfo (err -2)
[  137.369065] 88x2bu: Unknown symbol wiphy_unregister (err -2)
[  137.369091] 88x2bu: Unknown symbol cfg80211_ch_switch_notify (err -2)
[  137.369101] 88x2bu: Unknown symbol cfg80211_ch_switch_started_notify (err -2)
[  137.369108] 88x2bu: Unknown symbol ieee80211_get_channel_khz (err -2)
[  137.369118] 88x2bu: Unknown symbol cfg80211_ready_on_channel (err -2)
[  137.369143] 88x2bu: Unknown symbol wiphy_free (err -2)
[  137.369149] 88x2bu: Unknown symbol wiphy_new_nm (err -2)
[  137.369155] 88x2bu: Unknown symbol cfg80211_get_bss (err -2)
[  137.369168] 88x2bu: Unknown symbol ieee80211_freq_khz_to_channel (err -2)
[  137.369176] 88x2bu: Unknown symbol __cfg80211_send_event_skb (err -2)
[  137.369190] 88x2bu: Unknown symbol cfg80211_disconnected (err -2)
[  137.369197] 88x2bu: Unknown symbol cfg80211_michael_mic_failure (err -2)
[  137.369206] 88x2bu: Unknown symbol cfg80211_ibss_joined (err -2)
[  137.369232] 88x2bu: Unknown symbol cfg80211_scan_done (err -2)
[  137.369242] 88x2bu: Unknown symbol cfg80211_roamed (err -2)
[  137.369247] 88x2bu: Unknown symbol cfg80211_put_bss (err -2)
[  137.369258] 88x2bu: Unknown symbol cfg80211_connect_done (err -2)
[  137.369273] 88x2bu: Unknown symbol cfg80211_unlink_bss (err -2)
[  137.369284] 88x2bu: Unknown symbol cfg80211_inform_bss_frame_data (err -2)
[  137.369292] 88x2bu: Unknown symbol cfg80211_new_sta (err -2)
[  137.369306] 88x2bu: Unknown symbol __cfg80211_alloc_reply_skb (err -2)
[  137.369317] 88x2bu: Unknown symbol cfg80211_mgmt_tx_status (err -2)
[  137.369324] 88x2bu: Unknown symbol cfg80211_rx_mgmt_khz (err -2)
[  137.369333] 88x2bu: Unknown symbol cfg80211_external_auth_request (err -2)
            Last edited by allseemsfine; Jul 21, 2022, 09:13 AM.
            • Top
            • Bottom

            Comment

              #7
              If Intel made USB dongles, I'd suggest that, but they don't.

              I thought I had a working USB adapter, but I can't locate it. It definitely worked ootb when I got it a few years ago. Still looking.



              EDIT:
              Still can't find it, I must have given it away.
              BUT, I finally found the listing for it (once I thought to search for not just 'wifi' but also 'wi-fi')

              https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1
              I got this in 2017, and as far as I remember, I didn't need drivers or any extra work.
              Edimax dongle seem to have decent Linux support, and they do often provide drivers on their website, though they can be outdated.
              Reviews on this one can be misleading, as older kernels (from 2017 an earlier) did not work without an external driver, but it worked for me, as far as I recall.
              later reviews do show 20.04 and newer kernels seem to be fine.

              However, looking at your specs, depending on your motherboard, an m.2 key adapter, or a PCIe card might be a good choice
              This can get you Intel chips, which Just Work.
              PCIe:
              https://www.amazon.com/dp/B096SDN4DY...d12a830ca&th=1
              I have this one


              M.2 cards: https://www.amazon.com/s?k=intel+wif..._ts-doa-p_3_10
              Any similar cards that list an intel chip will be what you want.


              This is not Intel, but it definitely works OOTB, as I had this until last month, when I sold that PC
              https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1
              Of course, you have to have the correct slot as well as get antennas for this style, either stick on wire ones, or ones that stick out from an empty pci slot on the case
              • Top
              • Bottom
              • Likes 1

              Comment

              Previous template Next
              Working...
              X