I am trying to get Fedora running on the cubox. I am getting close but
no cigar yet.
- build cubox kernel and initramfs (from cubox git) on Fedora 17 ARM
- 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
udevd: starting version 182
dracut: Starting plymouth daemon
GCouldn't open /dev/ttyS0
GGEXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts:
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:
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
I'm running an F17 x86_64 host. This evening I downloaded the SFP XFCE
Desktop image and kernel for Versatile Express as described on the wiki
page, installed qemu-system-arm, and started it using the command line
give on that page. It when through normal-looking kernel startup,
started doing a bit of GUI stuff, then it displayed an unhappy monitor
icon and the completely useless message "Oh no! Something has gone
wrong. A problem has occurred and the system can't recover. Please
contact a system administrator."
Has anyone else seen that? Any hints on what's wrong or how to fix it?