looks like you might have already changed the config.. maybe before you started using the yabause-xbmc command.My guess the Graphics drivers are no longer correctly configured.

You may have to reinstall the setup-ogst-odroid package and hope it fixes the changes you did.. but it might also revert changes on other things like Rom Collection browser or that kind that you already done.You can also try fixing the configs manually.. all configs should be found somewhere unter /usr/local/share/setup-ogst/ in there you should find the templates for yabause... but I think you have to fix paths for the user and then copy the files to ~/.config/yabause/qt/

About the games you tried:Sonic R -> forget about it. Even if it starts the graphics are terrible.. It's one of the hardest games to emulate, and is a known issue for yearsGuardian Heroes -> works, but only until the end of the second level, then it freezes Sonic Jam -> no clue need to check on thatPanzer Dragoon 2 Zwei -> should work, but not very good, 3D games are not the best on yabause and it might be rather laggyNight Into Dreams -> works, but once again: mostly 3D and doesn't work that well..

EDIT... i got it to work now, i just did a fresh load on a spare card and just pulled the config file off of that one. tried Mega Man 8. this time i see the logo and i get a message about setting up the memory card. but it is starting. the screen is also really tiny, but that is just a setting i think. i will mess with that tomorrow. but it works. for the most part

Hello, the first thing is to thank for this great version, I have a question, how can I change the language in emulestation, I want to put it in Spanish but I do not know, any kind of help will be welcome, thanks in advance

Currently EmulationStation does NOT support different languages, although recently there is some development going on that may lead to translated UI, but most likely not translated scrapper informations.

currently there's no "select" it's something that I might need to implement.First you have to make sure the correct core is installed:all cores can be installed with apt-get install libretro-<core-name> for example apt-get install libretro-mame2000.You could edit the file /usr/local/bin/mame-libretro and write the name of the file inside that you want to use.Or copy the files and create new files if you want to start them manually from terminal.

I have an Odroid XU4 in a Cloudshell, with a 1TB 2.5" Mushkin Triactor SSD

I've tried over and over but cannot get the OGST to boot after following the guide on the front page and going into "Setup Odroid Gamestation" and doing the "move rootfs to hdd."

The "move to rootfs to hdd" succeeds, so upon exiting this utility, it asks to reboot. When it reboots, the system gets stuck at:

systemd-udevd[144]: starting version 215

I've tried it with two different SATA SSDs, the first one was a WD BLUE PC SSD 2.5" 500GB, I even checked to make sure the USB 3.0 connection was making good contact and has USB 3.0 speed (the cotton swab cleaning) and doing lsusb -t to verify the speed (has 5000M next to it, which I'm assuming USB 3.0's 5 Gb/sec spec).

Here is how I set up my Odroid XU4 and OGST image:

1) SD Card formatter to wipe the SD Card, SD card is Sandisk Ultra 32GB, HC I, A1 (The Samsung EVO and EVO+ cards I had would not work, it would freeze the OGST on the Desktop)2) Use Ether and write the OGST image onto SD Card3) Prepare the 2.5" SATA SSD by connecting the SATA to USB bridge to my PC (Windows 10), using Mini-Tools Partition Wizard, I delete the partition from the SSD, create an EXT4 partition, full span

Loading:

1) Wait for the system to reboot after the initial boot (as the guide states on the first page of this thread).2) After rebooting, I exit out of Kodi (hit or miss, if Kodi runs for a while, Kodi crashes on exit).3) Do my su -, apt-get upgrade/update/dist-upgrade until completion4) reboot5) exit Kodi again6) open console to change read/write permission on the SSD (it shows up on the desktop and it is mounted into /media/ordroid/), command I use on it is the good ole "sudo chmod 777" command7) Proceed to click on the "Setup Gamestation for Odroid" utility where the last item on the menu is the "move rootfs to hdd"8) The utility asks to move rootfs to either on /dev/sda or /dev/sda1 - I tried both, cannot move to /dev/sda, so I choose /dev/sda19) The utility proceeds to copy everything over10) After finishing, I exit, asks for reboot, I comply, and let the system reboot11) System hangs at "systemd-udevd[144]: starting version 215"

Any help would be appreciated. My goal is to move the rootfs to the SSD for performance, and I would also appreciate it if anyone can give or point me to a howto for resizing the rootfs to take up the entire disk as I'm not planning on making a separate partition for swap and etc.

There is an issue with the script that moves the rootfs to the harddrive.If the harddrive already holds a partition it's normally auto-mounted under /media/odroid/ and when I try to overwrite it it fails cause it's already mounted.

I've already fixed this and will upload a new script today which now will first unmount the partition and then try to convert it.It will also give more feedback in case something goes wrong.

meveric wrote:There is an issue with the script that moves the rootfs to the harddrive.If the harddrive already holds a partition it's normally auto-mounted under /media/odroid/ and when I try to overwrite it it fails cause it's already mounted.

I've already fixed this and will upload a new script today which now will first unmount the partition and then try to convert it.It will also give more feedback in case something goes wrong.

Hi meveric,

Thanks for looking into this, I really appreciate it. Do I just do a "sudo apt-get update" to pull this new script into the OGST?

Hi odroid members. Some one can translate this in french? My english is a little bit... bad. I want to install gamestation turbo for my XU4, but I don't understand some instructions... Thanks if some can do that for me...

danetco wrote:Hi odroid members. Some one can translate this in french? My english is a little bit... bad. I want to install gamestation turbo for my XU4, but I don't understand some instructions... Thanks if some can do that for me...

as this is a gaming image, the cpu governor is running on performance mode by default.This is normally not an issue for the board, but it CAN be an issue if you're using an XU4Q (passively cooled) and using a closed plastic case such as the XU4 default case or the OGST Gaming kit.. these cases are not very thermal friendly and passive cooling can run too hot.Although I've never seen 160°C... the board throttles if it reaches 95°C and will shutoff at "a hundred something" maybe 105 or 110 or so.

I don't have the XU4Q, just the XU4 but do have the OST Gaming kit.I have taken the case off completely and observe that the fan running for a minute or so and then it stops. Sometimes it goes for maybe 2 minutes but it shuts down each and every time.

I have another image with retropie and emulation station that works fine. Not sure what the setting is for the governor

meveric wrote:as this is a gaming image, the cpu governor is running on performance mode by default.This is normally not an issue for the board, but it CAN be an issue if you're using an XU4Q (passively cooled) and using a closed plastic case such as the XU4 default case or the OGST Gaming kit.. these cases are not very thermal friendly and passive cooling can run too hot.Although I've never seen 160°C... the board throttles if it reaches 95°C and will shutoff at "a hundred something" maybe 105 or 110 or so.

BloatedHeavyToad wrote:I don't have the XU4Q, just the XU4 but do have the OST Gaming kit.I have taken the case off completely and observe that the fan running for a minute or so and then it stops. Sometimes it goes for maybe 2 minutes but it shuts down each and every time.

I have another image with retropie and emulation station that works fine. Not sure what the setting is for the governor

Hmm then the system should run fine.. never had a system reporting 160°C.Have you checkec /var/log/syslog if it say something about it?

Not sure but it might be a SD card incompatibility, as the XU4 has a few SD cards it doesn't work with very good.The fan is off most of the time, hardkernel set the default to 65°C or higher before the fan comes on.

meveric wrote:Not sure but it might be a SD card incompatibility, as the XU4 has a few SD cards it doesn't work with very good.The fan is off most of the time, hardkernel set the default to 65°C or higher before the fan comes on.

I've had the same thing happen with my 16GB eMMC 5.0 Module XU4 Linux that I had purchased from hardkernely a I'll try some other SD cards and see if I can get it to work. here's log:

I've just build and uploaded the new Kernel that can solve the issue, but you have to install it to make it work, which probably can be a little bit hard for you as the system probably won't run stable through a normal update process, so here's a suggestion what you can do.1. download the package manually from here:https://oph.mdrjr.net/meveric/pool/xu3/ ... 3.10.106+/the files should have the date from today.2. put them on your SD/eMMC card via card-reader. If you have a linux PC or live-cd avaiable put them somewhere on your rootfs (for example into /root/)If you don't have a Linux system available, put the linux-image in the bootfs (this can be accessed via windows mac or other OS as well) it should have enough space that it should fit.You can securely delete files that have a different number than 3.10.106+ in the boot folder, so if you see a file that has a lower numner 3.10.105+ or something, just delete it, to make sure you have enough space.

From here on we have to "try" to fix it:3. boot up the odroid and as soon as you see the mouse pointer (starting the desktop) press CTRL + ALT + F1 login as root with password odroidIf you copied the files via another Linux system to /root/you can simply do a dpkg -i linux-image*if it's under boot do a dpkg -i /boot/linux-image*

If nothing "bad" happens and the system runs for 1-2 mins the Kernel update should install correctly and you can reboot after that and your problem should be gone.

IF the system crashes during update, it probably won't boot anymore after that and you have to restart the process by flashing a new image and copying the files again, until the Kernel update process finishes correctly. (kinda a game of chance)In two weeks or so I will upload a new image that has this fixed, but currently I'm on vacation and have limited access to my ODROIDs

Apologies for the noob questions but I've recently got a Odroid XU and have been (trying) to experience the delights of OGST and the new console kit. After a few false starts, I managed to get carry out all the updates and get the root transferred over to a HDD. However, I've hit one major problem and a few niggly ones that I can't seems figure out.

My major issue is that I can't seem to get my PC to recognise the Odroid on the network so I can start transferring roms over to the HDD via Win SCP. All my experience thus far has been with the Raspberry Pi 3 and getting it to appear on my PC just involved enabling SSH via the Pi Setup. Problem is, I can't seem to figure out how you do this on the XU4 via OGST.

My other minor giggles are once I boot the Odroid up;a) Once the desktop loads, it asks for an Authentication password. (2nd screenshot)b) I have to manually select the wireless connection despite it being selected as 'connect automatically' in the settings, followed by an 'Unlock Login Keyring' prompt. (1st screenshot)c) Not the end of the world for this one, but it there anyway to disable the text on startup? You could do it by manually editing the config.sys file on the PI. Is it the same principle for the XU4?

Obviously a) & b) will prevent me from having this to boot up straight into one of the front ends so any advice on how I can address these points so it can be automated would be greatly appreciated.

WylieCoyote wrote:My major issue is that I can't seem to get my PC to recognise the Odroid on the network so I can start transferring roms over to the HDD via Win SCP. All my experience thus far has been with the Raspberry Pi 3 and getting it to appear on my PC just involved enabling SSH via the Pi Setup. Problem is, I can't seem to figure out how you do this on the XU4 via OGST.

SSH is activated by default, just connect via WinSCP to the IP of the ODROID with the user odroid and the password odroid and you can copy files, that's it.

WylieCoyote wrote:My other minor giggles are once I boot the Odroid up;a) Once the desktop loads, it asks for an Authentication password. (2nd screenshot)b) I have to manually select the wireless connection despite it being selected as 'connect automatically' in the settings, followed by an 'Unlock Login Keyring' prompt. (1st screenshot)c) Not the end of the world for this one, but it there anyway to disable the text on startup? You could do it by manually editing the config.sys file on the PI. Is it the same principle for the XU4?

Obviously a) & b) will prevent me from having this to boot up straight into one of the front ends so any advice on how I can address these points so it can be automated would be greatly appreciated.

RegardsAndrew

The keyring is where Debian is storing passwords and WLAN settings in. By default this is encrypted so no one can read you settings.BUT if you remove the password (delete the keyring files from /home/odroid/.gnome2/keyrings/) you can create new settings without password protection, this works without entering the password to connect to WLAN.I'm not sure what the "second" screenshot is really about looks like the update manager asking for permissions, else I'm not quite sure what it's for.

The startup text can probably be disabled in the boot.ini, by removing the console=tty1 entry this should remove most of the messages I believe.

Apologies I am a complete Nood but I’m hoping someone can help with the following issues using XU4Q board with SD and external HDD with the ROMS stored on it.

1. Each time I launch a game from ES it goes to the Debian desktop then the game. When quitting it does the reverse. Is this normal?2. Can’t seem to run any FBA games (Street Fighter series). I see a black box quickly then dumps me back to ES.3. I seem to get a lot of crashes in ES as well.4. Importing in KODI was really slow. Any quicker way? Direct in ES maybe?5. My little screen is not showing any logos. Just a white screen.

Apologies I am a complete Nood but I’m hoping someone can help with the following issues using XU4Q board with SD and external HDD with the ROMS stored on it.

1. Each time I launch a game from ES it goes to the Debian desktop then the game. When quitting it does the reverse. Is this normal?

Yes that is normal, ODROIDs work different from RPis, while RPi can switch between FBDEV or X11 drivers, the ODROID can not, if you run X11 you run X11 so ES is running on X11 and so does the emulators.

SteveMo wrote:2. Can’t seem to run any FBA games (Street Fighter series). I see a black box quickly then dumps me back to ES.

There are different folder you can try: FBA, MAME, CPS1, CPS2, CPS3, NeoGeo... FBA, CPS1-3, and NeoGeo are using FBA - Cores, the MAME folder uses MAME libretro core, not all might be compatible, I'd suggest using FBA folder or CPS folder corresponding to the games.

SteveMo wrote:3. I seem to get a lot of crashes in ES as well.

Yes and No, ES has quite a lot of bugs, especially running under X11, it does not "return" to ES screen every time.. WHY - I don't know, but to avoid infinite hanging, I kill ES and restart it, if it does not recover after a few seconds.

Kodi uses 3 scrapper, thegamedb, giantbomb and mobygames to scrap artwork and descriptions, ES only uses thegamedb.So you have a higher chance getting infos within Kodi than with ES.thegamedb is sadly very unreliable often it doesn't work at all or is VERY SLOW, this can not be changed, as it's a problem with thegamedb and not Kodi or ES.

SteveMo wrote:5. My little screen is not showing any logos. Just a white screen.

Could be your screen is broken, you should try to contact HardKernel about it.

SteveMo wrote:6. My screen res needs adjusting. The picture is too big for the TV. How do I adjust this?

That sounds like an Overscan issue, ODROIDs do not support adjustment for overscan, this must be done on the TV itself.Check the picture settings on your TV, there's an option where you can switch between 4:3 and 16:9 picture mode and others.. one of these "others" may fix your overscan issue, if your TV supports this.

SteveMo wrote:7. Does the LCD screen work with RetroPie or only OGST?

"Technically" it works with any image that uses the correct Kernel, but it must be implemented by the developers of that image.I don't think RetroPie has implemented this yet.

SteveMo wrote:8. Along with the ROMS I actually have all the snaps/wheel/boxart/flyer but it did not seem to pick up during the scan. Is there a way to automatically grab all of my existing media files?

that depends on the frontend you use.For EmulationStation you can simply put the files into /home/odroid/.emulationstation/downloaded_images but for ROM Collection browser (Kodi) you probably have to manually select to scrap "local artwork".Although I admit I've never done that.