<Armbian-Discord> <r​pardini> FYI, Foundation's 6.1 branch is not producing DTBs correctly... wasted a bit trying to figure out why and gave up, let them work 6.1 a bit before trying again
<Armbian-Discord> <T​enkawa> @rpardini in what way? I just compiled a kernel amd was about to install/reboot so I don't want to melt my existing kernel deb yet
<Armbian-Discord> <T​enkawa> What did they break?
<Armbian-Discord> <r​pardini> Dunno, I just bumped the KERNELBRANCH and got no DTBs anymore.
<Armbian-Discord> <T​enkawa> even the base?
<Armbian-Discord> <r​pardini> flash-kernel (as always) should fail when installing.
<Armbian-Discord> <r​pardini> since it can't find the dtbs.
<Armbian-Discord> <T​enkawa> I'm using our builder not armbian so just a sec
<Armbian-Discord> <r​pardini> back to 6.0 and all was good.
<Armbian-Discord> <r​pardini> maybe it's just flash-kernel acting up again, but I doubt it this time
<Armbian-Discord> <T​enkawa> yeah broke here too
<Armbian-Discord> <T​enkawa> got a theory
<Armbian-Discord> <r​pardini> glad I was not completely unuseful
<Armbian-Discord> <r​pardini> no, sincerely, I don't care enough. I was just doing my round of 6.1's and this exploded in my face while everything else was ok
<Armbian-Discord> <T​enkawa> I need to start researching 6.1 on rpi so this was good info so I thank you for bringing it to attention
<Armbian-Discord> <T​enkawa> oh thats ... interesting
<Armbian-Discord> <T​enkawa> Looks like its a higher up problem
<Armbian-Discord> <T​enkawa> testing now
<Armbian-Discord> <T​enkawa> if I throw in my existing config and oldconfig to it it resets out ARCH_BCM which then of course cascades
<Armbian-Discord> <T​enkawa> trying to enable it by hand now and seeing if it holds
<Armbian-Discord> <T​enkawa> no.. it definitely seems... errored
<Armbian-Discord> <T​enkawa> issue was opened earlier it appears
<Armbian-Discord> <T​enkawa> @rpardini
<Armbian-Discord> <T​enkawa> peiwei's latest post fixed the kernel problem... (at least for me)... I'm testing the full build now.. CONFIG_RASPBERRYPI_FIRMWARE=y has to be explicitly added
<Armbian-Discord> <T​enkawa> there was another dependency turning it off.. ( I think it was the mailbox needed to be turned on)
<Armbian-Discord> <T​enkawa> @rpardini definitely looks better now during the build.. I had to add ARM too to my config so I think they have some dependency issues in the Kconfig but they are correctable I think
<Armbian-Discord> <T​enkawa> by setting things in a certain order until fixed completely
<Armbian-Discord> <r​pardini> Wow that's a deep hole, thanks for the investigation @Tenkawa . Sincerely sticking to 6.0 while they sort this mess out.
<Armbian-Discord> <T​enkawa> heheh
<Armbian-Discord> <T​enkawa> yeah nasty eh?
<Armbian-Discord> <T​enkawa> I'll let you know if it "boots"... its still compiling
<Armbian-Discord> <T​enkawa> (Reminds me too muhc of when I did this for a living with the odd things I ran into...)
<Armbian-Discord> <r​pardini> Let's pin one of those messages, so ppl are aware.
<Armbian-Discord> <T​enkawa> Good idea
<Armbian-Discord> <T​enkawa> I should've used my MBP M1 to build this kernel... then I would've been done in 5 min lol
<Armbian-Discord> <T​enkawa> but I'm building it on the rpi4 its on lol
<Armbian-Discord> <T​enkawa> This might cause a failure shortly
<Armbian-Discord> <T​enkawa> WARNING: modpost: drivers/mailbox/bcm2835-mailbox.o: section mismatch in reference: UNIQUEIDaddressable_cleanup_module376 (section: .exit.data) -> cleanup_module (section: .init.text)
<Armbian-Discord> <T​enkawa> we shall see... its in the module build stage
<Armbian-Discord> <T​enkawa> @rpardini no luck on first boot attempt. I'm going to hook up ttl cable tomorrow morning and start debugging