10-08-2018, 05:17 PM
(10-08-2018, 04:52 PM)evilbunny Wrote:Yup - the SDcard is my usual boot but it calls for rootfs on the NVMe. (And the eMMC is normally unplugged else I cant boot 4.18 or 4.19.)(10-08-2018, 04:46 PM)dukla2000 Wrote: Not sure what my setup gets wrong but no matter. (t is something weird if I leave my SDcard in - if I remove it all is fine with 0.7.10 on the eMMC.)
Does the sdcard have a bootable image on it? If so it could be a race condition between which root is mounted.
At the moment really perplexed: my understanding of the RockPro64 says the eMMC takes preference in all cases, all ways, if it is present. Now I do know that I have hacked my eMMC mercilessly trying to sort out what is wrong booting 4.18 or 4.19, including some low-level hacks on the (eMMC) boot sections.
But the giveaway symptom is this: on my normal setup my machine name is rpro64 (not the default rockpro64). If I dd 0.7.10 to the eMMC and reboot with the SDcard in, the login prompt is for rockpro64 but rock64/rock64 does not work. (Nor does my normal userid/password which are both changed from the default.) But the real giveaway was when I tried stretch - the line above the login prompt was for ubuntu 18.04. Which lead me to remove the SDcard and all was as expected.
Puzzling but as I say (I think) irrelevant as a comment on 0.7.10!
- ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
- PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
- PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC