![]() If the command executed without any errors, no additional output on screen is expected. As first step you need to mount overlays for retroarch, so type in following command and hit the Enter key: systemctl start retroarch.target If everything was set up correctly, you should end up with a shell prompt Lakka:~ # (or similar). Gathering informationĪfter modifying the boot arguments it is time to boot up your device. grub.cfg is currently used only for compatibility with EFI32 systems, in all other cases (legacy boot / EFI64) syslinux.cfg is used. Note: For Generic PC it is recommended to modify both grub.cfg and syslinux.cfg. Line starting with APPEND in the LABEL live section Line starting with linux in the menuentry "Live" section Note that all arguments must be on the same line - this is very important - no line breaks. In general, this file is located on the first partition of your SD Card / USB thumb drive. Where to add these parameters depends on your device. Modify kernel cmdline argumentsĭepending on your device you must edit kernel cmdline arguments by adding retroarch=0 textmode ssh after the last parameter. router) and you will access your device via SSH. As we will by typing shell commands directly into the shell, it is essential that you either have a keyboard connected to your device, so you can use the shell/terminal directly on your device (recommended) OR connect your device to the network via ethernet cable and your network has DHCP autoconfiguration (devices on the network get and IP assigned automatically and you can determine the IP address assigned to your device on your e.g. This requires further steps to acquire the logs or any useful information to find out why. When you stuck after booting on the console with the Lakka flower logo, most certainly RetroArch is not able to start. Troubleshooting “Stuck on Lakka flower logo” The logs will be saved on the FAT32 partition, so you can easily get to them when you plug in your USB thumb drive / SD card to your computer. To: command -parameter > /flash/log.txt 2>&1 ![]() replace the redirection from: command -parameter > log.txt 2>&1 Then to save the logs to this partition, just redirect the output to a file on this partition, i.e. You only have to remount the partition into read-write mode: mount -o remount,rw /flash you have access only to the local terminal and you cannot read ext4 ( /storage, LAKKA_DISK) partition on your system, you can redirect the output of the logs to the FAT32 ( /flash, LAKKA) partition. If you are unable to copy-paste the output, e.g. The dmesg log lists each hardware device that the kernel detected along with information on how the device was configured by the system. Input device logsĭmesg displays all messages from the kernel ring buffer which typically is holding the messages generated by Lakka’s Linux kernel from the boot process. Audio device logsĪplay -L enumerates audio devices which have been detected by Lakka. Lspci -nnk | grep -A 3 VGA will give information about your graphic card. You can now copy the log file off of the Lakka system via an SCP file transfer. The file log.txt is now stored in the home directory. Restart the retroarch service in ‘verbose’ mode with this command: systemctl stop rvice LIBGL_DEBUG=verbose retroarch -menu -verbose > log.txt 2>&1 After the service restarts, the system log will begin appearing in the window where it can be copy-pasted to another location. Restart the retroarch service in ‘verbose’ mode with this command: systemctl stop rvice retroarch -v Lakka system logs Option A: Copying from the terminal window You should be able to access the shell also in case RetroArch does not start and you cannot enable SSH service via the RetroArch GUI. On PC (Generic) when booting from USB/SD card you may key in live ssh at the boot prompt to enable SSH service. The following procedures assume that the user has logged into Lakka via SSH. The information found in Accessing the Lakka Command Line Interface can be very helpful during this process as well. The script will create an archive with logs, which you can then either access on your SD card, via network share or upload. You only need to access the Lakka command line interface and run createlog. Since version 3.2 it is possible to collect all troubleshooting logs using one single script. A system log recorded when the problem occurs (if possible) along with any other logs that are relevant.When requesting help with a Lakka issue, please try to include: When problems arise during the operation of Lakka, it can be helpful for the developers and other volunteers to have certain standard information in order to find a solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |