Michael Ströder wrote:
Dirk Müller wrote:
Hi Michael,
Even if you have a running installation zypper dup will bring broken kernel! Afterwards booting does not work anymore!
There is currently *no* working kernel available in Factory.
Can you give me the kernel version that still worked / the first one that got broken?
Not sure. Update broke when updating package kernel-default from 3.18.5-1.1 to 3.19.1-1.1. Not sure whether any other version came in between although I'm doing updates quite often.
you still collect output from serial console on what the kernel is doing when it is trying to boot?
Hmm, will have to build a cable first...
Ciao, Michael.
Hi, The last Raspberry Pi 1 build I have that works is build 266.3 from ~14Feb15. It has kernel 3.17.4-1. With image: openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build295.1.raw.xz RasPi 1 is still broken. Both the serial terminal and HDMI show the same output: ---------------snip--------------- U-Boot 2015.04-rc4 (Mar 25 2015 - 20:23:29) DRAM: 384 MiB WARNING: Caches not enabled RPI Model B rev2 MMC: bcm2835_sdhci: 0 reading uboot.env ** Unable to read "uboot.env" from mmc0:1 ** Using default environment In: serial Out: lcd Err: lcd Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr reading /boot.scr 113 bytes read in 12 ms (8.8 KiB/s) ## Executing script at 00000000 2708 bytes read in 40 ms (65.4 KiB/s) ## Executing script at 00000200 switch to partitions #0, OK mmc0 is current device 4274192 bytes read in 677 ms (6 MiB/s) 47158755 bytes read in 6624 ms (6.8 MiB/s) 8127 bytes read in 65 ms (122.1 KiB/s) Kernel image @ 0x1000000 [ 0x000000 - 0x413810 ] ## Loading init Ramdisk from Legacy Image at 02100000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 47158691 Bytes = 45 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 02004fbe Starting kernel ... ---------------snap--------------- I've tried to get more by adding these options in uboot: ---------------snip--------------- setenv append "debug ignore_loglevel print_fatal_signals=1 LOGLEVEL=8 sched_debug" boot ---------------snap--------------- But the output is exactly the same. What am I missing? Best, Alex A. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org