Hi, Am 19.02.2015 um 11:12 schrieb Freek de Kruijf: > In ARM factory http://download.opensuse.org/ports/armv6hl/factory/images/ I > see a E17 version with extension raw.xz and I assume this one can be used as > described in https://en.opensuse.org/HCL:Raspberry_Pi.
That file looks rather old and probably somehow didn't get cleaned up. As Factory doesn't include the Raspberry Pi boot firmware, you can find the latest -raspberrypi images here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/ > However I am interested > in the JeOS version which is only available as .tbz. > > How do use this .tbz version? Careful, there's a difference between a JeOS-raspberrypi disk image and a pure JeOS rootfs tarball. You'll need to extract the tarball into a manually prepared partition. You'll also need... * the raspberrypi-firmware package extracted onto the FAT partition * a Config.txt bootloader config file on the FAT partition * if you want to use U-Boot, u-boot-rpib or whatever appropriate on the FAT partition plus a boot.scr boot script on the rootfs partition * your own kernel, with everything built-in as initial bootstrap step, as you'll need an initrd to boot the modularized openSUSE kernel It's going to be a whole lot easier if you can take a .raw.xz image as template and only tweak it as needed. In particular, you can fork the openSUSE:Factory:ARM JeOS image on OBS to create a JeOS-raspberrypi2 image, which I guess you are trying to accomplish here. For using a rootfs as a chroot, cf. https://en.opensuse.org/HCL:Chroot For using it with specific boards, someone would need to add board-specific documentation to the HCL pages. 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: [email protected] To contact the owner, e-mail: [email protected]
