[Solved] Newly updated kernel not loading modules

Head_on_a_Stick · 2015-08-19 21:25:46

kabads wrote:

just to be sure, will it be as easy as pointing fstab to /dev/sdb1 as the boot partition?

Yes.

Check the output of `cat /proc/mounts`

JPL · 2015-08-24 15:57:24

I had this exact problem, and I think it's because the installer I used defaulted to mounting the ESP as /boot/efi, and/or because I was using gummiboot. I'm relatively new to Arch so I want to make sure I understand the fix clearly. A few questions:

1) I did my initial Arch install months ago and I've installed several kernel updates since then with no problem; did this break with the update to kernel 4.1.5 because of a change from gummiboot to its systemd equivalent, or something else?

2) Here's what the relevant bits of my fs look like:

$ ls -l /boot/
drwxr-xr-x 5 root root     1024 Dec 31  1969 efi
-rw-r--r-- 1 root root 18540754 Aug 21 10:59 initramfs-linux-fallback.img
-rw-r--r-- 1 root root  3539251 Aug 21 10:59 initramfs-linux.img
-rw-r--r-- 1 root root  4224352 Aug  3 14:32 vmlinuz-linux

$ ls -l /boot/efi
drwxr-xr-x 5 root root     1024 Jun 30 12:36 EFI
drwxr-xr-x 2 root root     1024 Jun 30 11:46 grub
-rwxr-xr-x 1 root root 18532162 Aug  4 01:05 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root  3529705 Aug  4 01:05 initramfs-linux.img
drwxr-xr-x 3 root root     1024 Jun 30 22:42 loader
-rwxr-xr-x 1 root root  4224352 Aug  3 14:32 vmlinuz-linux

And here's the line in my /etc/fstab that mounts the ESP:

UUID=288D-3C4D /boot/efi vfat defaults,rw,noatime 0 0

So clearly having the kernel in two different places is busted, and it's using the ones in /boot/efi instead of /boot. Is the fix then to simply change that /etc/fstab line to read this instead, ie make the mount point /boot instead of /boot/efi?

UUID=288D-3C4D /boot vfat defaults,rw,noatime 0 0

Last edited by JPL (2015-08-24 16:59:48)

jasonwryan · 2015-08-24 16:54:12

JPL wrote:

If so, does this reflect a bad default behavior on the part of the Antergos installer I used, and should I file a bug with their project?

Who cares? Antegros is not Arch: we only support Arch: https://wiki.archlinux.org/index.php/Fo … pport_ONLY

V1del · 2015-08-24 16:55:23

Probably a bug in their project, and it's a completely different distribution you should ask on their boards: https://wiki.archlinux.org/index.php/Fo … pport_ONLY

Edit

Got ninja'd again probably should shortcut the supportlink somewhere

Last edited by V1del (2015-08-24 16:56:12)

JPL · 2015-08-24 17:01:32

Apologies, I've edited my post and I'll be more careful about asking non-Arch support questions in the future. My two questions still stand though, any word on those?

jasonwryan · 2015-08-24 17:04:51

Did you bother to read the link I posted? We don't support your distro; so, no--there is no word on your questions as they don't stand here.

JPL · 2015-08-24 17:21:43

jasonwryan wrote:

Did you bother to read the link I posted? We don't support your distro; so, no--there is no word on your questions as they don't stand here.

I did read the link you posted, I apologized, and I will not make the same mistake again (Edit: FWIW I am going to ditch Antergos for Arch so I can get support for future issues on this forum, thank you for your patience). The two questions I asked would be valid for any Linux distro - this thread exists because an Arch user had the exact same problem - and I'm simply asking for clarification on the information already provided.

Last edited by JPL (2015-08-24 17:25:00)

kabads · 2015-08-24 18:10:40

@JPL - I fixed my problem by just switching the mount to my EFI partition for boot - it has since done a couple (I think) of kernel updates, with no issue. However, this does not mean that it will fix your distribution as that may be different from Arch - hence the lack of support on this forum for anything other than arch - here be dragons!

I really recommend you install Arch - I've been running it for over a couple of years now and only had a couple of big breakages in that time.

JPL · 2015-08-24 18:16:40

kabads wrote:

@JPL - I fixed my problem by just switching the mount to my EFI partition for boot

Ah... so again, does that mean setting the mount point to /boot instead of /boot/efi?

kabads wrote:

I really recommend you install Arch - I've been running it for over a couple of years now and only had a couple of big breakages in that time.

Absolutely, I am doing just that. Thank you!

jasonwryan · 2015-08-24 18:20:59

JPL wrote:

jasonwryan wrote:
Did you bother to read the link I posted? We don't support your distro; so, no--there is no word on your questions as they don't stand here.
I did read the link you posted, I apologized, and I will not make the same mistake again (Edit: FWIW I am going to ditch Antergos for Arch so I can get support for future issues on this forum, thank you for your patience). The two questions I asked would be valid for any Linux distro - this thread exists because an Arch user had the exact same problem - and I'm simply asking for clarification on the information already provided.

"Going to install Arch" is not the same as running Arch.

Closing

Arch Linux

#26 2015-08-19 21:25:46

Re: [Solved] Newly updated kernel not loading modules

#27 2015-08-24 15:57:24

Re: [Solved] Newly updated kernel not loading modules

#28 2015-08-24 16:54:12

Re: [Solved] Newly updated kernel not loading modules

#29 2015-08-24 16:55:23

Re: [Solved] Newly updated kernel not loading modules

#30 2015-08-24 17:01:32

Re: [Solved] Newly updated kernel not loading modules

#31 2015-08-24 17:04:51

Re: [Solved] Newly updated kernel not loading modules

#32 2015-08-24 17:21:43

Re: [Solved] Newly updated kernel not loading modules

#33 2015-08-24 18:10:40

Re: [Solved] Newly updated kernel not loading modules

#34 2015-08-24 18:16:40

Re: [Solved] Newly updated kernel not loading modules

#35 2015-08-24 18:20:59

Re: [Solved] Newly updated kernel not loading modules

Board footer