I had problems using the 8GB Image on a 8GB SD-Card. The 4GB Image worked fine, so i just had to extend the partition size of sda2.
I'm using a Class10 Sandisk and was a bit anxient, if it works but the disk was recognized and didn't show any errors with 17,7MB/s write and 320MB/s read speed (strike!!!)
[email protected]:/# dd if=/dev/zero of=/var/empty.file bs=100000 count=2000 2>&1 | grep bytes
200000000 bytes (200 MB) copied, 11.2758 s, 17.7 MB/s
[email protected]:/var/www/ss# dd if=/var/empty.file of=/dev/null bs=100000 2>&1 | grep bytes
200000000 bytes (200 MB) copied, 0.625965 s, 320 MB/s
However, I had some strange problems getting the new image running.
After putting the new microsd into the slot and booting up the dreamplug, i was thrown into the debuggin console. The error was something like ext2fsload: couldn't load uImage - wrong file system
I was rather bashing my head against the wall and tried the commands to load the system (again, the commands come from my brain and might be wrong in their syntax):
usb start
fatload usb 0 0x6400000 uImage
bootm 0x6400000
This worked like a charm and the dreamplug booted up the new wheezy system. Well, i really didn't understand what was going on - tried rebooting and was thrown into the debugger again.
After printenv i did see that the command for loading the image was
ext2load usb 0 0x.....
Why there was there ext2load?? I just bought the dreamplug some days ago, brand new, original system worked fine and apparently the sda1 was in ext2 format? I don't know.
I just changed the env-arg from ext2load to fatload and invoked a "saveenv" to write the settings persistant to the box and now everything works fine.
However, the whole precdure took me the whole friday evening - I mustn't say there was a pretty annoyed wife kicking my but

Maybe, someone can explain the file-system thing to me...