Troubleshooting
This page is a knowledge base on how to solve common problems in ChimeraOS. If you wish to add to it, please contact us.
We’ve seen this issue reported a few times and in one occasion it was related to Intel RST (Rapid Storage Technology). The fix was to disable this feature in the bios.
Unfortunately these issues are hard to isolate and give an easy answer too. It could be as simple as the Github servers are having problems and the download you received was corrupted so the install failed. Multiple users have reported that the installation worked after waiting a while and trying again or by trying a different network connection.
To get access to a bash shell, there are two options :
Using the Chimera web app, you can configure SSH access from another computer :
-
On your computer, generate a public SSH key and copy the whole file content to the clipboard
-
In the web interface, click the top-right cog wheel icon, then System
-
Under the SSH section, paste your clipboard’s content in the Add public key field, then hit Save.
You can now access your ChimeraOS box from this computer using SSH with the following default credentials :
-
Command :
$ ssh gamer@chimeraos.local
|
Warning
|
If you can’t access your ChimeraOS box through chimeraos.local, see [mdns]
|
If you can’t use another computer to SSH into your ChimeraOS box, the other option
is to plug a keyboard, and hit CTRL+ALT+F2 to switch from the GUI to a TTY
terminal. When you’re finished, to switch back to the GUI, hit CTRL+ALT+F7.
The default username/password is gamer/gamer.
First, try waiting at least a few minutes. This can be the result of Steam waiting for an internet connection and may resolve itself after a short time, or it may be downloading an update over a slow connection.
Second, check the Gamescope and Steam logs to see if you can identify an error or behavior that is causing the problem. A list of log files can be found here. Use the tail -f <logname> command to follow the log in real time, or less <logname> to look through the entire log.
If you’re unable to resolve the issue try resetting Steam. This will erase all games installed to the main drive through Steam so this should be a last resort. Access a shell ([shell]) and run the following command:
steam-runtime --resetIf that still doesn’t work, try this command:
rm ~/.steam/steam/config/config.vdf|
Warning
|
This will clear your login credentials and general configs, so you will need to adjust your preferences again after doing this. |
When launching an emulator game, for example Super Mario 64, you get a message similar to the following :
Your controller is not supported out-of-the-box by Retroarch, despite their very large list of supported controllers.
Try another controller instead. You can try to find one that suits you in their compatibility list. Otherwise the following controllers are well supported in most situations on PC :
-
Playstation 3 (or later) gamepad
-
Xbox 360 (or later) gamepad
-
Steam controller
The solution is to generate the config file for your controller on a computer running Retroarch :
-
Generate the autoconfig file on your computer by following these steps
-
Using SSH, login to your ChimeraOS box
-
Delete the symlink with:
rm /home/gamer/.config/retroarch/autoconfigto -
Create the necessary directories with:
mkdir -p /home/gamer/.config/retroarch/autoconfig/udev -
Upload the autoconfig file to your ChimeraOS box and place it under
/home/gamer/.config/retroarch/autoconfig/udev/ -
Launch the game and test again
-
Restore the original content:
-
rm -rf /home/gamer/.config/retroarch/autoconfig -
ln -s /usr/share/libretro/autoconfig /home/gamer/.config/retroarch/autoconfig
-
If it works properly, submit a pull request to contribute your file so that other ChimeraOS or Retroarch users who have the same controller can benefit from it.
When trying to open the Chimera web interface in a Web browser using the http://chimeraos.local URL, it fails to load.
-
The device you are using is not on the same network as your ChimeraOS box
-
The OS you are using does not support mDNS resolution. This is especially the case for Android.
If you are trying to access from Android, there is no solution. However, there is a workaround.
Windows 10 supports mDNS resolution out-of-the-box : check your updates if it still does not work. If you are using an earlier version, you may need to install Bonjour Print Services or another mDNS implementation. Otherwise, use the workaround.
Some Linux distribution disable mDNS by default, please refer to your distribution’s documentation for instructions. For example on Arch Linux, you may need to activate it in systemd-resolved.
Instead of using the http://chimeraos.local URL, you can replace chimeraos.local by the LAN IP address of your ChimeraOS box. To find it out, go into the settings menu in Steam. Example : http://192.168.0.16
At the command line, run the following command:
systemctl --user enable --now aya-air-audio.service
Now in the Steam Audio settings, select the "AYANEO" output device.
HDMI is a closed spec controlled by the HDMI Forum. They do not allow 4k @ 120 Hz to be implemented in open source code. https://www.techpowerup.com/319797/hdmi-forum-rejects-amds-hdmi-2-1-open-source-driver-proposal-no-4k-120-hz-or-5k-240-hz-on-linux
This is not an issue specific to ChimeraOS, but affects all Linux operating systems. A workaround is to use DisplayPort or a DisplayPort to HDMI adapter.
This is a known limitation. The Steam Deck and the Steam controller require the use of Steam Input, Steam’s virtual controller.
If Steam’s virtual controller is configured in RetroArch, then non-Steam Deck/Steam controller devices will experience duplicated input.
If we remove the configuration for other controllers, then RetroArch still picks up these other physical non-configured controllers and prioritizes them over the Steam Virtual controller resulting in controller input not working.
In order to support the widest possible set of controllers, the Steam Deck and Steam controller are not configured and thus not supported.
If the Steam Deck or Steam controller are the only controllers you will use, you can work around this issue by following the directions below.
-
Remove the existing link to the controller configuration directory with:
rm -f ~/.config/retroarch/autoconfig -
Create a new controller configuration directory with:
mkdir -p ~/.config/retroarch/autoconfig -
Download the Steam Virtual controller RetroArch config file.
-
Place the downloaded config file under
~/.config/retroarch/autoconfig