next »

[Keith]

I believe security is already disabled on both machines. Even so, it should still bring me to the OpenFirmware screen if I am holding the ESC key correct?

[tnahpele]

Try instead holding the "o" game button instead.

[mavrothal]

When I hold down the Escape key (upper left corner circle with X next to magnifying glass) nothing happens.

Do NOT hold the <esc> key (I believe the auto-repeat is disabled). Just keep tapping it while booting up, immediately after you press the power button, till you get to the "ok" prompt.

[Keith]

 
Still not working on either machine :-(.  As soon as I come up from off or restart I will begin tapping the ESC key and nothing.  I have tried to vary the frequency taptaptaptap to tap     tap     tap  and nothing seems to be different.  FWIW, both machines are G1G1 machines and are actuall from 2 different distros (one to VA and one to IL at different dates).  Yesterday I reflashed one machine to the latest/greatest.  I have tried with SD in and out.  Both machines will very quickly moves to the X man and then have the arrow go around him pointing at the little dots and then hit the sugar interface.  The only interesting thing of note is in the background at the frequent tap method starting in the upper left corner "home" position I will see a black cursor with a bracket come through the grey desktop and actually move across the screen on every tap.  In the bottom right corner of the bootup screen there is the Fedora Remix logo.  All software is up to date. 

As far as I can tell there are no obscure control panel settings checked (e.g. battery savings).  The 0 key recomendation just brings me to an error screen saying I need to reboot because there is no OS (or something like that) detected.  Reboot brings me back through the ordinary boot cycle. 

[mavrothal]

That is very strange. OFW functions (like the one we are discussing) have nothing to do with the OS  
Is your esc key working
You can  try a hardware test by pressing the left rocker key during boot (see cheat codes and self-test for more).

[blend]

Keith:One thing that messed me up for a good little while was I would press esc or whatever BEFORE the OLPC was turned on, and when the key was depressed just as the machine was turned on it wouldn't perform as expected.

Another thing that messed me up was the USB card took a little while to boot up, these problems happened ages ago and probably aren't the problems your encountering but perhaps you should do what I did and introduce a little randomness, try doing things a little bit differently or even get someone else to read the instructions and carry them out, maybe theres just one little quirky thing your doing that people didn't account for when they were writing the instructions.

[blend]

Has anyone gotten VLC working on this image?  I tried installing it by enabling the required repository with instructions from here:
http://www.videolan.org/vlc/download-fedora.html

The install process either hangs after a long time, or the cli eventually vanishes leaving the desktop and maybe a few things like the network manager, clock/calander, and bottom panel blank.  Also after the install process sometimes the /var/cache/yum/ folder is reported to be filled to 100%, I've tried to allocate more space with instructions from the internet but failed, is there something I have to do thats particular to this build?

I've installed mplayer with yum install mplayer but it installs only the base features, and the included player doesnt run xvid/divx.
I think I'll try installing vlc with yumex next and see if that works.

EDIT:
natet128:To install the OS initially I had to use the command copy-nand u:\os140py.img instead of copy-nand usb:\os140py.img
So theres at least 3 different methods that need to be used depending on the OLPC unless I'm mistaken, perhaps we could get the original instructions post modified to include
u:\os140py.img and disk:\os140py.img

[kimtoufectis]

So I've heard tell of an updated "180" version of this:
http://osdir.com/ml/fedora-olpc-list/2010-05/msg00021.html

Anyone taken it for a spin?  Worth updating from 140?

[kimtoufectis]

Okay, silence reigns...having no feedback on whether os180 is worth a try, I figured I'd try to blaze my own trail.  Shows what I know.

I downloaded the 180 files that corresponded to the 140 files, specifically the img and crc files, and left the zip file alone.  Followed the steps described near the start of this thread, and ran into the same problem as post#17.  Tried the post #18 solution without success, though with a slightly different error.  Instead of just "Can't open NAND image file" I got:

Can't open disk label package
Can't open NAND image file

Went back and added the zip file to the USB and repeated the whole sequence.  No change in the outcomes.  Tried it holding the "o" game key rather than escape.  Same failure.

Anyone listening with a diagnosis?

[mavrothal]

@ kimtoufectis
try this

[kimtoufectis]

mav--

Thanks for your reply.  I tried the u:/ part of it, and changeing USB ports, but got the same outcome.

Am I right in assuming I need all three files on the USB?  Do I need to unzip the zipped one there?  And while I'm asking what does the probe-usb step in this process even do?

I'm open to trying any theory before deciding the .img file is corrupt, since on my pretty horrible DSL it takes several hours to download 500+MB.  Since it never even starts moving data from the USB (and since I have no idea how it would know the file is corrupt until it loaded it) I've clung to that hope.  Besides, it sounds like the symptoms I have encountered have happened to others... 

[anna]

Am I right in assuming I need all three files on the USB?  Do I need to unzip the zipped one there?

No, you only need the .img and .crc files.  No need to download or mess with the .zip file.

When I want to make sure the XO is reading my usb drive, in addition to seeing what's on my usb drive, I'll type this at the ok prompt:

Code:

dir u:\

OFW should spit out the list of files on your usb drive.  Then, it should be a simple matter of:

Code:

copy-nand u:\<imagefile>.img

If you're having issues with the image file, you might compare your md5sum with someone who successfully flashed their XO with the same image.  I know that's been an issue in the past, where an internet connection is spotty or flaky and the download was somehow corrupted.

[SweetXOGrannie]

I had similar problems with 180. Found the problem was with the usb stick. When I changed to another (re-downloaded) it worked fine.

[mavrothal]

I do not know what you use to download the files but I find that in "difficult" connection the most reliable is the "wget -c http://your_file_url" from the terminal (note: although green, this is not the real URL  ).
I'm on the road so I do not have the file md5sum. Is a good idea though
Why not ask the developers directly?...

[kimtoufectis]

Closing the loop:

Thanks for the various replies; needed them all to succeed.  I reformatted my USB, reloaded the crc and img files, rebooted to the "ok" prompt and repeated the basic process.  Same failure, so then I tried u:\ in place of usb:\ and the copying has commenced.

For the record, there may have been a crc file problem (I found it misnamed as os180py.crc.crc when I copied it from the usb onto a mac).  In any case none of these problems happened when I put 140 on this same machine, making these problems seem pretty random.

After I've roamed around a bit in 180 I'll return to post whether the update adds to 140 in ways I as a non-savvy end user perceive...