Help: chroot and network problem

Hello. I am trying to fix a broken update with chroot through live media. I have internet access in the live media, I can ping google, but when I chroot into my existing installation to update it again, I just can't connect and ping www.google doesn't work. I'm really stuck. And I can't establish a cable connection at the moment, in case it's needed. What should I do?!

if you loose wifi juste after upgraded ,
it means drivers network ( or networkmanager ) breaks it

did you added other kernel linux , before trouble network ?

can you report

inxi -Fxxxz

No I didn't.

2v kernel 12bus ID 00:14.2 
           12chip ID 1022:780d 
           12Sound Server ALSA 12v k4.9.20-1-MANJARO 
12Network:   12Device-1 Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 12vendor Lenovo 
           12driver r8169 12v 2.3LK-NAPI 12port 2000 12bus ID 02:00.0 12chip ID 10ec:8168 
           12IF enp2s0 12state down 12mac <filter> 
           12Device-2 Realtek RTL8723BE PCIe Wireless Network Adapter 12vendor Lenovo 12driver rtl8723be 
           12v kernel 12port 1000 12bus ID 03:00.0 12chip ID 10ec:b723 
           12IF wlp3s0 12state up 12mac <filter> 
12Drives:    12Local Storage 12total 935.26 GiB 12used 228.94 GiB (24.5%) 
           12ID-1 /dev/sda 12vendor Seagate 12model ST1000LM014-SSHD-8GB 12size 931.51 GiB 12speed 6.0 Gb/s 
           12serial <filter> 
           12ID-2 /dev/sdb 12type USB 12model 058f USB Disk 12size 3.75 GiB 12serial <filter>

reboot with USB install key
open a terminal

manjaro-chroot -a
pacman -Syy ( check for network )
mhwd-kernel -i linux418
exit ( quit chroot )

on reboot press Esc and choose in Details good kernel

1 Like

This adapter has very big problems in Manjaro. There have probably been more help requests with this adapter than most any others. Were you using the kernel driver or a proprietary driver installed from elsewhere.

Sorry to interrupt you at work @stephane

My suggestion would be to walk him through an install of kernel 4.18 if he has it in his pacman cache.
I'm thinking a kernel update broke this driver again.

Kernel 4.18 was working with this adapter and it wouldn't have received any backports as it's EOL, so it still may work.

edit

Is that output current, because now that I look again, it says the adapter is "up".

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by