<DC-IRC> <tdwtp> Hi there. Does anybody know, why the images from the armbian website boot on the eMMC of a Nanopi NEO Core, but building using armbian/build tells me it can't find the eMMC (tries to boot from 2 and can't find 1)
<DC-IRC> <tdwtp> I am using armbian-install and tried dd too
<DC-IRC> <Werner> Maybe there was some regression since the images for the release were built
<DC-IRC> <Werner> Needs research
juri_ has quit [Ping timeout: 240 seconds]
<DC-IRC> <tdwtp> I can run the Nanopi Air from build and install on eMMC (which also has it on eMMC 2 not 1). Maybe the eMMC is not properly setup in the neo config/patches?
<DC-IRC> <tdwtp> Build root removed the boards entirely (?) and I can't figure out how to get this one patch back on armbian. Commit logs did not seem to change. I have no clue how to check uboot
<DC-IRC> <viraniac> Thanks for reporting. I think there might be some patches that are missing here for extra mmc support. Let me take a look
<DC-IRC> <viraniac> @tdwtp Raised https://github.com/armbian/build/pull/5447 for your mmc issue
<DC-IRC> <tdwtp> Nice thanks. I checked a little further and it seems ubiit is finding the eMMC, but it's not booting it? It tries to boot from mmc2 but as soon as it tries it fails to boot from 1 (which does not exist) and 0 (sdcard) is not inserted (see my picture). Basically uboot starts it but the /boot on the eMMC is messed up? (I am still trying to figure it out)
<DC-IRC> <tdwtp> Nice thanks. I checked a little further and it seems uboot is finding the eMMC, but it's not booting it? It tries to boot from mmc2 but as soon as it tries it fails to boot from 1 (which does not exist) and 0 (sdcard) is not inserted (see my picture). Basically uboot starts it but the /boot on the eMMC is messed up? (I am still trying to figure it out)
<DC-IRC> <viraniac> could you try creating a build from my branch?
<DC-IRC> <tdwtp> I try in a sec.
<DC-IRC> <tdwtp> So I need to rebuild, cuz image was unstable.
<DC-IRC> <viraniac> Yes, you have to rebuild
<DC-IRC> <viraniac> when you said image was unstable, did you mean you are facing some issues from my branch?
<DC-IRC> <tdwtp> Na i mean i started it and it rebooted every minute. It happens when dhcp does not work
<DC-IRC> <tdwtp> I no have network on it (just a co port)
<DC-IRC> <tdwtp> I no have network on it (just a com port)
<DC-IRC> <viraniac> so its still not detecting emmc even when using my branch?
<DC-IRC> <tdwtp> I can't know. Serial port won't do much. I'll retry
<DC-IRC> <tdwtp> Mostly a second build fixes it
<DC-IRC> <viraniac> Is there any output on serial port?
<DC-IRC> <tdwtp> Yes. It boots and then it crashes after the motd
<DC-IRC> <tdwtp> Maybe balena does not detect something. But it's seems to be a minor issue
<DC-IRC> <viraniac> Allright, that's progress, I guess. Could you please share the output from serial port
<DC-IRC> <tdwtp> Wait
<DC-IRC> <tdwtp> Aw yeah once it crashes it resets putty... I only have the shutdown I'll boot it in a sec again
<DC-IRC> <viraniac> In putty, there is option to log all output. May be you can use that. https://my.kualo.com/knowledgebase/?kbcat=0&article=888
<DC-IRC> <tdwtp> I am going to love that
<DC-IRC> <tdwtp> Eeyyyyy the OpenBSD secure shell is working again (withe air image on core it does not work)
<DC-IRC> <tdwtp> Aaaaaand eMMC is booting! Thank you!
<DC-IRC> <tdwtp> No i do food stuff thank you!
DC-IRC has quit [Read error: Connection reset by peer]
juri_ has joined #armbian-allwinner