Apologize, did not provide additional info - but thought my question was related. When I ran the expand option on a UHS-1 Class 10 64GB PNY on first boot, it appears to have failed in the process. Noticed a ton of error msgs via UART during reboot. Manual expansion via GParted/check-option yielded no fix either. So was wondering what magic makes some such 32GB+ devices compatible and some not.

In that context, I Wondered how you got your 128GB device to work. Hence the relation to compatibility...thanks.

My results so far: The most expensive card does not work, and the cheapest card does work. Of course.

DOES NOT WORK AT ALL: Samsung Pro 32GB, model MB-MG32DA white and grey card Class 10/UHS-I described as up to 90MB read/80MB write. Blue LED on the C1 never lights, only the red. Left it up for more than 10+ minutes and never boots at all. Tried multiple times & verified the image was written correctly to the card. No luck.http://www.samsung.com/in/consumer/memo ... -MG32DA/IN

venkatbo wrote:Apologize, did not provide additional info - but thought my question was related. When I ran the expand option on a UHS-1 Class 10 64GB PNY on first boot, it appears to have failed in the process. Noticed a ton of error msgs via UART during reboot. Manual expansion via GParted/check-option yielded no fix either. So was wondering what magic makes some such 32GB+ devices compatible and some not.

In that context, I Wondered how you got your 128GB device to work. Hence the relation to compatibility...thanks.

What about to run "resize2fs" on your linux desktop, if you have, with your MicroSD, not with Odroid Utility? This might be out of topic, but I like to have such field experience.

stlpaul wrote:My results so far: The most expensive card does not work, and the cheapest card does work. Of course.

DOES NOT WORK AT ALL: Samsung Pro 32GB, model MB-MG32DA white and grey card Class 10/UHS-I described as up to 90MB read/80MB write. Blue LED on the C1 never lights, only the red. Left it up for more than 10+ minutes and never boots at all. Tried multiple times & verified the image was written correctly to the card. No luck.http://www.samsung.com/in/consumer/memo ... -MG32DA/IN

Hi,Just to update, but I haven't had a chance to try another card yet.I updated to v1.1 ubuntu, and I had to COMMENT out "setenv disableuhs "disableuhs"" otherwise the device won't boot.My card is: Samsung Evo UHC1 32Gb

bohdans wrote:Hi,Just to update, but I haven't had a chance to try another card yet.I updated to v1.1 ubuntu, and I had to COMMENT out "setenv disableuhs "disableuhs"" otherwise the device won't boot.My card is: Samsung Evo UHC1 32Gb

EDIT: Device still will not reboot.

Could you tell us what is exact model name of your MicroSD?Do you success to boot every power cycle with the Card?Commenting out "disableuhs" can make your C1 boot is little weird to me.

I double checked, If I uncomment (enable) "setenv disableuhs "disableuhs"" the odroid will not boot with this SD-Card, I just get the Blue LED blinking.Commenting it out (disabling) allows me to boot, but not reboot.

Just for fun, I bought 2 of the mentioned microSD cards, I put a fresh image on the other card, same issue. Just on the off chance it was a faulty card.

bohdans wrote:Also on the wiki it seems you have the 64Gb model of my card under the "good" section and the 16Gb model under the "bad/slow"

You have Samsung Orange MicroSD. The 64GB MicroSD on WiKi have different orange behaviour, it supports SDXC. But yours is SDHC.Can you get a shell via serial console or ssh? If then, could you capture the log when "disableuhs" is enabled?Seems you have extra MicroSD, so please try Android as well.

The Kingston microSD card isn't corrupted its called "user error" failure between chair and keyboard...!

Its was to do with the Android image mucking up the partition table....

In GParted from Device >> create Partition Table

close GParted and then run the dd command

The lubuntu image on the kingston microSD boots fine --- I kinda get the impression that a lot of the problems people are having might be "user error !"

Why do you run Gparted for partitioning since you run "dd" command to flash official image. The official image already include partition table at the beginning of itself, and resize the partition by "resize2fs" to extend the size in Ubuntu.

You are probably correct, it was just that in GParted the /dev/sdc drive had a little red stop sign by it,"no partition table" and I think I was having problems running the dd burn image command....it was just rapidly running though the dd output but not actually burning the image onto the micoSD card.

Created the table in Devices >> Create Part.. Table and the dd burn image command worked fully. Basically to burn the lubuntu image takes about 5 mins +/- a few mins.

Didn't you have delayed start up with the card on power cycle? Could you check if disableuhs is commented in boot.ini? Some card should be enable the option to start, but it also makes another problem that reboot does not work.

The first C1 boots most of the time (I'd say about 80%) without delay. The second C1 boots nearly never, no matter how long I wait. But if I connect the UART module for debugging and reconnect power, it starts most of the time with ~15 seconds delay and sometimes even without delay. I never had the case of UART module connected and the C1 not booting at all. This behaviour is the same with all 3 SD cards.

Can hardkernel give us a list of compatible cards... It's getting old pretty fast to buy cards at random and "hope" tehy work. The same is also true for micro hdmi cables.. we have bought a few, most of them simply don't work... some need extra ground wire between the Micro-hdmi jack shield and ground, other simply don't work on the C1 yet work perfectly well on other hosts. Frrustration is sinking in withh these little snags that hurt an otherwise great product.

So please give us your list of known compatible SD cards so we can buy cards knowing they WILL work instead of playing trial and error.

At this moment, we can say only "99.9% of Sandisk cards works with C1".

It is very hard to make the list of cards due to the irregular/erratic different reports.For example, Samsung EVO UHS-1 works well except for the 30-secodns-delay-boot issue.But some people told us it boots quickly but it shows the non-reboot-issue.We've thought that each batches of SD card might be slightly different characteristics.. But we are not sure.

As we noted on this link, there are some cable manufacturers don't follow the HDMI standard.viewtopic.php?f=80&t=3323At this moment, we can say "Hardkernel web store", "Ameridroid web store" and "LiliputeDirect web store" are selling the compatible cable.We heard from some customers that "Pollin" seems not to be selling the compatible cable. BTW, we are shipping around several thousands of ODROIDs every month. Only 15~20% of customers are buying our HDMI cable probably.I think 1% or less of ODROID users might have the issue of the HDMI cable compatibility.We really regret why we didn't apply the standard HDMI type-A connector even the board size could be bigger.