Alex Armstrong wrote: > Guillaume Gardet wrote: >> Le 23/09/2014 09:54, Dirk Müller a écrit : >>> Hi Alex, >>> >>>> But if I don't load the fdt file (bcm2835-rpi-b.dtb - what is that >>>> anyway?), I get all the way to the network: >>> the fdt file is the device tree, its a binary blob that should exactly >>> describe the hardware. This is used to avoid the kernel having to >>> guess about the hardware (as sometimes probing is not possible on ARM >>> hardware due to lack of standardization). The obvious question for me >>> is whether you actually use a Raspberry Pi - Type B board. It looks >>> like the device tree is not actually matching your hardware. >>> >>> if it boots without it - we might consider building an image without >>> the device tree, since I find it actually surprising that it works >>> without device tree. >> I think you can use 2 kernel images for RPi: >> * upstream kernel which need a device tree >> * downstream kernel which still uses a *.c source file to describe the >> board and not a device tree. >> >> I thought I fixed that in my last JeOS commit (with the partition >> problem fix). >> >> >> Guillaume >> > Thanks for filling me in on the fdt files. I do have a RPi Model B > revision 2 board (not the B+). This board works with the 13.1 JeOS > images (build 38.14). I didn't see a fdt file there, which lead me to > the experiment earlier. But then it hangs when loading the network > module, so it doesn't quite work with auto detection. I'm not sure what > the problem is, but I'm happy to keep testing. > > -Alex > So, I tried using some different images and had different results.
I'm a bit confused actually, I had originally been using this image: openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build215.1.raw.xz from here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/ Which give the output I reported earlier - claims to boot the kernel, but just hangs. Poking around the build website a bit, I found this image: openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build219.1.raw.xz from here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/images/ And using this image, the kernel starts booting but stops with a panic - here are the interesting bits: ########## Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.17.0-rc6-1-default (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #1 Mon Sep 22 14:43:00 UTC 2014 (811b3a2) [ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] Machine model: Raspberry Pi Model B ... [ 0.664553] Unpacking initramfs... [ 7.048904] Initramfs unpacking failed: write error [ 7.243054] Freeing initrd memory: 58956K (c2101000 - c5a94000) ... [ 8.301281] AppArmor: AppArmor sha1 policy hashing enabled [ 8.307272] ../drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 8.316152] Freeing unused kernel memory: 420K (c0759000 - c07c2000) /bin/bash: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory [ 8.349982] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 8.349982] [ 8.359121] CPU: 0 PID: 1 Comm: init Not tainted 3.17.0-rc6-1-default #1 [ 8.365854] [<c0020544>] (unwind_backtrace) from [<c001d468>] (show_stack+0x18/0x1c) [ 8.373607] [<c001d468>] (show_stack) from [<c04fc008>] (panic+0x84/0x1f8) [ 8.380496] [<c04fc008>] (panic) from [<c00330cc>] (do_exit+0x8a8/0x8e0) [ 8.387199] [<c00330cc>] (do_exit) from [<c0033188>] (do_group_exit+0x48/0xa4) [ 8.394422] [<c0033188>] (do_group_exit) from [<c00331fc>] (__wake_up_parent+0x0/0x20) [ 8.402332] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 8.402332] [ 82.639768] random: nonblocking pool is initialized ########## (If anyone wants to see all 170 lines let me know.) This seems like progress or a sort. I also noticed that this boots the recent kernel 3.17 rc, but the first image I was using (when I could get it to boot at all) only booted to 3.11.4. But my primary question is, am I even testing the correct images or should I be looking at something else? -A -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
