[OS] Debian Stretch

meveric · Post by **meveric** » Sun Jun 25, 2017 5:03 am

I've started working on a Debian Stretch minimal Image for the ODROID C2.
I'm not very satisfied with the arm64 support under Debian Jessie so I'll try and see if Debian Stretch will work out better.

It's a headless server image only with user root. But it has all my repositories included, which allows for easy installation and updates of packages such as Kernel and Headers and other packages.

The image has my usual setup: means on first boot it's resizing the rootfs partition and configures SSH. It will automatically reboot after the initial setup after which this image is ready to use.
Kernel and headers are already installed if you need to build your own drivers.
A few basic tools such as htop, mc, vim and bash-completion are already installed for your convenience.

Download: https://oph.mdrjr.net/meveric/images/St ... -C2.img.xz md5 sha512 sig

Size compressed: 96MB
Size uncompressed: 561 MB

Default Login: root
Default Password: odroid

It's ready to be used as a server image.

First things first:
Since there's constantly new development for this image and ODROIDs in general the First thing you should do after the image is up and running is to install all updates:

Code: Select all

apt-get update && apt-get upgrade && apt-get dist-upgrade

How to convert the image into a Desktop image:
The image can easily converted into a full Desktop image looking similar to this:

I created a setup tool that's already preinstalled:

Code: Select all

setup-odroid

Which should easily allow you to install a Desktop Environment.

Please Note:
Make sure you have the latest version of setup-odroid installed, or else installation of Desktop will fail due to a bug in Debian Stretch.

Currently Kodi is not working, as it fails to create a Window. It's currently unknown what is causing this issue and how to solve it.

Hints:
Changing language:
If you install a Desktop environment you should already have keybord-configuration installed, it will ask upon the first installation what keyboard layout it should use.
This configuration is for your X11 Desktop so you have your desired keyboard layout.
For console you need to install console-setup to do the same, so just in case:

Code: Select all

apt-get install console-setup keyboard-configuration
dpkg-reconfigure keyboard-configuration

should be all that is needed to change your keyboard layout.
You probably want to set timezone as well

Code: Select all

dpkg-reconfigure tzdata

Installing Chromium Webbrowser (with hardware acceleration):
Chromium is part of the Default Debian Stretch repository and can be installed with:

Code: Select all

apt-get install chromium

You will need to configure 3D acceleration for yourself.
Therefore you need to create a config file under /etc/chromium.d/ and add the following line:

Code: Select all

CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl=egl --ignore-gpu-blacklist --disable-accelerated-2d-canvas --num-raster-threads=4 --audio-buffer-size=4096"

Chromium might still complain about missing GLESv2 drivers if so you can solve this by creating the following links:

Code: Select all

ln -sf /usr/lib/aarch64-linux-gnu/libGLESv2.so /usr/lib/chromium/libGLESv2.so
ln -sf /usr/lib/aarch64-linux-gnu/libEGL.so /usr/lib/chromium/libEGL.so

DVB support:
I've package a lot of Kernel modules that allow you to use DVB devices such as USB-DVB sticks, you can install them with:

Code: Select all

apt-get install media-tree-odroid

===============================================================

Please don't ask about Debian Stretch support for other boards, it will come "eventually". I can't do all at once.

Fourdee · Post by **Fourdee** » Mon Jun 26, 2017 3:02 am

Legend!

Many thanks for sharing this.

PHP 7.0 will make a vast performance improvement for NextCloud/OwnCloud etc.

mlenhart · Post by **mlenhart** » Mon Jul 10, 2017 1:04 am

Hello, any idea (at least very rough estimation) when the final build can be available?

meveric · Post by **meveric** » Mon Jul 10, 2017 1:26 am

good question... basically everything except Kodi seems to work fine.
I can probably release it and just disable an option for Kodi at the moment.

adelias · Post by **adelias** » Mon Jul 10, 2017 1:51 am

This build has been stable for me with the exception of lirc which I have not yet managed to get working.

meveric · Post by **meveric** » Mon Jul 10, 2017 4:40 am

adelias wrote:This build has been stable for me with the exception of lirc which I have not yet managed to get working.

Just tried lirc from setup-odroid, everything is working fine (tried it with the ODROID remote).

adelias · Post by **adelias** » Mon Jul 10, 2017 5:47 am

After installing lirc from setup-odroid it now works fine. Thanks.

danielfmo · Post by **danielfmo** » Wed Jul 12, 2017 2:10 am

Hi,

Sorry for the dumb question, I'm not very experienced with this.
but is it supposed to have Kernel debug output in the console? How can I turn them off?

Cheers

meveric · Post by **meveric** » Wed Jul 12, 2017 3:17 am

by editing the boot.ini there's a section:

Code: Select all

# Default Console Device Setting
setenv condev "consoleblank=0 console=ttyS0,115200n8 console=tty0"   # on both

here you can define where it should put the debug messages. If you remove console=tty0 it should go away.

endecotp · Post by **endecotp** » Sat Jul 15, 2017 7:18 am

meveric wrote:I've started working on a Debian Stretch minimal Image for the ODROID C2.

Great, this will be more useful to people than Jessie.

FYI I've been running Stretch on my C2s for a long time, and everything that I use runs fine.

TheBigG · Post by **TheBigG** » Sun Jul 16, 2017 4:40 am

will there be a version with mainline kernel? That would be awesome.

meveric · Post by **meveric** » Sun Jul 16, 2017 4:44 am

As long as there is no support from HardKernel for mainline Kernel I won't support it either.
Newest Kernel doesn't mean it's always running better, in most cases it means it runs worse than with the older Kernels and causes more problem than it solves (like missing or partly broken GPU/VPU support, as it can be seen on XU4 4.9 LTS Kernel).

TheBigG · Post by **TheBigG** » Mon Jul 17, 2017 1:11 am

Does this kernel get patches backported? Like against dirty COW and so on?

meveric · Post by **meveric** » Mon Jul 17, 2017 5:56 am

I always try to patch high security issues, even all the way back with the old 3.8 Kernels for Exynos 4 boards.
But I won't be able to include ALL security fixes. Dirty COW was already included in 3.14 and other security issues patches well.
You can find some tests for them here: https://oph.mdrjr.net/meveric/other/security/
Where you can find exploits to test if your Kernel is affected from these issues or not.

gb.yolo · Post by **gb.yolo** » Thu Jul 27, 2017 9:37 pm

Great work, I will test it. Is it possible to upgrade from jessie just as a "normal" debian upgrade on x86/64 systems? I mean, if I change both debian repository and your repository from jessie to stretch, will the upgrade work?
My situation is the following:

/etc/apt/sources.list:

Code: Select all

deb http://ftp.debian.org/debian jessie main contrib non-free
deb http://ftp.debian.org/debian jessie-updates main contrib non-free
deb http://security.debian.org jessie/updates main contrib non-free
deb http://ftp.debian.org/debian jessie-backports main contrib non-free
deb http://ftp.debian.org/debian jessie-proposed-updates contrib non-free main

deb-src http://ftp.debian.org/debian jessie main contrib non-free
deb-src http://ftp.debian.org/debian jessie-updates main contrib non-free
deb-src http://security.debian.org jessie/updates main contrib non-free
deb-src http://ftp.debian.org/debian jessie-backports main contrib non-free
deb-src http://ftp.debian.org/debian jessie-proposed-updates contrib non-free main

in /etc/apt/sources.list.d I have:

meveric-all-C2.list

Code: Select all

deb [arch=arm64] http://oph.mdrjr.net/meveric all c2

meveric-all-main.list

Code: Select all

deb http://oph.mdrjr.net/meveric all main

meveric-all-testing.list

Code: Select all

deb http://oph.mdrjr.net/meveric all testing

meveric-jessie-backports.list

Code: Select all

deb http://oph.mdrjr.net/meveric jessie backports

neveric-jessie-main.list

Code: Select all

deb http://oph.mdrjr.net/meveric jessie main

I suppose I would edit /etc/apt/sources.list, /etc/apt/sources.list.d/meveric-jessie-backports.list and /etc/apt/sources.list.d/meveric-jessie-main.list.

Thank you for your support.

meveric · Post by **meveric** » Thu Jul 27, 2017 9:42 pm

It should work if you change the repositories from Jessie to Stretch, although not all packages you have installed may already exist under Debian Stretch (I just started porting all software to it).

hami · Post by **hami** » Wed Aug 16, 2017 4:46 pm

Dear Meveric,
I've came to test your image. I tried to install media-tree-odroid but stacked on unmet dependencies,
media-tree-odroid : Depends: linux-image-3.14.79+ (= 3.14.79-20170408-C2) but 3.14.79-20170722-C2 is to be installed
Does it mean that for each kernel version this package should be rebuild too?
Cheers,
Petr

meveric · Post by **meveric** » Wed Aug 16, 2017 9:20 pm

Yes it does... still I wonder why there should be a missmatch of Kernel and media-tree, since I always compile them together.
I just checked on it and found the package was uploaded to the wrong repostitory.. I'm gonna fix that in a couple of minutes.

hami · Post by **hami** » Thu Aug 17, 2017 2:25 am

meveric wrote:Yes it does... still I wonder why there should be a missmatch of Kernel and media-tree, since I always compile them together.
I just checked on it and found the package was uploaded to the wrong repostitory.. I'm gonna fix that in a couple of minutes.

Ok, now it is install-able. Thank you.

Braulio · Post by **Braulio** » Sun Aug 20, 2017 2:37 pm

Hello , when I try to install Mate desktop on this image the installation stucks at 81% when apt configures the dbus.

I check with Htop on another tty and the status of all the proceses are "S".

I try 5 times , after launch "apt update && apt upgrade && apt dist-upgrade " I reboot ,like the alert message sugest.

I dont know what to do.

meveric · Post by **meveric** » Sun Aug 20, 2017 4:58 pm

That's new.. I'll check on it later. Wonder if they changed something on the repositories.

Braulio · Post by **Braulio** » Wed Aug 23, 2017 5:03 am

Nothing new about the problem?

brad · Post by **brad** » Wed Sep 06, 2017 5:01 pm

Thanks meveric this is working great (im using it headless)

Now using it as a base for realtime MachineKit testing for odroid c2 support.

I wrote up a quick basic README on how I compiled and installed (hacked in) a development version of Realtime Kernel v4.11.12-rt11 for my current project of running machinekit realtime. Please note this kernel is not supported by hardkernel or meveric and should only be used for testing/ development of realtime projects. http://www.builtonline.net/c2rt-v4.11.12-rt11/README

johndowe · Post by **johndowe** » Thu Sep 07, 2017 1:57 am

Super slick headless so far.. getting ready to tryout some desktop action.

I saw earlier that you said kodi did not work, has that changed since?

Thanks again for all your awesome work

meveric · Post by **meveric** » Thu Sep 07, 2017 2:00 am

Sadly no.. I tried again Kodi 17.4 yesterday, but still no luck.. the packages looks fine and I doubt it's an issue with Kodi itself.

Still whenever I try to start it, it's unable to find the display and GPU drivers, although many other 3D applications have no issues with this.

I still suspect it's the new Xorg Sever 1.19 that is causing this issue, but I haven't found a way around it yet.

johndowe · Post by **johndowe** » Thu Sep 07, 2017 2:31 am

Ah thats a shame.

Is there anything us lowly noncoders can do to help you troubleshoot?

meveric · Post by **meveric** » Thu Sep 07, 2017 2:57 am

On the C2, I highly doubt it. Unless you are a Linux and ODROID Guru and can downgrade the entire XOrg Server without breaking the rest of the system to try my theory I doubt it.

johndowe · Post by **johndowe** » Thu Sep 07, 2017 4:13 am

Yeaaah a little out of my pay grade. I will patiently rock your jessie image.

meveric · Post by **meveric** » Thu Sep 07, 2017 7:31 am

I checked myself a little bit ago and with some experimenting I could downgrade xorg to the version of Debian Jessie, but the result was the same.. I try a couple other things..

I still get:

Code: Select all

21:27:58.598 T:548364713984   ERROR: Failed to find matching visual
21:27:58.598 T:548364713984  NOTICE: GL_VENDOR = NULL
21:27:58.598 T:548364713984  NOTICE: GL_RENDERER = NULL
21:27:58.598 T:548364713984  NOTICE: GL_VERSION = NULL
21:27:58.598 T:548364713984  NOTICE: GL_SHADING_LANGUAGE_VERSION = NULL
21:27:58.598 T:548364713984  NOTICE: GL_EXTENSIONS = NULL

as an error and I don't know yet how to solve this, but I'll keep trying.

pld · Post by **pld** » Mon Sep 11, 2017 3:30 am

Could you please provide me an xorg.conf?
I'm mostly interested what is the appropriate GPU driver in case of stretch.

PS. Thanks for your grate work!

meveric · Post by **meveric** » Mon Sep 11, 2017 3:58 am

do an apt-get install setup-odroid it should help you figure it out.. it also has some xorg.conf files.

Besides, that xorg.conf does not change.. it's the same for Debian Jessie and Debian Stretch, even for Ubuntu.. it's all the same.

pld · Post by **pld** » Mon Sep 11, 2017 4:16 am

meveric wrote:Besides, that xorg.conf does not change.. it's the same for Debian Jessie and Debian Stretch, even for Ubuntu.. it's all the same.

Hm.. I did use mali driver when running jessie. After upgrading to strech I'm not able to find the package containing the mali driver.
So I did switch to fbturbo but I get the following error:
[ 119.432] (EE) AIGLX error: dlopen of /usr/lib/aarch64-linux-gnu/dri/lima_dri.so failed (/usr/lib/aarch64-linux-gnu/dri/lima_dri.so: cannot open shared object file: No such file or directory)
[ 119.432] (EE) AIGLX: reverting to software rendering

Any suggestions?

meveric · Post by **meveric** » Mon Sep 11, 2017 4:58 am

pld wrote:Hm.. I did use mali driver when running jessie. After upgrading to strech I'm not able to find the package containing the mali driver.

Yes initially I did not port xf86-video-mali-odroid to Stretch, since fbturbo did perform far better under Debian Jessie and Ubuntu than Mali ever did.
Still I ported it eventually for some testing, but did not upload it, but I'm doing it right now and it will be available in a couple of minutes.

pld wrote: So I did switch to fbturbo but I get the following error:
[ 119.432] (EE) AIGLX error: dlopen of /usr/lib/aarch64-linux-gnu/dri/lima_dri.so failed (/usr/lib/aarch64-linux-gnu/dri/lima_dri.so: cannot open shared object file: No such file or directory)
[ 119.432] (EE) AIGLX: reverting to software rendering

Any suggestions?

This is the wrong fbturbo driver. It's the driver directly coming from Debian Stretch and is meant for other boards (not for ODROIDs), I tried that one myself but couldn't get it to work either.
Make sure to install either xf86-video-fbturbo-odroid or xf86-video-mali-odroid. Non of the other will work.

Once again, setup-odroid should be able to take care of all of this, so you don't have to handle it manually.

brad · Post by **brad** » Sun Sep 24, 2017 9:23 am

meveric wrote:I checked myself a little bit ago and with some experimenting I could downgrade xorg to the version of Debian Jessie, but the result was the same.. I try a couple other things..

I had partial success installing and starting xorg and lightdm and a display with 14.4.0-rc1. I was missing keyboard / mouse support for whatever reason (using wrong virtual console somehow) so was unable to do any further testing. 4.14.0-rc1 is a bit broken for the moment for emmc. It has a bug causing CRC errors on my setup which is a little dangerous and I had to manually enable basic HDMI in the device tree.

I had some issues with permissions initially starting x, but all I needed was to add my user to video, audio and tty groups. I am probably missing some more config to set the virtual console to match my keyboard and mouse? Keyboard works find in text mode console until X starts.

Post by **odroid** » Sun Sep 24, 2017 10:38 am

Great to hear kernel 14.4.0 RC1 works with HDMI even partially.
Can you please check the status of the meson DRM display driver?

brad · Post by **brad** » Sun Sep 24, 2017 11:08 am

odroid wrote:Great to hear kernel 14.4.0 RC1 works with HDMI even partially.
Can you please check the status of the meson DRM display driver?

Here is the Xorg log for startup

Code: Select all

X.Org X Server 1.19.2
Release Date: 2017-03-02
[    90.612] X Protocol Version 11, Revision 0
[    90.612] Build Operating System: Linux 4.9.0-3-arm64 aarch64 Debian
[    90.612] Current Operating System: Linux odroid-stretch64 4.14.0-rc1-dirty #4 SMP PREEMPT Sat Sep 23 04:56:58 UTC 2017 aarch64
[    90.612] Kernel command line: console=tty0 root=/dev/mmcblk1p2 no_console_suspend consoleblank=0 ro rootwait 
[    90.612] Build Date: 07 July 2017  06:15:16AM
[    90.612] xorg-server 2:1.19.2-1+deb9u1 (https://www.debian.org/support) 
[    90.612] Current version of pixman: 0.34.0
[    90.612] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    90.612] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    90.613] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 24 01:51:42 2017
[    90.613] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    90.615] (==) No Layout section.  Using the first Screen section.
[    90.615] (==) No screen section available. Using defaults.
[    90.615] (**) |-->Screen "Default Screen Section" (0)
[    90.615] (**) |   |-->Monitor "<default monitor>"
[    90.624] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    90.625] (==) Automatically adding devices
[    90.625] (==) Automatically enabling devices
[    90.625] (==) Automatically adding GPU devices
[    90.625] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    90.625] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    90.625] 	Entry deleted from font path.
[    90.625] (==) FontPath set to:
	built-ins
[    90.625] (==) ModulePath set to "/usr/lib/xorg/modules"
[    90.625] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    90.625] (II) Loader magic: 0xaaaacd1bbdc8
[    90.625] (II) Module ABI versions:
[    90.625] 	X.Org ANSI C Emulation: 0.4
[    90.625] 	X.Org Video Driver: 23.0
[    90.625] 	X.Org XInput driver : 24.1
[    90.625] 	X.Org Server Extension : 10.0
[    90.627] (++) using VT number 7

[    90.627] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    90.628] (II) xfree86: Adding drm device (/dev/dri/card0)
[    90.628] (II) no primary bus or device found
[    90.628] 	falling back to /sys/devices/platform/soc/d0100000.vpu/drm/card0
[    90.628] (II) LoadModule: "glx"
[    90.629] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    90.743] (II) Module glx: vendor="X.Org Foundation"
[    90.743] 	compiled for 1.19.2, module version = 1.0.0
[    90.743] 	ABI class: X.Org Server Extension, version 10.0
[    90.746] (==) Matched modesetting as autoconfigured driver 0
[    90.746] (==) Matched fbdev as autoconfigured driver 1
[    90.746] (==) Assigned the driver to the xf86ConfigLayout
[    90.746] (II) LoadModule: "modesetting"
[    90.746] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    90.753] (II) Module modesetting: vendor="X.Org Foundation"
[    90.753] 	compiled for 1.19.2, module version = 1.19.2
[    90.753] 	Module class: X.Org Video Driver
[    90.754] 	ABI class: X.Org Video Driver, version 23.0
[    90.754] (II) LoadModule: "fbdev"
[    90.754] (WW) Warning, couldn't open module fbdev
[    90.754] (II) UnloadModule: "fbdev"
[    90.754] (II) Unloading fbdev
[    90.754] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    90.754] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    90.791] (II) modeset(0): using drv /dev/dri/card0
[    90.791] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    90.791] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    90.791] (==) modeset(0): RGB weight 888
[    90.791] (==) modeset(0): Default visual is TrueColor
[    90.791] (II) Loading sub module "glamoregl"
[    90.792] (II) LoadModule: "glamoregl"
[    90.792] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    90.878] (II) Module glamoregl: vendor="X.Org Foundation"
[    90.878] 	compiled for 1.19.2, module version = 1.0.0
[    90.878] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    90.878] (II) glamor: OpenGL accelerated X.org driver based.
[    93.426] (II) glamor: EGL version 1.4 (DRI2):
[    93.426] EGL_MESA_drm_image required.
[    93.439] (EE) modeset(0): glamor initialization failed
[    93.439] (II) modeset(0): ShadowFB: preferred NO, enabled NO
[    93.548] (II) modeset(0): Output HDMI-1 has no monitor section
[    93.658] (II) modeset(0): EDID for output HDMI-1
[    93.658] (II) modeset(0): Manufacturer: SAM  Model: 7fc  Serial#: 1
[    93.658] (II) modeset(0): Year: 2010  Week: 49
[    93.658] (II) modeset(0): EDID Version: 1.3
[    93.658] (II) modeset(0): Digital Display Input
[    93.658] (II) modeset(0): Max Image Size [cm]: horiz.: 131  vert.: 74
[    93.658] (II) modeset(0): Gamma: 2.20
[    93.658] (II) modeset(0): No DPMS capabilities specified
[    93.658] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
[    93.658] (II) modeset(0): First detailed timing is preferred mode
[    93.658] (II) modeset(0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 0.600
[    93.658] (II) modeset(0): blueX: 0.150 blueY: 0.060   whiteX: 0.312 whiteY: 0.329
[    93.658] (II) modeset(0): Supported established timings:
[    93.658] (II) modeset(0): 720x400@70Hz
[    93.658] (II) modeset(0): 640x480@60Hz
[    93.658] (II) modeset(0): 640x480@67Hz
[    93.658] (II) modeset(0): 640x480@72Hz
[    93.658] (II) modeset(0): 640x480@75Hz
[    93.658] (II) modeset(0): 800x600@60Hz
[    93.658] (II) modeset(0): 800x600@72Hz
[    93.658] (II) modeset(0): 800x600@75Hz
[    93.658] (II) modeset(0): 832x624@75Hz
[    93.658] (II) modeset(0): 1024x768@60Hz
[    93.658] (II) modeset(0): 1024x768@70Hz
[    93.658] (II) modeset(0): 1024x768@75Hz
[    93.658] (II) modeset(0): 1280x1024@75Hz
[    93.658] (II) modeset(0): 1152x864@75Hz
[    93.659] (II) modeset(0): Manufacturer's mask: 0
[    93.659] (II) modeset(0): Supported standard timings:
[    93.659] (II) modeset(0): #0: hsize: 1152  vsize 864  refresh: 75  vid: 20337
[    93.659] (II) modeset(0): #1: hsize: 1280  vsize 800  refresh: 60  vid: 129
[    93.659] (II) modeset(0): #2: hsize: 1280  vsize 960  refresh: 60  vid: 16513
[    93.659] (II) modeset(0): #3: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[    93.659] (II) modeset(0): #4: hsize: 1440  vsize 900  refresh: 60  vid: 149
[    93.659] (II) modeset(0): #5: hsize: 1440  vsize 900  refresh: 75  vid: 3989
[    93.659] (II) modeset(0): #6: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[    93.659] (II) modeset(0): #7: hsize: 1600  vsize 1200  refresh: 60  vid: 16553
[    93.659] (II) modeset(0): Supported detailed timing:
[    93.659] (II) modeset(0): clock: 148.5 MHz   Image Size:  160 x 90 mm
[    93.659] (II) modeset(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    93.659] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[    93.659] (II) modeset(0): Supported detailed timing:
[    93.659] (II) modeset(0): clock: 85.5 MHz   Image Size:  160 x 90 mm
[    93.659] (II) modeset(0): h_active: 1360  h_sync: 1424  h_sync_end 1536 h_blank_end 1792 h_border: 0
[    93.659] (II) modeset(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 795 v_border: 0
[    93.659] (II) modeset(0): Ranges: V min: 24 V max: 75 Hz, H min: 26 H max: 81 kHz, PixClock max 235 MHz
[    93.659] (II) modeset(0): Monitor name: SAMSUNG
[    93.659] (II) modeset(0): Supported detailed timing:
[    93.659] (II) modeset(0): clock: 148.5 MHz   Image Size:  160 x 90 mm
[    93.659] (II) modeset(0): h_active: 1920  h_sync: 2448  h_sync_end 2492 h_blank_end 2640 h_border: 0
[    93.659] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[    93.659] (II) modeset(0): Supported detailed timing:
[    93.659] (II) modeset(0): clock: 74.2 MHz   Image Size:  160 x 90 mm
[    93.659] (II) modeset(0): h_active: 1280  h_sync: 1720  h_sync_end 1760 h_blank_end 1980 h_border: 0
[    93.659] (II) modeset(0): v_active: 720  v_sync: 725  v_sync_end 730 v_blanking: 750 v_border: 0
[    93.659] (II) modeset(0): Supported detailed timing:
[    93.659] (II) modeset(0): clock: 74.2 MHz   Image Size:  160 x 90 mm
[    93.659] (II) modeset(0): h_active: 1920  h_sync: 2448  h_sync_end 2492 h_blank_end 2640 h_border: 0
[    93.659] (II) modeset(0): v_active: 540  v_sync: 542  v_sync_end 547 v_blanking: 562 v_border: 0
[    93.659] (II) modeset(0): Number of EDID sections to follow: 1
[    93.659] (II) modeset(0): EDID (in hex):
[    93.659] (II) modeset(0): 	00ffffffffffff004c2dfc0701000000
[    93.659] (II) modeset(0): 	3114010380834a780aee91a3544c9926
[    93.659] (II) modeset(0): 	0f5054bdef80714f8100814081809500
[    93.659] (II) modeset(0): 	950fb300a940023a801871382d40582c
[    93.659] (II) modeset(0): 	4500a05a0000001e662150b051001b30
[    93.659] (II) modeset(0): 	40703600a05a0000001e000000fd0018
[    93.659] (II) modeset(0): 	4b1a5117000a202020202020000000fc
[    93.659] (II) modeset(0): 	0053414d53554e470a202020202001dc
[    93.659] (II) modeset(0): 	020332f14b901f041305140312202122
[    93.659] (II) modeset(0): 	2309070783010000e2000fe305030172
[    93.659] (II) modeset(0): 	030c002000b82d20d0080140073f4050
[    93.659] (II) modeset(0): 	90a0023a80d072382d40102c4580a05a
[    93.659] (II) modeset(0): 	0000001e011d00bc52d01e20b8285540
[    93.659] (II) modeset(0): 	a05a0000001e011d80d0721c1620102c
[    93.660] (II) modeset(0): 	2580a05a0000009e0000000000000000
[    93.660] (II) modeset(0): 	000000000000000000000000000000a8
[    93.660] (--) modeset(0): HDMI max TMDS frequency 225000KHz
[    93.660] (II) modeset(0): Printing probed modes for output HDMI-1
[    93.660] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[    93.660] (II) modeset(0): Modeline "1920x1080"x50.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[    93.660] (II) modeset(0): Modeline "1920x1080i"x60.0   74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[    93.660] (II) modeset(0): Modeline "1920x1080i"x50.0   74.25  1920 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[    93.660] (II) modeset(0): Modeline "1920x1080"x30.0   74.25  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (33.8 kHz e)
[    93.660] (II) modeset(0): Modeline "1920x1080"x24.0   74.25  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[    93.660] (II) modeset(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[    93.660] (II) modeset(0): Modeline "1280x720"x50.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[    93.660] (II) modeset(0): Modeline "720x576"x50.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[    93.660] (II) modeset(0): Modeline "720x480"x59.9   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[    93.660] (II) modeset(0): Output HDMI-1 connected
[    93.660] (II) modeset(0): Using exact sizes for initial modes
[    93.660] (II) modeset(0): Output HDMI-1 using initial mode 1920x1080 +0+0
[    93.660] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    93.660] (==) modeset(0): DPI set to (96, 96)
[    93.660] (II) Loading sub module "fb"
[    93.660] (II) LoadModule: "fb"
[    93.660] (II) Loading /usr/lib/xorg/modules/libfb.so
[    93.671] (II) Module fb: vendor="X.Org Foundation"
[    93.671] 	compiled for 1.19.2, module version = 1.0.0
[    93.671] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    93.671] (==) Depth 24 pixmap format is 32 bpp
[    93.698] (==) modeset(0): Backing store enabled
[    93.698] (==) modeset(0): Silken mouse enabled
[    93.705] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    93.721] (==) modeset(0): DPMS enabled
[    93.721] (--) RandR disabled
[    93.740] (II) SELinux: Disabled on system
[    93.741] (II) AIGLX: Screen 0 is not DRI2 capable
[    93.741] (EE) AIGLX: reverting to software rendering
[    93.747] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[    93.749] (II) IGLX: Loaded and initialized swrast
[    93.749] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    93.750] (II) modeset(0): Damage tracking initialized
[    93.750] (II) modeset(0): Setting screen physical size to 508 x 285
[    93.950] (II) config/udev: Adding input device meson-ir (/dev/input/event1)
[    93.950] (II) No input driver specified, ignoring this device.
[    93.950] (II) This device may have been added with another device file.
[    93.951] (II) config/udev: Adding input device C-Media USB Headphone Set   (/dev/input/event0)
[    93.951] (II) No input driver specified, ignoring this device.
[    93.951] (II) This device may have been added with another device file.
[    93.953] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event2)
[    93.953] (II) No input driver specified, ignoring this device.
[    93.953] (II) This device may have been added with another device file.
[    93.954] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event3)
[    93.954] (II) No input driver specified, ignoring this device.
[    93.954] (II) This device may have been added with another device file.
[    93.956] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event4)
[    93.956] (II) No input driver specified, ignoring this device.
[    93.956] (II) This device may have been added with another device file.
[    96.023] (II) modeset(0): Disabling kernel dirty updates, not required.

Its using this dri card..

Code: Select all

root@odroid-stretch64:/var/log# cat /sys/kernel/debug/dri/0/state 
plane[29]: meson_primary_plane
	crtc=meson_crtc
	fb=38
		format=XR24 little-endian (0x34325258)
			modifier=0x0
		size=1920x1080
		layers:
			pitch[0]=7680
			offset[0]=0
	crtc-pos=1920x1080+0+0
	src-pos=1920.000000x1080.000000+0.000000+0.000000
	rotation=1
crtc[30]: meson_crtc
	enable=1
	active=0
	planes_changed=0
	mode_changed=0
	active_changed=0
	connectors_changed=0
	color_mgmt_changed=0
	plane_mask=1
	connector_mask=1
	encoder_mask=1
	mode: 0:"" 0 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x0 0x5
connector[28]: HDMI-A-1
	crtc=meson_crtc

And the meson drm startup

Code: Select all

Nov  3 17:16:43 localhost kernel: [    0.079963] meson-drm d0100000.vpu: Queued 2 outputs on vpu
Nov  3 17:16:43 localhost kernel: [    0.080406] meson-drm d0100000.vpu: Failed to create debugfs directory
Nov  3 17:16:43 localhost kernel: [    0.080442] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Nov  3 17:16:43 localhost kernel: [    0.080451] [drm] No driver support for vblank timestamp query.
Nov  3 17:16:43 localhost kernel: [    0.080527] meson-drm d0100000.vpu: CVBS Output connector not available
Nov  3 17:16:43 localhost kernel: [    0.102555] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
Nov  3 17:16:43 localhost kernel: [    0.102764] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
Nov  3 17:16:43 localhost kernel: [    0.102957] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
Nov  3 17:16:43 localhost kernel: [    0.407818] Console: switching to colour frame buffer device 240x67
Nov  3 17:16:43 localhost kernel: [    0.440121] meson-drm d0100000.vpu: fb0:  frame buffer device
Nov  3 17:16:43 localhost kernel: [    0.440474] [drm] Initialized meson 1.0.0 20161109 for d0100000.vpu on minor 0

Patch to enable HDMI I used is here https://github.com/superna9999/meta-mes ... d-C2.patch

Post by **odroid** » Sun Sep 24, 2017 12:09 pm

Great!
Most basic features seem to be working except for GPU/VPU HW acceleration.

brad · Post by **brad** » Sun Sep 24, 2017 12:24 pm

odroid wrote:Great!
Most basic features seem to be working except for GPU/VPU HW acceleration.

I installed xserver-xorg-input-all and now have keyboard and mouse working but its doubling or missing keystrokes.

Then Installed xserver-xorg-video-fbdev and Xorg is then using it and performanced improved somewhat. Chromium runs poor through consuming alot of CPU but works.

Post by **odroid** » Sun Sep 24, 2017 12:35 pm

Ah... DRM driver might break the faster FBturbo implementation.

brad · Post by **brad** » Sun Sep 24, 2017 12:50 pm

odroid wrote:Ah... DRM driver might break the faster FBturbo implementation.

I wasn't using fbturbo initially, performance is much better now with it installed, thank you:)

Code: Select all

machinekit@odroid-stretch64:~$ sudo apt-get remove xserver-xorg-video-fbdev
machinekit@odroid-stretch64:~$ sudo apt-get install xserver-xorg-video-fbturbo

Chromium is now tell me im hardware accelerated in chrome://gpu/

Post by **odroid** » Sun Sep 24, 2017 2:27 pm

Thank you for the confirmation. Yes, fbturbo is quite faster than stock fb driver.

But the GPU(Mali) might not work AFAIK.
Can you please try "es2gears" to check the Mali driver status on the command line?

If Kernel 4.14 utilize the Mali GPU correctly, you will see a message something like this with rotating three gears.

Code: Select all

odroid@odroid64:~$ es2gears                                                     
EGL_VERSION = 1.4 Linux-r6p1-01rel0                                             
vertex shader info:                                                             
fragment shader info:                                                           
info:                                                                           
300 frames in 5.0 seconds = 60.000 FPS                                          
301 frames in 5.0 seconds = 59.996 FPS                                          
300 frames in 5.0 seconds = 60.000 FPS                                          
301 frames in 5.0 seconds = 59.996 FPS                                          
300 frames in 5.0 seconds = 60.000 FPS                                          
300 frames in 5.0 seconds = 60.000 FPS                                          
^C                                                                              
odroid@odroid64:~$

I think we have to move to other thread.
These items are out of topic obviously.
Sorry meveric

brad · Post by **brad** » Sun Sep 24, 2017 3:01 pm

odroid wrote: I think we have to move to other thread.
These items are out of topic obviously.
Sorry meveric

Yes sorry meveric I have moved here viewtopic.php?f=138&t=28426

meveric · Post by **meveric** » Sun Sep 24, 2017 4:14 pm

brad wrote:
odroid wrote:Ah... DRM driver might break the faster FBturbo implementation.
I wasn't using fbturbo initially, performance is much better now with it installed, thank you:)
Code: Select all
machinekit@odroid-stretch64:~$ sudo apt-get remove xserver-xorg-video-fbdev
machinekit@odroid-stretch64:~$ sudo apt-get install xserver-xorg-video-fbturbo
Chromium is now tell me im hardware accelerated in chrome://gpu/

Be careful with xserver-xorg-video-fbturbo. This one comes directly from Debian and is NOT for ODROIDs. I still provide xf86-video-fbturbo-odroid which is optimized for ODROIDs.
My tests indicate that xserver-xorg-video-fbturbo wasn't really working all that great.

encore2097 · Post by **encore2097** » Wed Sep 27, 2017 4:23 pm

HDMI output is flickering.

I'm using a pretty long cable - 5M to a 4K monitor, but it should be outputting at 1080p.

Flickers on and off every few seconds and I also get green lines.

Luckily, ssh works by default so I was a able to start updating and working on the system.

meveric · Post by **meveric** » Wed Sep 27, 2017 5:19 pm

yes I think 5m is like a maximum for HDMI, could be that at this length you start to get serious issues.

encore2097 · Post by **encore2097** » Thu Sep 28, 2017 12:12 am

Yeah 5M is the max - I tested with another SBC, Raspberry Pi 3 and the same cable/monitor works without flickering.

I dont know if this means its a resolution issue or something else. I did catch some HDMI interrupts and a few lines being being printed on the login screen.

brad · Post by **brad** » Thu Sep 28, 2017 4:17 pm

encore2097 wrote:Yeah 5M is the max - I tested with another SBC, Raspberry Pi 3 and the same cable/monitor works without flickering.

I dont know if this means its a resolution issue or something else. I did catch some HDMI interrupts and a few lines being being printed on the login screen.

The Pi 3 only uses HDMI 1.4 so it might not be a 1 for 1 test as the Odroid is using HDMI v2.01a. Its suggested in the HDMI standards that HDMI 2.x might require shorter runs (2m or less) or higher quality HDMI 2.x cable. Not saying its your problem but worth investigating.

hami · Post by **hami** » Mon Oct 02, 2017 8:42 pm

Dear Braulio, Meveric and Odroid enthusiasts,

after some time I tried to install desktop (MATE via setup-odroid utility) but it stucks at 81%, as described by Braulio some time ago. Does somebody know how to resolve this or it is still not resolved? Thank you.

Braulio wrote:Hello , when I try to install Mate desktop on this image the installation stucks at 81% when apt configures the dbus.

I check with Htop on another tty and the status of all the proceses are "S".

I try 5 times , after launch "apt update && apt upgrade && apt dist-upgrade " I reboot ,like the alert message sugest.

I dont know what to do.

adamkex · Post by **adamkex** » Sun Nov 05, 2017 10:36 am

Does this support hardware acceleration (especially for video in mpv) and moonlight-embedded?

meveric · Post by **meveric** » Sun Nov 05, 2017 4:22 pm

no hardware acceleration for mpv... moonlight should work though.