Updated retropie asks for login

bonezinger

Like many other people, I've come across this problem. I've updated my retropie and now, instead of going straight to emustation, it instead asks me to login.

However, I have one hell of a problem: I completely lack any physical usb keyboards. I thought about trying a bluetoothone, but how am I supposed to pair it?
I haven't set up SSH, but I can still access things via Samba, though I doubt that will be really helpful.

The help I'd like is: what file under what directory should I change so that the OS boots straight into emustation? I can get the sd card on another computer to read and modify the files manually.

The last resort I'm considering is formatting the card again and start from scratch.

mitu

@bonezinger Set-up SSH and then re-configure the auto-login options. You can do that without a keyboard, just by adding an empty ssh file on the boot partition from the SDcard - see https://retropie.org.uk/docs/SSH/#enable-ssh.
The auto-login settings are no accessible from via Samba, unfortunately.

bonezinger

@mitu I created the file, but apparently the default username/password in the guide you linked are wrong, I can't login with them at all.
username: pigaming
password: retropie

I also tried combinations of retropie, retropi, pi, piegaming as username and password, no success.

BuZz

@bonezinger someone has messed with the wiki. Username is "pi" and password is "raspberry"

I'll go fix it

BuZz

I have fixed the page and blocked the person who made the edit as I don't want any more of their "help". Problem with having user editable documentation! They probably bought a premade RetroPie set-up which has a different user and password :/

bonezinger

@buzz Ah, should've thought of that combination, it worked! Thanks!
Also thanks @mitu for the help with setting SSH, everything is working fine now!

fnkngrv

@buzz said in Updated retropie asks for login:

I have fixed the page and blocked the person who made the edit as I don't want any more of their "help". Problem with having user editable documentation! They probably bought a premade RetroPie set-up which has a different user and password :/

Our build of RetroPie at Odroid Retro Area uses "pigaming" and "retropie". When I started the initiative a year ago to me it didn't make any sense at all that RetroPie uses the same user account name for anything other than Raspberry Pi boards especially the "raspberry" password. That being said if there was a willingness from RetroPie official to allow us to collaborate to provide our work for more than "basic" support for the Odroid XU4 other than what has been suggested which is "do a push request" it would help. I personally don't have much experience with GitHub and all of this push/pull stuff nor do I have the time to mess with it tbh. I ensured that we have a solid build log for our current v1.1 which has all of the steps mapped out in detail, but that apparently isn't good enough. It also doesn't help that the forum doesn't appear to have a way to PM/DM someone to discuss anything on the side just like there is not on GitHub which I won't go down a rabbit hole for my opinion on it. I would be interested to know who made this edit on the Wiki to know if they are part of my team and address it if so because it was not something that was discussed with me or authorized.

BuZz

@fnkngrv If you are unable to contribute your work back via github, I cannot really collaborate. if you have forked retropie and are changing stuff around, you should point your users to your own documentation. Also make sure you are compliant with the licence with code changes. I would certainly do things properly via source control.

PM is disabled for good reason (and I don't have any wish to discuss code changes in private as discussion should be in public on github). If you don't have the time to spend to do things properly via github (which is how we collaborate code wise), I cannot help.

A Former User

@fnkngrv said in Updated retropie asks for login:

I would be interested to know who made this edit on the Wiki to know if they are part of my team and address it if so because it was not something that was discussed with me or authorized.

Don't know if they were on your team but this is who made the edit: https://github.com/austin987

fnkngrv

@buzz we have forked it and yes we always tell our users to view our release notes and also FAQ on our website. We recently added someone well versed with GitHub so perhaps we can come to a collaboration together. When I started the initiative the whole goal was to assist with providing RetroPie official with the tools to be able to provide a usable build for the XU4 so I will discuss after our upcoming release is out with the team to see how best to provide you with our work. I know that someone on your team has an XU4, but you have your hands full for sure otherwise. I think that we have put together something pretty solid. It is on an older kernel, but then again we have to use what Hard Kernel provides for an OS base. Thanks for your candid, courteous, and speedy reply. Once again I do hope that it was not someone on my team that caused the hubbub on the wiki. For now all I can say is if that is so my deepest apologies.

fnkngrv

@livefastcyyoung said in Updated retropie asks for login:

@fnkngrv said in Updated retropie asks for login:

I would be interested to know who made this edit on the Wiki to know if they are part of my team and address it if so because it was not something that was discussed with me or authorized.

Don't know if they were on your team but this is who made the edit: https://github.com/austin987

No, that person is not affiliated with us at all. Good to know that we didn't muck things up!

BuZz

@fnkngrv I have an XU4 and added the support originally. I am aware of a few things here and there that need improving, but haven't had time to do any work on the XU for a while. Unfortunately there have not been many contributions from anyone else regarding the XU4. I would encourage you to try and get any scriptmodule improvements back into our codebase rather than maintaining all the changes in a separate project.

Where do you keep your source changes?

fnkngrv

@buzz we have a github ourselves. Once we get this latest base released I'll touch base again on it to see what can be done.

BuZz

@fnkngrv URL ?