On Monday 26 July 2010 07:01, Rob Landley wrote: > On Saturday 24 July 2010 17:23:18 Denys Vlasenko wrote: > > On Tuesday 13 April 2010 20:09, Rob Landley wrote: > > > I can confirm this on my armv4tl system image: > > > > > > wget > > > http://impactlinux.com/fwl/downloads/binaries/system-image-armv4tl.tar.bz > > >2 tar xvjf system-image-armv4tl.tar.bz2 > > > cd system-image-armv4tl > > > ./run-emulator.sh > > > > > > wait through the boot messages... > > > > > > (armv4tl) /home # time hwclock -w > > > real 0m 24.98s > > > user 0m 0.01s > > > sys 0m 0.01s > > > > > > This assumes you have qemu 0.12.x installed. > > > > Wanted to run system-image-i686 today. It did not work. > > Thus I went back to this old email and system-image-armv4tl indeed works, > > but system-image-i686 from the same location > > (http://impactlinux.com/fwl/downloads/binaries/) does not. Boot ends with: > > wget http://impactlinux.com/aboriginal/downloads/binaries/system-image- > i686.tar.bz2 > cd system-image-i686 > ./run-emulator.sh > ... > VFS: Mounted root (squashfs filesystem) readonly on device 3:0. > Freeing unused kernel memory: 216k freed > e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX > Not using distcc. > Type exit when done. > (i686) /home # > > It worked for me? What qemu version are you using?
Yeah, it was old one: "QEMU PC emulator version 0.9.0". 0.10.6 is ok. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
