Phil Elwell

Thanks for the heads up. I'm interested to hear the outcome of any investigation, but this is all unmodified upstream code.

That's the easy bit - now work out _why_ it's happening, and how to prevent it.

`brcmfmac.debug=0x100000` enables the printing of messages from the firmware to the kernel log; you should look for lines beginning `brcmfmac: CONSOLE:`. It won't change the contents of the WARNING dumps.

The Pi reads the overlays the same way it reads the kernel image and config.txt - there is a filing system abstraction that works over SD card, USB drive and...

> The log I posted was one boot process I thought it might be, but wanted to confirm. > And I can not see any access of dtbo files in...

There does seem to be a 4096 byte limit for config.txt, but I haven't worked out where that limit is coming from.

@mkreisl gpio_ir_recv does load with gpio-ir on my network-booted 3B+. If you have `vcdbg` available on your system, what does `sudo vcdbg log msg |& grep -vi hdmi` report?

-9 is ERR_BADMAGIC - the file doesn't look like an FDT file. My gpio-ir.dtbo is 1212 bytes long, but the log above suggests yours is only 508 bytes long -...

That tcpdump would really help...

Thanks, I agree - it does all look OK. In the absence of much of a theory about what could be going wrong, you could try loading a few overlays...