<DC-IRC> <lanefu> or alternateively make them crash 30 seconds after boot
<DC-IRC> <rpardini> @markatlnk hey you're the first with such a board. code for it was contributed by @.richn -- I merged it months ago as "WiP" (zero support) but never had any feedback much less access to the board. Looks like the DTB is either wrong or invalid. Can you check (by mounting the image on another computer) that `/boot/extlinux/extlinux.conf` points to a valid/existing DTB ?
<DC-IRC> <.richn> which board
<DC-IRC> <.richn> the vf1 or the vf2
<DC-IRC> <.richn> we have the vf1 working
<DC-IRC> <.richn> never got the vf2 fully working
<DC-IRC> <.richn> the Nezha or the Mangopi
<DC-IRC> <.richn> we had them working but the kernel src had issues
<DC-IRC> <.richn> I ordered but never recieved my board but got a refund
<DC-IRC> <markatlnk> This is the ping MangoPi MQ-Pro, will mount up the SD card on another system in a bit.
<DC-IRC> <markatlnk> This is the pink MangoPi MQ-Pro, will mount up the SD card on another system in a bit.
<DC-IRC> <markatlnk> Plugged the SD-card into a running Pi4 system, get the following.... Can't seem to mount it. Now I did attempt to boot with this SD card on the Mango.
<DC-IRC> <rpardini> I'd guess that's an unrelated problem...
<DC-IRC> <markatlnk> Ok, will re-flash the SD-card and put it in the Pi4. Wonder if the expansion is failing.
<DC-IRC> <markatlnk> Interesting, I re-flashed it from Armbian_23.8.0-trunk.55_Mangopi-mq_lunar_edge_6.1.0-rc3 and put that in the Pi4, this is what I got. Looks like when the Mango expands the card, it fails.
<DC-IRC> <markatlnk> Let me capture the first boot log with that card.
<DC-IRC> <markatlnk> It looked the same as last time, "ERROR: Did not find a cmdline Flattened Device Tree". It didn't seem to trash the card like last time, after putting in the Mango and back in the Pi4, I can mount it
<DC-IRC> <markatlnk> Not an expert on OS related things at this level. Looking at the directory, the /dev directory is empty.
<DC-IRC> <rpardini> You're having unrelated, but typical, SD card troubles.
<DC-IRC> <rpardini> what you gotta look for is the contents of `boot/extlinux/extlinux.conf` and the actual files in `boot/dtb`
<DC-IRC> <rpardini> "Wonder if the expansion is failing": no, expansion only ever runs if kernel boots, which it isn't, due to DTB/fdt problems.
<DC-IRC> <markatlnk> Here is the boot and dtb directories. Sorry I know a lot about linux, just not the boot process here.
<DC-IRC> <rpardini> get `cat boot/extlinux/extlinux.conf` pls
<DC-IRC> <markatlnk> Here you go.
<DC-IRC> <rpardini> hmm. I misread the bootlog there, dtb is there. you might wanna try changing to the mangopi dtb, but I think the problem lies deeper:
<DC-IRC> <rpardini> ```
<DC-IRC> <rpardini> Retrieving file: /boot/dtb/allwinner/sun20i-d1-nezha.dtb
<DC-IRC> <rpardini> Moving Image from 0x40040000 to 0x40200000, end=41ae6000
<DC-IRC> <rpardini> ## Loading init Ramdisk from Legacy Image at 41c00000 ...
<DC-IRC> <rpardini> Image Name: uInitrd
<DC-IRC> <rpardini> Image Type: RISC-V Linux RAMDisk Image (gzip compressed)
<DC-IRC> <rpardini> Data Size: 20122365 Bytes = 19.2 MiB
<DC-IRC> <rpardini> Load Address: 00000000
<DC-IRC> <rpardini> Entry Point: 00000000
<DC-IRC> <rpardini> Verifying Checksum ... OK
<DC-IRC> <rpardini> ERROR: Did not find a cmdline Flattened Device Tree
<DC-IRC> <rpardini> Could not find a valid device tree
<DC-IRC> <rpardini> ```
<DC-IRC> <rpardini> might be that initrd is a _bit large_ for the default loadaddr's
<DC-IRC> <markatlnk> How would I do that? Really haven't studied the boot process much.
<DC-IRC> <rpardini> do what, exactly?
<DC-IRC> <markatlnk> change to the magopi dtb? I am used to running Raspberry Pi systems. Is there a better image I should download or is this a change to the one I have already downloaded?
<DC-IRC> <rpardini> yeah this is not RPi-user-level stuff. you could edit the extlinux.conf file to change the dtb.
<DC-IRC> <rpardini> but again, I suspect this is a more complex problem that will need building your own image at the very least, and more probably some u-boot hacking to get going. since you have uart bootlogs, chase the errors on forums/google/etc.
<DC-IRC> <rpardini> also, get a working (vendor?) image, check _their_ bootlogs and compare the sources... that'll tell you a lot.
<DC-IRC> <rpardini> my best guesses would be 1) bump u-boot & blobs; 2) hack uboot loadaddr's.
<DC-IRC> <markatlnk> I do have another image that does boot so I know the machine itself is fine. I can get you the boot logs from that. I was just attempting to get the Armbian image listed for this device to run. I suspect others would grab this image as it is the one listed for the Mango and have the same issues. I have way too many projects on my desk to get really deep into it. Figured I would g <clipped message>
<DC-IRC> <markatlnk> et the information out there in a chance that someone could point at a simple fix. I do appreciate the assistance with this. Currently in the middle of a redesign of a projected based on the BeepBerry.
<DC-IRC> <rpardini> Yeah I think Oleg / balbes150 had a working image around 2022, you can try that, but it not supported.
<DC-IRC> <rpardini> That effort somehow got lost in time, and the actual `mangopi-mq.wip` board we have is just a copy of `nezha-d1.wip` btw all riscv64 boards are wip, none are supported. we've too few users and few devs on riscv64.
<DC-IRC> <rpardini> Good luck in your endeavours 🖖
<DC-IRC> <.richn> is it usb or mmc
<DC-IRC> <markatlnk> The MangoPi MQ-Pro is attempting to boot off a SD card with the image provided on the Armbian site listed for that device. That is where I started.
<DC-IRC> <markatlnk> Thanks for the help. If I get more time, will get back to it to dig in deeper.
<DC-IRC> <.richn> well its a wip and never got is fully going
<DC-IRC> <.richn> there where kernel src issues
<DC-IRC> <rpardini> heh looky this https://mangopi.org/mangopi_mqpro
<DC-IRC> <rpardini> image listed is... very unofficial... and I'd bet, balbes'
<DC-IRC> <markatlnk> Most of my projects are wip and they never get out of that stage. Started off attempting to figure out what I was doing wrong.
<DC-IRC> <markatlnk> I do have that site bookmarked, and the one image I have does boot from there. I thought that maybe a newer image would have the activity light do something. At least that is where I started.
<DC-IRC> <rpardini> Yeah get a complete bootlog and dmesg from that image. I'd bet it's Oleg's, and if proven so you can bugger him about it 😉
<DC-IRC> <rpardini> also, would be great if you reported/complained about this to the so-called vendor (MangoPi?) so maybe they realize they gotta talk to Armbian before putting up an Armbian image, heh.
<DC-IRC> <markatlnk> This image is listed on the Armbian site as working with the MangoPi MQ-Pro. Maybe it should get tagged there that it might not boot.