thrown solid days into this; thought it's worth asking.
My Pogo Plug Mobile (single USB) came with a third party image which successfully replaced through uart and tftp, etc to have:
- the latest UBoot and env.
- Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 boots off of the USB drive just fine
Debian 3.17 won't boot with the same image in the MMC drive. I get a ramfs saying it can't mount root/ find the rootfs (LABEL route) or /dec/mmc.... the trouble is it doesn't seem to be mounted at all even though mmc is initialized (twice) and the kernel is being read from it. (looking at /dev/ and no mension of mmc or kwsdio 0)
If I put a copy of ALARM on the same MMC drive, it boots fine and no panic there (except that eth0 is down. I hop on one leg when it comes to debian let alone figuring my way through Arch and systemd.
So to summarize, the same uBoot + env settings boots all USB and only Arch MMC but not Debian 3.17 MMC.
Suggestions are very welcome.
My Pogo Plug Mobile (single USB) came with a third party image which successfully replaced through uart and tftp, etc to have:
- the latest UBoot and env.
- Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 boots off of the USB drive just fine
Debian 3.17 won't boot with the same image in the MMC drive. I get a ramfs saying it can't mount root/ find the rootfs (LABEL route) or /dec/mmc.... the trouble is it doesn't seem to be mounted at all even though mmc is initialized (twice) and the kernel is being read from it. (looking at /dev/ and no mension of mmc or kwsdio 0)
If I put a copy of ALARM on the same MMC drive, it boots fine and no panic there (except that eth0 is down. I hop on one leg when it comes to debian let alone figuring my way through Arch and systemd.
So to summarize, the same uBoot + env settings boots all USB and only Arch MMC but not Debian 3.17 MMC.
Suggestions are very welcome.