Hello,
I have a Dell Vostro 3550 laptop with Realtek network card, at home I connect via hotspot with my Xiaomi Redmi Note 4 phone. In this last period I have problems with the unstable connection and I immediately blamed my telephone provider since Part of the time the connection is unstable between 15:30 and 17:30. However, a few days ago I noticed that on my phone, which I use as a router, the connection is stable while on the PC, with Manjaro up-to-date, it goes and comes back, forcing me to restart the hotspot on the phone or the PC Wifi and in doing so I return to normal. What I don’t understand is if the problem is the laptop’s network card, the phone or the internet provider. And worse, I can’t even figure out what I could do. With Windows 10 Pro, in dual boot with Manjaro, the problem is less serious but it exists. The Kernel in use in the system is 5.4.184-1.
Thank you if someone can give me a light! Thank you
r8169 is an in-tree kernel driver that supports a few Ethernet adapters including R8168.
r8168 module built from source provided by Realtek.
In some cases new adapters don’t get good support by Linux kernel immediately after they are released. In that case using r8168 makes sense as a temporary solution till Linux driver is fixed.
So if your Ethernet adapter works well, then there is no need to install r8168. People get problems if they install r8169-dkms and forget about it. Later they get a kernel upgrade to another major version and the driver doesn’t build.
Grazie, avevo installato il r8169aspm-dkms e poi ho disinstallato e installato r8168-dkms. Secondo te dovrei cambiare Kernel? Adesso sto usando 5.4.184-1.
Thanks, I had installed the r8169aspm-dkms and then I uninstalled and installed the r8168-dkms. Do you think I should change Kernel? I am now using 5.4.184-1.
Hi, it seems to me that the connection is going better now, but I would like to understand how I can be sure that the installed driver is actually installed and running. Thank you.
Now, here’s the thing. I don’t know if the driver shows differently for the two drivers. Because they are different, but also the same. I know, I know. I’m king of making sense.
Anyway, this:
Looks the same as the previous one:
So I don’t know. Although, if it is better, as you mentioned, I’m guessing it is, indeed, the other, or a different one.
Although, I have in the meantime come across this page, that explains:
r8169 is an in-tree kernel driver that supports a few Ethernet adapters including R8168.
r8168 module built from source provided by Realtek.
So, you are welcome to rather try that instead. To do so, first remove the r8169aspm-dkms driver:
sudo pamac build r8168-dkms 1 ✘ 5s
Avviso: Building packages as dynamic user
Avviso: Preparazione directory di costruzione in /var/cache/pamac
Preparazione...
Controllo delle dipendenze di r8168-dkms in corso...
Avviso: r8168-dkms-8.049.02-2 è aggiornato ma sarà reinstallato
Risoluzione delle dipendenze...
Controllo conflitti tra i pacchetti...
Da costruire (1):
r8168-dkms 8.049.02-2 AUR
Modifica file di costruzione : [e]
Applica la transazione ? [e/s/N] s
Clonazione r8168-dkms file di costruzione in corso...
Running as unit: run-u267.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 922ms
CPU time consumed: 103ms
Creazione informazioni r8168-dkms...
Running as unit: run-u268.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 3.091s
CPU time consumed: 3.578s
Costruzione in corso di r8168-dkms...
Running as unit: run-u269.service
Press ^] three times within 1s to disconnect TTY.
==> Creazione del pacchetto: r8168-dkms 8.049.02-2 (mar 5 apr 2022, 17:25:27)
==> Controllo delle dipendenze durante l'avvio in corso...
==> Controllo delle dipendenze durante la compilazione in corso...
==> Download dei sorgenti in corso...
-> Clonazione del repository r8168-dkms git in corso...
Clone nel repository spoglio '/var/cache/private/pamac/r8168-dkms/r8168-dkms' in corso...
remote: Enumerating objects: 249, done.
remote: Counting objects: 100% (28/28), done.
remote: Compressing objects: 100% (24/24), done.
remote: Total 249 (delta 8), reused 11 (delta 4), pack-reused 221
Ricezione degli oggetti: 100% (249/249), 689.05 KiB | 588.00 KiB/s, fatto.
Risoluzione dei delta: 100% (156/156), fatto.
-> Download di linux517.patch in corso...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1308 100 1308 0 0 2259 0 --:--:-- --:--:-- --:--:-- 2259
-> È stato trovato dkms.conf
==> Validazione di source file con sha256sums...
r8168-dkms ... Ignorato
linux517.patch ... Verificato
dkms.conf ... Verificato
==> Rimozione dell'esistente directory $srcdir/ in corso...
==> Estrazione dei sorgenti in corso...
-> Creazione di una copia di lavoro del repository r8168-dkms git in corso...
Clone in 'r8168-dkms' in corso...
fatto.
==> Avvio di prepare() in corso...
patching file src/r8168_n.c
==> Entro nell'ambiente fakeroot...
==> Avvio di package() in corso...
==> Rimozione dei dati superflui in corso...
-> Rimozione dei file libtool in corso...
-> Eliminazione dei file indesiderati in corso...
-> Rimozione dei file dalle librerie statiche...
-> Rimozione dei simboli non necessari dai binari e dalle librerie in corso...
-> Compressione delle pagine man ed info in corso...
==> Controllo per il rilascio dei pacchetti in corso...
==> Creazione del pacchetto "r8168-dkms" in corso...
-> Generazione del file .PKGINFO in corso...
-> Generazione del file .BUILDINFO in corso...
-> Aggiunta del file install in corso...
-> Creazione del file .MTREE in corso...
-> Compressione del pacchetto in corso...
==> Uscita dall'ambiente di fakeroot.
==> Compilazione terminata: r8168-dkms 8.049.02-2 (mar 5 apr 2022, 17:25:34)
==> Pulizia in corso...
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 9.695s
CPU time consumed: 8.231s
Running as unit: run-u270.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 2.603s
CPU time consumed: 3.015s
Controllo portachiavi... [1/1]
Verifico l'integrità dei pacchetti... [1/1]
Caricamento dei file dei pacchetti... [1/1]
Controllo conflitti tra file... [1/1]
Controllo spazio disponibile su disco... [1/1]
Esecuzione pre-transaction hooks...
Creating Timeshift snapshot before upgrade... [1/2]
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
Remove upgraded DKMS modules [2/2]
==> dkms remove r8168/8.049.02
Reinstallazione r8168-dkms (8.049.02-2)... [1/1]
Creating symlink /var/lib/dkms/r8168/8.049.02/source -> /usr/src/r8168-8.049.02
==> The module r8168 conflicts with r8169. You can blacklist it with:
==> echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf
Esecuzione post-transaction hooks...
Arming ConditionNeedsUpdate... [1/2]
Install DKMS modules [2/2]
==> ERROR: Missing opt kernel headers for module r8168/8.049.02.
==> ERROR: Missing lib kernel headers for module r8168/8.049.02.
==> ERROR: Missing sbin kernel headers for module r8168/8.049.02.
==> ERROR: Missing mnt kernel headers for module r8168/8.049.02.
==> ERROR: Missing var kernel headers for module r8168/8.049.02.
==> ERROR: Missing rootfs-pkgs.txt kernel headers for module r8168/8.049.02.
==> ERROR: Missing bin kernel headers for module r8168/8.049.02.
==> ERROR: Missing boot kernel headers for module r8168/8.049.02.
==> ERROR: Missing run kernel headers for module r8168/8.049.02.
==> ERROR: Missing usr kernel headers for module r8168/8.049.02.
==> ERROR: Missing timeshift kernel headers for module r8168/8.049.02.
==> ERROR: Missing proc kernel headers for module r8168/8.049.02.
==> ERROR: Missing desktopfs-pkgs.txt kernel headers for module r8168/8.049.02.
==> ERROR: Missing root kernel headers for module r8168/8.049.02.
==> ERROR: Missing lost+found kernel headers for module r8168/8.049.02.
==> ERROR: Missing etc kernel headers for module r8168/8.049.02.
==> ERROR: Missing srv kernel headers for module r8168/8.049.02.
==> ERROR: Missing tmp kernel headers for module r8168/8.049.02.
==> ERROR: Missing lib64 kernel headers for module r8168/8.049.02.
==> ERROR: Missing home kernel headers for module r8168/8.049.02.
==> ERROR: Missing sys kernel headers for module r8168/8.049.02.
==> ERROR: Missing dev kernel headers for module r8168/8.049.02.
Transazione completata con successo.