There are multible entries to load the driver in your rc.local please delete it and leave just one in it, or delete everything in it and Activate Console Kit Support again with Setup ODROID Gamestation Turbo tool

ind1fference wrote:Thanks. Also how do I stop the keyring unlock window from always popping up at startup? The option to stop it is greyed out.

The first time you use it it's gonna ask for a password, if you enter a password it will always ask for the password, if you do not enter a password it can work without but passwords and settings (WiFi) will be stored unprotected in the keyring file.If there's already a password set you can remove the keyring in the .gnome2/keyrings folder and start with a new blank one.

What needs to be done to use a bluetooth controller?i have one of the hardkernel dongles that works with other images, but i see no way of syncing a controller in either debian, emulation station or kodi

hmm this doesn't touch the login screen in the least, it only replaces a file under /home/odroid/.config/autostart/ which is AFTER the login when the desktop is already loaded.So it should not affect the login in the least.I just tried it on my ODROID and it worked perfectly fine. I saw the desktop for a split second then ES booted up and now I'm sitting in ES.Can you check /var/log/syslog if you see any issues? Maybe there's a file damaged or something.

which shouldn't show up at all, as the system is set to auto-login.Anyway yes you can access other things, just press CTRL + ALT + F1 to go to VT1 here you can login as root with password odroid and navigate through the system.Using "mc" (Midnight Commander) should make it easier to navigate through the system you can use arrow keys to go up down, enter to open a folder and F3 to read text files. It's a rather handy tool.

At this point you're already logged in.it complains that the "command" "odroid" that you entered is not a valid command, means you have to be logged in to even be able to enter "commands".So just type mc / as a command.

There's so much here and I don't know what I'm looking for. I'm lost. I'm wondering if my SD has an issue because there was no degradation of performance or warning signs just a restart and an unexpected login screen.

the file is very long that is true.. here's what you can try instead:1. exit mc (type exit) or press F102. use the command: tail -f /var/log/syslog3. press enter a couple of times so you have a couple of blank lines4. press CTRL + ALT + F7 to go back to the login screen5. try to login6. switch back to CTRL + ALT + F1 and check what was written in the log when you tried to login.Shouldn't be too much text.. if it's still more than one page, you can go UP a page by pressing SHIFT + page UP that should allow you to scroll a few pages up and down... it's hopefully something obvious.One of my guesses, the files under /home/odroid/ do not all belong to odroid anymore, but some might have been altered by root and odroid no longer has access to them, causing the system to fail login as it can't write the files.

If that's the case you can try chown odroid:odroid -R /home/odroid to make sure all files belong to the user odroid.Once that is fixed the system should act normal again, IF that is really the problem currently.If not, I hope the syslog tells us what it is.

It contains four tools which helps you to access the Gaming Kit LCD and user button in an easy to use script able way, you can do things like this:

gpio_button:

This tool can run as daemon and start scripts/programs when the user button is either pressed or released, this gives you the opportunity to measurethe time between the keypress to start different events or just fire up a script only when the button is released, you can run it from console to testyour script like so gpio_button -f /home/odroid/LCDTools/test.sh -r /home/odroid/LCDTools/test2.sh and add it to auto start later and run it as daemon like this:

as you can see each line has to send separate to the LCDthe first line backups the framebuffer contains in a file the second line draws not only the text with x and y position, it adds an overlay with transparency 128the third line draws also a text but this time without overlay, because it's already there fourth sleeps 5 secondsfifth restore the original framebuffer

P.S.: for more detailed info look on GitHub

Last edited by AreaScout on Thu May 31, 2018 1:26 am, edited 2 times in total.

It looks like something is not correct... it says fatal IO error and ressource not available for :0 which is normally when it tries to connect to the X-Server.I still think something got messed up with the permissions.This is not the default behavior of the image, so I wonder how that happened.

If there's nothing important on the image yet you can always start from a fresh image.Once again, this is not normal behavior, but something is broken.

Now I am curious why romcollection browser in kodi skips some titles, like i added 4 n64 roms to the folder, and it added 007, but skipped the 3 other 3 big names like mario kart and super mario

emulation station finds them no problem

thanks again

What do you mean by skips it? Scrapping or just to show them in the overview?Scrapping can be repeated, sometimes not all sites are up and you can restart the scrapping process, by pressing C and selection to rescrap the selected game.

yes the rom collection browser is actually a very old project and was kinda dead for a couple years, it recently started development again and I'm looking into it to see if it works better now.You can always re-scrap the collection and see if it works. Maybe disabling mobygames for now as this is the one often causing issues.

So sftping roms just resulted in Filezilla erring everything out and upon a restart I'm looking at the aqua Debian 8 desktop again. I give up. GameStation is trash for me. No fancy LCD for me unless another image starts using it. Shame.

ind1fference wrote:So sftping roms just resulted in Filezilla erring everything out and upon a restart I'm looking at the aqua Debian 8 desktop again. I give up. GameStation is trash for me. No fancy LCD for me unless another image starts using it. Shame.

ind1fference wrote:So sftping roms just resulted in Filezilla erring everything out and upon a restart I'm looking at the aqua Debian 8 desktop again. I give up. GameStation is trash for me. No fancy LCD for me unless another image starts using it. Shame.

How are you flashing the OS, with what hardware? Are you using MicroSD to SD?

I've used etcher each time and I'm on my 6th-7th attempt to get it to work. There's always an issue once I start copying roms via sftp. I eventually restart and get the aqua desktop and I'm unable to get back the default debian desktop. I'm using a 128GB Samsung EVO Select micro SD card. This card never gave me problems on my raspberry pie.

ind1fference wrote:So sftping roms just resulted in Filezilla erring everything out and upon a restart I'm looking at the aqua Debian 8 desktop again. I give up. GameStation is trash for me. No fancy LCD for me unless another image starts using it. Shame.

It kinda looks like .Xauthority or something got messed up.like someone messes up the permissions.Which user do you use for sftp?Also I wonder why Filezilla is touching these files at all when you copy ROMs.

could it be that you filled the rootfs to 100% during file copy?If the rootfs is 100% full login should also fail as it can't create certain status or log files anymore.Also I still think there are some SD cards that have issues with the XU4, meaning that their filesystem get's damaged while the system is "running".That is why I prefer eMMC or HDD instead, especially for large images with lots of ROMs and such.My OGST image at home has over 300GB worth of data it's using, way too big for SD cards

Will the "activate console kit" work on a Cloudshell 1? I bought one of the original Cloudshell kit but never really got the screen to work quite well, since I bought a console kit for my original Odroid XU4, was thinking about buying another Odroid XU4 to stuff it back into the Cloudshell kit if the Console Kit's software (mainly the display is what I'm after) works with it...

Would be nice to have one that looks like an N64 to gift to my younger bro and keep the one with the Cloudshell kit for myself since I don't really care too much about aesthetics. The fact that the display shows which console is currently being played is a beautiful thing IMO

Please let me know, I wouldn't mind ponying up some more dough to pull in another Odroid XU4 to use with the Cloudshell since I generally like to have all my electronics doing work and not go to waste!

Also, if Hardkernel has an Odroid XU5 in the works, I wouldn't mind waiting for that either... Will hardkernel spin another SBC based on a more recent Exynos? These Samsung SoCs are badass...