Hello everyone, I have been working on getting opensuse running on the Cubox-i for a while and want to tell about the progress:
So far, I have patched the u-boot and JeOS packages to provide a booting image. That is, bootloader is in place and kernel, ramdisk and fdt are loaded. Work is done in home:mayerjosua:cubox-i project on OBS. While the Cubox-i should boot a vanilla 3.14 kernel, the current kernel-default never gets to detecting the sdcard. I haven't tried to debug this yet. Instead I have packaged the 3.0.35 kernel by SolidRun and am using that one currently. But there are issues with this setup: firstboot works, but then there is no new initrd created. That has to be done manually after postinstall by running: mkinitrd -k /boot/zImage-3.0.35-cubox-i -i /boot/initrd-3.0.35-cubox-i -M /boot/System.map-3.0.35-cubox-i mkinitrd says in its output that kernel modules are not available. I have no cue whats going on there, but I some kernel modules are installed. The important stuff is builtin to the kernel so no modules are needed at boot time. Yet I dont like this behaviour, mkinitrd should treat that kernel like any other. The 3.0.35 kernel can not be used for kiwi image builds. Building an image fails with parted: error notifying kernel about <whatever> -- invalid argument I wonder if anyone knows a simple fix for this problem. There is a 3.10 kernel available for the cubox-i, but it doesn't work with my monitor so I am not using it. Vivante Binary Blobs: The 3.0.35 kernel has the vivante kernel parts integrated and I have succeeded in running the vivante demos exactly once now. I am working on creating proper packages of them. What I wonder is how they might be provided to the user in the future. At the moment I am hosting a repository with them on a server, but can tehy be provided by opensuse? Kind regards and happy ARMing Josua Mayer -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
