Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
display_issues [2023/12/30 05:28] – [I see the Batocera splash screen, but then it turns black/no input] fix typo maximumentropydisplay_issues [2025/07/26 14:05] (current) – [My screen shows tearing in both EmulationStation and games] hankerde
Line 20: Line 20:
  
 If the correct drivers are being used and it's still not working, it's possible that the prime switcher also needs to be toggled (common on modern laptops connected to external displays). In case Batocera hasn't been able to automatically detect this for you, [[:supported_pc_hardware#hybrid_optimus_nvidia_laptops|you can manually activate the prime switching]] by editing the ''batocera-boot.conf'' file. If the correct drivers are being used and it's still not working, it's possible that the prime switcher also needs to be toggled (common on modern laptops connected to external displays). In case Batocera hasn't been able to automatically detect this for you, [[:supported_pc_hardware#hybrid_optimus_nvidia_laptops|you can manually activate the prime switching]] by editing the ''batocera-boot.conf'' file.
 +
 +It can also be the case of a dead USB flash disk. The USB flash drive isn't "dead enough" to prevent from booting, but some there are missing parts in the boot sequence and it just hangs at some point, and we've seen this happening after the splash screen. In doubt, try with another USB flash drive.
  
 If using a HP EliteDesk specifically, [[:usff_nuc_mini_pcs#hp_mini_micro_small_form_factor_pcs|it may require certain BIOS settings]] or else the GPU might be disabled by the motherboard. If using a HP EliteDesk specifically, [[:usff_nuc_mini_pcs#hp_mini_micro_small_form_factor_pcs|it may require certain BIOS settings]] or else the GPU might be disabled by the motherboard.
 +
 +As a general rule, when you face a black screen during the boot sequence, it can be helpful to [[troubleshooting#verbose_boot|enable verbose boot mode]] for troubleshooting.
  
 ===== The edges of my screen are cut off! ===== ===== The edges of my screen are cut off! =====
Line 39: Line 43:
 Older 8-bit and 16bit systems, or arcade systems from the 80s and 90s were using 4:3 CRT screens. Modern displays are now 16:9 or wider, and can go up to 4K, i.e. 2160 pixels high (compared to 480 or 546 at the time!). Older 8-bit and 16bit systems, or arcade systems from the 80s and 90s were using 4:3 CRT screens. Modern displays are now 16:9 or wider, and can go up to 4K, i.e. 2160 pixels high (compared to 480 or 546 at the time!).
  
-Having so many pixels to render on the screen is impactful on the system performance. When you have a 4K screen or an ultra-wide screen, Batocera will limit the resolution by default to HD 1920x1080. It's more than enough to render emulators, even the most recent ones. However, when you have an ultra-wide monitor, the display may be stretched. +Having so many pixels to render on the screen is impactful on the system performance. When you have a 4K screen or an ultra-wide screen, Batocera **v31** to FIXME will limit the resolution by default to HD 1920x1080. In Batocera FIXME and higher, you must edit the resolution used in **SYSTEM SETTINGS** -> FIXME to the display's compatible 1920x1080 mode. It's more than enough to render emulators, even the most recent ones. However, when you have an ultra-wide monitor, the display may be stretched. 
  
 For 4K monitors, because the resolution is by default resized to 1920x1080, you might see a screen that looks like this one (actually it's what 1:1 pixel scaled 1920x1080 is, centered in a 3840x2160 screen): For 4K monitors, because the resolution is by default resized to 1920x1080, you might see a screen that looks like this one (actually it's what 1:1 pixel scaled 1920x1080 is, centered in a 3840x2160 screen):
Line 74: Line 78:
 </WRAP> </WRAP>
  
-There are some SBC + TV combinations where EmulationStation feels sluggish (default theme seems to be lagging behind, with a refresh rate like 10 FPS). It's really depending on your own configuration, but we have reproduced this with a Raspberry Pi 4 and a couple 4K TV models. By default, ES should negotiate with your TV to fix its resolution to 1080p, but sometimes your TV brand doesn't accept it and stays at 4K/2160p resolution. You can force a particular resolution by [[:edit_boot_partition|editing]] it into ''/boot/batocera-boot.conf''.+There are some SBC + TV combinations where EmulationStation feels sluggish (default theme seems to be lagging behind, with a refresh rate like 10 FPS). It's really depending on your own configuration, but we have reproduced this with a Raspberry Pi 4 and a couple 4K TV models. By default, ES should negotiate with your TV to fix its resolution to your specified resolution in FIXME, but sometimes your TV brand doesn't accept it and stays at 4K/2160p resolution. You can force a particular resolution by [[:edit_boot_partition|editing]] it into ''/boot/batocera-boot.conf''.
  
 ==== Force 1080p as the maximum resolution despite what the EDID may report ==== ==== Force 1080p as the maximum resolution despite what the EDID may report ====
Line 128: Line 132:
 Then any HDMI mode can be used (even ones that your display won't work with, be careful!). Refer to [[https://www.raspberrypi.com/documentation/computers/config_txt.html#video-options|Raspberry Pi's official documentation]] for more information. Then any HDMI mode can be used (even ones that your display won't work with, be careful!). Refer to [[https://www.raspberrypi.com/documentation/computers/config_txt.html#video-options|Raspberry Pi's official documentation]] for more information.
  
 +===== I cannot get the 7" official Raspberry Pi screen working =====
 +
 +As reported by a user using the official 7-inch touchscreen on a Raspberry Pi 3B+, if you screen fails with the following message in your ''dmesg'':
 +
 +<code>
 + rpi_touchscreen_attiny 10-0045: Unknown Atmel firmware revision: 0xe1
 +</code>
 +
 +You might be able to fix it by adding ''dtparam=i2c_vc_baudrate=50000'' to your ''config.txt'' file.
 +
 +More information on the [[https://www.reddit.com/r/raspberry_pi/comments/18rdnj0/raspberry_pi_os_lite_official_7_touchscreen/|Reddit post]].
 +
 +===== My screen shows tearing in both EmulationStation and games =====
 +
 +<WRAP center round important>
 +This issue occurs at least with the ITX motherboard //ITX-N100-2L V1.31//. A special feature of this board is that, in addition to a VGA output (reported as "DP-1") and an HDMI output ("HDMI-1"), it also includes an internal display connector (LVDS, reported as "eDP-1"). There is also a variant with a DisplayPort instead of VGA, which explains why Batocera refers to the VGA output as "DP-1".
 +
 +It is likely that similar motherboards are also affected. Some mini PCs on the Asian market use the //ITX-N100-2L// or similar boards with such an internal LVDS connector.</WRAP>
 +
 +A typical symptom of this issue is screen tearing in games as well as in EmulationStation, even when VSYNC is enabled (which is the default setting). This is particularly noticeable in the intro/attract mode of //Marvel vs. Capcom 2//, but it should also be clearly visible in other fast side-scrolling games.
 +
 +To fix the problem, go to EmulationStation’s **SYSTEM SETTINGS**, then under **MULTISCREENS**, set the video output to **NONE**.
 +
 +If graphical issues still occur afterward, check whether **PERFORMANCE** or similar is enabled under **DECORATIONS** / **HUD** and disable it.
 +
 +<WRAP center round tip>
 +Disabling eDP-1 at least on the ITX-N100-2L causes graphical glitches during game start animations (e.g., **GAME LAUNCH TRANSITIONS** like **FADE**). The only known workaround as of version v41 is to go to **USER INTERFACE SETTINGS** → **GAME LAUNCH TRANSITION** and set it to **INSTANT**.</WRAP>
 ===== Display issues, when xrandr is your friend ===== ===== Display issues, when xrandr is your friend =====
  
  • display_issues.1703914129.txt.gz
  • Last modified: 2 years ago
  • by maximumentropy