[Raspi 4B] HDMI lost power for seconds when booting

[latipun]

I installed ArchLinuxARM-rpi-aarch64 from the download page few months ago. I didn't install GUI since I use this to be a server.

Then I configured /boot/config.txt so I have some borders around the monitor, here is my /boot/config.txt settings are:
$this->bbcode_second_pass_code('', '
enable_uart=1
disable_overscan=0
overscan_scale=1
')

When booting, it works as intended, I have some borders around monitors, the overscan is scaled correctly. But after some time, the HDMI power is lost, in my monitor showing "HDMI not detected" and the screen goes black for a while. After that, the screen suddenly came online, but my boot setting didn't apply, no more borders. After login, here is what I got with tvservice output.
$this->bbcode_second_pass_code('', '❯ sudo tvservice -s
state 0x2 [TV is off]')

Here is my video to show what is looks like from what I describe here:
https://photos.app.goo.gl/xAAfa64zEbNPpgc27

Thanks for your help.

[robg]

Assuming that the generic kernel handles the settings in /boot/config.txt just as the Raspberry Pi kernel does, you might try adding

$this->bbcode_second_pass_code('', 'dtoverlay=vc4-kms-v3d')
and/or

$this->bbcode_second_pass_code('', 'hdmi_force_hotplug=1')

(cf. https://forums.raspberrypi.com/viewtopic.php?t=255478 (a slightly outdated summary, but KMS is now the default development target for RPI; and https://www.raspberrypi.com/documentati ... ce_hotplug)

[latipun]

Thank you for your reply.

Unfortunately, that does not work.

Trying to add those two didn't do anything. Add one of them, still same result. In fact, whenever I have hdmi_force_hotplug=1 option, when booting there's rainbow screen. After a while, the screen was online showing my login screen, but overscan_scale didn't take account.

[darksky]

I am not completely clear on what you are doing with the rpi image and linux-aarch64. From your video it did not appear that you were trying to boot into a DE. I have no idea if you are using uboot or not either. I do not use uboot to boot the upstream kernel by the way but it does need a special cmdline.txt/config.txt.

With the linux-aarch64 upstream kernel there should not be an overlays directory in /boot so specifying an overlay is not going to work. Some overlays should work with the linux-aarch64 upstream kernels but they have to be manually copied over but not gpu related overlays like dtoverlay=vc4-kms-v3d. V3D is not presently in the upstream kernels but it will be starting with kernel 5.20. I compiled the upstream linux-next kernel to test and so far V3D seems to be working good on my rpi4.

I do not know if your issue is related is related or not to what I posted near the bottom of an old issue they revived last week or not because I am not really sure what you are doing but I told them last week starting a few weeks back I was booting up to my GUI login screen and then getting a no monitor attached message with upstream kernels 5.15 and 5.18 but kernel 5.19-rc was working good. We also talked about the new 5.20 kernel and V3D. They also said they were not going to submit any upstream upstream changes with fixes with my new issue as they were concentrating on kernel 5.20 now because it will be their new LTS kernel. I have posted a pic of the of me booted into the new upstream linux-next kernel this week with V3D reporting various stats by the way in the thread.

https://github.com/raspberrypi/firmware ... 1184264733

Have you tried the linux-aarch64-rc kernel to see if there is any difference?

[latipun]

Yeah, thank you for your response, I didn't install GUI because I'm learning and trying to make rpi to be a server that I don't need GUI (edited my post).

Since downloading that image a few months ago, as far as I remember, I didn't tweak the kernel and the firmware, only the /boot/config.txt. I just downloaded my packages that I need and configured them. Whenever I run pacman -Syu, I didn't get an error. But it always has that "HDMI not found" for a second when booting. I just had a chance to make this thread recently. So, I didn't understand what made that behavior. I didn't know much about rpi, kernel, and firmware.