Display not working with v1.36 #252
Comments
|
@jlinton any ideas? |
|
Alright, a new update (on Arch Linux) has rendered v1.35 without display as well. However, by adding |
|
Same behaviour is happening with Fedora 39 and Fedora 40. |
|
Maybe something here? |
|
"HDMI audio is inherently linked to the video mode, and running audio from the firmware and video from the kernel will run into issues should the video mode ever be changed or otherwise not match." Makes sense. Same error message seems to plague opensuse. Have you tried Arch with pftf v1.34 ? |
|
It works with v1.34 and below. |
|
opensuse devs came to the conclusion that changes in raspberrypi-firmware-dt from 2023/11/21 messed with the device tree. The solution being reverting to an old version (as seemingly pftf 1.34 and prior are including...?) and or DMA patches at kernel level. Ref.: https://bugzilla.opensuse.org/show_bug.cgi?id=1217512 "I am afraid that vendor changes around new RPi5 makes new |
|
I copied the |
|
Same here. Fedora 40 working fine now after copying *.dtb files from pftf 1.34 ove pftf 1.36. |
* This is a workaround for #252 * Also update EDK2 to latest
|
Please try with the newly released v1.37 that reverts the DTB to a version before the HDMI Audio changes and see if that works better. |
|
I can confirm that release 1.37 is working fine in a dual boot with Windows 11 (wor) & Fedora 40. |
|
Interesting discovery: booting current Raspberry Pi OS with DTB from pftf 1.37 mostly works but it is impossible to reboot or power down the device (the usb disk stays always on). |
|
Also, I am not sure mini-uart is working properly. I have to disable it to make bluetooth work both in Fedora and Raspberry Pi OS. |
|
@Roburetto You should probably open a new issue containing applicable logs for the BT problem. I personally never got BT to work on any OS, getting |
|
The BT issues are almost assuredly because the Linux kernel cannot flip the secret console mux, and the PFTF config.txt is defaulting the firmware/linux consoles to the pl011. Although its a bit hit/miss the unmerged patch on the edk2 mailing lists to set the baud on both the pl011 and the miniuart fixes BT enough to pair with slow devices like keyboards in ACPI mode they still need to be inverted back to the defaults in config.txt because the BT/DT configs don't work in mainline otherwise. |
|
In my experience Bluetooth seems to work best (only tested pairing headphones and listening to music) if I switch both uart and mini-uart OFF in pftf's config.txt (the drawback being keyboard input on pftf becoming unstable). On the Raspberry Pi OS disabling mini-uart alone renders the device unable to fully power off - something which is fixed when you additionally disable uart. On Raspberry Pi OS I am now facing a different issue: Kwin busts in KDE (the desktop environment does run on X11 provided you disable enabling the composer on start-up but freezes the Pi altogether if you try to run Plasma on Wayland ). It’s worth nothing that Wayland works fine with the default WM provided (LXDE over Wayfire I believe). I wonder if this can have something to with the way the monitor resolution is picked...? |
I am running Arch Linux ARM on my Raspberry Pi 4 (yes I know there is a specific Raspberry Pi version, but I am simply testing for compatibility purposes). I was able to sucessfully boot from it with v1.35, but I have lost my display with v1.36. However, this display issue only occurs sometime during the systemd boot process, as by invoking
fs0:\Image root=/dev/sda2 init=/bin/bash rootwait roat the UEFI shell, I am able to enter a rescue shell. I am still able to SSH into the machine, so I can still try to debug it.dmesg:
Attached is a low-quality video of how the display is lost upon systemd startup.
My.Movie.1.2.mp4
The text was updated successfully, but these errors were encountered: