[SOLVED] 3.18.3-3 kernel + initrd

by **pezz** » Fri Jan 23, 2015 8:23 am

Hey there,

Have any options changed for linux-raspberrypi-latest 3.18.3-3?

It wont load an initrd any more, just wondering if something has changed?

Thanks.

by **pepedog** » Fri Jan 23, 2015 9:03 am

Check txt files in /boot
$this->bbcode_second_pass_code('', '+ backup=('boot/config.txt' 'boot/cmdline.txt')
')
Pretty soon -latest will vanish, linux-raspberrypi will be as latest is

by **pezz** » Fri Jan 23, 2015 9:15 am

Yeah, I noticed the pacsave's and got them right, pretty sure I did anyway.

Because I can't copy and paste the error, I need to paraphrase but it was something like:

"Unable to load initrd at address 0"

Anyway, after a lot of screwing around, I managed to get back onto 3.18.3-1 and have my pi working again.

by **pezz** » Sat Jan 24, 2015 3:51 pm

So I've gone from linux-raspberrypi-latest to just linux-raspberrypi, which still has the version of 3.18.3-1 and it still won't load an initrd.

I also noticed that kernel.img is about half the size of the previous 3.18.3 on the previous -latest kernel (11MB versus 5.5 MB or so).

There's something very different about this kernel. Once again I've had to revert to 3.18.3-1 of the linux-raspberrypi-latest kernel in order to have my system boot.

Are there any changes in the way this kernel is built as opposed to the previous latest branch?

Cheers.

by **jskier** » Sat Jan 24, 2015 5:07 pm

Same problem here. Working on reverting.

UPDATE:
I reverted by using arch-chroot and another pi. All worked, but not static networking, so I tried to upgrade everything again, updating the root directive in cmdline.txt to the right place. Same issue, networking still borked, but it booted. Turns out netctl was updated and ifplugd was hosing up my static profile by starting the interface first so it wouldn't give a static ip. After adding these two lines below to my ethernet static netctl profile, it works. Removing or disabling ifplugd also works. I don't anticipate this solving the thread, however hopefully it helps others.

$this->bbcode_second_pass_code('', 'SkipNoCarrier=yes
ExcludeAuto=no
')

by **zmetcalf** » Sun Jan 25, 2015 4:30 am

I had an issue with this too. cmdline.txt seems to have an issue with it. I fixed it by using the old cmdline.txt and adding rw after the "root=" parameter. If this does not exist, it opens the file-system as read-only.

by **pezz** » Sun Jan 25, 2015 5:15 am

Unfortunately, I'm not even getting to the point where the kernel tries for a root filesystem, this is why I need to load an initial ramdisk.

Setting rw in cmdline.txt is unrelated to my issue.

by **pezz** » Tue Jan 27, 2015 12:17 pm

Tried updating to linux-raspberrypi 3.18.3-3 (non -latest standard repo version now).

Still can't boot my setup because it won't load an initial ramdisk.

Edit: I've just done diffs on the kernel configs for the old latest branch and this one, the only difference is appears to be CONFIG_STRICT_DEVMEM=y which seems unrelated. Need to debug further, not sure why the older kernel works and this one doesn't.

by **pezz** » Tue Jan 27, 2015 12:57 pm

Got it working!

In config.txt I changed:
$this->bbcode_second_pass_code('', 'initramfs initrd 0x00f00000')
To:
$this->bbcode_second_pass_code('', 'initramfs initrd 0x01f00000')
And changed cmdline.txt to match:
$this->bbcode_second_pass_code('', '... initrd=0x01f00000 ...')

by **lockheed** » Tue Jan 27, 2015 2:17 pm

Does anyone know if this is a permanent change, or will it render my remote system unbootable on the next update?