This is for general networking issues. If you're specifically after assistance with Wi-Fi connections (such as missing drivers), check out its dedicated page instead.
If you can't get access to SSH because the network is not available, on x86/x86_64 you can still access the local xterm command line with a mouse and keyboard.
[F1] to open the file manager.xterm.
In case you can't access the file manager for whatever reason, you can skip straight to another TTY session with a command line by pressing [Ctrl]+[Alt]+[F5]. You will need to enter your user (root) and password (by default, linux). You can return to Batocera by pressing [Ctrl]+[Alt]+[F2].
How to change the layout for your keyboard? You can select your favorite keyboard layout by putting system.kblayout=<keymap_you_want> in /userdata/system/batocera.conf.
All available keymaps are available under /usr/share/keymaps/, and you need to write only the keymap name, not its path nor its extension. Example: system.kblayout=fr-latin1.
In Batocera v31 and below, the shortcut is [Ctrl]+[Alt]+[F3], however this terminal is very buggy (prone to garbling inputs/characters and illegible output) and should only be used in emergency situations.
If it's just not appearing, first of all ensure that your computer and the Batocera machine are connected to the same network (sometimes routers will separate the Wi-Fi and Ethernet networks, but most will combine them internally). Then, you can type \\BATOCERA (under Windows or MacOS) or smb://BATOCERA.local (under Linux) to directly navigate to the Batocera network share. If your router doesn't support hostnames properly (many old routers do not), type in the IP address of the Batocera machine instead of its hostname (for example, \\192.168.1.2). You can find the IP address under MAIN MENU → NETWORK SETTINGS → IP ADDRESS.
If you are on Windows, it could be the following:
\\BATOCERA again.[F5] to refresh the list. If there are no items, you can click anywhere in the window and this will still work.\\BATOCERA network share again.\\BATOCERA again.If you are on Windows 10 version 1709 or above specifically on Enterprise, Education or Server 2019 (Datacenter and Standard) editions, access to guest shares is disabled by default. Blame Microsoft (they did it for security reasons though, but that isn't applicable for local home networks). You can refer to this DevAnswers guide for a walkthrough, but here are those instructions summarized:
c:\net use \\BATOCERA. If you get “System error 1272 has occurred” then continue with these steps. If something else, it may not be this issue, but you can continue anyway just to be sure.[Win]+[R] and type regedit then press [Enter].[Ctrl]+[F] and search for AllowInsecureGuestAuth.1. The first time this is done, it will configure this setting only for the current user.[Ctrl]+[F], uncheck Keys and Data and search for RequireSecuritySignature.1.This is for if you having trouble connecting to the network via an ethernet cable, which otherwise works fine with Windows. Note if the link LED (the orange one that stays steadily lit, not the yellow one which flashes) turns on when your computer shows you the POST screen (where you press a button to enter BIOS settings) or if until Windows has started booting. If it doesn't turn on until Windows is booting, you may need to disable the 'Shutdown Wake-On-LAN' feature of your Realtek ethernet adapter.
If that did not do anything, you may need to also activate such a feature within your BIOS settings. This may be referred to as “Onboard LAN Boot ROM”, “Allow waking via LAN ROM” or something similar.
This is how to manually configure and initiate a network connection if the auto-configuration has failed. Note that the Ethernet cable must be connected and the status lights on the connector must be lighting up, otherwise it is simply a hardware issue (try a different cable, port, etc.).
[F1] on the system list → Appplications → xterm)connmanctl services
( what does this return?)
<> symbols: connmanctl config ethernet_<MAC_address>_cable --ipv4 manual <IP_address> <netmask> <gateway> --nameservers <DNS_1> <DNS_2>
( provide real-world example)
Changes will take effect immediately.
In certain cases it may be required to disable the Linux kernel driver in favor of the vendor driver if provided ( where from?).
( how can Ethernet adapters be identified?)
( if we know which models specifically don't work can't we fix this at the source?)
Actual instructions.
/etc/init.d/816x.conf blacklisting r8169 instead of r8168.batocera-save-overlay./etc/init.d/blacklist-r8169.conf and remove the comment from the line blacklist r8169.batocera-save-overlay.
RealTek 8169 Ethernet Ethernet controller does not run at 2.5GHz on a supported LAN. ( this should link to the Github report for updates)