Something messed up with my laptop and it lost functionality to access the internet, to which I connected my old adaptor in and it wasn’t working.My friend tried to fix the problem but couldn’t, and now there’s 2 wifi networks. (wlan0 and wlp2s0). When wlp2s0 disappeared for a moment I was able to connect to wlan0 for about an hour but then it disconnected again and now when I try to connect wlan0 it deactivates, tries to connect to wlp2s0, and fails
Apologies in advance, this is my first time posting in a forum and I’m still getting used to Linux
1 Like
Update, now the normal network appears instead of the two but I still can’t connect lol
cscs
14 November 2021 18:51
3
Hi there … best to start here:
Welcome to Manjaro!
To allow all of us helpful people on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly.
Someone else probably linked you to this tutorial, so if you’re reading this in response to a question, please click the link above this text to bring you to the full and unabridged text of the tutorial…
Kernel: 5.15.2-2-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=a1879eb5-3902-41a1-afe7-76e0ffd88393 rw quiet apparmor=1
security=apparmor resume=UUID=46a7b5c6-4f03-4f8f-9145-0c3ef7db6eda
udev.log_priority=3
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: HP product: HP Laptop 17-by0xxx v: Type1ProductConfigId
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: HP model: 84CA v: KBC Version 74.19 serial: <filter> UEFI: Insyde
v: F.05 date: 04/09/2018
Battery:
ID-1: BAT0 charge: 31.3 Wh (100.0%) condition: 31.3/31.3 Wh (100.0%)
volts: 13.0 min: 11.6 model: HP Primary type: Li-ion serial: <filter>
status: Full
Memory:
RAM: total: 7.65 GiB used: 3.06 GiB (40.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP
arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: A (10)
microcode: EA cache: L2: 6 MiB bogomips: 28808
Speed: 700 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 700 2: 700 3: 700
4: 700 5: 700 6: 700 7: 700 8: 700
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon art
avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid
cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb erms est f16c flush_l1d
fma fpu fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor
movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
syscall tm tm2 tsc tsc_adjust tsc_deadline_timer vme x2apic xgetbv1 xsave
xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915
v: kernel bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver:
loaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1280x720 s-dpi: 96 s-size: 337x190mm (13.3x7.5")
s-diag: 387mm (15.2")
Monitor-1: HDMI-1 res: 1280x720 hz: 60 dpi: 2032 size: 16x9mm (0.6x0.4")
diag: 18mm (0.7")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.2.2
direct render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
chip-ID: 8086:9d71 class-ID: 0403
Sound Server-1: ALSA v: k5.15.2-2-MANJARO running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.35 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 4000 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp1s0 state: down mac: <filter>
Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
vendor: Hewlett-Packard driver: rtw_8822be v: N/A modules: rtw88_8822be
port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:b822 class-ID: 0280
IF: wlp2s0 state: down mac: <filter>
Device-3: TP-Link 802.11ac NIC type: USB driver: rtl88x2bu bus-ID: 1-3:18
chip-ID: 2357:0138 class-ID: 0000 serial: <filter>
IF: wlan0 state: down mac: <filter>
IF-ID-1: enp0s20f0u1 state: unknown speed: -1 duplex: half mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
WAN IP: <filter>
Bluetooth:
Device-1: Samsung Galaxy series misc. (tethering mode) type: USB
driver: rndis_host v: kernel bus-ID: 1-1:21 chip-ID: 04e8:6863
class-ID: 0a00 serial: <filter>
Report: This feature requires one of these tools: hciconfig/bt-adapter
Device-2: Realtek Realtek Bluetooth 4.2 Adapter type: USB driver: btusb
v: 0.8 bus-ID: 1-8:3 chip-ID: 0bda:b00b class-ID: e001 serial: <filter>
Report: ID: hci0 rfk-id: 1 state: up address: N/A
Logical:
Message: No logical block device data found.
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: 5060 bus-ID: 00:17.0 chip-ID: 8086.282a rev: 21 class-ID: 0104
Drives:
Local Storage: total: 931.51 GiB used: 125.43 GiB (13.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10JPCX-24UE4T0
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 5400 serial: <filter> rev: 1A01 scheme: GPT
Optical-1: /dev/sr0 vendor: hp model: DVDRW DA8AESH rev: XH6M
dev-links: cdrom
Features: speed: 24 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r state: running
Partition:
ID-1: / raw-size: 300 GiB size: 294.23 GiB (98.08%) used: 125.34 GiB (42.6%)
fs: ext4 dev: /dev/sda7 maj-min: 8:7 label: N/A
uuid: a1879eb5-3902-41a1-afe7-76e0ffd88393
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%)
used: 36.6 MiB (14.5%) fs: vfat dev: /dev/sda2 maj-min: 8:2 label: N/A
uuid: 29A7-9777
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8 GiB used: 50.8 MiB (0.6%) priority: -2
dev: /dev/sda6 maj-min: 8:6 label: N/A
uuid: 46a7b5c6-4f03-4f8f-9145-0c3ef7db6eda
Unmounted:
ID-1: /dev/sda1 maj-min: 8:1 size: 300 MiB fs: ntfs label: Recovery
uuid: D22662912662767F
ID-2: /dev/sda3 maj-min: 8:3 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-3: /dev/sda4 maj-min: 8:4 size: 622.37 GiB fs: ntfs label: N/A
uuid: C0B866A5B8669A24
ID-4: /dev/sda5 maj-min: 8:5 size: 553 MiB fs: ntfs label: N/A
uuid: C67C1B7A7C1B6509
USB:
Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0
speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 1-1:21 info: Samsung Galaxy series misc. (tethering mode)
type: Bluetooth,CDC-Data driver: rndis_host interfaces: 2 rev: 2.0
speed: 480 Mb/s power: 500mA chip-ID: 04e8:6863 class-ID: 0a00
serial: <filter>
Device-2: 1-2:19 info: Logitech Unifying Receiver type: Keyboard,Mouse
driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s
power: 98mA chip-ID: 046d:c534 class-ID: 0301
Device-3: 1-3:18 info: TP-Link 802.11ac NIC type: Network driver: rtl88x2bu
interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 500mA chip-ID: 2357:0138
class-ID: 0000 serial: <filter>
Device-4: 1-8:3 info: Realtek Realtek Bluetooth 4.2 Adapter type: Bluetooth
driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 500mA
chip-ID: 0bda:b00b class-ID: e001 serial: <filter>
Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.0 speed: 5 Gb/s
chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
System Temperatures: cpu: 36.0 C mobo: 0.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 239 Uptime: 4h 7m wakeups: 1 Init: systemd v: 249 tool: systemctl
Compilers: gcc: 11.1.0 Packages: pacman: 1386 lib: 421 flatpak: 0 Shell: Zsh
v: 5.8 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06```
What do I do now?
cscs
14 November 2021 19:17
5
I suppose those are the 2 … any idea which you prefer? They are both a bit problematic.
If we want to test out the rtw_8822be
first you could try this:
Edit /etc/default/grub
line GRUB_CMDLINE_LINUX
to contain the following:
pcie_aspm.policy=performace
so it looks like (assuming no others are there):
GRUB_CMDLINE_LINUX="pcie_aspm.policy=performace"
Then run
sudo update-grub
And reboot.
You may want to remove the other card if that is simple enough.
Otherwise we could disable it with modprobe or similar.
I do not know what you mean by which I prefer, I only have 1 adapter plugged in, and the built-in one for the laptop which doesn’t work
I’ll give that a shot though
cscs
14 November 2021 19:25
7
Yeah all the better to start with trying to work out the internal since we can remove the USB.
When finished, assuming its not working still, please return again:
inxi -Nazy
It’s not working still, so-
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 4000 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
vendor: Hewlett-Packard driver: rtw_8822be v: N/A modules: rtw88_8822be
port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:b822 class-ID: 0280
Device-3: TP-Link 802.11ac NIC type: USB driver: rtl88x2bu bus-ID: 1-3:4
chip-ID: 2357:0138 class-ID: 0000 serial: <filter>```
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 10:62:e5:58:32:b3 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
link/ether 90:32:4b:20:26:b3 brd ff:ff:ff:ff:ff:ff
5: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether 98:48:27:60:c3:70 brd ff:ff:ff:ff:ff:ff
6: enp0s20f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 16:3a:1a:e0:97:ed brd ff:ff:ff:ff:ff:ff
cscs
14 November 2021 19:44
11
sudo modprobe rtw88_8822be && sudo ip link set enp1s0 up
anything there?
(PS - even with the extra usb the output of 6 here is a bit odd)
1 Like
modprobe: FATAL: Module rtw_8822be not found in directory /lib/modules/5.15.2-2-MANJARO
(PS, I have no idea other than the fact it’s tethered to my phone)
cscs
14 November 2021 19:49
13
Ah that could make sense.
Could you also try an earlier LTS kernel?
Like 5.10 ?
I can, it may take awhile though as my tethered connection is a few bits per second
I have 5.12.19-1 if that works
cscs
14 November 2021 19:52
16
Sadly its EOL … so it may be worth a try since its already installed … but I think 5.10 is the way to go, especially with the modules and all.
Is 5.10.79-1 fine? Idk if there’s a difference between this and what you mention, but I do have this one
cscs
14 November 2021 19:55
18
Oh already installed? Then yes please just drop to that one from a reboot.
(hit shift to pull up grub and select kernel)
But this talk makes me wonder … is the system up to date? Or avoided because of this situation?
I haven’t used this laptop in 3 months, I haven’t fully updated everything due to the internet problem yeah
I’ll boot into the older version
cscs
14 November 2021 20:00
20
When you do … can we get an output of the full inxi again (make sure the boot param is applied, etc)
inxi -Fazy