[SOLVED] Unable to boot after pacman -Syu on fresh install

[netfun81]

Strange it would be the sd card. I have this same issue with Arch, however debian wheezy, raspbmc, and even riscos, all work perfectly with the same SD card. Also before I do an update (pacman -Syu) everything works fine with the original image. I think something happened in one of these new updates.

[ingamedeo]

Simply do: $this->bbcode_second_pass_code('', 'pacman -S raspberrypi-frimware') after $this->bbcode_second_pass_code('', 'pacman -Syu') and everythink will work!

[netphyx]

Pepedog, a few posts back you noticed that the kernel won't load any modules with old firmware. Any ideas on how to circumvent that?

[pepedog]

I think what we were talking about was using the firmware from raspberry pi GitHub site.
Their firmware includes not only firmware but kernel and modules. If you copy their /boot it will include a kernel, so you have to find modules that were downloaded also, and put in right place
If you installed the asdeb package, it's doing all this for you

[netphyx]

Sorry for being unclear: I'm now using the old kernel from September, because the newer kernels don't work for me (can't boot). Problem now is that this old kernel does not load any modules and I want to modprobe fuse. When I do lsmod I get an empty list. If the module directory is hardcoded I suppose I have to rename /lib/modules/x.x.x-ARCH to the appropriate version. I will try this when I get home. If this works then I finally have a full solution to the orginal problem of this thread. But I would be surprised if this works .

On a side note: I emailed popcornmix about the fact that I have to use the September kernel because otherwise my pi won't boot with my sd card. I suppose he's not going to reply since that was about 3 days ago.

[pepedog]

No good renaming, uname -a must match /usr/lib/modules/ directory name, AND module compiled for that kernel.
Have you tried the -next kernel and firmware? Or --ignore when upgrading?

[netphyx]

When ignoring, everything seems to work except module loading. It's weird. I can try downloading the -next packages.

By the way: uname -a gives 3.2.27-5-ARCH+ and my modules directory is 3.2.27-18-ARCH+. I guess things will work then if I can find the .ko.gz file for 3.2.27-5 and create a new directory with the (old) modules I want.

[pepedog]

I am guessing here
3.2.27-5-ARCH+ came with the original rootfs
You ran pacman -Syu and haven't rebooted yet, and when you do it won't come up.
So nothing to lose
$this->bbcode_second_pass_code('', 'pacman -S linux-raspberrypi-next raspberrypi-firmware-next')
sync and reboot

[netphyx]

It did come up after just rebooting. You get my results when you do pacman -Syu whilst ignoring raspberrypi-firmware. This way, you have the 3.2.27-5-ARCH+ kernel with 3.2.27-18-ARCH+ modules.

Getting linux-raspberrypi-next raspberrypi-firmware-next results again in the pi being unable to boot.

I guess the only solution to my problem is to stick with this outdated kernel. It seems someone of the pi kernel developers committed a bug between October - December.

Solution: you also need to ignore linux-raspberrypi along with raspberrypi-firmware for the modules to work with old kernel. Since I have the newer modules now I just have to revert.

[pepedog]

A suggestion, copy /boot and /usr/lib/modules somewhere before updating