Arch linux lib modules

Arch Linux

I could not connect to neither wifi or ethernet despite the modules loading so I did a reboot and now I’m trying to modprobe ath9k :

modprobe: FATAL: Module ath9k not found in directory /lib/modules/4.7.6-1-ARCH

In my/lib/modules/ there is 4.8.3-1-ARCH and extramodules-4.8-ARCH

So why modprobe is looking for a previous version ?

#2 2016-10-27 13:05:37

Lone_Wolf Member From: Netherlands, Europe Registered: 2005-10-04 Posts: 11,087

Re: modprobe looking in wrong /lib/modules folder

compare uname -a and pacman -Q linux output .

If they don’t show the same kernel version, the kernel in your initramfs is older/different from the installed kernel .

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

#3 2016-10-27 13:14:33

Re: modprobe looking in wrong /lib/modules folder

uname -a and pacman -Q linux show different versions as predicted, should I mkinitcpio -p linux again ?

#4 2016-10-27 13:17:52

Lone_Wolf Member From: Netherlands, Europe Registered: 2005-10-04 Posts: 11,087

Re: modprobe looking in wrong /lib/modules folder

yes, but verify first if your /boot is mounted ,

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

#5 2016-10-27 13:30:00

Re: modprobe looking in wrong /lib/modules folder

I did it and /boot was mounted but when I reboot I’m still on 4.7.6-1, what did I forget ?

#6 2016-10-27 13:36:32

Lone_Wolf Member From: Netherlands, Europe Registered: 2005-10-04 Posts: 11,087

Re: modprobe looking in wrong /lib/modules folder

post lsblk -f & «mkinitcpio -p linux» output .

What bootloader are you using, is this a bios or uefi booting system ?

Last edited by Lone_Wolf (2016-10-27 13:37:17)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

#7 2016-10-27 13:37:23

Re: modprobe looking in wrong /lib/modules folder

mkinitcpio -p linux stat /boot/vmlinuz-linux /boot/initramfs-linux*

#8 2016-10-27 13:55:56

Re: modprobe looking in wrong /lib/modules folder

#9 2016-10-27 14:14:04

Re: modprobe looking in wrong /lib/modules folder

In general, please refrain from sscreenshots.
Unless your update was 7 days ago, vmlinuz-linux is most likely outdated.
Ensure /boot to be mounted and re-install the «linux» package.

#10 2016-10-27 15:26:32

Re: modprobe looking in wrong /lib/modules folder

I chrooted and updated the packages (including linux) but after a reboot it is still 4.7.6-1 .

#11 2016-10-27 15:30:37

Re: modprobe looking in wrong /lib/modules folder

chrooted? is 4.7.6-1 from booting eg. the install iso or from booting the installED system?

#12 2016-10-27 15:34:33

Re: modprobe looking in wrong /lib/modules folder

Where does your bootloader point to, what does its configuration look like? My wild guess would be you now have a /boot directory where your old kernel is, that gets opened and started by GRUB or whatever then your old kernel loads mounts the boot partition with your new kernel on but that’s already too late of course.

#13 2016-10-27 18:57:32

Re: modprobe looking in wrong /lib/modules folder

#14 2016-10-27 19:41:02

Re: modprobe looking in wrong /lib/modules folder

I just rebuilt grub with grub-mkconfig -o /boot/grub/grub.cfg but it did nothing, still on 4.7.6-1 after reboot.

#15 2016-10-28 05:22:48

Re: modprobe looking in wrong /lib/modules folder

Check if you umount /boot and there are files in /boot after that.
Check if you have /EFI /efi /boot/EFI /boot/efi directories and if there’s any of those, list the contents here.
This kernel booted from somewhere and you should know best from where.
Do you have additional hard drives or SSDs?
/etc/fstab ?

Last edited by smirky (2016-10-28 05:23:45)

Personal spot :: https://www.smirky.net/ :: Try not to get lost!

#16 2016-10-28 07:35:09

Re: modprobe looking in wrong /lib/modules folder

Direct test: «sudo mv /boot/initramfs-linux-fallback.img /boot/not-the-initramfs-linux-fallback.img», then reboot and select the failsafe variant. If that just boots, you’re not booting whatever is listed in mounted /boot 😉

#17 2016-10-28 09:10:32

Re: modprobe looking in wrong /lib/modules folder

So I just checked /boot with /boot partition unmounted and there are the usual boot files, so do I need only to remove them from / partition ?

(I am booting what’s in/boot on the root partition, not on /boot partition)

Last edited by Bmdntg (2016-10-28 09:28:31)

#18 2016-10-28 11:22:46

Re: modprobe looking in wrong /lib/modules folder

Well, you should remove them, yes.
But that doesn’t really guarantee that you’ll boot from your /boot partition the next time.
If it’s not a problem for you to test, then do it. Otherwise, cat /etc/fstab

Personal spot :: https://www.smirky.net/ :: Try not to get lost!

#19 2016-10-28 11:29:55

Re: modprobe looking in wrong /lib/modules folder

I removed all the files in /boot/ and now GRUB enters rescue mode.

Last edited by Bmdntg (2016-10-28 11:34:09)

#20 2016-10-28 11:33:40

Re: modprobe looking in wrong /lib/modules folder

Personal spot :: https://www.smirky.net/ :: Try not to get lost!

#21 2016-10-28 11:44:09

Re: modprobe looking in wrong /lib/modules folder

Then do grub-install -o /boot/grub/grub.cfg or whatever guide you followed to install grub to re-configure the bootloader.

Personal spot :: https://www.smirky.net/ :: Try not to get lost!

#22 2016-10-28 12:08:05

Lone_Wolf Member From: Netherlands, Europe Registered: 2005-10-04 Posts: 11,087

Re: modprobe looking in wrong /lib/modules folder

your fstab matches the lslbk output, but in the grub cfg you posted a UUID is used that doesn’t even occur in lsblk/fstab !

If smirky’s suggestions don’t help:

boot from liveiso, chroot , remove grub .
exit chroot
erase boot partition and recreate it .

check the installation guide and follow the instructions to setup boot partition & bootloader.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

Источник

Arch Linux

I am using linux (arch linux to be precise) for about 3-4 weeks now, and set me up a gaming VM with gpu passthrough.
Everything went pretty well, i wrote some scripts etc. and everything is running fine.

Today i wanted to upgrade my system.

This is my first post in this forum, as I am kind of depressed and out of solutions after trying to fix this problem. (Solutions means i am out of things i can try to google)

I can’t boot into my system anymore (Restored a snapshot to post this), after i used the following command to upgrade my system:

While upgrading, pacman does not give any special outputs.

After a reboot, i get the following messages:

:: running early hook [udev] warning: /lib/modules/4.16.8-1-ARCH/modules.devname not found - ignring starting version 238 :: running hook [udev] :: Triggering uevents. Waiting 10 seconds for device /dev/disk/by-partuuid/[. ] ERROR: device 'PARTUUID=[. ]' not found. Skipping fsck. mount: /new_root: can't find PARTUUID=[. ]. You are now being dropped into an emergency shell. sh: can't access tty; job control turned off [rootfs ]#

Of course i did some research, and the overall answer was:
Just boot from live, mount your partitions, arch-chroot into it, mkinitcpio -p linux

==> 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: 4.16.8-1-ARCH -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [filesystems] -> Running build hook: Arch linux lib modules -> Running build hook: [resume] -> Running build hook: [fsck] ==> 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 ==> Starting build: 4.16.8-1-ARCH -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] ==> Warning: Possibly missing firmware for module: wd719x ==> Warning: Possibly missing firmware for module: aic94xx -> Running build hook: [filesystems] -> Running build hook: Arch linux lib modules -> Running build hook: [resume] -> Running build hook: [fsck] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initamfs-linux-fallback.img ==> Image generation successful

Strange thing:
When i boot from a live ISO, mount my broken installation, arch-chroot into it and issue

the output is my old kernel. (4.16.5)

I tried to use pacman -Syu when chrooted into my system, but it just says «all packages up to date, there is nothing to do».

UUID=3ace7ab6-baac-4752-a80e-881091359045 / ext4 rw,defaults,noatime,discard 0 1 UUID=4790-7878 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2 UUID=3f4edb19-8077-4c50-8229-74bf98dfe90e none swap defaults,noatime,discard0 0 hugetlbfs /dev/hugepages/ hugetlbfs defaults 0 0

$ lsblk -f /dev/sdd1 /dev/sdd2 /dev/sd3

NAME FSTYPE LABEL UUID MOUNTPOINT sdd1 vfat 4790-7878 /boot sdd2 swap 3f4edb19-8077-4c50-8229-74bf98dfe90e [SWAP] sdd3 ext4 3ace7ab6-baac-4752-a80e-881091359045 /

# vim:set ft=sh # MODULES # The following modules are loaded before any boot hooks are # run. Advanced users may wish to specify all system modules # in this array. For instance: # MODULES=(piix ide_disk reiserfs) MODULES=(vfio_pci vfio vfio_iommu_type1 vfio_virqfd) # BINARIES # This setting includes any additional binaries a given user may # wish into the CPIO image. This is run last, so it may be used to # override the actual binaries included by a given hook # BINARIES are dependency parsed, so you may safely ignore libraries BINARIES=() # FILES # This setting is similar to BINARIES above, however, files are added # as-is and are not parsed in any way. This is useful for config files. FILES=() # HOOKS # This is the most important setting in this file. The HOOKS control the # modules and scripts added to the image, and what happens at boot time. # Order is important, and it is recommended that you do not change the # order in which HOOKS are added. Run 'mkinitcpio -H ' for # help on a given hook. # 'base' is _required_ unless you know precisely what you are doing. # 'udev' is _required_ in order to automatically load modules # 'filesystems' is _required_ unless you specify your fs modules in MODULES # Examples: ## This setup specifies all modules in the MODULES setting above. ## No raid, lvm2, or encrypted root is needed. # HOOKS=(base) # ## This setup will autodetect all modules for your system and should ## work as a sane default # HOOKS=(base udev autodetect block filesystems) # ## This setup will generate a 'full' image which supports most systems. ## No autodetection is done. # HOOKS=(base udev block filesystems) # ## This setup assembles a pata mdadm array with an encrypted root FS. ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices. # HOOKS=(base udev block mdadm encrypt filesystems) # ## This setup loads an lvm2 volume group on a usb device. # HOOKS=(base udev block lvm2 filesystems) # ## NOTE: If you have /usr on a separate partition, you MUST include the # usr, fsck and shutdown hooks. HOOKS=(base udev autodetect modconf block filesystems keyboard resume fsck) # COMPRESSION # Use this to compress the initramfs image. By default, gzip compression # is used. Use 'cat' to create an uncompressed image. #COMPRESSION="gzip" #COMPRESSION="bzip2" #COMPRESSION="lzma" #COMPRESSION="xz" #COMPRESSION="lzop" #COMPRESSION="lz4" # COMPRESSION_OPTIONS # Additional options for the compressor #COMPRESSION_OPTIONS=()

timeout 12 default arch-uefi-pass

title Arch Linux Pass linux /vmlinuz-linux initrd /intel-ucode.img initrd /initramfs-linux-pass.img options root=PARTUUID=7a63b918-a2de-432d-892c-397b61336fe4 rw intel_iommu=on iommu=pt hugepages=4608

I also tried to reinstall the kernel after i used

Does anyone have any ideas?

Last edited by Eispala (2018-05-14 18:58:06)

Источник