meandu229
Zubeman
Would it be possible to implement Partition Names?
E.g BOOTSD and OTHER or give a prompt to name them
E.g BOOTSD and OTHER or give a prompt to name them
I could change the script to name the partitions when they are formatted.Would it be possible to implement Partition Names?
E.g BOOTSD and OTHER or give a prompt to name them
I have just tried this, and it all seems to work fine while installing using latest firmware image - but when I restart all I'm getting is a black screen. I've left it for about 20 minutes and not a thing has shown on the screen (tried 2 PNY class 10 16GB SDHC's).
I have just tried this, and it all seems to work fine while installing using latest firmware image - but when I restart all I'm getting is a black screen. I've left it for about 20 minutes and not a thing has shown on the screen (tried 2 PNY class 10 16GB SDHC's).
The 16 GB card I used for testing (a TDK) took ages on first boot, much longer than all the other, smaller cards I tried. Maybe it was booting, just very slowly? Was the SD access light flashing?
Thanks for this change,By popular demand, there is a new version (1.4) of the SD installer which labels the partitions for you. These are set as PANDORABOOT (Window/VFAT) and PANDORAROOT (Linux/EXT3).
As I'm working on a few other Pandora related things, I've set up a new site pandorabits.org and that's where I've put the new version (as you can see, it's the only thing on there at the moment).
Even though the SD installer is now hosted elsewhere, if you have any questions, I'll still respond to them here so everyone can benefit.
md5sum sd_install.pnd
b3e7ab476fd28c4e40c68ca7e70f6452 sd_install.pnd
c26e2c326fe74a5ca5ba5597c87d2e21 pandora-rootfs-HF5.tar.bz2
pnd_run sd_install.pnd
I've just tried a fresh download of 1.4 straight onto the Pandora using Midori and it ran fine.
I'm wondering if there is something about the you are getting the files onto the Pandora that is causing the problem, but I've no idea what it could be.
Here is something you can try:
Open a terminal and go to the directory containing the SD installer 1.4 PND. Then enter:
Code:md5sum sd_install.pnd
You should get:
Code:b3e7ab476fd28c4e40c68ca7e70f6452 sd_install.pnd
If the number does not match then the file is corrupt.
You can also do this for the firmware file. If you are using the hotfix 5 file, you should get:
Code:c26e2c326fe74a5ca5ba5597c87d2e21 pandora-rootfs-HF5.tar.bz2
The name might be different but the number should be the same.
You could also try running the PND with the pnd_run program from the terminal:
Code:pnd_run sd_install.pnd
That might give you some more information on why it isn't running.
It's in /proc/filesystems so it should work.Finally a question. Does the current firmware support squashFS?
It sounds like part of the card is corrupt to me.
This sort of problem sometimes doesn't show up until something actually tries to write to the faulty area of the card, so the card might look fine in Windows but starts to have problems once you fill it up.
The md5sum values will be different from the ones earlier in this thread because they come form an earlier version (1.4 versus 1.4.1).