[opensuse-arm] kernel update breaks rasperry pi 1
HI! After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore! It hangs with message "Starting kernel...". Any clue how to work around this? I have another rasperry with files before the recent kernel update. Ciao, Michael.
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again. To make it clear: kernel-default-3.18.5-1.1 works. kernel-default-3.19.1-1.1 (from openSUSE-Factory-repo-oss) does *not* work! Ciao, Michael.
Am 10.03.2015 um 17:16 schrieb Michael Ströder:
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again.
What about the dtb-bcm2835 package? Is that the old or the new one?
To make it clear:
kernel-default-3.18.5-1.1 works.
kernel-default-3.19.1-1.1 (from openSUSE-Factory-repo-oss) does *not* work!
Maybe compare the kernel configs for any suspicious change? Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, 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
Andreas Färber wrote:
Am 10.03.2015 um 17:16 schrieb Michael Ströder:
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again.
What about the dtb-bcm2835 package? Is that the old or the new one?
How can I know? I see this installed: dtb-bcm2835-3.19.0-40.1.armv6hl Ciao, Michael.
Am 10.03.2015 um 23:40 schrieb Michael Ströder:
Andreas Färber wrote:
Am 10.03.2015 um 17:16 schrieb Michael Ströder:
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again.
What about the dtb-bcm2835 package? Is that the old or the new one?
How can I know?
I see this installed: dtb-bcm2835-3.19.0-40.1.armv6hl
3.19.0 -> new :) Not the problem then. Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, 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
Andreas Färber wrote:
Am 10.03.2015 um 23:40 schrieb Michael Ströder:
Andreas Färber wrote:
Am 10.03.2015 um 17:16 schrieb Michael Ströder:
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again.
What about the dtb-bcm2835 package? Is that the old or the new one?
How can I know?
I see this installed: dtb-bcm2835-3.19.0-40.1.armv6hl
3.19.0 -> new :) Not the problem then.
If this package is kernel specific then it's strange that this package works on a system running kernel-default-3.18.5-1.1. Ciao, Michael.
Am 11.03.2015 um 10:07 schrieb Michael Ströder:
Andreas Färber wrote:
Am 10.03.2015 um 23:40 schrieb Michael Ströder:
Andreas Färber wrote:
Am 10.03.2015 um 17:16 schrieb Michael Ströder:
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again.
What about the dtb-bcm2835 package? Is that the old or the new one?
How can I know?
I see this installed: dtb-bcm2835-3.19.0-40.1.armv6hl
3.19.0 -> new :) Not the problem then.
If this package is kernel specific then it's strange that this package works on a system running kernel-default-3.18.5-1.1.
Not that surprising - usually stuff gets added to the DT, not removed. Also the .dts files rarely change with maintenance releases, so often the version remains at 3.19.0 despite the kernel being at 3.19.1 or so. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, 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
Michael Ströder wrote:
Andreas Färber wrote:
Am 10.03.2015 um 23:40 schrieb Michael Ströder:
Andreas Färber wrote:
Am 10.03.2015 um 17:16 schrieb Michael Ströder:
Michael Ströder wrote:
After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore!
It hangs with message "Starting kernel...".
Any clue how to work around this? I have another rasperry with files before the recent kernel update.
I managed to go back to the older kernel (by modifying the symlinks in /boot) and the machines boot again.
What about the dtb-bcm2835 package? Is that the old or the new one?
How can I know?
I see this installed: dtb-bcm2835-3.19.0-40.1.armv6hl
3.19.0 -> new :) Not the problem then.
If this package is kernel specific then it's strange that this package works on a system running kernel-default-3.18.5-1.1.
Short summary of current situation: - No working kernel in all current repos. - rasperry pi armv6 currently not usable at all. :-[ My recent tests: The currently published images are broken and do *not* boot as well: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... I tried with a fresh installed image with a local copy of openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw which is not available in the repos anymore. During update: ----------------------------- snip ----------------------------- Output of kernel-firmware-20150209git-1.1.noarch.rpm %posttrans script: No kernel found in /boot or bad modules dir in /lib/modules Warning: kernel-firmware-20150209git-1.1.noarch.rpm %posttrans script failed (returned 1) ----------------------------- snip ----------------------------- But I have seen this warning when upgrading to former kernels too and the system still booted. kernel-default-3.18.5-1.1 was removed from the repos. Great! There's no working kernel available anymore. Ciao, Michael.
On 03/11/2015 12:48 PM, Michael Ströder wrote:
I tried with a fresh installed image with a local copy of openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw which is not available in the repos anymore.
I tried but this version stalls at starting kernel as well. greetings Kai Dupke Senior Product Manager Server Product Line -- Sell not virtue to purchase wealth, nor liberty to purchase power. Phone: +49-(0)5102-9310828 Mail: kdupke@suse.com Mobile: +49-(0)173-5876766 WWW: www.suse.com SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Jennifer Guild, Graham Norton,HRB 21284 (AG Nurnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Kai Dupke wrote:
On 03/11/2015 12:48 PM, Michael Ströder wrote:
I tried with a fresh installed image with a local copy of openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw which is not available in the repos anymore.
I tried but this version stalls at starting kernel as well.
Hmm, it works for me. To make sure we're talking about the very same image file here's the checksum of the *uncompressed* image file I used: # sha1sum openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw 8acf58d7cef204a1d16ac250ad5f8215f3323a48 Ciao, Michael.
On 03/12/2015 04:58 PM, Michael Ströder wrote:
To make sure we're talking about the very same image file here's the checksum of the *uncompressed* image file I used:
# sha1sum openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw 8acf58d7cef204a1d16ac250ad5f8215f3323a48
sha1sum openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw 8acf58d7cef204a1d16ac250ad5f8215f3323a48 seems to be the same, greetings Kai Dupke Senior Product Manager Server Product Line -- Sell not virtue to purchase wealth, nor liberty to purchase power. Phone: +49-(0)5102-9310828 Mail: kdupke@suse.com Mobile: +49-(0)173-5876766 WWW: www.suse.com SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Jennifer Guild, Graham Norton,HRB 21284 (AG Nurnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Kai Dupke wrote:
On 03/12/2015 04:58 PM, Michael Ströder wrote:
To make sure we're talking about the very same image file here's the checksum of the *uncompressed* image file I used:
# sha1sum openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw 8acf58d7cef204a1d16ac250ad5f8215f3323a48
sha1sum openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build266.3.raw 8acf58d7cef204a1d16ac250ad5f8215f3323a48
seems to be the same,
Hmm, what hardware are you using? I have the model b first revision. Ciao, Michael.
On 03/12/2015 05:43 PM, Michael Ströder wrote:
Hmm, what hardware are you using? I have the model b first revision.
THis is a Rasberry Pi 1 Model B. Kai Dupke Senior Product Manager Server Product Line -- Sell not virtue to purchase wealth, nor liberty to purchase power. Phone: +49-(0)5102-9310828 Mail: kdupke@suse.com Mobile: +49-(0)173-5876766 WWW: www.suse.com SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Jennifer Guild, Graham Norton,HRB 21284 (AG Nurnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Michael Ströder wrote:
Short summary of current situation: - No working kernel in all current repos. - rasperry pi armv6 currently not usable at all. :-[
My recent tests:
The currently published images are broken and do *not* boot as well:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
I can confirm that neither of these images work. When trying build 255.3, we get: ----------------------------- snip ----------------------------- kernel image @ 0x1000000 [ 0x000000 - 0x27bb58 ## Loading init Ramdisk from Legacy Image at 02100000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 39316560 Bytes = 37.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Using Device Tree in place at 02000000, end 02004f42 Starting kernel ... Uncompressing Linux... done, booting the kernel. ----------------------------- snap ----------------------------- And here it hangs. But when trying the 277.1 build, we don't even get the kernel uncompressed: ----------------------------- snip ----------------------------- kernel image @ 0x1000000 [ 0x000000 - 0x413db8 ## Loading init Ramdisk from Legacy Image at 02100000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 46183556 Bytes = 44 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Using Device Tree in place at 02000000, end 03004fbe Starting kernel ... ----------------------------- snap ----------------------------- I don't even get any extra debugging info on the serial terminal. Greetings, -ARA -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Alex Armstrong wrote:
Michael Ströder wrote:
Short summary of current situation: - No working kernel in all current repos. - rasperry pi armv6 currently not usable at all. :-[
My recent tests:
The currently published images are broken and do *not* boot as well:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
I can confirm that neither of these images work.
When trying build 255.3, we get:
----------------------------- snip ----------------------------- kernel image @ 0x1000000 [ 0x000000 - 0x27bb58 ## Loading init Ramdisk from Legacy Image at 02100000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 39316560 Bytes = 37.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Using Device Tree in place at 02000000, end 02004f42
Starting kernel ...
Uncompressing Linux... done, booting the kernel. ----------------------------- snap -----------------------------
And here it hangs.
But when trying the 277.1 build, we don't even get the kernel uncompressed:
----------------------------- snip ----------------------------- kernel image @ 0x1000000 [ 0x000000 - 0x413db8 ## Loading init Ramdisk from Legacy Image at 02100000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 46183556 Bytes = 44 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Using Device Tree in place at 02000000, end 03004fbe
Starting kernel ... ----------------------------- snap -----------------------------
I don't even get any extra debugging info on the serial terminal.
Greetings, -ARA
I just tested the latest build: openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build280.1.raw.xz From: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... Still hangs at 'Starting kernel ...' Are there any u-boot commands I could use to make it more verbose? -ARA -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Alex Armstrong wrote:
I just tested the latest build:
openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build280.1.raw.xz
From:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
Still hangs at 'Starting kernel ...'
Same with recent openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build289.1.raw.xz Do we have to give up using openSUSE on rasperry pi? Ciao, Michael.
participants (4)
-
Alex Armstrong -
Andreas Färber -
Kai Dupke -
Michael Ströder