[SOLVED] Issues with network drivers

digitalpetra · 2024-06-09 13:48:50

Dear arch community,

after a couple of days of browsing for help and following guides regarding a pacman rescue, I figured out how to recover from a partial upgrade. At first my system was struggling with libicuuc.so.74 being replaced with 75. Basically I was stuck on the kernel loading console.

So I had to:
1. boot on archiso USB
2. mount the root and boot folders to respectively /mnt and /mnt/boot
3. proceed to a pacman -Syu by arch-chroot into /mnt
4. and finally reinstalling ‘mkinitcpio systemd linux’ all together (before exit umount and rebooting)

This was successful. Now I can get back to logging in and accessing to my DE and WM. But now I encounter one last issue, because I lack knowledge in the fields of access & permissions, systemctl, and firmware management: I can’t see eth0 or wlan0 in my NetworkManager. And rfkill outputs : “cannot open /dev/rfkill: no such file or directory”.

Since I have followed several guides and run commands, I don’t know which step I’ve missed or at which point of my recover I am. I went back to archiso to install linux-firmware package.

I’m on my phone because I really can’t access any network with my laptop (Dell xps 13 9350 with BCM4350 nw controller).

Can anybody help me with the next commands to run ?
When I do lspci -v I can se the Network Controller but no drivers mentionned.

Last edited by digitalpetra (2024-06-09 16:11:41)

seth · 2024-06-09 14:01:47

pacman -Qs kernel
uname -a
cat /proc/cmdline

A typical cause would be that the installed and booting driver fall apart and a typical cause for that is to forget to mount the /boot partition when installing/updatign the kernel.
Edit: the above is pointless from the installation iso, run it on the installed system. No chroot.

Last edited by seth (2024-06-09 14:02:19)

digitalpetra · 2024-06-09 14:10:24

seth wrote:

pacman -Qs kernel
uname -a
cat /proc/cmdline
A typical cause would be that the installed and booting driver fall apart and a typical cause for that is to forget to mount the /boot partition when installing/updatign the kernel.
Edit: the above is pointless from the installation iso, run it on the installed system. No chroot.

Thank you !
Now that I run these commands, what should I check ?

seth · 2024-06-09 14:11:37

You compare the kernel versions for a mismatch and the relative path to see where the initramfs resides to know whether you're currently booting from a dedicated partition.
Edit: those commands are for diagnostic output - they won't fix anything.

Last edited by seth (2024-06-09 14:12:10)

digitalpetra · 2024-06-09 14:23:30

seth wrote:

You compare the kernel versions for a mismatch and the relative path to see where the initramfs resides to know whether you're currently booting from a dedicated partition.
Edit: those commands are for diagnostic output - they won't fix anything.

Ok I see !

So in the pacman query I’ve got a lot of results that would take me very long to copy on the phone haha but linux kernel is:
6.9.3.arch1-1

uname -a is :
6.8.9.arch1-1

We can already see a difference… and quite a big one actually !

and the cmdline says :
BOOT_IMAGE=/boot/vmlinuz-linux
followed by root=UUID=<looooong uuid> rw loglvl=3 quiet

Now I’m wondering how can I harmonize that without using archiso because it seems to be the best way to access the network.

seth · 2024-06-09 14:46:35

You're bootign an old kernel from the root partition, ie. it's rather that you likely mounted a spurious /boot partition into place

I’m wondering how can I harmonize that without using archiso

You can't and you don't have to.
Boot the iso, chroot into the system, make sure to NOT boot any kind of boot partition and re-install the kernel.

digitalpetra · 2024-06-09 16:10:40

seth wrote:

You're bootign an old kernel from the root partition, ie. it's rather that you likely mounted a spurious /boot partition into place
I’m wondering how can I harmonize that without using archiso
You can't and you don't have to.
Boot the iso, chroot into the system, make sure to NOT boot any kind of boot partition and re-install the kernel.

Thank you very much for your help seth !

It's all working perfectly.

Arch Linux

#1 2024-06-09 13:48:50

[SOLVED] Issues with network drivers

#2 2024-06-09 14:01:47

Re: [SOLVED] Issues with network drivers

#3 2024-06-09 14:10:24

Re: [SOLVED] Issues with network drivers

#4 2024-06-09 14:11:37

Re: [SOLVED] Issues with network drivers

#5 2024-06-09 14:23:30

Re: [SOLVED] Issues with network drivers

#6 2024-06-09 14:46:35

Re: [SOLVED] Issues with network drivers

#7 2024-06-09 16:10:40

Re: [SOLVED] Issues with network drivers

Board footer