Hi, not sure if someone answered you already. Le 23/03/2013 20:41, G. Heim a écrit :
Standard, Mirabox is delivered with Debian. I would like to have it run OpenSUSE 12.3 for armV7 because I like openSUSE better :-) and it is natively compiled for armv7. Debian Squeeze (debian 6) is not (it is compiled for armv5 if I understand correctly, which sounds kind-of silly on an armv7 architecture).
So I downloaded the opensuse image from http://download.opensuse.org/ports/armv7hl/distribution/12.3/images/openSUSE... and put it on my sdcard. I made 2 partitions, one FAT ca. 100MB for uImage (from the rootfs in the tbz file) and the remainder ext4 for the rootfilesystem. I hoped it would work right away but it did not. Right after the loading phase of uboot it stopped after the message "uncompressing linux...done, booting the kernel" and nothing was displayed.
You need a uImage built for your board.
Then I thought I might use the precompiled uImage (from the debian distribution) together with the /lib/modules files from the debian distribution, so I copied /lib/modules from debian rootfs to the opensuse rootfs and the uImage to the FAT partition of my sdcard. It did boot but during the boot process it gave all strange errors and did not complete. uImage was from https://code.google.com/p/mirabox/downloads/detail?name=uImage-v2.6.35.9-gti-mirabox-v5-0-1-120924&can=2&q= and the debian rootfs from http://www.plugcomputer.org/405/us/mirabox/sources/rootfs/mira_fs-v5-0-1-120.... At some moment, I thought that might be logical because of the armv5 arch from debian and armv7 from opensuse.
It may be due to armv5 vs armv7. But you could give us more details about the strange errors.
Then I tried running opensuse in a chroot on the mirabox with debian as a base, as described on http://en.opensuse.org/HCL:Chroot. That worked really wonderful.
Good. :)
So that led me to the idea of compiling my own kernel on the mirabox when being in a chroot opensuse. I grabbed the kernel sources from http://www.plugcomputer.org/405/us/mirabox/sources/kernel/mira_kernel-v5-0-1..., did not modify the configuration in .config, ran "make", "make uImage", "make install", "make modules_install" and then booted opensuse with the resulting kernel. That did not work either. Right after the loading phase of uboot it stopped after the message "uncompressing linux...done, booting the kernel" and nothing was displayed.
Could you access it via SSH maybe ? (To know if it is running but display nothing or if it is crashing).
Then I tried compiling the kernel sources from opensuse (obtained from package "kernel-source" and "kernel-devel" via /sbin/yast2 in opensuse) by tweaking in the armada370 bits (including the same kernel .config file) from the kernel sources from the previous paragraph but it was too much tweaking and twiddling so I gave up on that.
I do not know the upstream support for your board. Maybe mainline kernel (used by openSUSE) does not have a full support for your board.
Why doesn't it work? What did I miss? Do I not understand the kernel building process? Any help is really appreciated.
Maybe try to tune the .config with make menuconfig. You forgot to do a "make modules" before your "make modules_install" but the last one should trigger the first one if not manually called before. Moreover, if you install kernel stuff in chroot, then you cannot boot directly on it since it is in chroot, not in the real rootfs or FAT partition. Guillaume
Thanks, Ge -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org