Linux wireless drivers development
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Helge Deller <deller@gmx.de>,
	Jes.Sorensen@gmail.com, Ping-Ke Shih <pkshih@realtek.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: RTL8188S WLAN Adapter failure
Date: Mon, 11 Aug 2025 15:56:01 +0300	[thread overview]
Message-ID: <aed4c8cb-b265-444d-a17c-eb464cf4dd78@gmail.com> (raw)
In-Reply-To: <34e345ed-a114-494a-b3f7-72dfab6b628a@gmx.de>

On 11/08/2025 14:46, Helge Deller wrote:
> On 8/11/25 00:12, Bitterblue Smith wrote:
>> On 10/08/2025 23:36, Helge Deller wrote:
>>> The USB dongle which came with my DreamBox DM7020HD years ago seems to fail now.
>>> Any idea or suggestion what I should try?
>>>
>>> [427792.562049] usb 3-7: new high-speed USB device number 56 using xhci_hcd
>>> [427792.689358] usb 3-7: New USB device found, idVendor=07b8, idProduct=8188, bcdDevice= 2.00
>>> [427792.689376] usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>> [427792.689381] usb 3-7: Product: RTL8188S WLAN Adapter
>>> [427792.689385] usb 3-7: Manufacturer: Manufacturer Realtek
>>> [427792.689388] usb 3-7: SerialNumber: 00e04c000001
>>> [427792.695145] usb 3-7: This Realtek USB WiFi dongle (0x07b8:0x8188) is untested!
>>> [427792.695151] usb 3-7: Please report results to Jes.Sorensen@gmail.com
>>> [427792.934142] usb 3-7: Dumping efuse for RTL8188CU (0x200 bytes):
>>> [427792.934151] 00000000: 29 81 00 00 a9 16 00 00 b8 07 88 81 90 85 62 9c  ).............b.
>>> [427792.934155] 00000010: 06 00 ec f0 0e 16 44 3f 17 03 4d 61 6e 75 66 61  ......D?..Manufa
>>> [427792.934157] 00000020: 63 74 75 72 65 72 20 52 65 61 6c 74 65 6b 20 18  cturer Realtek .
>>> [427792.934159] 00000030: 03 52 54 4c 38 31 38 38 53 20 57 4c 41 4e 20 41  .RTL8188S WLAN A
>>> [427792.934160] 00000040: 64 61 70 74 65 72 20 00 00 00 00 00 00 00 00 00  dapter .........
>>> [427792.934162] 00000050: 06 02 00 00 00 24 24 24 00 00 00 26 26 26 00 00  .....$$$...&&&..
>>> [427792.934163] 00000060: 00 00 00 00 00 00 00 00 12 00 00 09 0d 00 00 00  ................
>>> [427792.934164] 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>>> [427792.934166] 00000080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934167] 00000090: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934168] 000000a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934170] 000000b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934171] 000000c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934172] 000000d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934174] 000000e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934175] 000000f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934176] 00000100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934178] 00000110: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934179] 00000120: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934180] 00000130: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934182] 00000140: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934183] 00000150: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934184] 00000160: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934186] 00000170: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934187] 00000180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934188] 00000190: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934190] 000001a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934191] 000001b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934192] 000001c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934193] 000001d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934195] 000001e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934196] 000001f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
>>> [427792.934198] usb 3-7: RTL8188CU rev A (TSMC) romver 0, 1T1R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
>>> [427792.934203] usb 3-7: RTL8188CU MAC: 44:3f:17:03:4d:61
>>> [427792.934206] usb 3-7: rtl8xxxu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
>>> [427792.938371] usb 3-7: Firmware revision 88.2 (signature 0x88c1)
>>> [427792.939417] rtl8192cu_power_on: Enabling LDOV12D (24)
>>> [427793.115145] rtl8192cu_power_on: FSMCO_MAC_ENABLE poll failed
>>> [427793.115156] usb 3-7: rtl8xxxu_init_device: Failed power on
>>> [427793.116003] rtl8xxxu 3-7:1.0: probe with driver rtl8xxxu failed with error -16
>>>
>>
>> Your dongle has the RTL8188SU chip inside. rtl8xxxu and rtl8192cu
>> are not the right drivers.
>>
>> The right driver is r8712u, but it was removed in kernel 6.13.
> 
> Ah, ok.
> 
>> You can use kernel 6.12. Or you can compile r8712u for your current
>> kernel. Maybe r8712u could even be accepted back in the kernel if
>> you convert it to use mac80211/cfg80211.
>> https://lore.kernel.org/linux-staging/20241020144933.10956-1-philipp.g.hortmann@gmail.com/
> 
> According to that commit message, a replacement with MAC80211 support
> is available at https://github.com/chunkeey/rtl8192su
> But development on it seems to have stopped some years ago.
> Is there any specific reason for this?

I think the people working on it ran into some problems with the
driver/firmware and also didn't have time for it anymore:

https://lore.kernel.org/linux-wireless/3717687.FpcDfXaOEr@debian64/

> I have no clue on wireless development, so if I'm willing to test this
> driver and provide feedback, would someone be interested and may help to bring
> it upstream? Or doesn't it make sense to invest the time in that?
> 
> Helge

The work has to be done by someone who has the hardware. That makes
you the best candidate for the job.

  reply	other threads:[~2025-08-11 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 20:36 RTL8188S WLAN Adapter failure Helge Deller
2025-08-10 22:12 ` Bitterblue Smith
2025-08-11 11:46   ` Helge Deller
2025-08-11 12:56     ` Bitterblue Smith [this message]
2025-08-11 13:15       ` Helge Deller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aed4c8cb-b265-444d-a17c-eb464cf4dd78@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=deller@gmx.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox