Hm, that really should suffice. I occasionaly use a lab power supply and the amperage never goes over 1A with this image (I tried it out twice).
Soo, that looks like you may have a faulty image or suffer from recurring bad media.
Or there’s a problem with the hardware writing the image to media for you.
What you might try is to check the checksum of the downloaded zip image (with “md5sum </path/to/image>”) to what’s here at the top of the page.
And if that checks out, generate an md5sum of your unzipped image (you did unzip it did you?) and then md5sum your media with:
dd if=/dev/<your media root partition> bs=1M count=7456 | md5sum -
Mind you, that will take a while, depending on how fast your card and card reader are.
And then check if those last two match up.
For the MD5 of the Zip file, it’s OK.
For the unzipped file (image), i obtain this MD5 : 29d58237686680f916b7a78eef39549c
For the MD5 of the media, i obtain : 0a68e45007fdab89ccf461d45c6f3d2b
Okay, I just checked this here for myself. Looks like your card is the problem.
I copied the image to a card I’ve used for a custom install image and did the same I told you to do.
And the card yielded the same md5sum as the unzipped image file (same md5sum as you got off your unzipped file).
So, that leads me to the question as to how (with which command(s)) you copy the image to your sd card?
For me, I used (as user root):
dd if=2016-07-21-ubuntu-mate-16.04-desktop-armhf-raspberry-pi-bpi-m3-sd-emmc.img bs=1M of=/dev/sdc
Which ends with printing out:
7456+0 records in7456+0 records out7818182656 bytes (7.8 GB) copied, 275.051 s, 28.4 MB/s
And the md5sum of the card? If you still don’t get 29d58237686680f916b7a78eef39549c then I’m afraid your card(s) is(/are) defective or somehow incompatible.
This time i have à new MD5:
7456+0 enregistrements lus
7456+0 enregistrements écrits
7818182656 bytes (7,8 GB, 7,3 GiB) copied, 527,64 s, 14,8 MB/s
4ea5788eab3542609b2f74625fc90088
It’s strange, my two cards are defective or incompatible. Until now the other release works fine with this cards.
I had someone in another thread using win32diskimager and it might be he also somehow broke his SD card for the BPi. But the jury is still out on this…
i have the same problem. I cant boot any OS except Andoid. I use an 2.1 Amp Power Supply. I burnt the images with Win32 Disk Imager. I burnt Android with Phoenixcard and its work. But every OS i burnt with Win32 Disk Imager it never boot up. I can only see shortly the bpi Screen at the beginning.
Pls can u help me
Look at all the hints and tips in this thread, and also check this thread. If you can’t figure out what wrong with all of that, I might be able to make something out of your u-boot output.
Other than that, I can probably not help you.
Hello,
i have installed the image and after
apt update && apt upgrade
it shows the following error
…
fontconfig (2.11.94-0ubuntu1.1) wird eingerichtet …
Regenerating fonts cache… failed.
See /var/log/fontconfig.log for more information.
dpkg: Fehler beim Bearbeiten des Paketes fontconfig (–configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
fontconfig
E: Sub-process /usr/bin/dpkg returned an error code (1)
/var/log/fontconfig.log
…
/usr/share/fonts/type1: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/type1/gsfonts: caching, new cache contents: 35 fonts, 0 dirs
/.local/share/fonts: skipping, no such directory
Re-scanning /usr/share/fonts: fc-cache: symbol lookup error: fc-cache: undefined symbol: FcDirCacheRescan