Loving Lakka on dedicated pc box though having sound issues

As a foreword I am a novice Linux user. Advanced pc/windows user. I have some programming knowledge and used DOS for many years.

I am finding the documentation here a bit confusing similar to stereo instructions. If someone could get me to understand I am sure I could write out a better tutorial in my free time. I also have some experience in coding for a couple of games and map development.

What I am looking for is how to launch command line directly from the GUI. display sound options for device set lakka to use desired option by editing the config file

Thanks ahead of time

Sincerely Nicholas Dunton

Hitting tab while loading Lakka is not bringing up command line. I get that I need to fix my retroarc.cfg file to use the hdmi but cannot get command line to load :frowning: I have it installed on a sata drive so not running live. In fact I tried my onboard speaker, all my audio ports, and no audio is coming out of anywhere. Turned up the volume in the GUI to 12 too.

So my main question, is hitting tab the only way to get into command line?

Hello, hitting tab during the bootloader should work. There are alternatives, like connection through SSH. In the future, we will allow selecting that audio card from the GUI. In the meanwhile, you have to try SSH.

Well I am officially lost.

Connected Lakka box to LAN obtained its IP and tried to connect via PuTTY to no avail at all. Always told me Access denied.

Can I hard edit the config file on a windows box and paste it via network then reload retroarc?

Also there is no way inside the GUI to set up username/password for the SSH.

Since I am not sure of my values needed for my audio device I guess hard editing the cfg file would be useless sigh.

The access denied message can happen in very rare cases if your file system is corrupted. But I don’t think it is your case. It almost never happens on PC.

Why do you need to change the credentials for ssh?

That was more of a theory. Was wondering if I had to set it up, or if there was a default log in. I was not asked for one just the connection failed.

Now that I think about it I was using it’s ip location for the network. Perhaps I was misunderstanding after reading some documentation on SSH and I need to find it’s ip location as a server on the internet.

I was using 10.0.0.11 though from what I was reading it should look more like a domain ip and something like 12.32.53.97 sic.

Is there an option inside the GUI to find that location or do I need a third party program to locate this ip?

You were right to use the local IP. I don’t know why you get connection refused :confused:

Ok the problem was me being new like I thought. At install before I read enough I told it not to enable SSH because it said to say no if you are not familiar with linux :stuck_out_tongue:

now to find out the login info haha(found it root and root now we are cooking with gas!)

When i was done with editing and reloaded system on a screen it loaded in a monochrome GUI with several selection options(assume retroarch) and the lakka GUI was not present. :frowning: HE BROKE IT AGAIN!

If it dropped back to the low-res menu with green lettering (called RGUI), you can get back to the normal Lakka menu by going to settings > driver settings and changing the menu driver from rgui to xmb. You can also do it via retroarch.cfg over ssh by changing (or adding if it’s not there already) menu_driver = “xmb”

Will try also when I am in SSH and type retroarch to restart it I get an error about screen saver not loading properly then just a flashing Console cursor without the Lakka:# in front of it. Like it is hanging. I hit ctrl C and it breaks is, is that normal?

Alright think I edited something I was not suppose to. Got the xmb back but it is black background with white fonts and boxes all over. The controller is not working now either. Maybe since I understand a bit more I should reinstall and start over heh

there is no core being loaded apparently, something I do not remember changing

Ok got it to work :smiley:

Had to reinstall lakka I must of messed with something before I knew what I was doing in SSH.

Thanks for all the assistance :smiley: (and patience)

UPDATE: It stopped working so I looked at the Audio Option and under device it was properly stated hdmi:CARD=Generic_1,DEV=0 I accidently chose device and hit enter clearing it. Though not sure why that would not let me reenter the path.

You can’t start retroarch over ssh. It tries to start through your tunnel, which obviously doesn’t work.

Black background with white fonts and boxes all over means it can’t find your ‘assets’ for the menu. This likely means that either your asset directory has moved or you’ve changes the path in the cfg. You can get it back by going to settings > directory (or paths, depending on how old your build is) settings and direct your assets directory to wherever those assets are.

However, you may be better off reinstalling your whole system, as you mentioned, now that you know a little better what you’re doing. :slight_smile:

EDIT: ninja’ed. glad you got it going :slight_smile:

Yeah I did do a reinstall, a couple of times heh. Got the hdmi working after loading a test game. Moved a couple games over and rebooted and it went away :(. It seems I can restart all over the ssh all it does though is turn off the GUI and leaves just a mouse cursor on a black screen.

Using systemctl stop retroarch and start retroarch commands to turn it on and off. Do I just need to turn it off, edit .cfg, then shut down with hard power off? Is it not saving properly cause of hard shut downs?

if you’re editing a cfg over SSH while RetroArch is running, RetroArch will overwrite your changes when you exit because it loads the config into memory when it starts up and then writes it to file when it exits. So, either exit out of RetroArch before editing the cfg or turn off the option to save configs on exit while you’re working on it.

alright my card is generic not generic_1 my mobo routes PnP os to generic_1 so I had to direct route to generic for my CARD. Got it going well now :smiley:

Oh, that can happen if your filesystem is corrupted.

Try reinstalling again?

Sorry for this bug, we really need to fix that.