Am 20.12.2015 um 15:50 schrieb Ludwig Nussel: > Am 17.12.2015 um 13:04 schrieb Freek de Kruijf: >> I tested the latest released Tumbleweed image for the Raspberry Pi 2B, >> Build354.2 which shows a black screen and does not boot at all, same >> as the >> latest one from Staging, which is from a few days back. >> >> Currently there are no working Tumbleweed images for any of the >> Raspberry Pi >> systems. Is there anything I can do, apart from testing the latest >> images? > > Same here. None of the available images work. The kernel seems to be > a patched copy of some kernel devel project state. Any chance to > rebase that on something current? Looks like the sources come from > some git, but where?
The first thing you guys could do is provide some more substantial info of what you are actually testing. Build numbers are not really telling. On the Pi 1 the official openSUSE kernel-default 4.3.0 from Tumbleweed works just fine (not 4.4-rcX due to USB, as reported). I.e., you need to double-check which kernel package you have and which repository you are installing your kernel from if it looks like "a patched copy of some kernel devel project state" - it might be kernel-rpi from devel:ARM:Factory:Contrib:RaspberryPi or kernel-rpi2 from devel:ARM:Factory:Contrib:RaspberryPi2, which are not maintained by the kernel team. Ludwig's serial log is from the Pi 2. The Pi 2 is still not supported by the mainline Linux kernel and therefore not by the openSUSE kernel either. The kernel-rpi2 package is built from: https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi2/kernel-source These Contrib packages have no magic cron jobs unlike the openSUSE kernels and thus need to be manually updated like any other package, via osc bco / sr, by whomever cares about them. I guess the kernel will be from somewhere at https://github.com/raspberrypi/linux/ - there's several branches including an rpi-4.4.y that you might want to try building and packaging. One of my Hackweek projects was to clean up Raspberry Pi images and move the Pi 1 closer to first-class Tumbleweed citizen. raspberrypi-firmware was accepted into Tumbleweed and JeOS-raspberrypi "moved" from devel:ARM:Factory:Contrib:RaspberryPi:upstream project to official openSUSE:Factory:ARM, i.e. the download locaction will change to: http://download.opensuse.org/ports/armv6hl/tumbleweed/images/ As mentioned multiple times already, armv6 image builds keep hanging. Any help debugging that is appreciated - it's been broken for weeks and months, so waiting and complaining is seriously not going to help! https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS-raspberrypi Depending on your host kernel, a local osc build on x86_64 may work. Also, you can always check the list archives - long before we got the now-broken JeOS image, I had posted a how-to for manually partitioning and bootstrapping an upstream-based rpi1 card based on the armv6 rootfs (which still seems building fine) that with some tweaks should still work. Only the lazy way of installing a new Raspberry Pi is broken. :) Just today my Hackweek submission of raspberrypi-firmware was accepted, adding a Config.txt template and moving the files from /boot to /boot/vc so that the FAT partition can be automatically updated by zypper in the future. https://build.opensuse.org/request/show/347964 The matching change to JeOS has just been submitted: https://build.opensuse.org/request/show/349929 The corresponding u-boot change I haven't accepted yet, to not interfere with Guillaume's -rc2 submission. https://build.opensuse.org/request/show/350127 > Also, it takes ages to even boot up to this point. Kernel/initrd too big? On first boot of Kiwi images, a huge initrd is loaded and it will resize partitions, which both can take some time. For ARMv6 we mainly enable the Raspberry Pi, for ARMv7 the number of SoCs and boards and thus of drivers is significantly higher. 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: [email protected] To contact the owner, e-mail: [email protected]
