You are not logged in.

#1 2021-03-03 06:09:56

horo
Member
Registered: 2016-03-13
Posts: 47

ugh.. Realtek issues

Hello. I recently purchased a new laptop to replace my old workhorse that is falling apart. I live booted into the latest Lithium build but found I had no WIFI capabilities. The laptop does not have an ether cable jack and is WIFI only.
My hopes are to figure out how to fix this, alter the live boot to confirm everything is working, then install Lithium. If this can't be done, I have about 30 days to get my money back on the laptop and try another model, but my budget is tight so I would rather not go that route.

Here's what I know so far-
Laptop- HP 14-dq0005cl

the laptop case is marked with the following:
Realtek Radio Model: RTL8822CE
FC ID: TX2-RTL8822CE

some useful commands-

uname -rv
4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28)

lspci -knn | grep -EiA2 net
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:c822]
	Subsystem: Hewlett-Packard Company Device [103c:85f7]

sudo dmesg|grep -Ei 'wlan|firmw|dhc'
[    3.433316] sdhci: Secure Digital Host Controller Interface driver
[    3.433317] sdhci: Copyright(c) Pierre Ossman
[    3.438711] sdhci-pci 0000:00:1c.0: SDHCI controller found [8086:31cc] (rev 3)
[    3.439292] mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
[    3.544866] [drm] GuC: No firmware known for this platform!
[    3.544867] [drm] HuC: No firmware known for this platform!
[    3.546130] i915 0000:00:02.0: firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[    3.546427] [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4)
[    9.851049] Bluetooth: hci0: RTL: rtl: assuming no firmware upload needed
[  885.348498] (NULL device *): firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[  886.709484] Bluetooth: hci0: RTL: rtl: assuming no firmware upload needed
[ 1027.282686] (NULL device *): firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[ 1028.779928] Bluetooth: hci0: RTL: rtl: assuming no firmware upload needed

sudo cat /var/log/syslog |grep -Ei 'net|wpa|dhc'
Mar  2 19:42:13 localhost systemd[1]: Starting Raise network interfaces...
Mar  2 19:42:13 localhost systemd[1]: Started Raise network interfaces.
Mar  2 19:42:13 localhost systemd[1]: Starting Network Manager...
Mar  2 19:42:13 localhost systemd[1]: Starting WPA supplicant...
Mar  2 19:42:13 localhost kernel: [    0.578129] NET: Registered protocol family 16
Mar  2 19:42:13 localhost kernel: [    0.578351] audit: initializing netlink subsys (disabled)
Mar  2 19:42:13 localhost kernel: [    0.782320] NET: Registered protocol family 2
Mar  2 19:42:13 localhost kernel: [    0.783293] NET: Registered protocol family 1
Mar  2 19:42:13 localhost kernel: [    0.783304] NET: Registered protocol family 44
Mar  2 19:42:13 localhost kernel: [    3.151403] NET: Registered protocol family 10
Mar  2 19:42:13 localhost kernel: [    3.172624] NET: Registered protocol family 17
Mar  2 19:42:13 localhost kernel: [    3.433316] sdhci: Secure Digital Host Controller Interface driver
Mar  2 19:42:13 localhost kernel: [    3.433317] sdhci: Copyright(c) Pierre Ossman
Mar  2 19:42:13 localhost kernel: [    3.438711] sdhci-pci 0000:00:1c.0: SDHCI controller found [8086:31cc] (rev 3)
Mar  2 19:42:13 localhost kernel: [    3.439292] mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
Mar  2 19:42:13 localhost kernel: [    9.740207] NET: Registered protocol family 31
Mar  2 19:42:13 localhost systemd[1]: Started WPA supplicant.
Mar  2 19:42:13 localhost wpa_supplicant[793]: Successfully initialized wpa_supplicant
Mar  2 19:42:13 localhost NetworkManager[791]: <info>  [1614714133.9147] NetworkManager (version 1.14.6) is starting... (for the first time)
Mar  2 19:42:13 localhost NetworkManager[791]: <info>  [1614714133.9148] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Mar  2 19:42:13 localhost systemd[1]: Started Network Manager.
Mar  2 19:42:13 localhost NetworkManager[791]: <info>  [1614714133.9204] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Mar  2 19:42:13 localhost systemd[1]: Starting Network Manager Wait Online...
Mar  2 19:42:13 localhost systemd[1]: Reached target Network.
Mar  2 19:42:13 localhost systemd[1]: Starting Network Time Service...
Mar  2 19:42:13 localhost NetworkManager[791]: <info>  [1614714133.9426] manager[0x5610e55c8030]: monitoring kernel firmware directory '/lib/firmware'.
Mar  2 19:42:13 localhost NetworkManager[791]: <info>  [1614714133.9427] monitoring ifupdown state file '/run/network/ifstate'.
Mar  2 19:42:13 localhost dbus-daemon[790]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.6' (uid=0 pid=791 comm="/usr/sbin/NetworkManager --no-daemon ")
Mar  2 19:42:14 localhost systemd[1]: Started Network Time Service.
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.1900] hostname: hostname: using hostnamed
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.1900] hostname: hostname changed from (none) to "debian"
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.1919] dns-mgr[0x5610e55d40f0]: init: dns=default, rc-manager=resolvconf
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.1927] manager[0x5610e55c8030]: rfkill: WiFi hardware radio set enabled
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.1927] manager[0x5610e55c8030]: rfkill: WWAN hardware radio set enabled
Mar  2 19:42:14 localhost dbus-daemon[790]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=791 comm="/usr/sbin/NetworkManager --no-daemon ")
Mar  2 19:42:14 localhost systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar  2 19:42:14 localhost systemd[1]: Started Network Manager Script Dispatcher Service.
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2705] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2705] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2706] ifupdown: management mode: unmanaged
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2706] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown.so")
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2706] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2800] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2801] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2802] manager: Networking is enabled by state file
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2804] dhcp-init: Using DHCP client 'dhclient'
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.2852] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-adsl.so)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.3423] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-bluetooth.so)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4002] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-team.so)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4117] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wifi.so)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4121] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wwan.so)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4186] device (lo): carrier: link connected
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4190] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4255] manager: startup complete
Mar  2 19:42:14 localhost NetworkManager[791]: <info>  [1614714134.4281] modem-manager: ModemManager available
Mar  2 19:42:14 localhost systemd[1]: Started Network Manager Wait Online.
Mar  2 19:42:14 localhost systemd[1]: Reached target Network is Online.
Mar  2 19:42:15 localhost systemd[920]: Listening on GnuPG network certificate management daemon.
Mar  2 19:42:24 localhost systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mar  2 19:42:28 localhost NetworkManager[791]: <info>  [1614714148.4669] agent-manager: req[0x5610e55ff940, :1.32/org.freedesktop.nm-applet/1000]: agent registered
Mar  2 19:56:20 localhost systemd[1392]: Listening on GnuPG network certificate management daemon.
Mar  2 19:56:42 localhost NetworkManager[791]: <info>  [1614715002.5843] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar  2 19:56:42 localhost NetworkManager[791]: <info>  [1614715002.5843] manager: NetworkManager state is now ASLEEP
Mar  2 20:15:39 localhost NetworkManager[791]: <info>  [1614716139.1972] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Mar  2 20:15:39 localhost NetworkManager[791]: <info>  [1614716139.1973] manager: NetworkManager state is now DISCONNECTED
Mar  2 20:15:53 localhost systemd[1392]: Closed GnuPG network certificate management daemon.
Mar  2 20:17:59 localhost NetworkManager[791]: <info>  [1614716279.5923] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar  2 20:17:59 localhost NetworkManager[791]: <info>  [1614716279.5924] manager: NetworkManager state is now ASLEEP
Mar  2 21:01:14 localhost NetworkManager[791]: <info>  [1614718874.1804] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Mar  2 21:01:14 localhost NetworkManager[791]: <info>  [1614718874.1804] manager: NetworkManager state is now DISCONNECTED
Mar  2 21:01:17 localhost systemd[1629]: Listening on GnuPG network certificate management daemon.
Mar  2 21:02:07 localhost systemd[1629]: Closed GnuPG network certificate management daemon.
Mar  2 21:15:59 localhost systemd[1714]: Listening on GnuPG network certificate management daemon.
Mar  2 21:33:58 localhost systemd[1714]: Closed GnuPG network certificate management daemon.

lsusb|grep Realtek
Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp.

I have also found the following git projects of note
https://github.com/juanro49/rtl88x2ce-dkms
https://github.com/bserem/Realtek-RTL8822x-Linux

If i'm not mistaken, Lithium is shipping with kernel 4.19, while these github projects are using 5.4+

I believe my best course of action is to update the kernel, apply one of the fixes from github, then flash that onto a thumb drive and live boot to see if things are working. I have never done anything like that though and maybe am over thinking things. Any advice would be appreciated.

Offline

#2 2021-03-03 11:45:01

brontosaurusrex
Middle Office
Registered: 2015-09-29
Posts: 2,258
Website

Re: ugh.. Realtek issues

It seems to be in bullseye, if that helps
https://packages.debian.org/bullseye/firmware-realtek

Offline

#3 2021-03-03 12:46:22

sleekmason
zoom
From: Ozarks
Registered: 2018-05-22
Posts: 570
Website

Re: ugh.. Realtek issues

I'm in the same boat.  My laptop lid is hanging by a thread so I'm forced after 12 years to get another laptop. ugh.  Hoping to make it the two weeks until it arrives.

So, the only thing I wanted to offer, was that I found that 10 gen intel requires at least kernel version 5.4, and that seems to match the github patches you found as well.

To see if you can get it going, you could try the "unstable" version of 'my build' below.  No where near as complete as Bunsenlabs, but usable, and can get you up and running.
https://sourceforge.net/projects/lilido … /Releases/

My 'unstable' build 'Lilidog-Custom', is actually very stable, as it is built on stable with just the kernel and firmware from sid.  So, upgraded firmware, and kernel 5.10 as of now.

*edit - Any Debian based distro running Bullseye or sid should do for this as well.

I would think you could get BL up and running afterwards by replacing the necessary firmware from my build to BL (same stuff), and grabbing the latest kernel from backports. 

In fact, on my github is a custom kernel 5.4 that should work until you upgrade through apt. (there are others out there as well.)

Grab the kernel and headers to install through dpkg, and copying the firmware over and done!

Or if you have computer access with net, just grab the kernel and install onto Bunsenlabs through dpkg, and the firmware from an upgraded install.

Well if nothing else, maybe I sparked some ideas.)

Last edited by sleekmason (2021-03-03 13:03:24)

Offline

#4 2021-03-03 16:24:20

horo
Member
Registered: 2016-03-13
Posts: 47

Re: ugh.. Realtek issues

Found a usb-wifi dongle that works

How difficult would it be to upgrade the kernel from a fresh install? I'm thinking I'll use the dongle to get me up and running then upgrade the kernel and drivers. This should be an easier route if it works, but I would still rather test before I install over the old os

Offline

#5 2021-03-03 17:32:27

sleekmason
zoom
From: Ozarks
Registered: 2018-05-22
Posts: 570
Website

Re: ugh.. Realtek issues

Yes! good idea. Should be easy peasy.)

Uncomment or add the line for backports in / /etc/apt/sources.list.d/debian-buster-backports.list - Then apt update, and
install the latest kernel available.

You will need to add "/buster-backports" to your command like so:

sudo apt install linux-image-amd64/buster-backports

Where "linux-image-amd64" is the version you want. You can find the versions after an update with:

apt-cache search linux-image

Install the newest firmware as well. And then reboot into the new kernel. (Should now be default).


Line to add if needed.
# Debian backports

deb https://deb.debian.org/debian buster-backports main contrib non-free

per here: https://forums.bunsenlabs.org/viewtopic.php?id=6915

Last edited by sleekmason (2021-03-03 18:22:23)

Offline

#6 2021-03-03 18:04:17

sleekmason
zoom
From: Ozarks
Registered: 2018-05-22
Posts: 570
Website

Re: ugh.. Realtek issues

Updated the above to include some relevant info. Oh man. Having a day of it to be sure. Sorry about all the edits roll

Last edited by sleekmason (2021-03-03 18:23:23)

Offline

#7 2021-03-04 05:15:17

horo
Member
Registered: 2016-03-13
Posts: 47

Re: ugh.. Realtek issues

Problem-
wifi dongle works in the live session, but is not found during the installation process.

I there anyway to edit the ISO with updated kernel?

Offline

#8 2021-03-04 07:20:28

ohnonot
...again
Registered: 2015-09-29
Posts: 5,383
Website

Re: ugh.. Realtek issues

Why don't you try to get the internal wifi working first?
Have you tried getting backported firmware & possibly also kernel packages?


Please use CODE tags for code.
Search youtube without a browser: repo | thread
BL quote proposals to this thread please.
my repos / my repos

Offline

#9 2021-03-04 19:51:38

mdiemer
Member
Registered: 2021-02-25
Posts: 16

Re: ugh.. Realtek issues

horo wrote:

Found a usb-wifi dongle that works

I had the same problem with an HP notebook my wife purchased. Our plan was to trash windows 10 and install Linux, but I could not get the wifi going. It did work with a dongle. There seems to be something about HP's and Linux.

I'm going to watch this thread, as I still have hopes of liberating this machine from windows and making it Linux only.

What dongle did you use, just for the record?

Offline

#10 2021-03-05 03:06:07

horo
Member
Registered: 2016-03-13
Posts: 47

Re: ugh.. Realtek issues

Well crap.

I tried installing the system without internet and figured I knew enough CLI to get me going, but I ran into an issue with GRUB failing to install a boot loader.

There was a note saying i could manually start the system with /vmlinuz by passing root=/dev/mmcblk0 or something like that as a kernel parameter.

Kinda outa my depths here. Now that the system is installed can i use the liveboot USB to pass through the kernel upgrades? Or boot the system in a VM and run the upgrades there?

also the dongle that works for me is maked TP-link on the outside and lsusb brings up-

Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

edit::
Doing some digging, I used the guided partition feature of the text installer and it put an ESP partition at the front. This seems to be for UEFI booting, but I had to turn on Legacy mode in the BIOS to live boot. Could that be the reason GRUB failed?

edit2::
I apt-get grub2 and try to run it. got the following error

Installing for i386-pc platform.

grub-install: error: failed to get canonical path of `overlay'.
grub-probe: error: failed to get canonical path of `overlay'.

not sure why it's trying to install for i386

edit3:the editing:
should i start a new thread on this particular issue since it's larger and different than the wifi driver one?

edit4:The Return of EDIT:

OK.

So i got a live USB of Arch and used that todo a minimal Arch install. This has gotten me around the GRUB failure issue of the Lithium install. I've performed what sleekmason suggested.
I've added

deb https://deb.debian.org/debian buster-backports main contrib non-free

to /etc/apt/source.list and added

deb http://pkg.bunsenlabs.org/debian buster-backports main

to /etc/apt/sources.list.d/bunsen.list

I updated apt-get then used apt-cache to find the most likely kernel
I then installed linux-image-5.10.0.0-bpo.3-amd64 (going by memory that might be spelled wrong)
this loaded succesfully. I rebooted and ran uname -a only to find the kernel had not changed.

The good news is that Arch had the 5.11 kernel and this saw and used my onboard wifi without a hitch. I have a feeling the kernel not being update when i reboot may be a grub thing. I tried running grub-mkconfig in Arch with my Lithium partition mounted, but this did notchange things.

will work on it more later

edit5:Son of Edit:

Ok turns out grub did work right, it just had a separate sub menu with poor labeling for the kernel versions. I'm now in Lithium with 5.10 kernel! Wifi still not working, though. Look at drivers now for a solution and reviewing the github projects.

edit6:The curse of Edit:

SUCCESS! After getting the new kernel used

apt-cache policy firmware-realtek

to verify my driver versions. they where the 20200918 version from the backports repo, but google showed me that a newer 20201218-3 version was available. Why i couldn't get this version in the backport repos i don't know but i used apt-get remove to clear out the old then dled the deb file from https://pkgs.org/download/firmware-realtek

reboot and here I am on glorious WiFi 5G. i have yet to test bluetooth capabilities

Last edited by horo (2021-03-07 21:44:35)

Offline

Board footer

Powered by FluxBB