Hi Stefan, Am 02.12.2015 um 17:08 schrieb Brüns, Stefan:
the dtb was not renamed, but added. RPi 1 B really has revisions 1.x and 2.0 with hardware differences. Rev 2.0 has 2 mounting holes, the P6 reset header, and most importantly the (unpopulated) P5 header with GPIOs 28-31, providing the I2S signal needed for HifiBerry and the like.
www.raspberrypi-spy.co.uk/2012/09/raspberry-pi-board-revisions/#prettyPhoto/2/
You are right. The problem however was that for whatever reason the non-rev2 .dtb file was not present in my filesystem (dtb -> dtb-foo migration fallout?). I have confirmed that it is in the .rpm, and a zypper install -f restored it. Anyway, booting works the same with either, only GPIOs should be affected I guess. Fact is that rev2 users like me have to deal with a changing file name. Another mysterious phenomenon is that my Pi is the only device that can still read its SD card, whereas other readers don't even recognize it is inserted. That's especially bad because despite me running systemctl disable purge-kernels earlier, my 4.3.0-1/-2 and 3.16.x kernels got removed and I was left with a USB- and network-less Pi... Since armv6l Tumbleweed images are currently stuck building, and using some old image with a new SD card wasn't so appealing to me, here's my recovery solution: Naive idea: Transfer the Tumbleweed kernel rpm via serial console: pi$ base64 -d > kernel-default.rpm host$ base64 kernel-default-foo.rpm | base64 > /dev/ttyUSB0 Took a long time and ended in "base64: invalid input". Unfortunately the JeOS did not seem to contain any other helpful tools for serial file transfer (uuencode, rz). And trying the same base64 approach for the rzsz package (93KB < 28MB) failed the same way. Workaround was to split it into chunks after base64'ing it: host$ dd if=rzsz-foo.rpm.b64 of=/dev/ttyUSB0 bs=16k count=1 skip=0..n checking the file size to match for each chunk (ll vs. dd output) and repeating otherwise, finally cat'ing them together, running base64 -d and checksumming it (sha256sum). zypper in ./rzsz.rpm then installed it fine. From here on pi$ rz can be used to receive files, and minicom can be used to upload them with zmodem protocol, providing automatic error detection and retransmission as well as convenient file name transfer. Took around an hour for transferring the kernel rpm but worked fine. 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