You are not logged in.
Hi
I'm having a weird issue since last update/upgrade
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 ?
Offline
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.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
uname -a and pacman -Q linux show different versions as predicted, should I mkinitcpio -p linux again ?
Offline
yes, but verify first if your /boot is mounted ,
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I did it and /boot was mounted but when I reboot I'm still on 4.7.6-1, what did I forget ?
Offline
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.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
What's the
mkinitcpio -p linux
stat /boot/vmlinuz-linux /boot/initramfs-linux*
output?
Offline
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.
Offline
I chrooted and updated the packages (including linux) but after a reboot it is still 4.7.6-1 ...
Offline
chrooted? is 4.7.6-1 from booting eg. the install iso or from booting the installED system?
Offline
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.
Offline
Here is my GRUB.cfg : https://paste.pound-python.org/show/Oo9 … 087kfiD4G/
Offline
I just rebuilt grub with grub-mkconfig -o /boot/grub/grub.cfg but it did nothing, still on 4.7.6-1 after reboot.
Offline
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!
Offline
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 ;-)
Offline
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)
Offline
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!
Offline
This is my fstab : https://paste.pound-python.org/show/A5I … 56HVxrUX7/
I removed all the files in /boot/ and now GRUB enters rescue mode.
Last edited by Bmdntg (2016-10-28 11:34:09)
Offline
Then reboot...
Personal spot :: https://www.smirky.net/ :: Try not to get lost!
Offline
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!
Offline
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.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I did reconfigure with grub-mkconfig but again, I'm still on rescue, there is something I do wrong, it has to do with /boot and /boot/ I think...
Offline
Ok, back to it after several month of letting the laptop in a closet, I did reformat /boot partition, (mkfs), relabel fstab, install linux-lts and now that I try to reinstall grub with
grub-install --target=i386-pc /dev/sdb1
I encounter another issue :
grub-install: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map
, I don't know where I messed up again.
Edit : I tried to grub-install on sdb1 instead of sdb
Last edited by Bmdntg (2017-02-02 17:56:33)
Offline
I did a reboot and now I have a timed out device, dependency failed for boot, local file system and file system check...
Offline