Forum Replies Created
-
Posts
-
Of course 0xF0000000 is not exactly 4GB. However, iMX6 is a 32bit machine and some address space is required for the SoC’s control registers. Therefore the area above 0xF0000000 is not reported as valid memory. It’s actually present, but cannot be used.
But anyway, the output tells us that u-boot is detecting the memory size correctly. Now the question is why the kernel would not report it. I suspect CONFIG_VMSPLIT_2G…
-
I’ve uploaded an omxplayer to the location mentioned above. Our pgrep tool (busybox) does not support some options that are used by this player’s startup script, but a quick test shows that it at least can play a file…
-
Please try the *.opk file found here.
Since these packages are pre-built, the solution mentioned in the blog must be applied on our side.P.S.: You are the first person reporting to use Geexbox on a RaspberryPi3. I wonder, if there are more ?
-
No, I was thinking about a kernel compile-time configuration. BTW, can you attach a micro USB cable to the console port of your box, open a terminal and abort the boot process by pressing a key during the 3 second countdown. This should get you to an u-boot prompt. Then type:
bdinfo
and post the output here.
-
Well, I enabled SOAP support in PHP and phpinfo now says something about SOAP, which it did not do before. However, googling a bit more reveals that your “php_soap” is probably a 3rd-party package that is not part of PHP itself. So it would have to go into a separate *.opk as well. I don’t have time to look into that before middle of next week…
-
You reported that before, but unfortunately I don’t have a 4×4 to test. I know that the memory size detection in u-boot is somewhat flaky. Jon N. changed something a while ago but I heard bad things (i.e. some non-booting units) about this change. So I did not include it. However, I’m also not 100% sure if our kernel config has something to do with this. There is one parameter that looks suspicious… Maybe next week I can build a kernel with that param changed, so that we can rule that out.
-
Try the PHP package found here.
-
BTW, recent versions of make-sdcard allow to specify the URL of a *.tar.xz directly. So if you know your internet connection is good and you have curl installed on your system you can do something like:
sudo ./make-sdcard /dev/sdX http://download.geexbox.org/snapshots/geexbox-kodi-imx6-cuboxi/latest/binaries.cuboxi/geexbox-devel-20160927-r209a22e.cuboxi.tar.xz -
Geexbox is a stripped-down Linux that is supposed to automatically boot up and run a single application (usually Kodi MediaCenter). It is not supposed to be used as a regular desktop OS (even though it might be possible to configure our build system to spit out a desktop environment).
-
What do mean with “I extracted files in newly formatted Ext4”? There are two ways of preparing an SD card for our ARM platforms:
1.) Download the *.tar.xz file (the root fs tarball) and make-sdcard (the setup script). The script will partition your card, copy the files and – depending on the platform – write boot record(s) that may reside outside the regular file area.
2.) Download the *.img.xz file (the root fs image), extract it (xz or 7zip) an use either dd (on Linux) or Win32DiskImager (on Windows) to dump it to the card.
None of the described methods requires the card to be formatted with any particular file system or even to be partitioned before. Note that in the second case, the root file system will automatically resize itself when booted for the first time. This step is not neccessary in the first case.
-
Could it be that your tar is too old to handle xz-compressed archives (option -xJ) or that you used an old version of our make-sdcard script? What exactly was the command line?
-
Well, I contacted the guy who did the last commits to Kodi master. It turned out that this stuff is pretty much broken :(. However, he gave me a link to an improved version on his GitHub. I’m still not quite happy with that code, but at least it is usable… Currently I’m in the process of analysing the stuff and trying to get a better understanding of how this all works. Maybe I’ll start some more overhaul. Our recent Geexbox already contains a few fixes and cleanups.
As for the “Delay after change of refresh rateâ€, I was told that this will have some subtle side effects. So a value other than 0 is discouraged. Fortunately, the current code does not expose the initial problem anymore. So it is not necessary either.
As for DVD playback: I only tested two (unencrypted) ISO images. These worked for me. Besides that the disc menu of “Matrix” was a bit choppy. At the moment I cannot test a real DVD, because my “el cheapo” USB-DVD drive draws some much current out of the USB port, that it will only work on the USB3 of my desktop PC. I’m really wondering how a company can manufacture/sell a device with power requirements that are way beyond every standard! And they even print it on the label! -
With the recent update I did the transition from eglibc to glibc. So it’s probably better to do a full fresh install (/root/.kodi can be copied over to retain the settings).
-
O.K.: I’ve created a fix for the hang-during-exit-problem. Should work now. “No-sound-via-HDMI” can be avoided by setting “Delay after change of refresh rate” to a nonzero value (System settings/Video, Mode: Advanced or Expert). There still seem to be some issues. Investigating…
-
4) For me Yahoo also is the only one that works. At least on Jarvis and Krypton (Gotham is another story…). In earlier days XBMC was using “The Weather Underground” by default. However, it seems that the site got too many traffic from non-paying users. So in order to use that service, you have to sign up on their web site and get an API key, which you have to enter in the addon settings. I don’t know if you have to pay for that or not. Also I’m not sure if other weather providers use the same approach.
For all the other points: I also did not try any of them. At the moment I’m struggling with Krypton…
