Wifi is working in kernel 6.8.2 much better than before

[sanjarbek-ismatov]

I installed Fedora 40 beta with kernel 6.8.2. I even enabled secure boot. Wifi is working great now. It rarely changes and doesn't drop. What happened? So I haven't installed rtl8821ce with dkms and I don't have to do that. I'm satisfying with the default state. I installed Fedora 2 times to check. When I use other distros with older kernel it worked badly, but In Fedora 40, it's pretty stable

[dubhater]

I finally fixed it! https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=e1dfa21427baeb813f9a2f9ceab6b7d32c3ca425

The fix is in the older stable kernels too.

[sanjarbek-ismatov]

I finally fixed it! https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=e1dfa21427baeb813f9a2f9ceab6b7d32c3ca425

The fix is in the older stable kernels too.

But for long distances, sometimes the signal changes quickly(like older version) without affecting wifi strength

[APIVersa]

Not an issue, more a praise. Ubuntu 24.04 --- Your plugin is working PERFECTLY -- where others on Github have failed. ! :) Thank you for this. This is a perfectly ported driver in my opinion.

The other one here on Github worked at first but failed after reboot. Using the remove-driver script from you, then the dkpg-make, then the install-driver, all works so flawlessly.

You guys are the best :)

Just thought I should include Ubuntu 24.04 LTS info: (I know it isn't common 24.04 yet.. but we forced upgrade to maintain LTS status (change config to normal upgrade, do-release-upgrade, after 23.10, do-release-upgrade -d, done --- this is from 22.04 LTS).

Anyways... The specs incase anyone is curious:

lsb_release -a

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04 LTS
Release:	24.04
Codename:	noble

And the specs of the kernel:

uname -a

6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

[OBLIXi-ON]

Can you please confirm the supported modes? Just do iw list and there'll be a section named Supported interface modes. Thanks.

[APIVersa]

Can you please confirm the supported modes? Just do iw list and there'll be a section named Supported interface modes. Thanks.

Wiphy phy0
	wiphy index: 0
	max # scan SSIDs: 9
	max scan IEs length: 2304 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
		* CMAC (00-0f-ac:6)
		* GCMP-128 (00-0f-ac:8)
		* GCMP-256 (00-0f-ac:9)
		* CCMP-256 (00-0f-ac:10)
		* GMAC-128 (00-0f-ac:11)
		* GMAC-256 (00-0f-ac:12)
		* CMAC-256 (00-0f-ac:13)
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * monitor
		 * P2P-client
		 * P2P-GO
	Band 1:
		Capabilities: 0x1862
			HT20/HT40
			Static SM Power Save
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 16 usec (0x07)
		HT Max RX data rate: 150 Mbps
		HT TX/RX MCS rate indexes supported: 0-7
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps
			* 5.5 Mbps
			* 11.0 Mbps
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412.0 MHz [1] (16.0 dBm)
			* 2417.0 MHz [2] (16.0 dBm)
			* 2422.0 MHz [3] (16.0 dBm)
			* 2427.0 MHz [4] (16.0 dBm)
			* 2432.0 MHz [5] (16.0 dBm)
			* 2437.0 MHz [6] (16.0 dBm)
			* 2442.0 MHz [7] (16.0 dBm)
			* 2447.0 MHz [8] (16.0 dBm)
			* 2452.0 MHz [9] (16.0 dBm)
			* 2457.0 MHz [10] (16.0 dBm)
			* 2462.0 MHz [11] (16.0 dBm)
			* 2467.0 MHz [12] (16.0 dBm) (no IR)
			* 2472.0 MHz [13] (16.0 dBm) (no IR)
			* 2484.0 MHz [14] (disabled)
	Band 2:
		Capabilities: 0x862
			HT20/HT40
			Static SM Power Save
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 7935 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 16 usec (0x07)
		HT Max RX data rate: 150 Mbps
		HT TX/RX MCS rate indexes supported: 0-7
		VHT Capabilities (0x03c00022):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			short GI (80 MHz)
			+HTC-VHT
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: not supported
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 434 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: not supported
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 434 Mbps
		VHT extended NSS: not supported
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180.0 MHz [36] (13.0 dBm)
			* 5200.0 MHz [40] (13.0 dBm)
			* 5220.0 MHz [44] (13.0 dBm)
			* 5240.0 MHz [48] (13.0 dBm)
			* 5260.0 MHz [52] (13.0 dBm) (radar detection)
			* 5280.0 MHz [56] (13.0 dBm) (radar detection)
			* 5300.0 MHz [60] (13.0 dBm) (radar detection)
			* 5320.0 MHz [64] (13.0 dBm) (radar detection)
			* 5500.0 MHz [100] (13.0 dBm) (radar detection)
			* 5520.0 MHz [104] (13.0 dBm) (radar detection)
			* 5540.0 MHz [108] (13.0 dBm) (radar detection)
			* 5560.0 MHz [112] (13.0 dBm) (radar detection)
			* 5580.0 MHz [116] (13.0 dBm) (radar detection)
			* 5600.0 MHz [120] (13.0 dBm) (radar detection)
			* 5620.0 MHz [124] (13.0 dBm) (radar detection)
			* 5640.0 MHz [128] (13.0 dBm) (radar detection)
			* 5660.0 MHz [132] (13.0 dBm) (radar detection)
			* 5680.0 MHz [136] (13.0 dBm) (radar detection)
			* 5700.0 MHz [140] (13.0 dBm) (radar detection)
			* 5720.0 MHz [144] (disabled)
			* 5745.0 MHz [149] (13.0 dBm)
			* 5765.0 MHz [153] (13.0 dBm)
			* 5785.0 MHz [157] (13.0 dBm)
			* 5805.0 MHz [161] (13.0 dBm)
			* 5825.0 MHz [165] (13.0 dBm)
			* 5845.0 MHz [169] (disabled)
			* 5865.0 MHz [173] (disabled)
			* 5885.0 MHz [177] (disabled)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * set_bss
		 * join_ibss
		 * set_pmksa
		 * del_pmksa
		 * flush_pmksa
		 * remain_on_channel
		 * frame
		 * set_channel
		 * tdls_mgmt
		 * tdls_oper
		 * connect
		 * disconnect
	WoWLAN support:
		 * wake up on anything (device continues operating normally)
	software interface modes (can always be added):
		 * monitor
	interface combinations are not supported
	Device supports SAE with AUTHENTICATE command
	Device supports scan flush.
	Device supports randomizing MAC-addr in scans.
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0xd0
		 * managed: 0x40 0xb0 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
	Supported extended features:
		* [ RRM ]: RRM

[OBLIXi-ON]

Thanks man!

[APIVersa]

Thanks man!

No issues man. Enjoy it :)

I have been running it on Ubuntu 24.04 for about 3-4mo now without issues for the most part.

There is only 1 issue I've noticed, but I think it's more the device that I have than the driver (mine is a knock-off I think, LB-LINK but on windows shows up as this same version that this thread is about and all the drivers for this work, so assuming a Chinese clone). The device in bootup is recognized as a USB drive or something and tries to do a drive-scan in boot, which eventually times out, adding 1 minutes or more to boot time. The WiFi doesn't come up at boot then, and you need to simply unplug it and plug it back in. The second you plug it back in, it starts working instantly. I think it has something to do with the fact that there is USB drive partition on it that usually contains the Windows Driver installer, but isn't able to be used by Linux. Not sure if that is anything wrong with the driver though.