Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
troubleshooting [2020/09/16 19:25] – [Audio issues] lbrpdx | troubleshooting [2020/10/28 00:33] – [Boot Issues:] 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 '' | ||
+ | |||
+ | If you have sound on EmulationStation, | ||
+ | - 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 / | ||
+ | |||
+ | This command will create an alsa config file as ''/ | ||
+ | |||
+ | On a PC, depending on your hardware configuration, | ||
+ | |||
+ | First, through SSH, get the list of audio outputs with the command '' | ||
+ | # 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 '' | ||
+ | |||
+ | Worst case, if it doesn' | ||
+ | |||
+ | ====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 ''/ | ||
+ | |||
+ | 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 13: | Line 67: | ||
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==== | + | Don' |
- | + | ||
- | How to get access to a Linux console for troubleshooting? | + | |
- | * If you can' | + | |
- | * on an x86_64 or x86 PC you can get a console with full graphical capabilities by pressing the '' | + | |
- | * for other architectures, you can get to a text console by pressing simultaneously '' | + | |
- | + | ||
====Video issues==== | ====Video issues==== | ||
Line 32: | Line 79: | ||
# | # | ||
- | ====Audio issues==== | + | ====Network |
- | 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 |
- | - Identify what audio output is used by Kodi. Go back to the audio settings in EmulationStation | + | * on an x86_64 or x86 PC you can get a console with full graphical capabilities by pressing the '' |
- | - You can also diagnose some sound issues with the '' | + | |
- | If you have sound on EmulationStation, | ||
- | - 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 / | ||
- | |||
- | This command will create an alsa config file as ''/ | ||
- | |||
- | On a PC, depending on your hardware configuration, | ||
- | |||
- | If it doesn' | ||
- | ====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 ''/ | ||
- | |||
- | ====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