RTL8723DE issues and Kernel 5.5

hi

a friend has a HP laptop with build in RTL8723DE, for issues related to power drain I switched him over from Leap to Tumble and update him every few months, so far been working okay.
However as of todays update where he went from 5.4 to 5.5 the RTL8723DE no longer works, this has happened before in the past, but most of the time a remove/reinstall solved it or in one case removing the firmware package.

I am using the drivers from https://download.opensuse.org/repositories/home:Sauerland:hardware/openSUSE_Tumbleweed

Just the rtlwifi_new-extended-kmp-default 20200221_k5.5.4_1-2.1

I have 2 questions :slight_smile:

  1. is there an good out of the box wifi dongle which simple works with Tumbleweed/kernel 5.5+ as I am getting tired of this tbh does the Asus USB-AC51 AC600 work ?

  2. anybody have any idea how to get this working again, just feels like the driver is simply not loaded

linux-mq72:~ # dmesg | grep rtl
    9.367795] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723d_fw.bin
    9.373370] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723d_config.bin
linux-mq72:~ # lsusb
Bus 001 Device 005: ID 0bda:b009 Realtek Semiconductor Corp. 
Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0408:5321 Quanta Computer, Inc. 
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
linux-mq72:~ # lspci -nnk | grep -i -A3 net
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        DeviceName: Realtek PCIe FE Family Controller
        Subsystem: Hewlett-Packard Company Device [103c:84d0]
        Kernel driver in use: r8169
--
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
        Subsystem: Hewlett-Packard Company Device [103c:8319]
linux-mq72:~ # hwinfo --netcard
07: PCI 300.0: 0280 Network controller                          
  [Created at pci.386]
  Unique ID: svHJ.qRNrg88_gN6
  Parent ID: JCE+.XZwpGIabNM5
  SysFS ID: /devices/pci0000:00/0000:00:02.5/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Model: "Realtek RTL8723DE 802.11b/g/n PCIe Adapter"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0xd723 "RTL8723DE 802.11b/g/n PCIe Adapter"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x8319 
  I/O Ports: 0xd000-0xdfff (rw,disabled)
  Memory Range: 0xfe900000-0xfe90ffff (rw,non-prefetchable,disabled)
  IRQ: 255 (no events)
  Module Alias: "pci:v000010ECd0000D723sv0000103Csd00008319bc02sc80i00"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #10 (PCI bridge)

13: PCI 200.0: 0200 Ethernet controller
  [Created at pci.386]
  Unique ID: rBUF.8K7LRahxD1B
  Parent ID: Rtk9.XZwpGIabNM5
  SysFS ID: /devices/pci0000:00/0000:00:02.4/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Device Name: "Realtek PCIe FE Family Controller"
  Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x84d0 
  Revision: 0x15
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: eth0
  I/O Ports: 0xe000-0xefff (rw)
  Memory Range: 0xfea04000-0xfea04fff (rw,non-prefetchable)
  Memory Range: 0xfea00000-0xfea03fff (rw,non-prefetchable)
  IRQ: 34 (no events)
  HW Address: 10:62:e5:52:4e:5f
  Link detected: no
  Module Alias: "pci:v000010ECd00008168sv0000103Csd000084D0bc02sc00i00"
  Driver Info #0:
    Driver Status: r8169 is active
    Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #25 (PCI bridge)

solved it for now by building the drivers from git and using the ant_sel=2 option, without it the driver would be loaded but not connect.
still thank you Larry if you reading this :wink:

Still would love to know of wifi dongle that I don’t have to worry about.