Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
troubleshooting [2020/09/16 19:27] – [Audio issues] lbrpdx | troubleshooting [2023/11/18 00:23] (current) – [x86/x86_64] Legacy boot "Boot error" recovery maximumentropy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== System Troubleshooting ===== | + | ====== System Troubleshooting ====== |
+ | |||
+ | ===== Emulators not launching/ | ||
+ | |||
+ | When an emulator fails to launch, you will be immediately returned to the game list in EmulationStation. Most of the time when this happens, you will find some useful information in ''/ | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | If you're having issues with only a particular system, first refer to its respective [[: | ||
+ | </ | ||
+ | |||
+ | If there' | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | In many cases, one of these logs will contain a self-evident error message such as missing BIOS files, a bad ROM format, etc. If not, come to the Discord channel with this file, and you'll usually get some pointers as to what's wrong. | ||
+ | </ | ||
+ | |||
+ | If there isn't an obvious error message and you'd like to try some things in the meantime: | ||
+ | * Remove any unnecessary devices plugged into your machine and try again. This includes any additional controllers, | ||
+ | * Remove any [[: | ||
+ | * If you are using any [[emulationstation: | ||
+ | * If using an exotic storage option (such as a NAS), try resorting back to using the userdata partition on the Batocera drive itself. | ||
+ | * Your storage medium (read: a cheap USB stick) might be too slow to be usable. This is rare, but certain USB sticks can't transfer at a rate faster than 1 MB/s, which could lead to problems. This is irrelevant of what " | ||
+ | * For weaker SBCs, you can also try turning on interface preloading in **SYSTEM SETTINGS** -> **DEVELOPER** -> **INTERFACE PRELOADING**. You can also try " | ||
+ | * Perform a [[# | ||
+ | * If using the official Nvidia drivers, try disabling them and use the default Nouveau drivers. | ||
+ | |||
+ | ===== Games/ | ||
+ | |||
+ | Batocera only shows systems for which games have been added. First, try [[: | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | All available cores are always installed by Batocera; you never need to " | ||
+ | </ | ||
+ | |||
+ | If your games/ | ||
+ | * That the games are in an acceptable file format. The included '' | ||
+ | * If you are using any [[emulationstation: | ||
+ | * Remove any [[: | ||
+ | * If using an exotic storage option (such as a NAS), try resorting back to using the userdata partition on the Batocera drive itself. | ||
+ | |||
+ | ==== NAS workaround for affected systems ==== | ||
+ | |||
+ | The following systems will not work when using a NAS of any filesystem: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | * [[systems: | ||
+ | |||
+ | If you want to continue using your NAS for the majority of your games, but to use your internal storage for these affected systems so they can continue to work (not being on your NAS, obviously), save the following script as ''/ | ||
+ | |||
+ | <file bash custom.sh> | ||
+ | # | ||
+ | # This allows you to still use Windows/ | ||
+ | |||
+ | case " | ||
+ | start) | ||
+ | mkdir -p / | ||
+ | mount --bind / | ||
+ | mkdir -p / | ||
+ | mount --bind / | ||
+ | mkdir -p / | ||
+ | mount --bind / | ||
+ | ;; | ||
+ | esac | ||
+ | |||
+ | exit $? | ||
+ | |||
+ | </ | ||
+ | |||
+ | <WRAP center round info> | ||
+ | Batocera **v36** and below do not require the '' | ||
+ | </ | ||
+ | |||
+ | ===== Poor game performance ===== | ||
+ | |||
+ | First thing to check, is to make sure you have a reference. It could just be that the game on the emulated system takes more resources than expected due to the nature of being emulated. For instance, emulating the PS2 requires a fairly beefy system, despite being an old sixth generation console. You can typically test for reference with how well the emulated game performs on Windows on the same computer, or for other devices other distributions. It's also possible to see performance for that particular game online, do your research. | ||
+ | |||
+ | Once you're sure that your game's poor performance is abnormal, and your system is ordinarily capable of much better, here are a few things you can try: | ||
+ | * Reset all your settings back to " | ||
+ | * Change the graphics API being used by your emulator; each piece of hardware may prefer or run slower with any given API. This can typically be found in the system' | ||
+ | * Ensure that your audio buffer isn't being choked; if your system is unable to process audio frames as quickly as they are being produced, this could put a throttle on the device' | ||
+ | * Remove any [[: | ||
+ | * Lower the resolution of your game. This is especially so if the system isn't normally meant to be upscaled, like fifth generation and below consoles. | ||
+ | * If using Nvidia hardware and on Batocera **v33** or lower, [[: | ||
+ | |||
+ | If you're still having poor performance after checking all of the above, come to the [[https:// | ||
+ | |||
+ | ===== Audio issues ===== | ||
+ | |||
+ | If trying to use HDMI sound on a Radeon GPU, first check [[: | ||
+ | |||
+ | When that's all clear, first experiment with different settings in **MAIN MENU** -> **SYSTEM SETTINGS** -> **AUDIO PROFILE**. You should get sound immediately when exiting back to the **MAIN MENU** (there is background music playing by default). If you're still not able to get any sound, try also manually setting an **AUDIO OUTPUT** device (they change with each different profile, you need to exit back to **MAIN MENU** to update the list). To rigidly test all your hardware' | ||
+ | |||
+ | - Go to **MAIN MENU** -> **SYSTEM SETTINGS** -> **AUDIO PROFILE** and select the first profile, then back out to the **MAIN MENU**. | ||
+ | - Go back into **SYSTEM SETTINGS** -> **AUDIO OUTPUT** and test all available outputs, exiting to the **MAIN MENU** between each change. | ||
+ | - If none of the **AUDIO OUTPUT** options worked, repeat steps 1-2 for a different **AUDIO PROFILE**. Your **AUDIO OUTPUT** options might change depending on the **AUDIO PROFILE** selected. | ||
+ | |||
+ | <WRAP center round info> | ||
+ | Batocera **v32** reworked the way it handles audio, so most issues are now resolved by simply selecting the right device and profile in the settings menu. If you're still having issues or are using an older version of Batocera, audio issues is on [[: | ||
+ | </ | ||
+ | |||
+ | ===== Where' | ||
+ | |||
+ | Batocera puts a lot of the large " | ||
+ | |||
+ | ===== "Not enough free space" even though I just removed some files from the drive! ===== | ||
+ | |||
+ | Perhaps the Trash folder still has your files stored on the drive? You can clear these out by going to the file manager ('' | ||
+ | |||
+ | If you've already done that and still get the error, it could be that **Trash Can** has failed to actually removed the files. If so, you can forcefully remove the files by navigating to ''/ | ||
+ | |||
+ | If you'd like to avoid this issue in the future you can tell the file manager to not use your trash folder and default to instantly deleting files. Click on **Edit** in the menu bar located at the top of the screen in the file manager, then go to **Preferences** and uncheck the "Move deleted files to "trash can" instead of erasing from disk" checkbox. Click **Close** to save the setting. Files that are deleted via the network share aren't sent to the trash can. [[https:// | ||
+ | |||
+ | If you were managing files from an external source such as another computer, ensure that //its// Trash bin is emptied as well while the drive is connected. This can usually be checked for by searching for a hidden " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Usage of the trash utility for removable drives can (usually) be configured from the respective OS. Most //should// have this disabled by default. | ||
+ | |||
+ | ===== "Not enough free space" but I can't find the files that are filling up my disk! ===== | ||
+ | |||
+ | Open xTerminal or access batocera [[: | ||
+ | |||
+ | Run '' | ||
+ | |||
+ | < | ||
+ | [root@BATOCERA / | ||
+ | Filesystem | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | In this example, the external HD shows 0 free space and 100% used. | ||
+ | |||
+ | Run '' | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | Files can be removed directly from '' | ||
+ | |||
+ | Now running '' | ||
+ | |||
+ | < | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | </ | ||
+ | ===== My games are taking very long to load/ | ||
+ | |||
+ | It could be that you're using an extremely slow USB drive (like 1.0, though all of those are likely to have already died due to their age), have a faulty SD card, or if using a USB connected portable drive are using an cheap SATA-to-USB cable which does not support the [[wp> | ||
+ | |||
+ | If the latter, you can check what driver has been loaded to use your USB with the '' | ||
+ | |||
+ | < | ||
+ | [root@BATOCERA / | ||
+ | ... | ||
+ | /: Bus 02.Port 1: Dev 1, Class=root_hub, | ||
+ | |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M | ||
+ | |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | In this example, device 3 ('' | ||
| | ||
- | ====Boot | + | ===== Boot issues ===== |
- | * You may need to change your BIOS to allow legacy and unsecured boot | + | |
- | * Unplug any attached storage or controllers | + | |
- | In order to get more information on your boot sequence, you can edit the '' | + | ==== x86/x86_64 ==== |
- | APPEND label=BATOCERA console=tty3 quiet loglevel=0 vt.global_cursor_default=0 | + | You can first check for the BIOS settings on [[install_batocera# |
+ | * You may need to change your BIOS to allow legacy/ | ||
+ | * If the system has a UEFI BIOS, and Secure Boot can't be disabled, and legacy boot is not available, see the [[secureboot|Secure Boot]] page for setup instructions. | ||
+ | * If the system has a Trusted Platform Module (TPM) that is enabled, Batocera **v39** and higher will display '' | ||
+ | * If using Grub bootloader on UEFI to chainload the Batocera bootloader, ensure that the correct path is being chainloaded: | ||
+ | * For Batocera **v39** and higher: ''/ | ||
+ | * For Batocera **v38** and lower: ''/ | ||
+ | * If also using Windows on the same machine, ensure that Windows isn't hibernating or otherwise holding the system access hostage by some means (fast boot, quick start, etc.) | ||
+ | * Windows 8 and above have renamed the " | ||
+ | * Unplug any other storage devices (such as your internal drive with another OS on it) or controllers. | ||
+ | * The Batocera image may not have been flashed correctly, try reflashing with Etcher and make sure the validation says " | ||
+ | * If flashing the image using Windows onto a USB drive, a bug within Windows prevents it from seeing other partitions on a hardware level. If the drive initially has multiple partitions, it may need to be completely wiped first before Windows is able to completely see it. An alternative would be to flash Batocera using another operating system. | ||
+ | * If using a SATA-to-USB cable for a USB hard drive or SSD (all 2.5" and 3.5" hard drives use them, even if they hide it in the case), your cable may not support TRIM which is required to properly boot; try a different SATA-to-USB cable or a different drive. | ||
+ | * Some USB drives (particularly USB 3.0 and above ones) may not be properly read/ | ||
+ | * Try disabling/ | ||
+ | * Try switching AHCI/ | ||
+ | * If your motherboard' | ||
- | With: | + | === Verbose boot === |
- | APPEND label=BATOCERA console=tty3 loglevel=9 vt.global_cursor_default=0 | + | By default Batocera will suppress most of the boot related messages during the boot sequence. If you'd instead like to see these to help with diagnosing your boot issue, enable the verbose boot mode. |
- | ====Troubleshooting==== | + | To enable the verbose mode in Batocera **v36** and higher, repeatedly press the down arrow key on the keyboard while booting, and then select the verbose boot mode. You may need to hold the Enter button down for half a second to register it, as the boot menu polls for input slowly. |
- | How to get access to a Linux console for troubleshooting? | + | --> For Batocera |
- | * If you can't use SSH because the network is not available, you can plug a USB keyboard on your Batocera | + | |
- | * on an x86_64 or x86 PC you can get a console with full graphical capabilities by pressing the '' | + | |
- | * for other architectures, | + | |
+ | To do so, [[: | ||
+ | * For legacy boot: ''/ | ||
+ | * For EFI/UEFI boot: ''/ | ||
- | ====Video issues==== | + | and replace the following line: |
- | Several video issues on PC x86 and x86_64 can be investigated [[display_issues|with xrandr as described on this page]]. | + | MENU SHIFTKEY |
- | If you use Batocera | + | with: |
- | | + | |
- | ## Workaround when correct DPI setting is not detected | + | |
- | ## if fonts are too small, uncomment next line | + | |
- | # | + | |
- | ====Audio issues==== | + | Then, when next booting Batocera, rapidly press the down arrow key to interrupt the boot and open the syslinux menu. Select the verbose option (or press the hotkey '' |
- | No sound on EmulationStation and/ | + | <WRAP center important> |
- | - Lauch [[kodi|Kodi]] from the main menu, and check that you have sound on when playing | + | Be careful |
- | - Identify what audio output is used by Kodi. Go back to the audio settings | + | </ |
- | - You can also diagnose some sound issues with the '' | + | |
- | If you have sound on EmulationStation, and in the emulators, but you can' | + | If accessing Batocera over SSH or through terminal, don' |
- | - First, make sure you have enabled video snaps sounds | + | |
- | - 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 ''/ | + | === Legacy boot === |
- | On a PC, depending on your hardware configuration, your GPU and audio chipset, it might be trickier | + | On x86_64 legacy boot systems, if the file ''/ |
- | If it doesn't work and you want to go back to the original state, just remove | + | To recover from this: |
- | ====Emulators | + | - Boot from a Linux distribution on another drive (procedure was tested with the live installer'' |
+ | - Get to a root shell ("Try Ubuntu", | ||
+ | - Attach | ||
+ | - Ensure that the Batocera boot partition is **not** mounted: | ||
+ | - Ensure that the " | ||
+ | - Reinstall | ||
- | 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==== | + | ==== Single board computer (RPi, Odroid, etc.) ==== |
+ | |||
+ | This is for if you're struggling to even boot on an SBC, which is a rare occurrence (SBCs tend not to be nearly as modular as standard desktop PCs) and usually only caused by hardware faults/ | ||
+ | |||
+ | * It could be running undervoltage and failing to boot (the most intensive task for the CPU). First try unplugging any external USB devices you may be using, including external hard-drives, | ||
+ | * Disable any [[: | ||
+ | * Remove your game's metadata ('' | ||
+ | * As a final resort, try [[: | ||
+ | |||
+ | ===== Laggy splash video on boot ===== | ||
+ | |||
+ | Since the graphics drivers aren't loaded at boot the splash video is rendered entirely on the CPU. If you have either 1. an absurdly high resolution display like a 4k TV, 2. a really weak CPU to begin with then this could cause the boot video to lag. You can solve this by forcing the splash video to render at a lower resolution (say 1920x1080 or 1280x720) by [[: | ||
+ | |||
+ | < | ||
+ | splash.video.resize=1280x720 | ||
+ | </ | ||
+ | |||
+ | This can be done in either '' | ||
+ | |||
+ | ===== Video/ | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | [[: | ||
+ | </ | ||
+ | |||
+ | ==== Incorrect radeon/ | ||
+ | |||
+ | This is for the less common problem of the small range of AMD Radeon GPUs in the RX 200 and RX 300 series (Southern Islands SI and Sea Islands CIK) choosing the older '' | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | If you're finding the performance of the automatically chosen '' | ||
+ | </ | ||
+ | |||
+ | <WRAP center round important> | ||
+ | By following this procedure, you are going to force Batocera to use a particular driver at a kernel level instead of allowing it to choose the most appropriate driver. By doing this, you may encounter video/audio glitches/ | ||
+ | |||
+ | Please note, RX and R cards older than the R7 240 just **do not support the '' | ||
+ | </ | ||
+ | |||
+ | Edit the '' | ||
+ | |||
+ | < | ||
+ | radeon.cik_support=0 amdgpu.cik_support=1 radeon.si_support=0 amdgpu.si_support=1 | ||
+ | </ | ||
+ | |||
+ | If you are not getting sound output via HDMI after doing this, then you may also have to append this: | ||
+ | |||
+ | < | ||
+ | amdgpu.dc=1 | ||
+ | </ | ||
+ | |||
+ | ===== Network issues ===== | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | [[: | ||
+ | </ | ||
+ | |||
+ | ===== Bluetooth issues (not connecting, no devices detected, etc.) ===== | ||
+ | |||
+ | First, check the [[: | ||
+ | |||
+ | Check the following: | ||
+ | * Ensure that '' | ||
+ | * Make sure that you've put your controller into its " | ||
+ | * If failing to re-pair a controller, that you've cleared the previously remembered controllers from memory. | ||
+ | * That there is no significant wireless interference, | ||
+ | * That you're only using one Bluetooth interface. eg. if you have an on-board BT module and a USB-connected BT dongle, they might disrupt each other. | ||
+ | * Turn off other wireless interfaces such as Wi-Fi. | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | You can disable a Raspberry Pi 3/4's on-board Bluetooth by [[: | ||
+ | </ | ||
+ | |||
+ | ==== Issues with the Bluetooth dongle specifically ==== | ||
+ | |||
+ | You can try [[: | ||
+ | |||
+ | Sometimes, a computer will keep delivering power to a USB slot even if the machine itself is switched off. Some dongles assume this means " | ||
+ | |||
+ | You should also try plugging the BT dongle into a USB 2.0 port instead of a USB 3.0 port, as some BT dongles have issues with 3.0 ports (noted in the compatible dongle list). | ||
+ | |||
+ | <WRAP center round help> | ||
+ | Some users have reported Bluetooth to stop working indefinitely if the userdata partition ever becomes completely full (such as by scraping), even after freeing up some space afterwards. The only reported solution to this is to [[: | ||
+ | </ | ||
+ | |||
+ | ==== Installing Bluetooth firmware binaries ==== | ||
+ | |||
+ | If your Bluetooth device complains about requiring certain binary firmware files (check with '' | ||
+ | |||
+ | An example of a BT device complaining about binary firmware files in '' | ||
+ | |||
+ | < | ||
+ | [ 1.797311] Bluetooth: hci0: RTL: firmware file rtl_bt/ | ||
+ | </ | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | If you've done this and it worked successfully, | ||
+ | </ | ||
+ | |||
+ | ===== My controller is acting weird/not detecting any inputs even after connecting successfully ===== | ||
+ | |||
+ | First, check the [[: | ||
+ | |||
+ | If you have the option, use a wired connection. Wireless connections have far more things that can "go wrong" to make your controller not work, whereas wired has a much higher chance of working correctly. If you'd still like to use a wireless Bluetooth connection, check the [[# | ||
+ | |||
+ | If using a third-party controller, they may have multiple " | ||
+ | |||
+ | If you'd like to get your hands dirty with SSH and '' | ||
+ | |||
+ | ===== Batocera can't read my hard-drive using its file manager! I know it's fine because I boot Windows off of it. ===== | ||
+ | |||
+ | Windows has a tendency to " | ||
+ | |||
+ | To turn off "fast startup (hybrid boot)": | ||
+ | - Open the old **Control Panel** (icons view), accessible from the Start menu search, and click on the **Power Options** icon. | ||
+ | - Click the **Choose what the power buttons do** link on the left side. | ||
+ | - Click the **Change settings that are currently unavailable** link at the top (administrator permissions required). | ||
+ | - Under **Shutdown settings**, uncheck the **Turn on fast startup** box. | ||
+ | - Click the **Save changes** button. | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | In addition to this, there may be a setting in your BIOS configuration that also needs to be disabled. This can be referred to as "Fast boot", " | ||
+ | |||
+ | ==== I can see the drive but still can't access it! ==== | ||
+ | |||
+ | Maybe you have Bitlocker drive encryption enabled? This is a feature of Windows that allows you to encrypt your drive' | ||
+ | |||
+ | First, type " | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | ===== MacOS, strange files starting with ._ ===== | ||
+ | |||
+ | If you are a Mac user, you might wonder why you see lots of files starting with '' | ||
+ | |||
+ | In order to list them all, you SSH into your Batocera system and enter: | ||
+ | |||
+ | find /userdata/ -name " | ||
+ | |||
+ | And to remove them all: | ||
+ | |||
+ | find /userdata/ -name " | ||
- | Please refer to [[diagnose_joysticks_issues|this page for joystick issues]] | + | ===== Create a Batocera support file ===== |
- | ====Create | + | In case you want to share a snapshot of your system log files to [[: |
+ | * Wi-Fi SSID and password is in '' | ||
+ | * RetroAcheivements username and password are in '' | ||
+ | * ScreenScraper username and password are in '' | ||
- | 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 ''/ | + | You could also just use a freshly installed Batocera that contains no such information instead |
- | ====Emulator Troubleshooting==== | + | ===== Factory reset ===== |
- | Emulators will not show up in the EmulationStation system meny unless you have a rom in their respective folders. All available cores are always installed by Batocera, you never need to "add" | + | When things go really wrong, and you want to "factory reset" |
- | **3DS** | + | |
- | * Does not support Encrypted Games - they must be Decrypted | + | / |
+ | mv / | ||
+ | reboot | ||
+ | </ | ||
+ | | ||
+ | | ||
+ | * Open the file manager so EmulationStation is not holding the system files (if this is not possible, then close EmulationStation via SSH: ''/ | ||
- | **PS2** | + | Upon (re)boot, all your settings will be cleared out to their default values. You'll have to re-enter some parameters like your Wi-Fi credentials |
- | * Bios may be needed if having graphical 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://pcsx2.net/compatibility-list.html|on this webpage.]] | + | |
- | * To access | + | |
- | **Gamecube and Wii** (Dolphin emulator). | + | <WRAP center round info> |
- | * To access all configuration options for Dolphin, you need to run its app in **APPLICATIONS** menu of the File Explorer that you can access | + | It is also possible |
- | * There is a [[emulators: | + | </ |
- | ====Factory Reset==== | + | If not even this resolves your issue, as a last resort you can try [[: |
- | When things go really wrong, and you want to " | + | ===== Other issue ===== |
- | * If you access your Batocera user data from the network, simply rename the directory '' | + | Here are a few other topics with notable troubleshooting sections: |
- | * Or, if you are [[access_the_batocera_via_ssh|connected through SSH]], just enter '' | + | |
- | 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 ''/ | + | * **Batocera can't update:** Try [[: |
+ | * **Batocera keeps resetting my clock:** Then [[: | ||
+ | * **I don't have X new feature:** Update | ||
- troubleshooting.1600277232.txt.gz
- Last modified: 4 years ago
- by lbrpdx