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.
Night Into Dreams -> works, but once again: mostly 3D and doesn't work that well..
There are already a couple of articles in the ODROID magazine about my favorite Sega Saturn games on the XU4, there are quite a lot.
Maybe you find some you like in these article as 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.
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.
what set version is the MAME emu using with your build? i did not come across a definite answer.
i have tryed 0.78 with no luck.
mame (default) ~> unclear, as it is latest development branch.. should be 0.19x maybe 0.192 or 0.194 or 0.198 im not sure.
how do you pick what Mame it uses or is that throught retroach?
currently there's no "select" it's something that I might need to implement.
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'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."
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).
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).
7) Proceed to click on the "Setup Gamestation for Odroid" utility where the last item on the menu is the "move rootfs to hdd"
11) System hangs at "systemd-udevd: 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.
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?
after that you should have the new script.
Please let me know if you encounter more issues.
Not sure how good it is, but have you tired google translate?
en fait j'essaie de comprendre l'ensemble, mais le tuto n'est pas très récent, j'ai réussi a passer debian en français, je fais les mises a jour avec les commandes sudo get-apt mais ensuite je rame sur la compréhension du reste. Je ne sais pas comment faire pour me connecter en SSH car mon pc ne voit pas l'odroid et y mettre les roms. Pour info je suis habitué a recalbox sur raspberry pi 3. J'ai tout recommencé depuis le début en essayant de suive une vidéo et je vais voir ce que ça donne, car pas habitué a xbmc ni a l'autre front end, j'ai réussi a entrer dans emulstation mais il est bizarre et peu d'options comme l'impossibilité de le mettre en français. comme j'ai dit, j'ai refais une installation propre et là je refais les étapes.
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.
danetco wrote: en fait j'essaie de comprendre l'ensemble, mais le tuto n'est pas très récent, j'ai réussi a passer debian en français, je fais les mises a jour avec les commandes sudo get-apt mais ensuite je rame sur la compréhension du reste. Je ne sais pas comment faire pour me connecter en SSH car mon pc ne voit pas l'odroid et y mettre les roms. Pour info je suis habitué a recalbox sur raspberry pi 3. J'ai tout recommencé depuis le début en essayant de suive une vidéo et je vais voir ce que ça donne, car pas habitué a xbmc ni a l'autre front end, j'ai réussi a entrer dans emulstation mais il est bizarre et peu d'options comme l'impossibilité de le mettre en français. comme j'ai dit, j'ai refais une installation propre et là je refais les étapes.
Tu es sous Linux ou Windows ? Sous Linux, pour moi gamestation apparaît et je peux me connecter avec putty.
Il n'y a que le Emulationstation de Recalbox qui a été traduit, donc celui-ci est effectivement seulement en anglais.
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.
meveric wrote: as this is a gaming image, the cpu governor is running on performance mode by default.
BloatedHeavyToad wrote: I don't have the XU4Q, just the XU4 but do have the OST Gaming kit.
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?
meveric wrote: Hmm then the system should run fine.. never had a system reporting 160°C.
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.
May 28 15:45:21 gamestation-turbo systemd: Started /etc/rc.local Compatibility.
May 28 15:45:22 gamestation-turbo systemd: Started /etc/rc.local Compatibility.
May 28 15:45:22 gamestation-turbo systemd: Started Getty on tty1.
May 28 15:45:22 gamestation-turbo systemd: Started Serial Getty on ttySAC2.
May 28 15:45:22 gamestation-turbo systemd: Starting Login Prompts.
May 28 15:45:22 gamestation-turbo systemd: Reached target Login Prompts.
May 28 15:45:22 gamestation-turbo systemd: Starting Multi-User System.
May 28 15:45:22 gamestation-turbo systemd: Reached target Multi-User System.
May 28 15:45:22 gamestation-turbo systemd: Starting Graphical Interface.
May 28 15:45:22 gamestation-turbo systemd: Reached target Graphical Interface.
May 28 15:45:22 gamestation-turbo systemd: Started Update UTMP about System Runlevel Changes.
May 28 15:45:22 gamestation-turbo systemd: Startup finished in 11.073s (kernel) + 1min 5.172s (userspace) = 1min 16.245s.
e, but there was actually nothing to write.
(null)'. Please report this issue to the ALSA developers.
subsequent snd_pcm_avail() returned 0 or another value < min_avail.
May 28 15:45:32 gamestation-turbo systemd: Starting user-0.slice.
May 28 15:45:32 gamestation-turbo systemd: Created slice user-0.slice.
May 28 15:45:32 gamestation-turbo systemd: Starting Session c2 of user root.
May 28 15:45:32 gamestation-turbo systemd: Started Session c2 of user root.
May 28 15:45:32 gamestation-turbo systemd: Starting Paths.
May 28 15:45:32 gamestation-turbo systemd: Reached target Paths.
May 28 15:45:32 gamestation-turbo systemd: Starting Timers.
May 28 15:45:32 gamestation-turbo systemd: Reached target Timers.
May 28 15:45:32 gamestation-turbo systemd: Starting Sockets.
May 28 15:45:32 gamestation-turbo systemd: Reached target Sockets.
May 28 15:45:32 gamestation-turbo systemd: Starting Basic System.
May 28 15:45:32 gamestation-turbo systemd: Reached target Basic System.
May 28 15:45:32 gamestation-turbo systemd: Starting Default.
May 28 15:45:32 gamestation-turbo systemd: Reached target Default.
May 28 15:45:32 gamestation-turbo systemd: Startup finished in 173ms.
May 28 15:45:32 gamestation-turbo systemd: Started User Manager for UID 0.
One of the thermal sensors in the SoC seemed to be partially damaged.
We made a patch set for Kernel 4.14 a few months ago.
We will prepare the same patch 3.10 within a couple of days.
odroid wrote: One of the thermal sensors in the SoC seemed to be partially damaged.
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.
the files should have the date from today.
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.
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.
The directory /lib/modules/3.10.106+ still exists. Continuing as directed.
Connection to 192.168.1.13 closed by remote host.
It's up and running now, more testing later, thanks much!
Enjoy your vacation! Two weeks sounds awesome.
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.
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.
The image comes with ssh active. Input the odroid ip into winscp and login with odroid/odroid.
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.
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.
Thank you for the prompt responses. I'll have a tinker later tonight.
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.
Think that's it for now. Apologies if I'm doing something stupid.
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.
SteveMo wrote: 4. Importing in KODI was really slow. Any quicker way? Direct in ES maybe?
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.
Stupidly I copied loads of ROMS on there and it took maybe 4/5 days of importing. Think I will start from scratch with a few at a time and build it up that way.
Will contact them about the screen.
6. My screen res needs adjusting. The picture is too big for the TV. How do I adjust this?
7. Does the LCD screen work with RetroPie or only OGST?
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.
Thanks again meveric. Great help.
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?
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.
OK will have a play around.
Thanks meveric. I'll try not to bother you any more.
I've been trying to install the image available from the site and haven't been able to get a successful boot.
Only a select few images (18.04, 16.04) seem to boot successfully on my eMMC card.
Any ideas of what I should try? TY!
Is your emmc orange by any chance? It needs an updated kernel to boot and it's possible the original image comes with an older kernel.
The image was updated to support that eMMC some months ago.
I have just bought one kit today, wish me luck. I hope this will work with the SDCard.
mad_ady wrote: Is your emmc orange by any chance? It needs an updated kernel to boot and it's possible the original image comes with an older kernel.
My eMMC is colored orange and of 16GB size card sold/shipped from HardKernel.
meveric wrote: The image was updated to support that eMMC some months ago.
Is there another link that I should refer to other than the ODROID-GameStation-Turbo-3.9.5-20171115-XU3+XU4-Jessie.img.xz ?
I appreciate your contribution to maintaining this image for the odroid immensely.