ODROID GameStation Turbo with XBMC

bpbiszkopt · Post by **bpbiszkopt** » Thu Nov 16, 2017 1:53 am

Ok, Thx

Just install your image and make update, that's all...

aric1979 · Post by **aric1979** » Fri Nov 17, 2017 2:55 pm

meveric wrote:yes some time ago mdrjr changed his webspace a little while ago from http to https and apt needs special treatment for that:
Code: Select all
su -
cd /etc/apt/sources.list.d/
sed -i "s/^/#/" *.list
apt-get update
apt-get install apt-transport-https ca-certificates
sed -i "s/^#//" *.list
# after this you can update as usual again:
apt-get update && apt-get upgrade && apt-get dist-upgrade

Ok I did all of this and the updates worked awesome but now the old XBMC does not work. I can hear it but not see it. I thought well maybe I need to upgrade to Kodi. I tried your instructions on that per page 17 of this thread but that doesn't work for me either. It says
Unable to loacate package.

meveric · Post by **meveric** » Fri Nov 17, 2017 4:30 pm

give me a little time to investigate..

aric1979 · Post by **aric1979** » Fri Nov 17, 2017 4:32 pm

aric1979 wrote:
meveric wrote:yes some time ago mdrjr changed his webspace a little while ago from http to https and apt needs special treatment for that:
Code: Select all
su -
cd /etc/apt/sources.list.d/
sed -i "s/^/#/" *.list
apt-get update
apt-get install apt-transport-https ca-certificates
sed -i "s/^#//" *.list
# after this you can update as usual again:
apt-get update && apt-get upgrade && apt-get dist-upgrade
Ok I did all of this and the updates worked awesome but now the old XBMC does not work. I can hear it but not see it. I thought well maybe I need to upgrade to Kodi. I tried your instructions on that per page 17 of this thread but that doesn't work for me either. It says
Unable to loacate package.

One thing I forgot to mention is I did the select all copy and paste of what you had wrote without noticing the "#after this you can update as usual again:" Then I just did the update line without closing the window and reopening it. I don't know if that could have messed anything up or not since it was in a different section or directory. I guess I can just start all over flash the old base image to my sd card boot it up then copy and paste it correctly? When it updates is it supposed to install kodi? Or leave Xbmc and I need to past in apt-get kodi-odroid line?

meveric · Post by **meveric** » Fri Nov 17, 2017 5:59 pm

lines starting with a # are comments, and terminal will just ignore them, so there's no issue with that.
It will not update from xbmc to kodi. Kodi has to be installed manually.

meveric · Post by **meveric** » Sun Nov 19, 2017 11:04 pm

Ok I've tested the update for the U3 and came across a few issues.
In fact it does upgrade from XBMC to Kodi, as I put that into setup-ogst-odroid.
I had some issues starting Kodi afterwards and when I checked into it I found it was complaining about the language which apparently was not found, but I could easily correct this with:

Code: Select all

sed -i "s?<language>English (US)</language>?<language>English</language>?" ~/.kodi/userdata/guisettings.xml

The issue with the missing items for the RCB is in fact the rcb_useOldAlignment value it's located in ~/.kodi/userdata/addon_data/skin.confluence/settings.xml and needs to be set to "false".
After that I had no issues with Kodi anymore and everything was working as expected.

I'll update the image on the first page to the recent version of this image in a little bit, therefore you don't have to do these steps yourself.
But, if you can't wait, the above information should be enough to fix the image yourself.

Edit:
new version is uploaded and linked on the first page.

bpbiszkopt · Post by **bpbiszkopt** » Wed Nov 22, 2017 7:49 pm

Thx meveric... i don't why i didn't saw rcb_useOldAlignment line in confluence skin file...
Kodi working fine...i see scrappers.
I have two more question.
How should works retroarch...if i run it from desktop, it runs like oldschool...

If i run it from terminal with sudo it looks like this

This one form sudo looks much user friendly but when i trying to update/load any core it refresh and nothing happens.
And the second question at the menu there is something like mame arcade emulator, when i trying to lunch it nothing happens, form terminal i have segmentation fault.

meveric · Post by **meveric** » Wed Nov 22, 2017 9:21 pm

bpbiszkopt wrote:Thx meveric... i don't why i didn't saw rcb_useOldAlignment line in confluence skin file...
Kodi working fine...i see scrappers.
I have two more question.
How should works retroarch...if i run it from desktop, it runs like oldschool...

If i run it from terminal with sudo it looks like this

starting it from menu starts retroarch as user odroid (using the settings I prepared)
starting from terminal with sudo starts retroarch as user root (sudo = super user do -> super user = root) and with the settings for root (which are not configured by me).

bpbiszkopt wrote:This one form sudo looks much user friendly

It's just the setting what design you want to use and can be changed in the driver settings, I'm actually thinking about changing the design to the new one soon.
In the past the new design was very buggy and did not work correctly, but that was fixed some time ago.

bpbiszkopt wrote:but when i trying to update/load any core it refresh and nothing happens.

No surprise, the root user has no configuration for retraorch, the default config does not know where cores are located and such, don't use sudo, there's no point what so ever for useing sudo to start retroarch, it just makes your system more vulnerable to attacks.

bpbiszkopt wrote:And the second question at the menu there is something like mame arcade emulator, when i trying to lunch it nothing happens, form terminal i have segmentation fault.

Don't know about this, that's nothing I installed (at least it shouldn't).

aric1979 · Post by **aric1979** » Tue Nov 28, 2017 1:25 am

meveric wrote:Ok I've tested the update for the U3 and came across a few issues.
In fact it does upgrade from XBMC to Kodi, as I put that into setup-ogst-odroid.
I had some issues starting Kodi afterwards and when I checked into it I found it was complaining about the language which apparently was not found, but I could easily correct this with:
Code: Select all
sed -i "s?<language>English (US)</language>?<language>English</language>?" ~/.kodi/userdata/guisettings.xml
The issue with the missing items for the RCB is in fact the rcb_useOldAlignment value it's located in ~/.kodi/userdata/addon_data/skin.confluence/settings.xml and needs to be set to "false".
After that I had no issues with Kodi anymore and everything was working as expected.

I'll update the image on the first page to the recent version of this image in a little bit, therefore you don't have to do these steps yourself.
But, if you can't wait, the above information should be enough to fix the image yourself.

Edit:
new version is uploaded and linked on the first page.

Thank you very very much. All fixed up

aric1979 · Post by **aric1979** » Tue Nov 28, 2017 7:45 am

I installed a xu4 fan on top of my u3 heat sink and plugged it in. Is there a way I can have it come on like you do the XU4 game station turbo build on my U3? The fan noise doesn't bother me at all.

meveric · Post by **meveric** » Tue Nov 28, 2017 1:19 pm

it should do that automatically when needed... the U3 is much cooler than the XU4 therefore it's rarely needed.. and stays off most of the time.

poopins · Post by **poopins** » Fri Mar 09, 2018 11:18 am

I used to use this image years ago and remember it being excellent. Recently I've been trying to get this image running and for some reason whenever X starts it is an ungodly mess - it looks like huge slanting diagonal streaks, as if the rendering is trying to rending an image much too large.

Weirdly, the mouse cursor is rendered on top of this and works perfectly. I believe this is because Xorg renders the mouse cursor seperately? Once XBMC starts the mouse cursor disappears (I presume because it starts rendering it with the mali drivers) but the rest of the screen is still rendered in the same broken slanting horizontal fashion. The console works fine an renders normally. I cant get a working vesa or fbdev xorg config to test, but am sure it has to do with the armsoc drivers.

It seems to affect my system with both the 2015 and 2017 disk images.

It's not the system itself, as the console and boot process are fine, as are an android image I tested.

Does anyone else have this issue, and how do I fix it? What also I don't understand is how is this not affecting everyone using the image, as it does this to my system with the default settings?

Thanks for any light you can shed on the issue.

meveric · Post by **meveric** » Sat Mar 10, 2018 7:58 am

poopins wrote:I used to use this image years ago and remember it being excellent. Recently I've been trying to get this image running and for some reason whenever X starts it is an ungodly mess - it looks like huge slanting diagonal streaks, as if the rendering is trying to rending an image much too large.

The U2/U3 officially only supports 720p and 1080p resolution, but thanks to armsoc framebuffer drivers other resolutions are possible as well, but not all will work.
So depending on your TV/Monitor the resolution might not be supported.

poopins wrote:Weirdly, the mouse cursor is rendered on top of this and works perfectly. I believe this is because Xorg renders the mouse cursor seperately?

Yes it does.

poopins wrote:Once XBMC starts the mouse cursor disappears (I presume because it starts rendering it with the mali drivers) but the rest of the screen is still rendered in the same broken slanting horizontal fashion. The console works fine an renders normally.

Console renders in 720p. The U2/U3 comes with boot.scr files either for 720p or 1080p as 720p is more likely to support older TVs/Monitors it's set to 720p.
Console always renders in 720p while Desktop is on a "autodetect" from what your TV reports.

poopins wrote:I cant get a working vesa or fbdev xorg config to test, but am sure it has to do with the armsoc drivers.

vesa and fbdev are not supported, in fact aside from armsoc nothing will work.

poopins wrote:It seems to affect my system with both the 2015 and 2017 disk images.

My guess it's an issue with the TV/Monitor and not the board, so the image, either 2015 or 2017, does not matter as the driver did not change since then.

poopins wrote:Does anyone else have this issue

I can just say that it works fine on my Samsung TV in 1080p. I also used ODROID VU in 1080p mode which also works fine with the image.

poopins wrote:and how do I fix it?

Try to quit XBMC and do a system upgrade the system should use Kodi by now and no longer XBMC if it's all up to date.
Try open a terminal and type xrandr check the output interesting could be infos like "current" which gives you the current desktop resolution but also it might be interesting what other resolutions are reported that are claimed to be supported.
As the console is working, I guess 720p should work fine, so you can try (blindly) writing the following command in a terminal (NOT in the console under CTRL + ALT + F1! - You need to be on the Desktop for this to work):

Code: Select all

xrandr --output HDMI-1 --mode 1280x720

This will switch the desktop resolution to 720p and maybe this is working better for you.
Also if you can try a different TV/Monitor.

poopins wrote:What also I don't understand is how is this not affecting everyone using the image, as it does this to my system with the default settings?

First, the U2/U3 is rarely used anymore, it's no longer produced for several years and people moved on to other systems, so the number of people still using this particular image is getting smaller and smaller.
Still that doesn't mean it's no longer working.. I have a U3 running right now using the same image and as I said, it's working perfectly fine on my side.

poopins · Post by **poopins** » Sun Mar 11, 2018 4:51 am

Excellent, that worked perfectly! It was the tv, it was outputting at some 1366 resolution. I ran it on a different tv which put it at 1080, added the xrandr command to the startup section for mate under the settings directory, and now it seems to be working fine.

Thank you!

Guiseppe · Post by **Guiseppe** » Fri Jul 13, 2018 12:34 pm

I see in your repository that the latest chromium is 52. One of the sites I visit wants 55 or later.
Do you have that somewhere other than in the Chromium directory?

meveric · Post by **meveric** » Fri Jul 13, 2018 1:47 pm

Actually the latest chromium from my repository is chromium 57.

Code: Select all

root@gamestation-turbo:~# apt-cache policy chromium
chromium:
  Installiert:           57.0.2987.98-1~deb8u1
  Installationskandidat: 57.0.2987.98-1~deb8u1
  Versionstabelle:
 *** 57.0.2987.98-1~deb8u1 0
        500 http://oph.mdrjr.net/meveric/ jessie/main armhf Packages
        100 /var/lib/dpkg/status

Guiseppe · Post by **Guiseppe** » Mon Jul 16, 2018 10:10 am

Thank you.

LeeMcNutt · Post by **LeeMcNutt** » Tue Nov 06, 2018 12:22 pm

So I use Recalbox cause I don't like having to use a keyboard and mouse to change settings and what not. I just tried ogst today and already ran into a problem. For some reason I had to go to the desktop to be able to set up my wifi. When I restart the system I have no wifi in Kodi. I have to go back to the desktop to click on the top right to get WiFi back. Also I keep getting a pop up and have to keep putting in the password. What am I doing wrong why don't my wifi stay connected.

meveric · Post by **meveric** » Tue Nov 06, 2018 4:08 pm

LeeMcNutt wrote:So I use Recalbox cause I don't like having to use a keyboard and mouse to change settings and what not. I just tried ogst today and already ran into a problem. For some reason I had to go to the desktop to be able to set up my wifi. When I restart the system I have no wifi in Kodi. I have to go back to the desktop to click on the top right to get WiFi back. Also I keep getting a pop up and have to keep putting in the password. What am I doing wrong why don't my wifi stay connected.

By default Linux uses a password store (keyring) to store passwords and configurations like SSID and such for WiFi in.
This keyring needs to be "unlocked" to use the data inside.
Normally this is done on "login" as you enter your username/password this is enough to verify you are you and the keyring is unlocked.
Since we use autologin for the desktop you are technically not authorized to use what's stored in the keyring. Therefore it asks for the keyring password when you try to connect to the WiFi and does not automatically connect.
Just so you know why this is happening.

What you can do:
Use an unencrypted keyring, means all login information for your WLAN is stored unencrypted in plain text, not recommend but doesn't really hurt either.
For this go to /home/odroid/.gnome2/keyrings/ and remove the keystore and keyring files in here (delete them or rename them whatever).
Restart the ODROID and setup your WiFi again (all settings are gone as we removed the keyring/store).
When you configure your settings for WLAN it will ask you to define a keyring password.
IMPORTANT: DO NOT SET UP A PASSWORD
leave this empty and you have an unencrypted keyring. From now on WiFi will connect automatically as the keyring does not need to be unlocked first.

mikmakmuk · Post by **mikmakmuk** » Sun Nov 25, 2018 10:01 pm

Did someone get kodi-next-odroid (Krypton) get to work with CEC?
I have libcec4, libp8-platform2v4, cec-utils installed and kodi seems to find the driver:

Code: Select all

13:47:27.899 T:3026309120   DEBUG: LoadMappings - loaded node "CEC Adapter"
13:47:27.899 T:3026309120   DEBUG: LoadMappings - loaded node "Pulse-Eight CEC Adapter"
13:47:27.899 T:3026309120   DEBUG: LoadMappings - loaded node "iMON HID device"
13:47:27.899 T:3026309120   DEBUG: LoadMappings - loaded node "WETEK Play remote"
13:47:27.899 T:3026309120   DEBUG: LoadMappings - loaded node ""
13:47:27.900 T:3026309120   DEBUG: CPeripheralBusUSB - initialised udev monitor
13:47:27.900 T:3026309120   DEBUG: SECTION:LoadDLL(libcec.so.4)
13:47:27.901 T:3026309120   DEBUG: Loading: libcec.so.4
13:47:27.927 T:2863653792   DEBUG: Thread PeripBusUSBUdev start, auto delete: false
13:47:27.927 T:2855265184   DEBUG: Thread PeripBusCEC start, auto delete: false

Code: Select all

$ dmesg | grep cec
[    0.205757] s5p_hdmi_cec_set_platdata()
[    2.820754] cec: Probe start
[    2.820757] s5p_cec_probe: pdata=e6cab940
[    2.820776] s5p_cec_mem_probe(): mapped cec_base to f007e000, size 0x1000
[    2.820884] cec: Requesting irq 146 for s5p-cec
[    2.820922] cec: probe successful

Code: Select all

$ uname -a
Linux gamestation-turbo 3.8.13.30 #1 SMP PREEMPT Wed Oct 26 17:53:58 CEST 2016 armv7l GNU/Linux

However:

Code: Select all

libCEC version: 4.0.1, compiled on Linux-3.10.104+ ... , features: P8_USB, DRM, P8_detect, randr
Found devices: NONE

and /dev/CEC exists...

With kodi-odroid (libcec3), CEC works perfectly fine so I can exclude general hardware incompatibilities.

I'm stuck here...

meveric · Post by **meveric** » Sun Nov 25, 2018 10:07 pm

I couldn't get it to work either

But I haven't looked into it in a very long time.

mikmakmuk · Post by **mikmakmuk** » Sun Nov 25, 2018 10:13 pm

Ouch, that's a bummer. Then I know at least it's not a solved problem...

meveric · Post by **meveric** » Sun Nov 25, 2018 10:16 pm

maybe I can find a way to rebuild CEC4 for Debian Jessie in a way it works.
Let's see what I can find out.

Edit:
Just found that by default Exynos Support is disabled, I'm rebuilding it with activated support and will do a small test, if it works I'll upload the new version of libcec4

mikmakmuk · Post by **mikmakmuk** » Sun Nov 25, 2018 11:00 pm

Great! Let me know if I can help with testing...

meveric · Post by **meveric** » Sun Nov 25, 2018 11:03 pm

mikmakmuk wrote:Great! Let me know if I can help with testing...

well good news and bad news... I got CEC4 working, BUT this results into a broken version of Kodi, as both use different versions of libp8-platform.

Which means, in order to get both working, I probably have to completely rebuild Kodi as well.

mikmakmuk · Post by **mikmakmuk** » Sun Nov 25, 2018 11:31 pm

Hm...

Code: Select all

ldd /usr/bin/cec-client | grep p8
        libp8-platform.so.2 => /usr/lib/arm-linux-gnueabihf/libp8-platform.so.2 (0xb6e79000)

Code: Select all

ldd /usr/local/lib/kodi/kodi.bin | grep p8

Kodi seems to be not linked at all to libp8...

meveric · Post by **meveric** » Sun Nov 25, 2018 11:38 pm

nah that's some other things.. cec is loaded as a module.. but I think I figured it out now.
I could compile CEC with the same libp8-platform kodi was compiled against and it seems to work fine.

mikmakmuk · Post by **mikmakmuk** » Sun Nov 25, 2018 11:42 pm

Nice! If you want I can test the new packages out here before you push them to the repo...

meveric · Post by **meveric** » Sun Nov 25, 2018 11:48 pm

I've uploaded them right now, since the old packages didn't work anyway, there shouldn't be any harm in it.
Please let me know if the new packages work for you or not.

mikmakmuk · Post by **mikmakmuk** » Mon Nov 26, 2018 12:02 am

Works like a charm, thanks!

meveric · Post by **meveric** » Mon Nov 26, 2018 12:06 am

glad it's working

mikmakmuk · Post by **mikmakmuk** » Sun Jan 13, 2019 1:21 am

Using kodi 17.6, I see horizontal tearing, consistently in the lower frame of the picture, in scenes with horizontal panning. I had no tearing whatsoever with kodi 16. Does someone observe the same and/or found a solution to that?

meveric · Post by **meveric** » Sun Jan 13, 2019 7:04 am

I haven't tried Kodi 17.6 on the U3 yet, so I'm not sure if this is a general issue.
Sadly I personally find Kodi got worse with each new version.
I loved XBMC 13.2 it was stable, did what it was suppose to do and everything was working perfectly fine.
After that Kodi got worse and more unstable little by little.

Anyway.. I'm not sure if it will help you but you could try pinning refresh rates of videos to 60 Hz.
There's an option for that in Setup ODROID GameStationTurbo.. it helped reducing tearing on the XU4 which suffers from terrible tearing issues.

mikmakmuk · Post by **mikmakmuk** » Sun Jan 13, 2019 9:18 am

I see. I'll try to play around with the refresh rates. I noticed that there is less tearing in videos that play at 24hz. I have set the refresh rate in Mate to "auto", so some videos play at 24, others at 60hz or even 50hz (according to my TV). In the ogst settings, I've unpinned the refresh rate as that seemed to worsen the tearing.

primustimus · Post by **primustimus** » Sun Feb 17, 2019 4:27 am

Hi meveric, first I want to say a huge thanks for all your work on making this project for the U3. I started out a number of years ago trying to build an arcade suitcase using a C1, and you were very helpful at that time. Since then I upgraded to the U3 and using your OGST, after a bunch of configuring for my keyboard encoder for my joysticks, and switching from pulse audio to get the audio working out the headphone jack instead of hdmi, it's been really stable and working great. Still using the wheezy image.
Now, however, there's a couple things I'm wanting to add/fix, and hoping you'd be able to steer me in the right direction.
I've designed, 3D printed, and built a spinner for the arcade, using a Leonardo Arduino, so it's recognized as a mouse when plugged in, moving the mouse on the X axis. Once I add a 2nd spinner for 2nd player, it will move it on the Y axis. I'm wanting to use these for games like Tempest and Warlords, however, I'm having issues getting mamelibretro to recognize it as input. I've tried setting the player1_mouse_index="0" or "1" in the retroarch.cfg or mamelibretro.cfg with no effect.
When I open the MAME config screen while in game and try changing the analog controls, I'll hit enter to change the dial input, and then turn the spinner, but nothing. Looking into it more, I read a wiki here that talks about mame-lr2003 got support for spinners and mouse-like hardware in 2016. I assumed from that that if I could just upgrade libretro to a newer version, it would support it. I've since cloned the git repository in, but not sure where to put the .so file or where to tell RCB to use that newer emulator than the one configured in your image.
Would really appreciate any suggestions or help you can offer.

The other issue I'm having is that when running older mame arcade games, like Gauntlet or Star Wars upright, ones that have voice sound effects, the sound is choppy, and almost like slow motion, and seems as if the whole emulation has slowed. I suspect this may be because I switched out of pulseaudio to get the audio to go through the headphone jack.
I tried flashing your new Jessie image on a different card to see if that would solve some of the issues, however, I've found that consistently my U3 will suddenly crash, go black screen, and I have to cut power and power it on again to try again. I've tried looking through the logs to try to troubleshoot this, however, I've not even sure I'm looking at the right log files, and wondering if my U3 is just overheating. I'm starting to seriously consider upgrading to an XU3 or XU4 after looking at the image you made for that, and reading of the claims of its performance being so much better, but if possible, I'd love to get this working with my U3, as so far everything else has been working flawlessly.

PS - if you're curious about my suitcase arcade build, let me know and I'll post pics.

Thanks in advance

meveric · Post by **meveric** » Sun Feb 17, 2019 8:12 pm

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
Looking into it more, I read a wiki here that talks about mame-lr2003 got support for spinners and mouse-like hardware in 2016. I assumed from that that if I could just upgrade libretro to a newer version, it would support it.

Since you're still using the Wheezy image, I also assume that your libretro core is simply to old to handle the input command. And ever since, there is no longer a "single Mame" core, the notion of "mame-lr2003" means that it's the libretro-mame2003 core that they are talking about, which is different from the mame-libretro core. There are now around 5 or 6 different cores, 2000,2003,2003-plus,2005,2010,2014,2016 and current mame plus a couple in between like mame-2003-midway.. mame-2003 or mame-2003-plus are probably the best candidates to look out for, as other cores are probably much different from what you're using right now.

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
I've since cloned the git repository in, but not sure where to put the .so file or where to tell RCB to use that newer emulator than the one configured in your image.
Would really appreciate any suggestions or help you can offer.

Check under /usr/local/share/retroarch/cores/ there you should find a folder called "good" I believe and in there are the cores used on the image.. you probably find a mame_libretro.so file here which needs to be replaced with the one you build.
Make sure you use the 2003 or 2003-plus one, as I believe you won't have much fun with the "mame_libretro.so" form upstream.
If you rename the file you build to the same name that you find in the folder mentioned above and copy it in that folder it should already work as it will just assume it's the same file.

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
The other issue I'm having is that when running older mame arcade games, like Gauntlet or Star Wars upright, ones that have voice sound effects, the sound is choppy, and almost like slow motion, and seems as if the whole emulation has slowed. I suspect this may be because I switched out of pulseaudio to get the audio to go through the headphone jack.

That is correct, it would have been better to keep puleaudio and set the default output to the headphone. This can be done with a tool called "pavucontrol" which allows you to configure pulseaudio.
Here you can select the audio device you want to use for output and could have selected the headphone jack (I do the same with my XU3).
Per default I configured retroarch to use OpenAL + Pulseaudio as OpenAL softens issues with sound, instead of choppy audio the game simply runs slightly slower but you don't experience the issues you encounter now.

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
I tried flashing your new Jessie image on a different card to see if that would solve some of the issues, however, I've found that consistently my U3 will suddenly crash, go black screen, and I have to cut power and power it on again to try again.

The U3 image is currently in a strange state, as it requires manual steps to update it to the latest version. I haven't had time to update the image yet to give a new out of the box experience.
Still I use the Jessie U3 image on my U3 and it's very very very stable.. the system is running for months without issues (no other board is that stable in my opinion).
Also with the Jessie image you get MUCH NEWER software and many more emulators. In fact I would suggest using FBA (Final Burn Alpha) instead of directly MAME, as FBA is more stable in my opinion.

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
I've tried looking through the logs to try to troubleshoot this, however, I've not even sure I'm looking at the right log files, and wondering if my U3 is just overheating. I'm starting to seriously consider upgrading to an XU3 or XU4 after looking at the image you made for that, and reading of the claims of its performance being so much better

The XU3/XU4 has much better performance, about 2-3 times as fast as the U3 which comes in handy if you want to play Dreamcast or PSP games, it's also the only board currently capable to work good with 3DO, Sega Saturn, N64, and other hard to emulate systems.

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
but if possible, I'd love to get this working with my U3, as so far everything else has been working flawlessly.

For the Wheezy image follow the steps above.. For Debian Jessie we probably have to check what you've done so far.. As I said, there are a lot of manual steps involved at the moment fixing repositories and installing updates and such.

primustimus wrote: ↑
Sun Feb 17, 2019 4:27 am
PS - if you're curious about my suitcase arcade build, let me know and I'll post pics.

You should make an article for the ODROID Magazine out of it. It might sponsor you a XU4 as a reward

primustimus · Post by **primustimus** » Sat Apr 13, 2019 2:06 pm

Hi meveric,

Sorry it's taken me long time to try some of those steps before responding. I've been struggling with getting the Jessie image to work, with little success unfortunately. Currently, the system boots, it auto-loads kodi, and instantly goes to black screen, and u3 appears to be off, with just the red power led lit. Pushing and holding the reset button resets the odroid and it attempts again, but no joy.
I've once or twice been able to quit kodi right away without it crashing, and interact with the terminal, but it's very inconsistent, and it takes a long time to boot in between. When I was able to get terminal open, I attempted to run apt-get update && apt-get upgrade, however, I think the source links are not updated, as I've read in a different forum that you updated your packages to work better from https, and all the links on update are showing connections to http.

I wish there was a way I could prevent kodi from auto-starting and crashing, so I could try and finish updating everything properly, but haven't found any sort of quick key or anything that prevents it from booting.
I think at this point, unless you have some other suggestions, I may go back to the Wheezy image I still have on a different sd card and works quite well.

meveric · Post by **meveric** » Sat Apr 13, 2019 4:35 pm

primustimus wrote: ↑
Sat Apr 13, 2019 2:06 pm
Hi meveric,

Sorry it's taken me long time to try some of those steps before responding. I've been struggling with getting the Jessie image to work, with little success unfortunately. Currently, the system boots, it auto-loads kodi, and instantly goes to black screen, and u3 appears to be off, with just the red power led lit.

This sounds like a failing power supply.

primustimus wrote: ↑
Sat Apr 13, 2019 2:06 pm
I attempted to run apt-get update && apt-get upgrade, however, I think the source links are not updated, as I've read in a different forum that you updated your packages to work better from https, and all the links on update are showing connections to http.

Ah yes.. the U3... It's been a while. Maybe I can create a new image with fixed sources, since it's been a while and by now there where a lot of changes regarding the URLs.

primustimus wrote: ↑
Sat Apr 13, 2019 2:06 pm
I wish there was a way I could prevent kodi from auto-starting and crashing

You will find kodi in /home/odroid/.config/autostart/
remove it from there and it will no longer autostart.

primustimus wrote: ↑
Sat Apr 13, 2019 2:06 pm
I think at this point, unless you have some other suggestions, I may go back to the Wheezy image I still have on a different sd card and works quite well.

I hope I will find the time to fix this image.
As the Jessie image has a lot more features than the Wheezy one.. I'll put it on my todo

primustimus · Post by **primustimus** » Sat Apr 13, 2019 11:37 pm

As usual, I'm so impressed and appreciate your quick response.
That would be amazing if you're able to find the time to update the U3 packages!

But also understand that you probably have many other more pressing priorities, as do I, often.

Thanks for the the suggestion about a failing power supply. Didn't think of that. I'll try swapping it out and let you know if that makes a difference.

Cheers!

srdz · Post by **srdz** » Fri Jun 07, 2019 4:50 pm

incredible rom

very good for my refreshed u3. after installation, a message about a small amount of space pops up, but it does not pop up anymore. Is it normal ? should I use some tools to increase the partition?

should I update this system or not make more sense?

meveric · Post by **meveric** » Sat Jun 08, 2019 3:11 am

srdz wrote: ↑
Fri Jun 07, 2019 4:50 pm
incredible rom very good for my refreshed u3. after installation, a message about a small amount of space pops up, but it does not pop up anymore. Is it normal ? should I use some tools to increase the partition?

It does that on it's own on the first boot. The partition for flashing on SD/eMMC is held as small as possible so it can be flashed quicker, but is then enlarged on the first boot/reboot.

srdz wrote: ↑
Fri Jun 07, 2019 4:50 pm
should I update this system or not make more sense?

It still makes sense, problem is, that it's currently not "easy" and involves a lot of manual steps (at least the first time to get this working again).

AlexH · Post by **AlexH** » Fri Jun 21, 2019 11:46 am

Thank you for this! Runs Smoking Fast on my XU4.

Sent from my SM-G892A using Tapatalk

Guiseppe · Post by **Guiseppe** » Thu Nov 07, 2019 1:53 pm

I cannot find any mention of Kodi 18.x on the U3 in this thread or the [HOWTO] Debian/Ubuntu repository for Games/Emulators/Kernel thread.

Is it available?

EDIT: I am using Debian Jessie.

meveric · Post by **meveric** » Thu Nov 07, 2019 3:57 pm

no for Debian Jessie Kodi 18 is not available.
Even 17 is very hard to get to work as some of the dependencies do not exist on Debian Jessie.
Also, officially Kodi 18 does no longer support X11, so with that it wouldn't work on the U3 at all.
But luckily @Steevee28 made a version that is able to run on X11 again.
Still, not for Debian Jessie.

cotonec · Post by **cotonec** » Tue Aug 11, 2020 10:56 am

Hello. I have been trying to get the 7601 wifi module to work for a very long time? VID_148F & PID_7601. How can use it?

meveric · Post by **meveric** » Tue Aug 11, 2020 2:14 pm

there should be a DKMS module for this available search for 7601 as a package name and try to install it.
Let me know if you encounter any issue.

cotonec · Post by **cotonec** » Tue Aug 11, 2020 7:29 pm

meveric wrote: ↑
Tue Aug 11, 2020 2:14 pm
there should be a DKMS module for this available search for 7601 as a package name and try to install it.
Let me know if you encounter any issue.

And what needs to be done for this?

Code: Select all

Dkms install mt7601

?
Sorry, I'm just getting started with Linux.

meveric · Post by **meveric** » Wed Aug 12, 2020 1:01 am

it should work if you do:

Code: Select all

sudo apt-get install mt7601-sta-dkms

from a terminal
You probably have to reboot the system after that and I'm not entirely sure if you need to install some firmware files as well.

Try to reboot and see if WLAN is working after that.

If the WLAN is still not shown try to check the output of:

Code: Select all

dmesg | grep firmware

Check if it complains about any missing firmware.. if that's the case let me know.

cotonec · Post by **cotonec** » Wed Aug 12, 2020 3:51 am

meveric wrote: ↑
Wed Aug 12, 2020 1:01 am
it should work if you do:
Code: Select all
sudo apt-get install mt7601-sta-dkms
from a terminal
You probably have to reboot the system after that and I'm not entirely sure if you need to install some firmware files as well.

Try to reboot and see if WLAN is working after that.

If the WLAN is still not shown try to check the output of:
Code: Select all
dmesg | grep firmware
Check if it complains about any missing firmware.. if that's the case let me know.

After installing
( sudo apt-get install mt7601-sta-dkms)
rebooted. But it didn't work. To answer (dmesg | grep firmware) got

Code: Select all

 [0.000000] Running under secure firmware [/ code]

meveric · Post by **meveric** » Thu Aug 13, 2020 2:53 pm

I will check if your particular device (VID_148F & PID_7601) is part of the driver or if the driver needs to be updated.

--> checked apparently it's part of it:

Code: Select all

        {USB_DEVICE(0x148f,0x7601)}, /* MT 6370 */

Edit:
So here are a couple things to check and that I found:
1. after installation of the DKMS module and the reboot is any device listed if you check ip a? It should show either wlan0 or ra0 or something similar
2. There is a file: /etc/Wireless/RT2870STA/RT2870STA.dat where you have to configure the device with your location specific settings.. there are different country codes that it knows which bandwidth to chose and things like that.
3. Can you check with lsmod if mt7601Usta is loaded? If not try modprobe mt7601Usta and check again with ip a if a wlan network adapter is listed or not.
4. also just in case please make sure the following package is installed: apt-get install firmware-misc-nonfree

If nothing works, let me know and I see if I can find a different driver for you