One card - many OS?

[rahlquist]

100% wrong. This is what the fake is all about: reporting the wrong capacity. And that's why it's necessary to check cards. And that's why it's necessary to point this out to someone who obviously bought a 512 GB fake TF card and refuses to check it (and now ask to do the impossible: Access OS images beyond the real capacity of his fake card). The very same person complains in other posts that he has a bricked board and most obviously the only reason is that his other cards are also faulty.

The reason why I insisted on this is that it's useless to proceed with software issues if you don't rule out simple hardware issues first.

BTW: Both longsleep and I know how to boot multiple OS installations on the same card. Good bye.

i have never seen the "df -H" fail in telling me the correct card size. as an example, i had a MicroSD i used for one of the linux images @longsleep that was 64 GB. of course, after first imaging the card with "dd," and booting from it, "df -H" showed it as only about 4 GB, the image size on the card. i then ran @longsleep's "resize_rootfs.sh" script, ran "df -H" again after a restart, and boom, 64 GB at my disposal.

and even if "df -H" did not work, i still pointed out two other examples from the first step on card imaging on the wiki itself that showed how to verify cards. you don't seem so ready to jump on the snark horse about that, eh? and yes, i ran all my 64 GB MicroSD's through F3 and they are what they say they are.

faddah, 

Please try to understand a bit here. Fake flash cards can respond with false information to any normal command. All df -H does is show how much disk space is being reported as used/free on the device. The device gives linux that info. The device can lie, this is a known thing. These carefully crafted devices will had a minim of flash, will let you copy a huge file over without sending the OS an error. Thats why it is critical to use the proper testing tools. What they do is get the size reported by the flash, then fill it with data they can reconstruct. Once they have written enough to fill the device they then read it back. A faked device will have truncated or mangled data because it wont have the space to store it all. 

As for the disrespect being shown we are at one of those impasses. Yourhighpriestess is laying claim to having a 512GB microsd. They dont exist in public yet. Period. They are also having problems but refusing to follow the known troubleshooting avenues laid out by others because "they know better". I have worked in IT for 23 years and when I troubleshoot a problem and someone suggests something, I do it. Why? because I learn every day. So by resisting the troubleshooting steps and demanding answers they are alienating the people who could help them. Also if you have a person who wants to know how to drive but refuses to turn on the lights because "they can see good enough in the dark" how willing are you going to be to help them? Thats the problem here.

[yourhighpriestess]

I have been using a REAL 32 for the last little bit for my Pi2. I used it for the Pine64 and it doesn't work at all with it. The program just stalls or after burning it, it doesn't do anything. At this point I'm done with the Pine64. Pi2 is better and at least I can use it. I'll be making a claim to my credit card company to get my money back.  At least the people in the forums for the RPi are not all assholes.

Nice. The stubborn guy proud to buy a fake 512GB TF card starts to elaborate a bit on his education.

So you still refuse to test your cards and refuse to understand what's different between burning Linux images on fake cards and trying to burn Android images with Phoenix card. I tried to summarize it in the relevant article even before you wrote the above:

A fake card could be used with a Linux image on a Raspberry Pi since years without a single error but will fail already when trying to burn an Android image with Phoenix card due to the totally different partition scheme used by Android.

high priestess is usually female. Not the first time an idiot confused me with a guy online. What makes you think I didn't test them? The 32 I use for everything is true. Would you like to stop bothering me about my cards and answer my question?

You do realize one of the reasons you are getting such a hard time is your 512GB TF is the only one on the planet right?

I'm not using a 512!! It's a 32. A WORKING 32. Try to keep up!

[rahlquist]

I have been using a REAL 32 for the last little bit for my Pi2. I used it for the Pine64 and it doesn't work at all with it. The program just stalls or after burning it, it doesn't do anything. At this point I'm done with the Pine64. Pi2 is better and at least I can use it. I'll be making a claim to my credit card company to get my money back.  At least the people in the forums for the RPi are not all assholes.

Nice. The stubborn guy proud to buy a fake 512GB TF card starts to elaborate a bit on his education.

So you still refuse to test your cards and refuse to understand what's different between burning Linux images on fake cards and trying to burn Android images with Phoenix card. I tried to summarize it in the relevant article even before you wrote the above:

A fake card could be used with a Linux image on a Raspberry Pi since years without a single error but will fail already when trying to burn an Android image with Phoenix card due to the totally different partition scheme used by Android.

high priestess is usually female. Not the first time an idiot confused me with a guy online. What makes you think I didn't test them? The 32 I use for everything is true. Would you like to stop bothering me about my cards and answer my question?

You do realize one of the reasons you are getting such a hard time is your 512GB TF is the only one on the planet right?

I'm not using a 512!! It's a 32. A WORKING 32. Try to keep up!

Post #1 of this thread?

[Ghost]

Come on, let's call time on this, it's getting silly. I feel like I'm in a famous novel written by Joseph Heller, or it's Groundhog Day or something.

[polypagan]

I take it you are referring to something equivalent to say, berryboot for the Pi, which is really excellent. Even allows you to add OS's that they don't offer.

So far as I can tell, nothing like that has (yet) been developed for Pine64(+).  Berryboot is quite open and you can figure out how they do it without too much trouble.

I've only had my Pine64+ for a day (typing this using it) so I really don't quite understand the bootstrap process.  It seems much more obscure than the (somewhat obscure) RPi.

I failed to create and Android sdcard (in part because I don't use Windoze).  The ubuntu image also fails to dd to the card (seems to change the card size during transfer and therefore doesn't fit!)

ArchLinuxARM worked as advertised.

Code:

uname -a
Linux alarm 3.10.65-5-pine64-longsleep #19 SMP PREEMPT Fri Apr 15 19:55:17 CEST 2016 aarch64 GNU/Linux

Best of luck!