Thanks to visit codestin.com
Credit goes to github.com

Skip to content

"display_auto_detect" is not enabled by default on Pi 5 #4033

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

Open
spockfish opened this issue Feb 19, 2025 · 7 comments · May be fixed by #4086
Open

"display_auto_detect" is not enabled by default on Pi 5 #4033

spockfish opened this issue Feb 19, 2025 · 7 comments · May be fixed by #4086
Labels
backlog We'll be getting to it eventually

Comments

@spockfish
Copy link

spockfish commented Feb 19, 2025

Describe the bug

The documentation states that display_auto_detect is on by default. However, on the Pi 5 it is not.

Steps to reproduce the behaviour

Without any graphics overlay configured, with display_auto_detect on, the touchscreen driver is loaded. So for an official Raspberry Pi touchscreen this is the raspberrypi_ts module. For the the official Display 2 this is the goodix_ts module.

However, on a Pi 5 this is not happening, unless display_auto_detect=1 is explicitly set in config.txt, suggesting that it is 0 by default.

Device (s)

Raspberry Pi 5

System

6.6.78

Logs

No response

Additional context

No response

@popcornmix
Copy link
Contributor

display_auto_detect is enabled by default in the config.txt file supplied with bookworm.

$ grep display_auto_detect /boot/firmware/config.txt 
display_auto_detect=1

It is not set by default in the bootloader/firmware.

@pelwell
Copy link
Contributor

pelwell commented Feb 19, 2025

This behaviour does not come from the kernel and it's by design.

@pelwell pelwell closed this as completed Feb 19, 2025
@spockfish
Copy link
Author

Ok.... but then I think the documentation is not entirely clear: you state that it is by default available in the config.txt provided by bookworm, but the documention does not mention a specific distribution anywhere. The only thing that is stated is this:

Auto detect

Auto detect allows your Raspberry Pi to connect with a display without a manually configured device tree overlay. Auto detection is enabled by default. You can enable display auto detect by adding the following line to config.txt:

@popcornmix popcornmix transferred this issue from raspberrypi/linux Feb 19, 2025
@popcornmix popcornmix reopened this Feb 19, 2025
@popcornmix
Copy link
Contributor

I've transferred this to the documentation repo issues.

For clarity the behaviour is:
bootloader/firmware defaults display_auto_detect to 0.
Default bookworm config.txt include display_auto_detect=1 to make feature enabled by default on bookworm.

camera_auto_detect behaves the same.

@lurch
Copy link
Contributor

lurch commented Feb 19, 2025

the documention does not mention a specific distribution anywhere.

The entirety of https://www.raspberrypi.com/documentation/ is written to target the latest version of Raspberry Pi OS. If you're using a 3rd-party OS, then you'll have to check the documentation for that other OS.

@nathan-contino Similar questions / issues have cropped up before, so perhaps this should be explicitly stated in https://github.com/raspberrypi/documentation/blob/develop/README.md ?

@popcornmix
Copy link
Contributor

I agree the current wording is imprecise:

Enabled by default.

When enabled, the firmware will automatically load overlays for recognised DSI displays.

To disable, set display_auto_detect=0.

As a config.txt option (where this is being documented) it is not enabled by default.
To disable it you just remove the line (display_auto_detect=0 is a no-op).

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@lurch lurch added backlog We'll be getting to it eventually and removed stale issue labels Apr 27, 2025
lurch added a commit that referenced this issue Apr 27, 2025
pelwell added a commit to pelwell/documentation that referenced this issue Apr 29, 2025
pelwell added a commit to pelwell/documentation that referenced this issue Apr 29, 2025
@pelwell pelwell linked a pull request Apr 29, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog We'll be getting to it eventually
Projects
None yet
4 participants