And it's not a bluetooth device

I tried sudo systemctl status NetworkManager

NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor>
  Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
           └─NetworkManager-ovs.conf
   Active: active (running) since Thu 2019-07-04 12:09:30 CEST; 2h 10min ago
     Docs: man:NetworkManager(8)
 Main PID: 2677 (NetworkManager)
    Tasks: 3 (limit: 4915)
   Memory: 8.9M
   CGroup: /system.slice/NetworkManager.service
           └─2677 /usr/sbin/NetworkManager --no-daemon

lug 04 12:09:36 BooMiki NetworkManager[2677]: <info>  [1562234976.0640] audit: op=>
lug 04 12:09:45 BooMiki NetworkManager[2677]: <info>  [1562234985.4072] audit: op=>
lug 04 12:24:43 BooMiki NetworkManager[2677]: <info>  [1562235883.8442] audit: op=>
lug 04 12:24:47 BooMiki NetworkManager[2677]: <info>  [1562235887.2475] audit: op=>
lug 04 12:35:22 BooMiki NetworkManager[2677]: <info>  [1562236522.0888] audit: op=>

Any output for lsmod | grep 8821?
Still trying to get some error info, see if sudo journalctl | grep Network shows any errors.

Ok, the first one doesn't give anything

for sudo journalctl | grep Network

ug 04 12:02:49 BooMiki kdeconnectd[746]: kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
lug 04 12:09:20 BooMiki polkit-kde-authentication-agent-1[735]: Message of action:  "Autenticazione richiesta per riavviare 'NetworkManager.service'."
lug 04 12:09:30 BooMiki kdeconnectd[746]: propsReply "Interfaccia «org.freedesktop.DBus.Properties» inesistente sull'oggetto nel percorso /org/freedesktop/NetworkManager"
lug 04 12:09:30 BooMiki kdeinit5[691]: propsReply "Interfaccia «org.freedesktop.DBus.Properties» inesistente sull'oggetto nel percorso /org/freedesktop/NetworkManager"
lug 04 12:09:30 BooMiki kdeconnectd[746]: nmReply "Interfaccia «org.freedesktop.NetworkManager» inesistente sull'oggetto nel percorso /org/freedesktop/NetworkManager"
lug 04 12:09:30 BooMiki kdeinit5[691]: nmReply "Interfaccia «org.freedesktop.NetworkManager» inesistente sull'oggetto nel percorso /org/freedesktop/NetworkManager"
lug 04 14:20:13 BooMiki sudo[11268]: siciliano : TTY=pts/0 ; PWD=/home/siciliano ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
lug 04 14:51:27 BooMiki NetworkManager[2677]: <info>  [1562244687.9677] audit: op="statistics" arg="refresh-rate-ms" pid=730 uid=1000 result="success"
lug 04 14:51:30 BooMiki NetworkManager[2677]: <info>  [1562244690.9964] audit: op="statistics" arg="refresh-rate-ms" pid=730 uid=1000 result="success"

esistente sull'oggetto nel percorso
Means "inexistent on the object of the path"

Still nothing wrong in the logs, are you trying to connect with Wifi during this session/boot or have you switched to ethernet?

I switched to Ethernet.

It worked until last night when I updated it, I turned off the notebook and when I turned it on today, it was this way.

Logs won't show anything wrong, if you use ethernet, the -b switch in the journalctl call means only output since last reboot 🙂
Though what I find everywhere is that the card you list in the first post is not supported in linux, so I do not understand how it ever worked.
To test changes in the kernel only, you can revert back to linux 5.0.9 if that is still in your cache and you have no modules depending on linux, check with pacman -Qi linux, look for the required by line. If you don't use nvidia or virtualbox, you can sudo pacman -U /var/cache/pacman/pkg/linux-5.0.9-1-x86_64.pkg.tar.xz

Oh God, do I have to test it without using ethernet?

For logs, yes you will have to use the Wifi device. To downgrade, no.

sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor>
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: active (running) since Thu 2019-07-04 18:01:39 CEST; 7min ago
Docs: man:NetworkManager(8)
Main PID: 422 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 14.8M
CGroup: /system.slice/NetworkManager.service
└─422 /usr/sbin/NetworkManager --no-daemon

lug 04 18:01:42 BooMiki NetworkManager[422]: <info> [1562256102.5997] keyfile: ad>
lug 04 18:01:42 BooMiki NetworkManager[422]: <info> [1562256102.7292] settings: (>
lug 04 18:01:42 BooMiki NetworkManager[422]: <info> [1562256102.7300] device (eno>
lug 04 18:01:43 BooMiki NetworkManager[422]: <info> [1562256103.1046] ovsdb: Impo>
lug 04 18:01:43 BooMiki NetworkManager[422]: <info> [1562256103.1063] bluez: use >
lines 1-17

I can't either downgrade it, is there something else I can do?

  • demm replied to this.

    Please make sure to get logs with actual errors, all you show so far is all perfectly working, repeat logs as I asked before, when you disable ethernet, also make sure to read https://kaosx.us/docs to give helpful info.

    ArcesilaoII I can't either downgrade it

    What does that mean? Downgrading can always be done, just a matter of wanting to.

      sudo pacman -U /var/cache/pacman/pkg/linux-5.0.9-1-x86_64.pkg.tar.xz

      Password:
      caricamento dei pacchetti in corso...
      errore: '/var/cache/pacman/pkg/linux-5.0.9-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto

      → Impossible finding or reading the package

      I re-installed Linux and it gave me those message, are they worth something?

      (1/1) reinstalling linux

      Updating module dependencies. Please wait ...

      :: Running post-transaction hooks...

      Updating linux initcpios
      ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
      ==> Starting build: 5.1.15-1
      ==> Generating module dependencies
      ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
      ==> Image generation successful
      ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
      ==> WARNING: Possibly missing firmware for module: aic94xx
      ==> WARNING: Possibly missing firmware for module: wd719x
      ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img

      Comando terminato OK!

      I think I didn't post this one before, I apologize for that

      pacman -Qi linux

      Nome : linux
      Versione : 5.1.15-1
      Descrizione : The Linux Kernel and modules
      Architettura : x86_64
      URL : http://www.kernel.org/
      Licenze : GPL2
      Gruppi : base
      Fornisce : acerhk=0.5.35 aufs3
      Dipenda da : coreutils linux-firmware kmod mkinitcpio>=0.7
      Dipendenze opzionali : crda: to set the correct wireless channels of your
      country [installato]
      → (Required by) Richiesto da : tomoyo-tools
      Opzionale per : Nessuno
      Conflitti con : acerhk
      Sostituisce : aufs3
      Spazio richiesto : 128,84 MiB
      Pacchettizzatore : Anke Boersma <demm@kaosx.us>
      Data di creazione : mar 25 giu 2019, 12:11:36
      Data di installazione : gio 4 lug 2019, 18:48:27
      Motivo dell'installazione : Installato esplicitamente
      Script di install : Sì
      Convalidato da : Somma SHA-256

      As expected, the kernel did not have the needed module, you must have done this before.....
      Please post the output ls /lib/modules
      But this is not the proper solution. As you now already noted, you forget about installing packages. Never install any outside of the package manager, you will end up with untracked files you don't remember where they came from, always use PKGBUILD/makepkg to install any.
      https://kaosx.us/docs/package/
      Example of a PKGBUILD for another RTL wifi module:
      https://github.com/KaOSx/main/blob/master/rtl8192eu/PKGBUILD

      With kernel modules like these you have to rebuild it on any kernel update, see the history for the above mentioned module

      a month later

      I apologize for the huge delay in the answer

      ls /lib/modules

      5.0.9-1/  5.1.14-1-next/  5.1.15-1/  extramodules-5.1/  extramodules-5.1-next/

      As you show, you did this before, and now have a bunch of untracked files. The manual installs did not take care of the fact that there are no longer kernels available for 5.0.9 & 5.1.14 next in KaOS.
      Make sure to follow the info from my previous post and let pacman/makepkg do the installing & tracking of any you add.