search

hyperion-project / hyperion.ng

The successor to Hyperion aka Hyperion Next Generation
https://hyperion-project.org/
MIT License
3.11k stars 384 forks source link

DispmanX is broken on RPi4 #954

Closed m-seker closed 3 years ago

m-seker commented 4 years ago

Bug report

DispmanX is broken on RPi4.

Steps to reproduce

Start hyperion on RPi4.

What is expected?

Hyperion should capture screen without breaking HDMI signal.

What is actually happening?

Hyperion can capture the screen without any problem. Logs are completely fine. However as soon as I start hyperion, the TV loses video signal.

I have to reboot the device to get the signal back. (Probably it can also be done without reboot but currently I don't know how)

System

Hyperion Server:

Hyperion Server OS:

m-seker commented 4 years ago

@Paulchen-Panther @tpmodding @Lord-Grey should we default to X11 on RPi4 until this is fixed ?

Paulchen-Panther commented 4 years ago

It is about time that we tackled the V4L2/GBM implementation

Paulchen-Panther commented 4 years ago

https://www.raspberrypi.org/forums/viewtopic.php?t=265883

m-seker commented 4 years ago

Disabling following line in /boot/config.txt fixes it :

#dtoverlay=vc4-fkms-v3d

https://www.raspberrypi.org/forums/viewtopic.php?t=266059

EDIT : Reboot required after changing.

EDIT : This makes KODI unusable. Don't use it.

jes1417 commented 4 years ago

Disabling following line in /boot/config.txt fixes it :

#dtoverlay=vc4-fkms-v3d

https://www.raspberrypi.org/forums/viewtopic.php?t=266059

EDIT : Reboot required after changing.

I am running hyperion on a pi4 with retropie installed and I guess they use this setting, after commenting out the line and rebooting emulationstation failed to start.

I am getting pretty bad screen tearing while watching video content on the device through kodi and the plex add-on.

I was hoping this would help.

TheEsch commented 4 years ago

Hello, after altering the config.txt now kodi shows following error: ERROR: Unable to create GUI. Exiting

what can i do now?

System: -Raspberry 4 4GB -Hyperion alpha8 -adalight

m-seker commented 4 years ago

@TheEsch Yes, it makes KODI unusable. PI4 is basically not supported yet.

barbiermathieu91 commented 3 years ago

Hello, I still have the same problem on a fresh raspberry OS et the Alpha 9.0.

Raspberry 4 2gb

Thank you for the amazing work

Chaphasilor commented 3 years ago

should we default to X11 on RPi4 until this is fixed ?

@m-seker can we manually switch to using X11 as a workaround? it seems like hyperion-x11 isn't installed by default though...

Lord-Grey commented 3 years ago

@m-seker can we manually switch to using X11 as a workaround? it seems like hyperion-x11 isn't installed by default though...

What OS are you running?

Chaphasilor commented 3 years ago

@m-seker can we manually switch to using X11 as a workaround? it seems like hyperion-x11 isn't installed by default though...

What OS are you running?

Beta release of OSMC, based on Debian 10 (Buster) :)

Lord-Grey commented 3 years ago

Closed as duplicate to #983

antoniocifu commented 9 months ago

In my case (rpi4 + retropie + kodi) Everything was working fine until I deleted the lines of /boot/config.txt

hdmi_group=1
hdmi_mode=16

DispmanX stopped working and now that I have disconnected them again it has worked again (These lines do not make Kodi go down to 1080, only at startup until it detects my HDMI and returns to 4K resolution)