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
Next revisionBoth sides next revision
troubleshooting [2020/09/15 21:54] – [Audio issues] lbrpdxtroubleshooting [2020/10/09 19:34] lbrpdx
Line 1: Line 1:
 ===== System Troubleshooting ===== ===== System Troubleshooting =====
 +
 +====Audio issues====
 +
 +No sound on EmulationStation and/or when launching emulators? Then your audio output might not be initialized correctly. The best way to diagnose audio issues is:
 +  - Lauch [[kodi|Kodi]] from the main menu, and check that you have sound on when playing a media file (audio or video). You might need to tweak the audio sources from Kodi settings to make it work.
 +  - Identify what audio output is used by Kodi. Go back to the audio settings in EmulationStation and find the audio output that looks as close as possible to the one used in Kodi. The names are not exactly the same, but you can identify what is the HDMI output number of sound card ID this way.
 +  - You can also diagnose some sound issues with the ''alsamixer'' sound mixer that is available when pressing ''[Ctrl][Alt][F4]'' (text-mode sound mixer). Make sure that all the outputs are enabled, and they have their volume up.
 +
 +If you have sound on EmulationStation, and in the emulators, but you can't hear the sound of the video snapshots, here are several steps that may help you:
 +  - First, make sure you have enabled video snaps sounds in the menu **SOUNDS SETTINGS** -> **ENABLE VIDEO AUDIO**
 +  - Then, you can try to [[access_the_batocera_via_ssh|connect to Batocera through SSH]] and enter the following command:
 +
 +  wget -O /userdata/system/.asoundrc https://www.batocera.org/users/lbrpdx/asoundrc
 +
 +This command will create an alsa config file as ''/userdata/system/.asoundrc''. It should fix your video snap sounds for most SBC like Odroid Go Advance, but maybe not on a PC. 
 +
 +On a PC, depending on your hardware configuration, your GPU and audio chipset, it might be trickier to get it working.
 +
 +First, through SSH, get the list of audio outputs with the command ''aplay -l''. In my setup, I get:
 +  # aplay -l
 +  **** List of PLAYBACK Hardware Devices ****
 +  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
 +    Subdevices: 1/1
 +    Subdevice #0: subdevice #0
 +  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
 +    Subdevices: 0/1
 +    Subdevice #0: subdevice #0
 +  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
 +    Subdevices: 1/1
 +    Subdevice #0: subdevice #0
 +  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
 +    Subdevices: 1/1
 +    Subdevice #0: subdevice #0
 +  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
 +    Subdevices: 1/1
 +    Subdevice #0: subdevice #0
 +  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
 +    Subdevices: 1/1
 +    Subdevice #0: subdevice #0
 +
 +If I want to use the audio output from HDMI0, I can see that it is ''card 0'' and ''device 3''. So, to make audio work on my setup, I need to edit the ''/userdata/system/.asoundrc'' file and replace ''pcm "hw:0,0"''  with  ''pcm "hw:0,3"'', and then save and on reboot, it worked. This method might not work in 100% cases, but it's worth a try.
 +
 +Worst case, if it doesn't work and you want to go back to the original state, just remove the file ''/userdata/system/.asoundrc'' (or ''\system\.asoundrc'' from the network share).
 +
 +====Emulators not launching====
 +
 +When you try to launch a game, the emulator stops and gets you back to EmulationStation. In most cases, you will find some useful information in ''/userdata/system/logs/es_launch_stderr.log'' (which is also ''/system/logs/es_launch_stderr.log'' from the network shared drive).
 +
 +Come to the Discord channel with this file, you'll get some help. In many case, you can see problems with BIOS missing, or bad ROM format.
 +
 +====Joystick Troubleshooting====
 +
 +Please refer to [[diagnose_joysticks_issues|this page for joystick issues]]
 +
      
 ====Boot Issues:==== ====Boot Issues:====
Line 12: Line 66:
  
   APPEND label=BATOCERA console=tty3 loglevel=9 vt.global_cursor_default=0   APPEND label=BATOCERA console=tty3 loglevel=9 vt.global_cursor_default=0
- 
-====Troubleshooting==== 
- 
-How to get access to a Linux console for troubleshooting? 
-   * If you can't use SSH because the network is not available, you can plug a USB keyboard on your Batocera box and: 
-   * on an x86_64 or x86 PC you can get a console with full graphical capabilities by pressing the ''[F1]'' key from the main system menu (to get into the file manager) and then ''[F4]'' for an ''xterm''. 
-   * for other architectures, you can get to a text console by pressing simultaneously ''[Ctrl][Alt][F3]''. 
- 
  
 ====Video issues==== ====Video issues====
Line 32: Line 78:
   #global.dpi=96   #global.dpi=96
  
-====Audio issues====+====Network issues and console access====
  
-No sound on EmulationStation and/or when launching emulators? Then your audio output might not be initialized correctly. The best way to diagnose audio issues is+How to get access to a Linux console for troubleshooting? 
-  - Lauch [[kodi|Kodi]] from the main menu, and check that you have sound on when playing a media file (audio or video). You might need to tweak the audio sources from Kodi settings to make it work. +   * If you can't use SSH because the network is not available, you can plug a USB keyboard on your Batocera box and
-  - Identify what audio output is used by Kodi. Go back to the audio settings in EmulationStation and find the audio output that looks as close as possible to the one used in Kodi. The names are not exactly the same, but you can identify what is the HDMI output number of sound card ID this way. +   * on an x86_64 or x86 PC you can get a console with full graphical capabilities by pressing the ''[F1]'' key from the main system menu (to get into the file manager) and then ''[F4]'' for an ''xterm''. You can get to a text console by pressing simultaneously ''[Ctrl][Alt][F3]''.
-  - You can also diagnose some sound issues with the ''alsamixer'' sound mixer that is available when pressing ''[Ctrl][Alt][F4]'' (text-mode sound mixer). Make sure that all the outputs are enabled, and they have their volume up.+
  
-If you have sound on EmulationStation, and in the emulators, but you can't hear the sound of the video snapshots, here are several steps that may help you: 
-  - First, make sure you have enabled video snaps sounds in the menu **SOUNDS SETTINGS** -> **ENABLE VIDEO AUDIO** 
-  - Then, you can try to [[access_the_batocera_via_ssh|connect to Batocera through SSH]] and enter the following command: 
- 
-  wget -O /userdata/system/.asoundrc https://www.batocera.org/users/lbrpdx/asoundrc 
- 
-This command will create an alsa config file as ''/userdata/system/.asoundrc''. It should fix your video snap sounds for most SBC like Odroid Go Advance, but maybe not on a PC.  
- 
-On a PC, depending on your hardware configuration, your GPU and audio chipset, it might be trickier to get it working. You can try to replace ''pcm "hw:0,0"''  with  ''pcm "hw:1,0"'', and reboot it might work. The mapping for HDMI1 is not always ''1,0'' unfortunately. We will make it much easier in a later version. 
-====Emulators not lauching==== 
- 
-When you try to launch a game, the emulator stops and gets you back to EmulationStation. In most cases, you will find some useful information in ''/userdata/system/logs/es_launch_stderr.log''. 
- 
-====Joystick Troubleshooting==== 
- 
-Please refer to [[diagnose_joysticks_issues|this page for joystick issues]] 
  
 ====Create a Batocera support file==== ====Create a Batocera support file====
  • troubleshooting.txt
  • Last modified: 4 months ago
  • by maximumentropy