[00:02] eeeeee [00:02] alguien aqui [00:04] sandroestaproban, try #lubuntu-es [00:04] como [00:04] "/join #lubuntu-es" [00:04] pon ese codigo son las comillas [00:04] en el cuadro [00:05] gracias === FrankF1 is now known as FrankF === danwe1 is now known as danwe === macc24_ is now known as macc24 === p4ngk3p is now known as vangkep [15:42] hey guys, wifi is disconnecting every 20' or so, unless I manually `run sudo service network-manager restart` [15:42] I'm pretty sure that's not the way to go. Any ideas? === lubuntu is now known as Guest33185 [17:10] santimir[m]: check your logs about it: journalctl -b are the full logs since boot (maybe start at the bottom there), journalctl -k are just kernel events. press q to quit. you're looking for something about network-manager (abbreviated 'nm'), or something specific to your wireless driver. which driver you have dpeends on which hardware you have. you can determine the hardware using lspci -knn | grep -EA3 '(Network|Ethernet) [17:10] controller' | nc termbin.com 9999 [17:10] santimir[m]: the last bit again (it hit the line break): you can determine the hardware using lspci -knn | grep -EA3 '(Network|Ethernet) controller' | nc termbin.com 9999 [18:19] how to turn off the monitor after xtrlock ? try using xset dpms force off but still the monitor up in a while https://askubuntu.com/questions/7295/how-to-turn-off-the-display-via-the-command-line [19:19] hummmm [19:19] algum sobrevivente da brasnet aqui? [20:32] its_Kyle was added by: its_Kyle [22:31] termbin.com/23kh [22:32] thanks, magic command [22:47] santimir[m]: so, looking at it, which one do you seem to have, and what seems to be its driver? [23:06] I don't quite follow what we're doing. I know we listed the pci devices, and I guess we need a driver/program that communicates the network card with something else? [23:06] but I believe this will be useful... [23:06] Jul 19 16:39:59 eoan NetworkManager[13758]: [1595173199.2197] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.3/0000:01:00.0/ieee80211/phy0/rfkill3) (driver rtl8821ae) [23:06] i.e is the option 1 [23:07] But i don't get why we listed ethernet as that's related to cable connections? (apologizes for the ignorance( [23:13] tomreyn: [23:16] santimir[m]: so looking at https://termbin.com/23kh you seem to have two network communication devides. [23:16] one of them is an ethernet device, so for wired networking. then the other one must be the wireless one, which is causing problems. [23:17] the wireless one is a "Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]" [23:17] the driver being used for it is rtl8821ae [23:18] on some kernel versions, and sometimes on most kernel versions, some wireless chipsets do not work well, or at all. [23:18] yours seems to not work well. maybe this is a generic problem with your driver on this kernel version. which ubuntu and kernel version are you running there? [23:19] nc termbin.com 9999 < <(lsb_release -ds;cat /proc/{version,cmdline};echo "Session: $XDG_CURRENT_DESKTOP ($XDG_SESSION_TYPE)";echo Shell: $SHELL) [23:20] 20.04, and uname -r outputs 5.4.0-40-generic [23:21] I can run the command if it's necessary [23:22] found this post: https://medium.com/@elmaxx/rtl8821ae-wifi-drivers-in-ubuntu-16-04-4c1286524afa [23:22] but they the git repo isn't there anymore [23:32] santimir[m]: i can't seemto find a better driver than the one integrated into your linux version. if you like, post the logs and i can have a look at what's failing. [23:32] the log line you posted earlier does not help [23:32] journalctl -b | nc termbin.com 9999