next »

[LesleyT]

I hope not, but it's certainly on artificial respiration at this point.

I used to be really active here but moving over the summer has kept me out of the XO community.

I've upgraded to 708? I think.  Somewhere in the 70x family. 

A day or so ago, when I opened up my XO and waited for the happy dancing sugar icon, it didn't do anything.  It didn't dance.  There was just the XO icon in the screen.  Whenever I hit reset, there was never really a reset -- no scrolling text, no prompts, just the frozen XO icon.

Tried to reflash, wouldn't read USB.  Updated the image on the USB, still no love.  I got to the screen where it shows a USB icon, an SD icon, and a computer icon and it froze. 

A few times it said that it couldn't read the NAND image and shut itself off.

I can boot the pong and diagnostic modes, but no safe modes or alternate boots.  It's like sugar is stuck but not the machine itself.  I'm sensing it's something to do with a bad sleep recovery issue? 

The last thing I'm going to try is to run down the battery and see if that does anything.  Removing the battery didn't help.

If you have any ideas, please let me know!
Thanks

[LesleyT]

I freaking give.

I checked and saw that my old way of rebotting with the img and the fs.zip? file wasn't cool anymore.  SO I redownloaded os711.usb and os711.toc I think? 

No love
not a bit
I'm really frustrated.  searching the wiki and the forms for help. 

Here's what I get on my screen before it stops:
Trying disk fs.zip
something else in here....


OLPC C2, 256 MiB memory installed, S/N #####

OpenFirmware CL1 Q2D16 Q2D


Trying disk:\boot-alt\bootfw.zip
Trying disk:\boot-alt\runos.zip

Oh happy happy joy joy

I still don't understand what's going on.
But it's rebooting and flashing the XO,  At this point, I don't even care that I lost everything on it. (the notes I needed for my test are no big loss now that I had to take the test without them... thanks XO)

I tried to upgrade using the standard img and fs zip files.  No luck.

Then I saw the link to the os711.usb and os711.toc files and thought that was what I had to do.

No luck.

As I was typing the above message. I realized that my computer was looking for fs.zip
So I redownloaded the zip and the img files to my usb and it's working!!!!!

(okay, the XO figure froze for a second and I swear my heart went thu-thunk but it was just a second) 


It didn't update my firmware because there was no external power (remember I was trying to drain the battery)

I don't understand why one wiki page would suggest the .usb file and one the .img file unless it's a firmware difference?  I must have missed a firmware upgrade this summer....

damn....  I'd forgotten how much WORK this thing can be. 

but I missed it.

[CanadaDry]

WB, Lesley, to the fun and games!

[AuntiMame]

I don't understand why one wiki page would suggest the .usb file and one the .img file...

Because the wiki is full of old and misleading info Not through malice, but because the structure of the wiki (if you can call it "structure") is pretty sloppy. I'm on the OLPC Wiki Gang mailing list: employees and volunteers who spend our time trying to make sure the wiki is up-to-date and understandable... and I can tell you that its a battle to find every reference and make sure it right!

When you find an entry like that please edit/fix it. And make sure your edit mentions the build # of the OS and/or the version # of the activity that you are working with. So that if its changes in a future build/version the next person will know 

Aunti

[LesleyT]

Thanks all.

I will try to change wiki info, but I think it was probably accurate, but I didn't have enough info to realize it.  Probably one page was telling me how to update AFTER I'd updated the firmware and the other page was before.  The problem was that I couldn't get far enough into my XO to see if I'd updated and I didn't remember.

[Atrh]

Hello LesleyT,
                        i've also been faced a similar problem like you.But My XO is a little better than yours.I downloaded fz zip file and another one(i forget file name).And then,it's worked.I feel great but not a long moment.It's firstly erase the old Sugar OS.In this state,it is halt in the middle of erasing state.I waited for a while...but nothing change.Still freeze.I think my USB may be a problem
.So..Try with another one.Same Result!! Damn it.
Now,How about your OS?
As for me,i don't know what to do?
The exact error message was"Erasing   2f5 Bad Hash for eblock #2f6".
Have some ideas?

[BoBraxton]

A donation arrived at the higher education institution where I work and the first time I tried the reflash to 767 (0.82) I used a 2 GB flash drive (for the first time). When the reflash failed, I was not surprised so I just reverted back to my trusty 1 GB Kingston, the one I used in June almost a year ago to flash 703 (from 5xx something). Using the 1 GB keychain drive worked fine and I am good to go; however, there is a touchpad problem in that the cursor can move left and right but seems not able to move up and down or on a diagonal. For the moment I work around this by using a USB optical mouse plugged in (I put it on the left side, mousing on the right). I was also able to install Opera web browser as I did last summer on one of six XO systems. That is as far as I got on Friday. The XO that "fell out of the sky" arrived Thursday afternoon so I am pleased.

[Dinky]

Bo:

Check the drive type with fdisk -l  .  My drive type 0e worked for flashing via UBS  from build 650 and 708 to 767.  Type 06 would work for 708 to 767, but not for 650 to 767.
Type 06 is Fat16 and type 0e is W95 FAT16 (VFAT)  LDA.  Have not tested with FAT32 (although it is widely reported to work).

The touch pad missing one coordinate (vertical or horizontal) appears to be a problem with the cable / connector at the ALPS board, which is located on the keyboard frame under the touchpad.  The ribbon cable slides into the connector and one of the pads / pins is not connecting.   Sometimes, sliding the cable out / in of the connector gives a different position that may (or may not) give a connection.  Do not over exercise the ribbon cable -- the ribbon pad material can be worn off.

The only sure solution is to replace the keyboad assembly (which is available).

Not recommended, but ....
The cable can be accessed by sliding out the bottom panel. This is done by removing the 5 screws in the battery compartment, removing the top cover of the battery compartment (display down) and the green trim strip at the top of the handle.  Lift the display and turn 90 degrees.  Lift cables out of guides at left of display support.  The bottom cover can then be pulled back about an inch -- the plastic piece just under display support must be severely twisted to clear the display support.  On reassembly, the plastic piece must again be twisted down and the tabs on bottom cover be engaged (bow cover) as the bottom cover is moved the last 1/2 inch.