Joggler stuck on O2 logo

[aitch]

My Joggler is stuck on the O2 logo during bootup. I have had this problem before and have successfully reflashed the OS. However this time it isn't working.
I have followed various suggestions on this forum including attempting to boot from another OS such as Mint to delete the internal partitions, but I don't seem to be having much success.
It seems that it is not recognising the USB stick, even though it is one that I have used ok in the past.
I had to reformat my USB stick at one point and I suspect that it isn't in the right format - I formatted it using BOOTICE as FAT16 - is this correct?

[offbeatdave]

I always use FAT32.

You may need to use the USB hub and a keyboard method to get theUSB stick to boot.

1. With the Joggler off plug the reflash USB stick and USB keyboard into the USB hub;
2. Power on the Joggler and immediately continuously press ESC button for about 20secs.
3. Blindly type in

Code: Select all

fs0:

and press enter. Nothing will appear on the screen.
4. Type

Code: Select all

boot

and press enter.
5. If the Joggler doesn't boot into the USB stick, type

Code: Select all

fs1:

and press enter before typing in

Code: Select all

boot

and pressing enter.
6. Still nothing? Try

Code: Select all

fs2:

and

Code: Select all

boot

I have had a Joggler which bizarrely needed fs3: to get the USB to be recognised.
After a reflash all should be well again with USB/Internal booting although sometimes I've found it takes a couple of goes.

[aitch]

I had also used FAT32 but that didn't work either - what did work was using a USB hub with a keyboard and USB stick, as you suggested. I am sure that I only used a USB stick before, but I my memory may be as bad as the Joggler!!

The main thing is that you pointed me in the right direction, and my Joggler is now working again - Thankyou

[offbeatdave]

Basically sometimes the joggler gets confused and needs telling where the usb is. It should normally go straight from the USB port but if this fails, the above is they fix.

[aitch]

I've now reinstalled PnP III, and I must the latest version is very impressive! Now got a fully functional Joggler again.

[aitch]

Well it seems that my Joggler may have given up the ghost once and for all.

As I said in my earlier posts, I managed to reflash it and installed PnP III, and all was going well until a couple of days ago when it rebooted itself and got stuck on the O2 logo once again. I went through the reflashing process again, and watched it go through the restoration process and the final shutdown, and everything seemed to be ok with the reflashing process. However on reboot, it is stuck on the O2 logo. I have tried reflashing it a number of times with the same result.

I might have to resort to running something from the USB stick instead.

Before I do this, I could edit the jogglerflash.sh and remove the joggleroff command from it (but which one?) to stop the shutdown. If I do this, any suggestions on what I can check out (filesystem, etc)?

Thanks, H

[Mevi]

Always sad when a Joggler decides to retire itself. Out of the 5 that I have is a Joggler refused to do anything but show a boot logo - no boot from USB so the reflash tool was a no-no.

What might interest you, if you fancy living life on the bleeding edge of Joggling, is that overwriting the EFI chip with the alpha v0.3 of Coreboot & SeaBIOS that Inaxeon has been working very hard on brought that particular Joggler to life. Currently the alpha version is limited to booting MSDOS with more work on SeaBIOS still remaining, but you might want to keep an eye on the progress of that project if your Joggler is otherwise R.I.P..

[dwl99]

The internal memory in Jogglers seems to be very fragile & they get corrupted very easily. I think it was Buzz who used to recommend sticking to booting from USB to prevent the internal memory from wearing out. My 3 Jogglers have all had recurring problems with the internal memory failing & needing a reflash.