04:30 <fatal> hi, anyone else got this problem? I connect power to a banana pi-m5 and it does not boot, so i have two options either i enter `boot` or do a reset after i connect via serial console.

04:31 <fatal> and yes, reset also only starts u-boot when i'm already connected via serial.

04:32 <fatal> this is what i see in tmux after i hit enter: Unknown command '����!<INTERRUPT>xX���!<Ee8X���<' - try 'help'

04:33 <DC-IRC> [Discord] <Werner> If other output is good using 115200 baud then this may indicate a corrupted boot loader or corrupted sdcard.

04:34 <fatal> but i now can press reset or type boot and it just boots

04:34 <fatal> it does not work when serial is disconnected on boot

04:35 <fatal> well sometimes, maybe after reflashing. but after that the same behaviour.

04:36 <fatal> i even zeroed out the first 10MB before dd'ing the image

04:37 <fatal> (just in case)

04:37 <DC-IRC> [Discord] <Werner> Using dd won't tell you if writing was successful since this method lacks verification of written data.

04:37 <fatal> i'm dumb. i' using screen not tmux ofc.

04:39 <fatal> i assume that it was successful when it boots after flashing the sd

04:44 <fatal> ok, so for some weird reason the board also boots when i have a screen plugged into the hdmi port.

04:45 <fatal> so it surely can't be the sd card

04:47 <DC-IRC> [Discord] <Werner> I guess its better to put a detailed report of what and how works into forums. From my guts feel there aren't many people dealing with amlogic nowadays. most are rockchip, and allwinner coming up a bit again.

04:53 <fatal> i'm not even sure if it boots successfully after the flash since i have done this so many times that the board mostly hangs on serial to usb. one more interesting thing is when i shut down the board get these outputs after it already powered off: https://paste.debian.net/1388027/

04:54 <fatal> don't know if it is even important but i just added

04:55 <DC-IRC> [Discord] <Werner> No clue

04:59 <fatal> i said powered off because of the led indication

04:59 <fatal> clearly there is something going on past runlevel 6

05:01 <fatal> er, 0.

05:06 <fatal> maybe not that important. i'll just stick around, thanks Werner.

05:08 <DC-IRC> [Discord] <Werner> As mentioned I'd try for once start over with a fresh image on a different sdcard flashed with something that actually verifies written data (preferred USBimager, alternatively BalenaEtcher where latter isn't actually recommend). Also try different kernel images since boot loader might be different (newer/older) as well.

05:08 <fatal> i'm just trying to get this to work and then flash u-boot to the nand and boot off a wd-blue via usb since it performs way better.

05:08 <DC-IRC> [Discord] <Werner> And for the other again, report in forums with details

05:11 <fatal> right, new sd card. noted. but kernel should be ok since we hang already before u-boot gets even picked up by the cpu.

05:12 <fatal> that's at least what i assume the cpu logic does on power on

11:16 <deskwizard> Hi, I was wondering if someone could give me a hand with a device tree overlay; I must be missing something obvious as usual. I know I have the right settings and my wiring is correct, since if I make the changes manually (ie. decompile dtb, make changes, recompile, reboot), it works. Since it's just a gpio pin change, I grabbed the orange-pi5 no-led or whatever it's called overlay, changed the required fields comparing the DTS'es and tried to use

11:16 <deskwizard> that, but it doesn't seem to get enabled after I run armbian-add-overlay. Here's the overlay content https://pastebin.com/Yd0b0Tsn

11:16 <deskwizard> thoughts?

16:43 <DC-IRC> [Discord] <crackcod> hello, i am new. can somebody help me with getting framebuffer working on my orange pi zero 2w, i tried to google this but nothing came up. i am pretty new to linux my self

21:55 <fatal> just search for linux/debian/arch/gentoo +framebuffer