On 01/23/2012 03:21 PM, Peter Robinson wrote:
On Mon, Jan 23, 2012 at 8:53 PM, Mark Langsdorf
<mark.langsd...@calxeda.com> wrote:
I'm trying to get a test build environment working for a
Versatile Express board. I'm currently working under
QEMU, with a plan to move to the physical board
when I have a drive image I trust.
I can follow the instructions on the Fedora project wiki
to get the FC12 rootfs (rootfs-f12.tar.bz2) running under
QEMU. Sadly, that doesn't seem to have make installed
so it isn't very useful for development/
"yum install make"?
I'm not getting a DHCP ack inside QEMU. I'll look into that.
Using similar steps, I can boot the rootfs-f14-alpha1.tar.bz2
image and get it to run to the end of the rc3.d scripts, but
the tty never launches. My launch command is
`qemu-system-arm -M vexpress-a9 -cpu cortex-a9
-kernel linux-stable/arch/arm/boot/zImage -sd rootfs-f14.img
-append 'root=/dev/mmcblk0' -net nic,vlan=0 -net
tap,vlan=0,ifname=tap0,script=./qemu-ifup`
Try disabling selinux by appending "selinux=0" to the end of the
command line or edit the /etc/selinux/config in the rootfs first.
Doesn't help. After completely the rc3.d scripts (or at least, after
running the last local script), it sits and waits, no TTY available.
I cut a new F-15 image for softfp or hardfp the other day you might
want to start with that.
http://nullr0ute.com/2012/01/fedora-15-arm-alpha-rootfs/
Using the same command line as above with the addition of selinux=0
on the append, this fails immediately after "Failed to load SELinux
policy" with "Failed to mount /dev: No such device." I'm using a
monolithic kernel so I'm not sure what's up with that.
--Mark Langsdorf
Calxeda, Inc.
_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
