On Thu, Oct 18, 2012 at 4:26 PM, Jurgen Kramer <gtmkramer(a)xs4all.nl&gt; wrote: > I am trying to get Fedora running on the cubox. I am getting close but > no cigar yet. > > Route followed: > - build cubox kernel and initramfs (from cubox git) on Fedora 17 ARM > (VM) > - convert Fedora initramfs img to u-boot uInitrd > - use F18 ARM HFP rootfs (latest nighties) > > The resulting kernel boots just fine and it seems initramfs is being > used but it ends with a panic: > > Freeing init memory: 192K > dracut: dracut-018-98.git20120813.fc17 > udevd[592]: starting version 182 > dracut: Starting plymouth daemon > GCouldn't open /dev/ttyS0 > GGEXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: > (null) > dracut: Checking ext4: /dev/mmcblk0p1 > dracut: issuing e2fsck -a /dev/mmcblk0p1 > dracut: cuboxf18arm: clean, 98087/1957888 files, 788822/7816704 blocks > dracut: Remounting /dev/mmcblk0p1 with -o rw > EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: > (null) > dracut: Mounted root filesystem /dev/mmcblk0p1 > dracut: Switching root > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 > > Any hints on what could cause this? Maybe some potential magic kernel > config options I forgot? > > Bootargs I used: console=ttyS0,115200n8 vmalloc=384M rw > root=/dev/mmcblk0p1 rootwait It's not finding the root filesystem. Is it on partition 1? You don't have a /boot filesystem there? The other thing you can try is to use either the blkid or volume name on the root file system and see if the kernel can find it from that.

On 10/18/2012 09:44 AM, Jurgen Kramer wrote: > On Thu, 2012-10-18 at 16:34 +0100, Peter Robinson wrote: >> On Thu, Oct 18, 2012 at 4:26 PM, Jurgen Kramer <gtmkramer(a)xs4all.nl&gt; wrote: >>> I am trying to get Fedora running on the cubox. I am getting close but >>> no cigar yet. I haven't had much luck yet, either, but I also haven't been able to spend a great deal of time with my CuBox (maybe all of an hour so far). I've been attempting an f17 rootfs, though. Is there some place I can go to and pick up the kernel/initrd you've got and try it so that I can replicate what you're seeing? Or, are you just using the kernel source from SolidRun?

On Thu, 2012-10-18 at 10:21 -0600, Al Stone wrote: > On 10/18/2012 09:44 AM, Jurgen Kramer wrote: > > On Thu, 2012-10-18 at 16:34 +0100, Peter Robinson wrote: > >> On Thu, Oct 18, 2012 at 4:26 PM, Jurgen Kramer <gtmkramer(a)xs4all.nl&gt;

> >>> I am trying to get Fedora running on the cubox. I am getting close

> >>> no cigar yet. > > I haven't had much luck yet, either, but I also haven't been able to > spend a great deal of time with my CuBox (maybe all of an hour so > far). I've been attempting an f17 rootfs, though. > > Is there some place I can go to and pick up the kernel/initrd you've > got and try it so that I can replicate what you're seeing? Or, are you > just using the kernel source from SolidRun? > I got a bit further by using different memory addresses for the kernel and initrd. Systemd now starts but complains about missing autofs4 and cgroups. As kernel source and config I am using the SolidRun kernel sources enhanced with several patches (https://github.com/vDorst/linux) . I'll put up the kernel/initrd once it's done compiling with cgroups and autofs4 enabled. What would be needed for Fedora to support the CuBox? CuBox support is not upstream (yet).

Jurgen _______________________________________________ arm mailing list arm(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm

On 10/18/2012 01:18 PM, Peter Robinson wrote: > > > On 18 Oct 2012 20:29, "Jurgen Kramer" <gtmkramer(a)xs4all.nl > <mailto:gtmkramer@xs4all.nl>> wrote: > > > > On Thu, 2012-10-18 at 10:21 -0600, Al Stone wrote: > > > On 10/18/2012 09:44 AM, Jurgen Kramer wrote: > > > > On Thu, 2012-10-18 at 16:34 +0100, Peter Robinson wrote: > > > >> On Thu, Oct 18, 2012 at 4:26 PM, Jurgen Kramer > <gtmkramer(a)xs4all.nl <mailto:gtmkramer@xs4all.nl>> wrote: > > > >>> I am trying to get Fedora running on the cubox. I am getting > close but > > > >>> no cigar yet. > > > > > > I haven't had much luck yet, either, but I also haven't been able to > > > spend a great deal of time with my CuBox (maybe all of an hour so > > > far). I've been attempting an f17 rootfs, though. > > > > > > Is there some place I can go to and pick up the kernel/initrd you've > > > got and try it so that I can replicate what you're seeing? Or, are > you > > > just using the kernel source from SolidRun? > > > > > I got a bit further by using different memory addresses for the kernel > > and initrd. Systemd now starts but complains about missing autofs4 and > > cgroups. > > As kernel source and config I am using the SolidRun kernel sources > > enhanced with several patches (https://github.com/vDorst/linux) . > > > > I'll put up the kernel/initrd once it's done compiling with cgroups and > > autofs4 enabled. > > > > What would be needed for Fedora to support the CuBox? CuBox support is > > not upstream (yet). > > Upstream support in a unified kernel. From the little I've read Marvell > plans on supporting this as part of the mvebu support as they mention > supporting dove as part of it which is what I think the cubox is based on. I don't know about the unified part, but I'll look into that. I'm pretty sure the CuBox is a Marvell Armada 510 SoC (single CPU version of the Armada XP 4-CPU chip). In theory, it should even be able to use the Armada XP kernel -- or so I've been told :).