don't you think it's somewhat odd to bug Intel who declared Yocto as their supported linux distro with questions about (unsupported) other distros?
Of course the EmutexLabs archive is not delivering Yocto. Your installation has simply failed. Besides, this issue has been discussed in the community beforeRe: Ubilinux installation fails : Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
Hey! I know it's not an Intel issue, but I thought I'd throw it out to the community.
I've certainly posted on the EmutexLabs forum as well. I'm basically just trying to get the community to let me know if they've had success. I think something with their image is wrong, honestly and I just want to know if other users have had the problem.
I have used those instructions and I've tried these instructions as well:
I thought this was COMMUNITY. But if this is only for issues, sorry I posted here. Apparently, there's no place to discuss if you're having problems. I've not had a successful install of this and I wondered if anyone had success with the current release is all.
Some information here... as soon as it gets to ROOTFS, it throws an error about "Cannot allocate memory of size 1610612736 (exactly the 1536MiB in the BIN file for the ext4). I'm wondering if my partitioning is failing in some way - it doesn't seem to partition correctly.
I think the steps from EmutexLabs should work without problems, are you doing changes in the partitions of the image?
I suggested you to contact EmutexLabs because they are the owners and experts with this image, so if there is something wrong with your install they should know the source of the problem.
Now as I said, their steps should work without problems. Have you tried with the Yocto image to see if the board boots correctly?
Thanks for the reply! Yep, I've tried on Mac & PC (but not linux as I don't have a hardware install - I might try from a VM).
I am working with them on this. Yep, I actually have confirmed I can successfully reload the Yocto image so I'm confident it's not BRICKED.
Seems like its definitely some kind of "size" problem with the download specifically. They say they haven't seen this problem. I have this problem even with their 2014 install (was able to find it after all).
I'm actually wondering if there's some kind of problem where the file system is not being properly partitioned or something.
Anyhow, thanks for the suggestion. I really wanted to share this to see if anyone else was running into this.