3.18.7-9 with initrd

[RadioGnome1971]

A short while ago, booting Arch on the Pi, with an initrd broke.
http://archlinuxarm.org/forum/viewtopic.php?f=31&t=8304
It was solved by pezz by loading the initrd at a different address.

Since yesterdays update to 3.18.7-9 my first pi (model B) does not boot anymore with symptoms smelling like a similar issue.

Do others have the same problem with 3.18.7-9 combined with an initrd?
If, does someone already have a solution?
Does anyone have a clue how I can determine the correct address to load the initrd? This stuff is far beyond my current knowledge, so I need some guidence where to start. My searches did not yield any results I could use to determine where to begin.

Kind regards,

Martin

[newtonaxiom]

Same here. But it seems, that not the kernel is the problem, but the new firmware/firmware-bootloader. With new firmware/bootloader and kernel 3.1.8.7-5 and initrd the raspberry will not boot.

Edit:

Kernel 3.18.7-9 and firmware 20150221-1 works with initrd.

$this->bbcode_second_pass_code('', '
local/linux-raspberrypi 3.18.7-9
The Linux Kernel and modules - Raspberry Pi
local/linux-raspberrypi-headers 3.18.7-9
Header files and scripts for building modules for linux kernel - Raspberry Pi
local/raspberrypi-firmware 20150221-1
Firmware files for Raspberry Pi
local/raspberrypi-firmware-bootloader 20150221-1
Bootloader files for Raspberry Pi
local/raspberrypi-firmware-bootloader-x 20150221-1
Bootloader with extra codecs for Raspberry Pi
local/raspberrypi-firmware-examples 20150221-1
Firmware example sources for Raspberry Pi
local/raspberrypi-firmware-tools 20150221-1
Firmware tools and header files for Raspberry Pi
')

[RadioGnome1971]

Thanks for the tip. I installed the new firmware along with the new kernel.

Chrooted the affected SDcard, reverted the firmware-bootloader to 20150221 from pacmans cache and System up and running again.

[RadioGnome1971]

Todays kernel 3.18.8-1 and firmware 20170227-1 work flawlessly with an initrd (at my pi B and pi B+ at least).

[pezz]

I had the issue again as well, I solved it by changing the loading address to 0x02f00000 and it worked.

I should have posted when I had the problem.