Hello I have a quick question, I have a raspberry pi and would like to put the new lakk/retroacrh gui on it. My understanding from what I have read and seen is that lakka basically installs as an os onto the pi and boot directly into it. This is great (exactly what I want), my question tho is does lakka have a shutdown option and if so does it do a proper sudo shutdown of the pi. I just wanted to find out before installing it to my pi. Thanks for the info.
Not yet, I don’t think, but it was brought up just yesterday in IRC, so I think it’s being looked into.
Alright thanks for the info, I was just curious. It would be a nice feature then you could just go to shutdown then kill yor pi with a kill switch on the power cord, no keyboard needed. :). anyways I will be trying out lakka after bit thanks again.
I think that the ARM devices has been though to be running 24x7. The power consum is very low. The same happend when you do a poweroff in Kodi or openelec the operating System does the poweroff but the device keep on.
You’re right. Some users plug the USB power wire directly on their TV though, so the device gets shutdown when they shut their TV.
This shutdown option will be interesting to workaround an anoying bug : when you flash Lakka for the first time, if you never quit RetroArch before unplugging your device, a blank/corrupted retroarch.cfg is created and RetroArch becomes unable to read it. The user is left with an unconfigured rgui. It’s not a RA bug, since the same happens for ssh. I have to rm this config file to get RA create a new one, and I have to rm .ssh to let sshd work again.
[QUOTE=Kivutar;18431]You’re right. Some users plug the USB power wire directly on their TV though, so the device gets shutdown when they shut their TV.
This shutdown option will be interesting to workaround an anoying bug : when you flash Lakka for the first time, if you never quit RetroArch before unplugging your device, a blank/corrupted retroarch.cfg is created and RetroArch becomes unable to read it. The user is left with an unconfigured rgui. It’s not a RA bug, since the same happens for ssh. I have to rm this config file to get RA create a new one, and I have to rm .ssh to let sshd work again.[/QUOTE]
Hi Kivutar, I’m trying to get run sshd but I remove the .ssh folder in the Storage partition several times and the sshd daemon never come back. Is this partition and folder that I have to delete to recover sshd??
Hi ralias, please check that the ‘ssh’ word is present in your cmdline, in your bootloader config. If you still get ‘connection refused’ after removing .ssh and .cache from the storage partition, then sorry but you will have to reflash.
In addition to a shutdown feature a reboot to another partition would be nice. So one could boot into OpenElec with Lakka. In the past I succesfully tested this with Noobs + Retropie + OpenElec.
sudo su -c ‘echo 7 > /sys/module/bcm2708/parameters/reboot_part’ sudo reboot
In this case the number 7 is the number of the partition you want to boot.
[QUOTE=belvsdragon;18689]In addition to a shutdown feature a reboot to another partition would be nice. So one could boot into OpenElec with Lakka. In the past I succesfully tested this with Noobs + Retropie + OpenElec.
sudo su -c ‘echo 7 > /sys/module/bcm2708/parameters/reboot_part’ sudo reboot
In this case the number 7 is the number of the partition you want to boot.[/QUOTE]
Interesting, I didn’t know that.
Interesting, I didn’t know that.
A second method would be to change the autoboot.txt. The the way mentioned above was a workaround because of a bug in the firmware. https://github.com/raspberrypi/noobs/issues/195
Thanks kivutar. I reflash and I had to delete retroarch.cfg and .ssh and now everything works.