could easily be actually. i forgot about the ram im not a hardware guy really heh. (yeh they are, just checked. i must have totally misread the part number earlier).
I suppose block devices are like hds in the fact they use blocks and they probably do show a device geometry, although something like cylinder size wouldnt be applicable to a flash device. although sector size is relevant for partitioning tools etc.
Off a bit on a tangent; on the Chumby the original 2Gb microSD had four partitions. The first boot one I could never read; just copy. The 2nd and 3rd were duplicates of each other and had the main Linux OS on them and the 4th was was just for storage and additional widgets. The 2nd, 3rd and 4th were EXT2 partitions. This was noted taking the microsd out of the device and looking at it on a Linux OS with GParted.
That said Joggler #5 has only been configured for booting into XP at this time via a USB stick or USB SSD stick. I did initially boot it into the Joggler OS. It initially booted fine. Last time though I tried without the USB sticks; it hung at the O2 screen. I used Roobarb!'s application to bring it back to O2 Joggler life.
- Pete
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Buzz, is it your belief that mmcblk0 takes up all the storage space of the 1GB chip?
What command in Linux would be used to create the partitions in mmcblk0?
What command would be used to create/define/name mmcblk0 itself?
Would any of those commands show the total size of the 1GB chip?
Sorry if these questions don't even make sense. I guess I'm still struggling to try and fit this into my past experiences.
mmcblk0 is the raw device, so it should be all of it yeh. not sure what you mean by create. mmcblk0 is the device. any partitions will show up as mmcblk0pX - reading from mmcblk0 should image the entire disk. try "sudo blockdev --getsize64 /dev/mmcblk0" to get the size in bytes.
I final got around to googling "mmcblk0" and have now learnt that this name/designation is used on other devices than the joggler!!!
So mmc refers to Multi Media Card or flash memory devices?
I tried "sudo blockdev --getsize64 /dev/mmcblk0" in a Putty SSH session to my Joggler booted into Tango and got:
# sudo blockdev --getsize64 /dev/mmcblk0
-sh: sudo: not found
#
Am I doing something wrong or should my mother have just held her water and drowned me at birth???
that means the "sudo" command was not found. you are already root, so no need to sudo, however you may or may not have the blockdev command. I hadn't intended my instructions for the build in linux anyway, but a full linux distro. boot ubuntu and try it. cat /proc/partitions may already have the cached size of the device in it.
After reading some of the previous comments in this thread that talk about having to reflash 6 or 7 times before it finally works I decided that I'd sit and watch the telly whilst repeatedly reflashing my jogger, giving it 30 minutes to reboot after each reflash.
After 3 reflashes it still stuck on the O2 logo screen. However I did notice that the number reported at the end of " rebuilding boot partition" changes each time. I had 0+1949, 0+1950 and the last reflash (it had to recreate the partition layout) it came up with 0+1944.
Shouldn't this number remain constant seeing as its reflashing the same content/files each time?
New version complete (System v1.07, Script v1.11). Tested on all the Jogglers in the house and it's working great for me.
The system, when run without the reflash script, now gives the option to press a key for a login screen, making it more useful for troubleshooting. I've also done some tidying up to the reflash script, adding a short pause before checking the flash memory, making sure network settings aren't carried over between units. The filesystem scan is also disabled by default now.
Uploading (slowly) now, so should be available from 7pm.
As noted elsewhere, I've just tested this version (System v1.07, Script v1.11) on two previously problematic machines and all is hunky-dory!
Many thanks (again!)
"EVERY DAY I'M JOGGLERING!" Jogglering since Dec '09;
Tinkering with Jogglers since Feb '10 thanks to PMJ, Jogtools, PnP & sqpOS;
Gave something back Feb '12 to Apr '14 with PnP Mk II & PnP III;
Finally 'completed' PnP III Apr '15!
Hi there,
Did anyone ever figure out how to get past the old 'All updates have downloaded, will now reboot' loop that some other people seem to have had?
I've used the reflash tool which seemed to work really well but I'm still just stuck with this loop problem
Any advice is much appreciated.
Cheers
samjog wrote:Did anyone ever figure out how to get past the old 'All updates have downloaded, will now reboot' loop that some other people seem to have had?
Yup, I wrote a patcher that fixed that problem last year. Posted a thread on it and everything.
Have a read of the thread (well, post, actually), or just hit the 'various tools' link in my sig and look for 'Update Control for Joggler'.
I've even got things working now that weren't working when I first got the Joggler
Thank you for your time and dedication.
That's okay - can't count how many lunchtimes and evenings I've spent on Joggler stuff, but I've learned a lot and this is one of the nicest little tech communities around, I think.
Turvey wrote:Small question though, where does the 'birdslikewires' name come from?
im not a hardware guy really heh. (yeh they are, just checked. i must have totally misread the part number earlier).
