[opensuse-arm] How to upgrade kernel on Raspberry Pi
Hi, I've got a Raspberry Pi running openSUSE Factory. The kernel is kernel-raspberrypi-3.11.4-1.7.armv6hl Recently, a new kernel update was installed: kernel-raspberrypi-3.11.4-10.1.armv6hl However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel? Regards, Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op vrijdag 4 september 2015 13:36:29 schreef Olav Reinert:
Hi,
I've got a Raspberry Pi running openSUSE Factory. The kernel is
kernel-raspberrypi-3.11.4-1.7.armv6hl
Recently, a new kernel update was installed:
kernel-raspberrypi-3.11.4-10.1.armv6hl
However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel?
The rpm should have support for building an initrd. You may try to reinstall the rpm. Otherwise you can use plymouth to build that new initrd. It should replace the current one. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 04.09.2015 um 17:36 schrieb Freek de Kruijf:
Op vrijdag 4 september 2015 13:36:29 schreef Olav Reinert:
Hi,
I've got a Raspberry Pi running openSUSE Factory. The kernel is
kernel-raspberrypi-3.11.4-1.7.armv6hl
Recently, a new kernel update was installed:
kernel-raspberrypi-3.11.4-10.1.armv6hl
However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel?
The rpm should have support for building an initrd. You may try to reinstall the rpm. Otherwise you can use plymouth to build that new initrd. It should replace the current one.
Unless you've modified the boot script, U-Boot will boot the zImage symlink - make sure it points to the right kernel. The initrd does not affect uname output, but reinstalling the kernel should update the symlink. ln -sf will be quicker on rpi1 though. :) Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fre, 2015-09-04 at 18:00 +0200, Andreas Färber wrote:
Am 04.09.2015 um 17:36 schrieb Freek de Kruijf:
Op vrijdag 4 september 2015 13:36:29 schreef Olav Reinert:
Hi,
I've got a Raspberry Pi running openSUSE Factory. The kernel is
kernel-raspberrypi-3.11.4-1.7.armv6hl
Recently, a new kernel update was installed:
kernel-raspberrypi-3.11.4-10.1.armv6hl
However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel?
The rpm should have support for building an initrd.
Unless you've modified the boot script, U-Boot will boot the zImage symlink - make sure it points to the right kernel.
The initrd does not affect uname output, but reinstalling the kernel should update the symlink. ln -sf will be quicker on rpi1 though. :)
Installing the new kernel did generate a new initr - or, at least, dracut is run after installation. And it updates the /boot/initrd and /boot/zImage symlinks correctly. So I tried to uninstall the new kernel RPM. This caused the initrd and zImage symlinks to become dangling. And yet rebooting worked fine, still to the old kernel. I'm suspecting the separate BOOT partition has something to do with it. That's where boot.scr lives, and there's a zImage file there, too. Does something in it need to be updated to activate the new kernel? Regards, Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fre, 2015-09-04 at 19:58 +0200, Olav Reinert wrote:
On Fre, 2015-09-04 at 18:00 +0200, Andreas Färber wrote:
Am 04.09.2015 um 17:36 schrieb Freek de Kruijf:
Op vrijdag 4 september 2015 13:36:29 schreef Olav Reinert:
Hi,
I've got a Raspberry Pi running openSUSE Factory. The kernel is
kernel-raspberrypi-3.11.4-1.7.armv6hl
Recently, a new kernel update was installed:
kernel-raspberrypi-3.11.4-10.1.armv6hl
However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel?
The rpm should have support for building an initrd.
Unless you've modified the boot script, U-Boot will boot the zImage symlink - make sure it points to the right kernel.
The initrd does not affect uname output, but reinstalling the kernel should update the symlink. ln -sf will be quicker on rpi1 though. :)
Installing the new kernel did generate a new initr - or, at least, dracut is run after installation. And it updates the /boot/initrd and /boot/zImage symlinks correctly.
So I tried to uninstall the new kernel RPM. This caused the initrd and zImage symlinks to become dangling. And yet rebooting worked fine, still to the old kernel.
I'm suspecting the separate BOOT partition has something to do with it. That's where boot.scr lives, and there's a zImage file there, too. Does something in it need to be updated to activate the new kernel?
Aha, success! The fix was to copy the files from /boot to the boot partition that are already present in both locations. Now my Pi boots to the new kernel, and removing the old one didn't cause any issues. Not idea if this is the canonical procedure, but it works. Tumbleweed on a Pi - smashing! Regards, Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op vrijdag 4 september 2015 22:33:02 schreef Olav Reinert:
The fix was to copy the files from /boot to the boot partition that are already present in both locations. Now my Pi boots to the new kernel, and removing the old one didn't cause any issues. Not idea if this is the canonical procedure, but it works.
Tumbleweed on a Pi - smashing!
I don't think you are fully using Tumbleweed. Tumbleweed uses kernel-4.1.6. What repositories are you using? I have: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... and http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/ The kernel I am using comes from the last repo, the one you use comes from the first repo. Installing a new kernel lately 4.1.6 from 4.1.4 went without the trick you needed. Most likely the post processing in the rpm for the kernel you use does not include the copy to /boot. The /boot on my RPi is on the second partition (ext3). -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Friday 04 September 2015 23.11:20 Freek de Kruijf wrote:
Op vrijdag 4 september 2015 22:33:02 schreef Olav Reinert:
The fix was to copy the files from /boot to the boot partition that are already present in both locations. Now my Pi boots to the new kernel, and removing the old one didn't cause any issues. Not idea if this is the canonical procedure, but it works.
Tumbleweed on a Pi - smashing!
I don't think you are fully using Tumbleweed. Tumbleweed uses kernel-4.1.6.
You're right - the kernel on my RPi way behind Tumbleweed.
What repositories are you using? I have: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi/standard/ and http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/
I'm using the same repositories.
The kernel I am using comes from the last repo, the one you use comes from the first repo.
Correct.
Installing a new kernel lately 4.1.6 from 4.1.4 went without the trick you needed. Most likely the post processing in the rpm for the kernel you use does not include the copy to /boot.
I tried to install kernel-default-4.1.6-3.1.armv6hl, and to make the same manual correction as above. That didn't boot at all, it didn't even get past the rainbow square.
The /boot on my RPi is on the second partition (ext3).
My RPi has only two partitions. Probably because it was zypper dup'ed from 13.1. I noticed that my RPi2 (also on Tumbleweed) has an extra partition for the low-level bootstrap stuff, then a /boot partition, and finally the root partition. I guess the kernel upgrade didn't work because the newer kernels expect this partition layout for the update to work properly. I tried to upgrade to the new layout by installing a fresh 13.2 image: http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Raspber... Unfortunately, that image won't boot properly. It gets as far as the "Starting kernel ...", then it seems to hang. \Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zondag 6 september 2015 12:58:55 schreef Olav Reinert:
I tried to upgrade to the new layout by installing a fresh 13.2 image:
<http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Raspbe rryPi/images/openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build36.9.raw. xz>
Unfortunately, that image won't boot properly. It gets as far as the "Starting kernel ...", then it seems to hang.
You probably should use the Tumbleweed image on: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... The ones on http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... never worked. The newest image is Build338.1. I did not test this image. The latest I tested was Build336.3, but that one has a distorted 3rd partition (ext4). Running fsck on that partition after moving the image on the SD card shows errors. The latest which was usable was Build 330.10 from Aug 6. A zypper up brings it in line with the latest repositories. This is what I am using now. All the problems I had with YaST are fixed now. I am still struggling with a Bluetooth device and/or Wi-Fi. When I have a few % packet loss, because of the distance on the Wi-Fi connection, curl does not deliver me a proper file. Curl is used by zypper and zypper shows wrong check sums. curl does not report an error, but the check sum is wrong. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sunday 06 September 2015 14.54:26 Freek de Kruijf wrote:
Op zondag 6 september 2015 12:58:55 schreef Olav Reinert:
I tried to upgrade to the new layout by installing a fresh 13.2 image:
<http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Rasp be rryPi/images/openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build36.9.r aw. xz>
Unfortunately, that image won't boot properly. It gets as far as the "Starting kernel ...", then it seems to hang.
You probably should use the Tumbleweed image on: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi:/upstream/images/
Tried it - it fails quite early in the boot process with out of memory. :-( I'm not soo concerned that the Tumbleweed images are finicky. But it bothers me that the 13.2 image doesn't work - that one is even mentioned in the wiki. \Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zondag 6 september 2015 19:02:53 schreef Olav Reinert:
On Sunday 06 September 2015 14.54:26 Freek de Kruijf wrote:
Op zondag 6 september 2015 12:58:55 schreef Olav Reinert:
I tried to upgrade to the new layout by installing a fresh 13.2 image:
<http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Ra sp be rryPi/images/openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build36.9. r aw. xz>
Unfortunately, that image won't boot properly. It gets as far as the "Starting kernel ...", then it seems to hang.
You probably should use the Tumbleweed image on: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ra sp berryPi:/upstream/images/
Tried it - it fails quite early in the boot process with out of memory. :-(
Tried it also, the upstream image, Build338.1. I followed the progress on my HDMI display and it finishes properly. The problem is however that it does not start the network on eth0. Inspection of the journal shows that it does not load the driver for the Ethernet interface, smsc95xx in previous images. This driver is present on the SD card. Apparently the udev system does not have a proper rule for this USB device.
I'm not soo concerned that the Tumbleweed images are finicky. But it bothers me that the 13.2 image doesn't work - that one is even mentioned in the wiki.
Unfortunately the wiki does not mention the Build version which was used when the page was written. I still have Build36.3 which I believe works. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Andreas Färber -
Freek de Kruijf -
Olav Reinert -
Olav Reinert