s5p_mfc_alloc_and_load_firmware:44: Firmware is not present

[snowhite]

I have 3x odroid U3 (I really like them) and I recently grabbed the latest archlinux ISO from http://archlinuxarm.org/platforms/armv7 ... s-ui-tabs2

One of my odroids works perfectly but when I try the same SD card + when I create a new SD card (using the same instructions) the other two odroids report the following error during boot-up:

s5p_mfc_alloc_and_load_firmware:44: Firmware is not present in the /lib/firmware directory nor compiled in the kernel.

Do I need to perform some sort of firmware SoC update?

[chromebookuser]

After running $this->bbcode_second_pass_code('', 'pacman -Syu') My wifi also would not load it's firmware. After some investigation I was able to determine that the latest update to systemd is what caused the problem.

It seems the newer version of systemd is having problems with firmware loading when running on top of older kernels, I found a related bug here:

https://bugs.archlinux.org/task/42785

I suppose that's not at all surprising considering what a huge piece of crap systemd is. I was able to fix my problem by downgrading all my installed systemd packages from version 217-6 to 216-3

I think I may actually use the "IgnorePkg" directive in "/etc/pacman.conf" to keep it from being updated anymore and stop any future incompatibilities that are almost certainly going to continue to crop up.

edit: Whoops forgot to say this is running on the older Samsung Chromebook which uses the which uses the Exynos5250:
http://archlinuxarm.org/platforms/armv7 ... chromebook

[WarheadsSE]

The s5p_mfc is not related to that wifi firmware @chromebookyuser but thanks for pointing that out. It's actually related to the fact that you're still using a 3.4 kernel for the moment instead of a 3.8 kernel (which we will hopefully be able to soon switch to a mainline kernel.

[stronnag]

So is there a 3.8 kernel for the Samsung chromebook1 in the repo?

[WarheadsSE]

No.