I did try following the build instructions from here btw if anyone wants to know how I tried to do this. Failed to initialize glamor at ScreenInit time. Hi there, is there a chance to have hardware acceleration for the armbian images for stretch? After I startup and configure the user X doesn’t come up , see the attached Xorg. Device pages are made when there’s a bunch of useful information for a particular device, and someone takes the time to make that page. Kodi can also be installed onto a CuBox-i that is running Android using the normal Android instructions. Check power supply, check SD card and check other people experiences Read more
|Date Added:||22 March 2011|
|File Size:||66.3 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
To enable the XF86 driver you have to add the following to the XF86 config: It’s a small arm based device which looks like a small black cube; it uses a micro SD card to boot from. So for now it is back to the bottom of the drawer for the cubox. In theroy they should work, though I have no vido on how X and the kernel and its drivers “hang together”.
Also chromium reports support for hardware acceleration now. After install I had to do the dd commands a second time in order to make the newly debian install bootable on another machine ; Code: Snag is though the X server seems to be using the framebuffer.
That’s pretty much what I did as well. I tried glmark2-drm on the console using the framebuffer directly it was smooth gave me a score dubox Here’s how I managed to get the cubox i4pro to boot debian; note: Mine’s been sat in a cardboard box full of other stuff for months, then before that sitting gathering dust in a drawer.
I tossed my Cubox-i in a drawer long ago, it’s not ready for prime-time and was a waste of money for me. By AnArmbianUserNovember 21, OK, so I build Armbian 5.
CuBox-i4Pro and X11 GPU support – NXP (Freescale) – Armbian forum
Sign in Already have an account? Devices Freescale Android Linux SolidRun CuBox-i These pages are maintained by the community and should not be considered an endorsement or recommendation.
But unfortunately X is not accelerated and performance is very poor.
Only Debian Stretch desktop is currently available to build for vjdeo based boards. After I startup and configure the user X doesn’t come upsee the attached Xorg.
From Official Kodi Wiki. Firstly, cuboxx links; http: Please note that the chromium ubuntu armhf build by default uses the setting “enable-low-end-device-mode” which shows webpages and especially pictures in a distored way. Active threads Mark site read. The front is not shown on the image.
First of all – some background.
SolidRun CuBox-i – Official Kodi Wiki
I did try following the build instructions from here btw if anyone wants to know videk I tried to do this. Well thanks to Astralix at least Vidwo could start X now. Can you just “get away” with compiling the driver or do you need to compile an entirely new kernel along with the driver or even with mesa for 3d? It is so easy to get all the needed licenses for legal use of the CoDecs but it is so hard to get the licensed code from the company who manufactures the iMX SOC Unfortunately, you hit another known Ubuntu Xenial bug.
Sign up for a new account in our community. Section “Device” Identifier “Driver0” Screen 0 Driver “armada” EndSection With this I was able to get glmark2 and glxgears to show up and apparently both are running vidoe hardware acceleration.
Viceo did try to compile the driver once but did not get very far. I build the debian stretch default desktop version, but there is no xserver-xorg-video-imx-viv and thus the desktop feels really laggy.
Kodi can also be installed onto a CuBox-i that is running Android using the normal Android instructions. Images and video may be under a different copyright.