[Solved] Kernel modules not loaded

[woody]

I recently cloned my existing ALARM install from my old Pogoplug onto a new Pogoplug. The new setup is very much like the old one, except that the new installation is on an SD card and the old one is on a USB hard drive. The new one is also partitioned differently, with /boot on a separate partition from /ROOTFS. Otherwise, everything is very similar.

The new Pogoplug seems to work ok except that I discovered that the kernel modules are not loading. An lsmod command shows nothing loaded. I discovered that systemd-modules-load was failing on boot because of a problem with loading /etc/modules-load.d/pl203.conf. I removed that module and then systemd-modules-load completed successfully, but lsmod still shows that the modules are not being loaded.

Can anybody give me any ideas about why the modules would not get loaded when systemd-modules-load seems to be working?

Here's my linux version:$this->bbcode_second_pass_code('', 'uname -r
3.15.1-1-ARCH
')

Any ideas for debugging this will be appreciated!

[hydro]

$this->bbcode_second_pass_quote('woody', 'T')he new one is also partitioned differently, with /boot on a separate partition from /ROOTFS. Otherwise, everything is very similar.

[WarheadsSE]

$this->bbcode_second_pass_code('', '
pacman -Qi linux-kirkwood
uname -a
')

[woody]

$this->bbcode_second_pass_code('', 'sudo pacman -Qi linux-kirkwood

Name : linux-kirkwood
Version : 3.15.5-1
Description : The Linux Kernel and modules - Marvell Kirkwood
Architecture : arm
URL : http://www.kernel.org/
Licenses : GPL2
Groups : None
Provides : kernel26 linux=${pkgver} aufs_friendly cryptodev_friendly
Depends On : coreutils linux-firmware kmod mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels of your country
Required By : None
Optional For : None
Conflicts With : linux-kirkwood-dt linux linux-olinuxino
Replaces : None
Installed Size : 20517.00 KiB
Packager : Arch Linux ARM Build System <builder+xu0@archlinuxarm.org>
Build Date : Fri 11 Jul 2014 01:37:45 AM EDT
Install Date : Tue 15 Jul 2014 11:26:01 PM EDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By : SHA256 Sum
')

And:

$this->bbcode_second_pass_code('', 'uname -a
Linux pogo2 3.15.1-1-ARCH #1 PREEMPT Mon Jun 16 21:27:37 MDT 2014 armv5tel GNU/Linux
')

[hydro]

Well, should be pretty obvious what to do, but in case not:

Assign a label to your boot partition (/dev/sda1 in this example) to make it unique:
$this->bbcode_second_pass_code('', '
tune2fs -L BOOT /dev/sda1
')
Add an entry to /etc/fstab, change the filesystem type to the one you created on your boot partition (ext2 in this example)
$this->bbcode_second_pass_code('', '
LABEL=BOOT /boot ext2 defaults 0 0
')
Mount it
$this->bbcode_second_pass_code('', '
mount /boot
')
Reinstall the kernel package
$this->bbcode_second_pass_code('', '
pacman -S linux-kirkwood
')
Create a symlink so U-Boot can find the kernel¹
$this->bbcode_second_pass_code('', '
cd /boot/
ln -s . boot
')
Reboot to run the new kernel
$this->bbcode_second_pass_code('', '
systemctl reboot
')
Due to the fstab entry /boot should always be mounted, so you don't have to repeat these steps after subsequent kernel updates, except for the last.

¹ In mainline U-Boot you can create and edit /boot/uEnv.txt instead
$this->bbcode_second_pass_code('', '
uimage=/uImage
')
The default is /boot/uImage, but when /boot is mounted on a different partition uImage is actually placed in the root tree of that partition.

[woody]

I probably should have thought of that, but unfortunately, I didn't. Thanks a lot for your suggestion. That makes perfect sense. I'm still learning a lot about basic linux stuff and the boot process is not an area I understand completely.