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/03/07 21:37] – lbrpdx | troubleshooting [2021/05/08 15:38] – typo yeppo | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== System Troubleshooting ===== | + | ====== System Troubleshooting ====== |
+ | |||
+ | =====Audio issues===== | ||
+ | ==== No sound in EmulationStation and/or emulators ==== | ||
+ | |||
+ | Your audio output might not be initialized correctly. The best way to diagnose audio issues is: | ||
+ | - Launch [[kodi|Kodi]] from the main menu, then navigate to Settings (the small gear symbol), " | ||
+ | - Remember the name/number of this working Audio output device (for example HDMI#0), exit Kodi and go to the Batocera Main Menu, " | ||
+ | - 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' | ||
+ | |||
+ | ==== No sound during the splash video ==== | ||
+ | |||
+ | First of all, check that the splash.screen.sound value in the '' | ||
+ | |||
+ | If this isn't the cause of the problem, you may need to edit the file containing the splash screen command to add the correct sound device: | ||
+ | |||
+ | - Run the command '' | ||
+ | - Locate the sound device you need to use, for exemple '' | ||
+ | - Edit the file ''/ | ||
+ | * find the line '' | ||
+ | - Run the command '' | ||
+ | - Reboot | ||
+ | - When updating batocera, those changes will be lost. | ||
+ | |||
+ | =====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===== |
- | * You may need to change your BIOS to allow legacy | + | First of all: |
+ | * You may need to change your BIOS to allow legacy | ||
+ | * Make sure you have enabled "unsecured boot" option in your BIOS, this is a requirement for most Linux distributions | ||
* Unplug any attached storage or controllers | * Unplug any attached storage or controllers | ||
+ | * If your BIOS is UEFI and you can't use legacy boot, make sure you can load '' | ||
- | In order to get more information on your boot sequence, you can edit the ’’/ | + | In order to get more information on your boot sequence, you can edit the '' |
APPEND label=BATOCERA console=tty3 quiet loglevel=0 vt.global_cursor_default=0 | APPEND label=BATOCERA console=tty3 quiet loglevel=0 vt.global_cursor_default=0 | ||
Line 13: | Line 85: | ||
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't forget you need to put the ''/ |
+ | =====Video issues===== | ||
+ | |||
+ | Several video issues on PC x86 and x86_64 can be investigated [[display_issues|with xrandr as described on this page]]. | ||
+ | |||
+ | If you use Batocera with a display that provides a high resolution like a 4K monitor, you might have trouble reading the text on the file browser ('' | ||
+ | |||
+ | ## DPI | ||
+ | ## Workaround when correct DPI setting is not detected | ||
+ | ## if fonts are too small, uncomment next line | ||
+ | # | ||
+ | |||
+ | =====Network issues and console access===== | ||
How to get access to a Linux console for 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: | * 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 '' | + | * on an x86_64 or x86 PC you can get a console with full graphical capabilities by pressing the '' |
- | * for other architectures, | + | |
- | ====Video issues==== | + | =====Create a Batocera support file===== |
- | Several video issues on PC x86 and x86_64 | + | In case you want to share a snapshot of your system log files to help developers diagnose your systemm you can use the menu **SYSTEM SETTINGS** -> **DEVELOPER** -> **CREATE A SUPPORT FILE** It will generate a tarball in ''/ |
- | ====Audio issues==== | + | =====Emulator Troubleshooting===== |
- | 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: | + | Emulators will not show up in the EmulationStation system meny unless |
- | - Lauch [[kodi|Kodi]] from the main menu, and check that you have sound on when playing | + | |
- | - Identify what audio output is used by Kodi. Go back to the audio settings | + | |
- | - You can also diagnose some sound issues with the '' | + | |
- | ====Emulators | + | **3DS** |
+ | * Does not support Encrypted Games - they must be Decrypted | ||
- | 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 | + | **PS2** |
+ | * Bios may be needed if having graphical issues and boot issues | ||
+ | * Most games let you invert your controls if you feel the left stick is swapped | ||
+ | * Compatibility between games and PCSX2 emulator can be checked [[https:// | ||
+ | * To access all configuration options for PCSX2, you need to run its app in **APPLICATIONS** menu of the File Explorer that you can access by pressing | ||
- | ====Joystick Troubleshooting==== | + | **Gamecube and Wii** (Dolphin emulator). |
+ | * To access all configuration options for Dolphin, you need to run its app in **APPLICATIONS** menu of the File Explorer that you can access by pressing '' | ||
+ | * There is a [[emulators: | ||
- | Please refer to [[diagnose_joysticks_issues|this page for joystick issues]] | + | =====Factory Reset===== |
- | ====Create a Batocera | + | When things go really wrong, and you want to " |
- | In case you want to share a snapshot of your system | + | * If you access |
+ | | ||
- | ====Emulator Troubleshooting==== | + | Those two commands are the same, and upon reboot, all your settings will be cleared out to their default values. You'll have to re-enter some parameters like your wifi credentials and so on... or, you can look at what you have in the previous configuration files like ''/ |
- | 3DS | ||
- | * Will not show up in Emulation-Station unless you have a rom in the folder | ||
- | * Does not support Encrypted Games - Must be Decrypted | ||
- | |||
- | PS2 | ||
- | * Bios may be needed if having graphical issues and boot issues | ||
- | * Most games let you invert your controls if you feel the left stick is swapped |
- troubleshooting.txt
- Last modified: 4 months ago
- by maximumentropy