linux-rpi-6.1.54-2-aarch64 hangs pi4 running GUI

[bloke]

with a config of
dtoverlay=vc4-fkms-v3d-pi4
dtoverlay=rpivid-v4l2

and if i upgrade to linux-rpi-6.1.54-2 my pi4 hangs dead.

Not sure what other info you might want to diagnose, happy to try and find and post if required.

Anyway, the way out of this i found on a pi4 is to comment out the above lines on another system and then boot the pi 4 again. The GUI wont start and you can downgrade the kernel package. Hope it might help someone out.

[graysky]

Can you try 2 tests?

Test 1:
dtoverlay=vc4-kms-v3d
display_auto_detect=1

Test 2:
dtoverlay=vc4-kms-v3d
display_auto_detect=1
dtoverlay=vc4-kms-v3d,cma-512
dtoverlay=
disable_overscan=1
disable_fw_kms_setup=1

[bloke]

I should have been a bit more detailed.

This is my config.txt in full.

See /boot/overlays/README for all available options

dtoverlay=vc4-fkms-v3d-pi4
dtoverlay=rpivid-v4l2
initramfs initramfs-linux.img followkernel

# Uncomment to enable bluetooth
dtparam=krnbt=on
# sound
dtparam=audio=on
max_framebuffers=2
disable_overscan=1
arm_64bit=1

[pi4]
# Run as fast as firmware / board allows
#arm_boost=1
over_voltage=10
arm_freq=2300
gpu_freq=900
v3d_freq=900
# had a crash with this....hmmmm
#force_turbo=1
# usb tweaks
#otg_mode=1


I use both displays, in extended fashion.

I'll try the tests. And let you know results.

[bloke]

I tried both the tests and they both work, however just as single monitor - other monitor switches off. Active physical port is 2nd port from usb-c.

$uname -a
Linux hostname 6.1.54-2-rpi-ARCH #1 SMP PREEMPT Fri Sep 29 12:39:18 MDT 2023 aarch64 GNU/Linux

I need to go back to previous kernel for extended display to work. Any other suggestions?

[graysky]

I don't use dual heads so cannot advise. If you feel there is a regression introduced, please open a ticket upstream:make_clickable_callback(MAGIC_URL_FULL, ' ', 'https://github.com/raspberrypi/linux/issues/new/choose', '', ' class="postlink"')

[bloke]

opened issue upstream.
make_clickable_callback(MAGIC_URL_FULL, '
', 'https://github.com/raspberrypi/linux/issues/5624', '', ' class="postlink"')

I know it works on every kernel version prior...

Thanks.

[bloke]

Hi Guys,

the guys @make_clickable_callback(MAGIC_URL_FULL, ' ', 'https://github.com/raspberrypi/linux/issues/5624', '', ' class="postlink"') asked to report here
This issue is also for linux-rpi-6.1.54-3-aarch64 here is what popcornmix said

[quote]
I think you should report this to Arch maintainers.
We don't know what the difference is between 6.1.54-1-aarch64 and rpi-6.1.54-2-aarch64.

If Arch can confirm exactly what the change is (e.g. config options or a bump in git hash) and the regression came from this repo, we can investigate further.[/quote]

[bloke]

Is anyone else running dual displays with fkms driver and experiencing this issue?

[solskogen]

Have you tried with the kms driver instead?

[bloke]

Hi yes I have tried. It works (when upgrading kernel), it only gives me a single display however.

I worked out that adding
hdmi_force_hotplug:0=1

allows me to have extended display with kms. but, if i upgrade the kernel i get mirrored display with a mouse movement of extended, totally bizarre. It works in extended on kms & kernel 6.1.54-1-aarch64

my issue then is I don't get jack audio from the pi4, just the 2 x hdmi. I use a headset quite often plugged into the 3.5mm audio jack.