On Wed, Sep 26, 2012 at 11:49 PM, Jerry James <loganjerry@xxxxxxxxx> wrote: > On Wed, Sep 26, 2012 at 3:57 PM, Jerry James <loganjerry@xxxxxxxxx> wrote: >> I'll give the F17 image a try. If I seem to be doing a lot of ARM >> work, I'll apply for one of the TryStack instances. Thanks for the >> offer, Mark. Regards, > > Wait, I remember now. I tried the F17 image a month or so ago, and > got nowhere with it. That's why I tried the F18 image. When I boot > the F17 image (hardfp, XFCE) from > https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express, I > see a bunch of systemd output, eventually culminating in this: > > network[383]: Determining IP information for eth0... done. > network[383]: [ OK ] > [ 359.961519] RPC: Registered named UNIX socket transport module. > [ 359.970705] RPC: Registered udp transport module. > [ 359.976688] RPC: Registered tcp transport module. > [ 359.982415] RPC: Registered tcp NFSv4.1 backchannel transport module. > > ... and that's it. The virtual terminals have been created, as I can > switch between 6 of them, but 5 of them are empty black screens. The > original VT shows only syslog output. I've let it sit for half an > hour now, with no shell prompt and no X Windows showing up. Hitting > enter does nothing on any of the 6 VTs. Perhaps I should try a later > snapshot? What happens if you connect on a serial console? I've only ever got around to using the qemu image once or twice and it was all via a virtual serial console. That might at least give you more details of where it's getting to. Peter _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
