Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/dev/dri is missing on the RPi 5 #3321

Closed
ShonP40 opened this issue Apr 19, 2024 · 2 comments · Fixed by #3335
Closed

/dev/dri is missing on the RPi 5 #3321

ShonP40 opened this issue Apr 19, 2024 · 2 comments · Fixed by #3335
Labels
board/raspberrypi Raspberry Pi Boards bug

Comments

@ShonP40
Copy link

ShonP40 commented Apr 19, 2024

Describe the issue you are experiencing

I was trying to set up a Jellyfin server on my RPi when I noticed that the /dev/dri directory doesn't exist (the GPU renderer is supposed to show up there to be able to set up hardware acceleration in Jellyfin)

What operating system image do you use?

rpi5-64 (Raspberry Pi 5 64-bit OS)

What version of Home Assistant Operating System is installed?

12.2

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. SSH into the RPi
  2. Attempt to find /dev/dri

Anything in the Supervisor logs that might be useful for us?

Nope

Anything in the Host logs that might be useful for us?

Nope

System information

System Information

version core-2024.4.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.1.73-haos-raspi
arch aarch64
timezone Asia/Jerusalem
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4981
Installed Version 1.34.0
Stage running
Available Repositories 1404
Downloaded Repositories 31
HACS Data ok
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 12.2
update_channel stable
supervisor_version supervisor-2024.04.0
agent_version 1.6.0
docker_version 25.0.5
disk_total 1833.0 GB
disk_used 163.9 GB
healthy true
supported true
board rpi5-64
supervisor_api ok
version_api ok
installed_addons Advanced SSH & Web Terminal (17.2.0), AirCast (4.2.1), Apache2 Minimal (2.7.10), Docker Wyze Bridge (2.7.0), ESPHome (2024.3.1), ESPresense Companion (0.6.5), Home Assistant Google Drive Backup (0.112.1), Immich (1.101.0), Jellyfin NAS (10.8.13-3-3), Lunar Sensor (1.0.0), MariaDB (2.7.1), Mosquitto broker (6.4.0), Netboot.xyz (1.6.3), Network UPS Tools (0.13.0), Nginx Proxy Manager (1.0.1), OpenSpeedTest (v2.0.3), Piper (1.5.0), Portainer (2.20.1), Postgres 15 (15.5-7), RPC Shutdown (2.5), Samba share (12.3.1), Scrypted (20-jammy-full.s6-v0.97.0), Studio Code Server (5.15.0), Transmission (4.0.5-3), Whisper (2.0.0), openWakeWord (1.10.0)
Dashboards
dashboards 3
resources 17
views 19
mode storage
Recorder
oldest_recorder_run April 12, 2024 at 5:55 AM
current_recorder_run April 19, 2024 at 6:42 PM
estimated_db_size 3931.09 MiB
database_engine sqlite
database_version 3.44.2

Additional information

image

@ShonP40 ShonP40 added the bug label Apr 19, 2024
@agners agners added the board/raspberrypi Raspberry Pi Boards label Apr 22, 2024
sairon added a commit that referenced this issue Apr 29, 2024
RPi 5 config uses BR2_LINUX_KERNEL_INSTALL_INTREE_OVERLAYS which builds
the device tree overlays from the Linux tree when building the kernel.
The overlays directory also contains overlay_map.dtb which is necessary
to correctly map overlays without RPi version suffix to the
platform-specific ones. Without this, some peripherals may not work
correctly on Pi 5 without any obvious error messages in the kernel log
because an incorrect (Pi 4) overlay is used as the default.

Fixes #3321

* buildroot cc0481f40e...0a64bfe8f1 (1):
  > Install overlay_map.dtb when using in-tree DT overlays
sairon added a commit that referenced this issue Apr 29, 2024
RPi 5 config uses BR2_LINUX_KERNEL_INSTALL_INTREE_OVERLAYS which builds
the device tree overlays from the Linux tree when building the kernel.
The overlays directory also contains overlay_map.dtb which is necessary
to correctly map overlays without RPi version suffix to the
platform-specific ones. Without this, some peripherals may not work
correctly on Pi 5 without any obvious error messages in the kernel log
because an incorrect (Pi 4) overlay is used as the default.

Fixes #3321

* buildroot cc0481f40e...0a64bfe8f1 (1):
  > Install overlay_map.dtb when using in-tree DT overlays
@sairon
Copy link
Member

sairon commented Apr 29, 2024

Thanks for reporting this, it should be fixed (along with some other possible yet so far unreported issues) by the fix mentioned above. It should be included in today's dev build, and later in release 12.3.rc2/12.3.

@ShonP40
Copy link
Author

ShonP40 commented Apr 29, 2024

Thank you

I won’t be installing a beta/rc build though as it’s my primary server & I'm not home atm

Gonna wait for the stable release

sairon added a commit that referenced this issue Apr 30, 2024
RPi 5 config uses BR2_LINUX_KERNEL_INSTALL_INTREE_OVERLAYS which builds
the device tree overlays from the Linux tree when building the kernel.
The overlays directory also contains overlay_map.dtb which is necessary
to correctly map overlays without RPi version suffix to the
platform-specific ones. Without this, some peripherals may not work
correctly on Pi 5 without any obvious error messages in the kernel log
because an incorrect (Pi 4) overlay is used as the default.

Fixes #3321

* buildroot cc0481f40e...0a64bfe8f1 (1):
  > Install overlay_map.dtb when using in-tree DT overlays

(cherry picked from commit fce19b7)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
board/raspberrypi Raspberry Pi Boards bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants