Thank you.
If it’s the debian you found here, it’s a headless version so it’s normal. This version aim to get you the maximum ram available for networking and I/O.
PmM activates GFX selector only if a /dev/mali exists (which means the mali driver is loaded).
If you need Xorg and Mali, i have release here an ubuntu with gfx support.
Bye.

Guillaume! I have bricked my device! I did, by hand, the steps in the MMC_to_NAND.sh. I have my own kernel and rootfs, and I wanted to burn it on the nand… But now the problem is that the device is showing:
NAND read: Can not find partition ‘boot’
boota: bad boot image magic, maybe not a boot.img?

what u-boot params are you using?

Also, as an aside-> is your server farm doing ok? no signs of wear and tear on the flash?

I made the changes to the A10’s nand driver and wrote the nand-part utility (originally posted on the miniand.com forums).

This version of PMM has a problem with the u-boot.bin not having the correct boot command string. I made changes to the lychee u-boot that fixed this (and uploaded it to http://dl.miniand.com/patwood/u-boot.bin); if you’re building your own, you should pull down the modified sun4i.h header from http://dl.miniand.com/patwood/sun4i.h (for 1G boards, change PHYS_SDRAM_1_SIZE to (1024 << 20)).

Hello guillaume,
I’ve been reading your article and testing on my cubieboard.
Both your ubuntu and debian imgs work successfully on cubieboard’s nand.
Yet my DVI+HDCP monitor couldn’t get any signal from cubieboard(as well as the andriod imgs)

So far, I’ve been trying all graphic settings on Pimp my Mele.
Also I tried to edit script.bin or added uEnv.txt from someone else’s DVI layout solutions, but still nothing changed

I’ve been trying to use different sources of USB power.
desktop, laptop, USB charger even portable battery.

but still it only respond to berryboot img.

it says on their website:
The On-Lap Monitor supports DVI signal through HDMI port. On-Lap Monitor can connect to laptop, iPhone/iPad or any electronics that provide DVI signal output and HDMI port to allow for expanded images and application use.

some say that A10 and android doesn’t really support DVI and VGA output.
but then it won’t explain why berryboot does the job.

so I am thinking it might be the kernel or A10 driver.
I tried to replace script.bin from bootberry img to your imgs but the outcome is still the same.

sorry I know it’s nothing reverent to your project.
but I was just hoping there could be a simply solution to it.

I’m not an expert of video stuff but as far as i know, hdmi signal is the same as dvi.
That’s why you can convert hdmi to dvi with a simple cable.

If you plug your cubieboard to a classic hdmi display (lcd, tv), is it working well ?
You should put your script.bin at hdmi-420p and try it.

If it’s working, perhaps your screen is not synchronizing with the live signal.
The hdmi is loading as module after the boot process. try to unplug the usb power and replug. try to unplug the hdmi and replug.