On Tue, Nov 11, 2008 at 8:38 PM, Rob K <robk@xxxxxxxxxxx> wrote: > On Wed, Nov 12, 2008 at 12:33 PM, Jon Stanley <jonstanley@xxxxxxxxx> wrote: >> On Tue, Nov 11, 2008 at 8:30 PM, Rob K <robk@xxxxxxxxxxx> wrote: >> >>> I had the same issue, but it went away after upgrading to the latest >>> firmware. Now I just need to fix the borken keyboard. >> >> Later than Q2E18? Where would one get such a thing? > > Apologies for the confusion, I meant latest firmware == Q2E18. > > > -- > Rob K > http://ningaui.net > I swear, if I collected all seven dragonballs, > I'd bring back Jon Postel. - Raph > > -- > fedora-test-list mailing list > fedora-test-list@xxxxxxxxxx > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > Jon, I believe this is an issue with the cards themselves, I haven't yet proved that theory but inode0 and myself are both getting the exact same problems with the 8gig cards we just bought, but I have no problem at all with my 4 gig card and if I recall you are trying to use a 16gig card. The XO can see the larger cards just fine if you boot straight into sugar but if you try to boot to the cards, we either get the message you are or unable to locate boot device. We even went so far as to split the 8 gig card in half and only use 4 gigs with the rest unpartitioned but that was a fail as well. -- Regards, BrianPowell http://fedoraproject.org http://wnylug.org -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
