[OS] Debian Jessie (arm64)

Moderators: mdrjr, odroid

Re: [OS] Debian Jessie (arm64)

Unread postby manuc0 » Tue Feb 06, 2018 8:50 pm

Hello
Does the image support the driver for PCF8563 RTC Module ?
and can this http://odroid.com/dokuwiki/doku.php?id=en:pcf8563rtc procedure be applied to enable the RTC ?

Thank you
manuc0
 
Posts: 4
Joined: Tue Jan 16, 2018 9:25 pm
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Wed Feb 07, 2018 7:03 am

The image normally has nothing to do with hardware support, as hardware support often comes through the Kernel and for this is OS independent.
Still to answer your question, yes it's supported, and if you start setup-odroid there should actually be an option for this :)
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby manuc0 » Thu Feb 08, 2018 4:44 pm

Hello when performing apt-get update after installing http://oph.mdrjr.net/meveric/images/Jes ... -C2.img.xz I got this error
Failed to fetch http://www.deb-multimedia.org/dists/jessie/InRelease Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file)

Could you help ? thank you !
manuc0
 
Posts: 4
Joined: Tue Jan 16, 2018 9:25 pm
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Thu Feb 08, 2018 4:49 pm

Yes the developer of deb-multimedia removed his arm64 support for Debian Jessie.
Check unter /etc/apt/sources.list.d/ and you should fine a deb-multimedia.list you can remove this file as it's no longer working.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby manuc0 » Thu Feb 08, 2018 11:25 pm

Thank you for prompt answer
manuc0
 
Posts: 4
Joined: Tue Jan 16, 2018 9:25 pm
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby roguerobots » Wed Mar 07, 2018 7:34 am

Hey I have a C2v0.2, I finally got this set up at work after having trouble with a few other distros and everything was fine until I took it home and plugged it in again, no HDMI output. At home I have some 1440p 144hz monitors, so I'm not sure if that has anything to do with it, but when I take it back to work it doesn't work here either. I've tried bridging the shell grounds with no luck as well. I still have access to SSH and the display really isn't crucial but I'd like to resolve the issue, I'm not sure where to start but here is my boot.ini
Attachments
boot.ini
(6.23 KiB) Downloaded 89 times
roguerobots
 
Posts: 3
Joined: Wed Mar 07, 2018 7:04 am
languages_spoken: english

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Wed Mar 07, 2018 8:38 am

The boot.ini is set to 1080p @ 60 Hz. So your 1440p monitor might have issues if it's not supported.
Not sure though why the other monitor should suddenly stop working if it worked before.
Maybe the 1440p damaged the HDMI port, but I'm not sure if that's possible.
I can't see any issues with the boot.ini script so the problem doesn't seem to be there.
During boot of the board does it show anything at all? Means is just the Console/Desktop missing or is nothing shown at all?
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby roguerobots » Thu Mar 08, 2018 9:00 am

Never any display output at all, never saw it again after moving it home, any ideas on how to debug this? Only things I've done so far is the beginning update/upgrade, installed plex, installed tmux and weechat, made a new user account, configure to boot to command line, but all of this worked when installed and rebooted while in the first location.

Oh I was also using an external hard drive with USB power only, I'd set it up in fstab as suggested by plex but I don't think that's the issue, the issue persists after removing the entry. The hard drive did seem odd or stuck in a spin up loop when plugged in again at home and I saw some comments about a protection circuit for external devices? Does this seem more hardware related, should I be asking questions somewhere else?
roguerobots
 
Posts: 3
Joined: Wed Mar 07, 2018 7:04 am
languages_spoken: english

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Thu Mar 08, 2018 9:14 am

if you have a spare SD card I'd suggest flash the image again on a spare card and see if that works (without modifications).
If it's working, then it's probably an issue with your configuration and we can dig deeper.
If it doesn't work that may point to an hardware issue... either cable or the ODROID itself and you should ask HardKernel directly what you can do about it.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby roguerobots » Fri Mar 09, 2018 9:43 am

Of course, flashing a second image skipped my mind but unfortunately no luck, I will investigate with other cables and if nothing comes up it sounds like I need to contact Hardkernel, thanks.
roguerobots
 
Posts: 3
Joined: Wed Mar 07, 2018 7:04 am
languages_spoken: english

Re: [OS] Debian Jessie (arm64)

Unread postby odroid » Fri Mar 09, 2018 10:17 am

@roguerobots,
Please try "ubuntu64-16.04.3-mate-odroid-c2-20170927.img.xz" image.
If you still have the HDMI output issue, create a new topic with your test result.
And we will help you.
User avatar
odroid
Site Admin
 
Posts: 28622
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: [OS] Debian Jessie (arm64)

Unread postby mkroman » Tue Apr 10, 2018 7:10 am

@meveric could you please provide the source package for the kernel(s)?

Or could you just add overlay filesystem support? It's needed to run Docker.

On a working machine:
Code: Select all
% zcat /proc/config.gz | rg -i overlay
CONFIG_OF_OVERLAY=y
CONFIG_OVERLAY_FS=m
CONFIG_OVERLAY_FS_REDIRECT_DIR=y
# CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW is not set
CONFIG_OVERLAY_FS_INDEX=y


When trying to start Docker on my ODROID C2:

Code: Select all
Starting Docker Application Container Engine...
time="2018-04-09T23:59:19.541788791+02:00" level=info msg="libcontainerd: started new docker-containerd process" pid=1368
time="2018-04-09T23:59:19+02:00" level=info msg="starting containerd" module=containerd revision=cfd04396dc68220d1cecbe686a6cc3aa5ce3667c version=v1.0.2
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.content.v1.content"..." module=containerd type=io.containerd.content.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.btrfs"..." module=containerd type=io.containerd.snapshotter.v1
time="2018-04-09T23:59:19+02:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.btrfs" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.overlayfs"..." module=containerd type=io.containerd.snapshotter.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.metadata.v1.bolt"..." module=containerd type=io.containerd.metadata.v1
time="2018-04-09T23:59:19+02:00" level=warning msg="could not use snapshotter btrfs in metadata plugin" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module="containerd/io.containerd.metadata.v1.bolt"
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.differ.v1.walking"..." module=containerd type=io.containerd.differ.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.gc.v1.scheduler"..." module=containerd type=io.containerd.gc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.containers"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.content"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.diff"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.events"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.healthcheck"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.images"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.leases"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.namespaces"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.snapshots"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.monitor.v1.cgroups"..." module=containerd type=io.containerd.monitor.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.runtime.v1.linux"..." module=containerd type=io.containerd.runtime.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.tasks"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.version"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg="loading plugin "io.containerd.grpc.v1.introspection"..." module=containerd type=io.containerd.grpc.v1
time="2018-04-09T23:59:19+02:00" level=info msg=serving... address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
time="2018-04-09T23:59:19+02:00" level=info msg=serving... address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
time="2018-04-09T23:59:19+02:00" level=info msg="containerd successfully booted in 0.010310s" module=containerd
time="2018-04-09T23:59:19.594311960+02:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
time="2018-04-09T23:59:19.594476939+02:00" level=error msg="[graphdriver] prior storage driver overlay2 failed: driver not supported"
Error starting daemon: error initializing graphdriver: driver not supported
docker.service: main process exited, code=exited, status=1/FAILURE
Failed to start Docker Application Container Engine.
Unit docker.service entered failed state.


Thanks in advance and thank you for your work!
mkroman
 
Posts: 4
Joined: Tue Apr 10, 2018 6:42 am
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Tue Apr 10, 2018 5:55 pm

The Kernel comes from HardKernel directly I use their git repository as a basis.
I also think it would be better to ask HardKernel directly to activate it, as others might want this as well.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby odroid » Tue Apr 10, 2018 9:25 pm

@mkroman & @meveric,
We will try the OverlayFS feature with new Kernel 3.16 LTS
We may need a week for testing and WiKi documentation.
User avatar
odroid
Site Admin
 
Posts: 28622
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: [OS] Debian Jessie (arm64)

Unread postby mkroman » Thu Apr 12, 2018 8:27 am

odroid wrote:@mkroman & @meveric,
We will try the OverlayFS feature with new Kernel 3.16 LTS
We may need a week for testing and WiKi documentation.


Excellent, thanks! :)
mkroman
 
Posts: 4
Joined: Tue Apr 10, 2018 6:42 am
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby odroid » Wed Apr 18, 2018 7:47 pm

User avatar
odroid
Site Admin
 
Posts: 28622
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Wed Apr 18, 2018 11:41 pm

I will update the Kernel so it's available.
Give me an hour or so ;)

Edit:
New Kernel is now available
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby mkroman » Thu Apr 19, 2018 5:52 am



Unfortunately Docker still won't start with overlayfs.

Starting with the overlay driver:

Code: Select all
mk@mkdroid ~ % sudo /usr/local/bin/dockerd --storage-driver overlay
INFO[2018-04-18T22:42:38.585693263+02:00] libcontainerd: started new docker-containerd process  pid=5353
INFO[0000] starting containerd                           module=containerd revision=cfd04396dc68220d1cecbe686a6cc3aa5ce3667c version=v1.0.2
INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
INFO[0000] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
WARN[0000] could not use snapshotter btrfs in metadata plugin  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module="containerd/io.containerd.metadata.v1.bolt"
INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
INFO[0000] loading plugin "io.containerd.gc.v1.scheduler"...  module=containerd type=io.containerd.gc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.leases"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
INFO[0000] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.010652s   module=containerd
ERRO[2018-04-18T22:42:38.641652378+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
Error starting daemon: error initializing graphdriver: driver not supported


Starting with the overlay2 driver:

Code: Select all
mk@mkdroid ~ % sudo /usr/local/bin/dockerd --storage-driver overlay2
INFO[2018-04-18T22:42:43.020553639+02:00] libcontainerd: started new docker-containerd process  pid=5375
INFO[0000] starting containerd                           module=containerd revision=cfd04396dc68220d1cecbe686a6cc3aa5ce3667c version=v1.0.2
INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
INFO[0000] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
WARN[0000] could not use snapshotter btrfs in metadata plugin  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module="containerd/io.containerd.metadata.v1.bolt"
INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
INFO[0000] loading plugin "io.containerd.gc.v1.scheduler"...  module=containerd type=io.containerd.gc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.leases"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
INFO[0000] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.009275s   module=containerd
ERRO[2018-04-18T22:42:43.072833681+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
Error starting daemon: error initializing graphdriver: driver not supported


Code: Select all
mk@mkdroid ~ % lsmod | grep overlay
overlayfs              29820  0


Code: Select all
mk@mkdroid ~ % zgrep OVERLAY /proc/config.gz
CONFIG_OVERLAYFS_FS=m


I went ahead and downloaded the script from https://github.com/moby/moby/blob/maste ... -config.sh and ran it, this is the output:

Code: Select all
% ./check-config.sh
info: reading kernel config from /proc/config.gz ...

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- apparmor: enabled, but apparmor_parser missing
    (use "apt-get install apparmor" to fix this)
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled
- CONFIG_NF_NAT_IPV4: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module)
- CONFIG_IP_NF_NAT: missing
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_NF_NAT_NEEDED: enabled
- CONFIG_POSIX_MQUEUE: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled

Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: missing
- CONFIG_CGROUP_PIDS: missing
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
    (cgroup swap accounting is currently enabled)
- CONFIG_MEMCG_KMEM: enabled
- CONFIG_RESOURCE_COUNTERS: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_CFQ_GROUP_IOSCHED: enabled
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: enabled
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_CGROUP_NET_PRIO: enabled
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: enabled
- CONFIG_IP_VS: enabled (as module)
- CONFIG_IP_VS_NFCT: enabled
- CONFIG_IP_VS_RR: enabled (as module)
- CONFIG_EXT3_FS: missing
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: missing
- CONFIG_EXT3_FS_SECURITY: missing
    (enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
  - "overlay":
    - CONFIG_VXLAN: enabled (as module)
      Optional (for encrypted networks):
      - CONFIG_CRYPTO: enabled
      - CONFIG_CRYPTO_AEAD: enabled
      - CONFIG_CRYPTO_GCM: missing
      - CONFIG_CRYPTO_SEQIV: enabled
      - CONFIG_CRYPTO_GHASH: missing
      - CONFIG_XFRM: enabled
      - CONFIG_XFRM_USER: enabled (as module)
      - CONFIG_XFRM_ALGO: enabled
      - CONFIG_INET_ESP: enabled
      - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled
  - "ipvlan":
    - CONFIG_IPVLAN: missing
  - "macvlan":
    - CONFIG_MACVLAN: enabled (as module)
    - CONFIG_DUMMY: enabled (as module)
  - "ftp,tftp client in container":
    - CONFIG_NF_NAT_FTP: enabled (as module)
    - CONFIG_NF_CONNTRACK_FTP: enabled (as module)
    - CONFIG_NF_NAT_TFTP: enabled (as module)
    - CONFIG_NF_CONNTRACK_TFTP: enabled (as module)
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: enabled (as module)
  - "btrfs":
    - CONFIG_BTRFS_FS: enabled (as module)
    - CONFIG_BTRFS_FS_POSIX_ACL: enabled
  - "devicemapper":
    - CONFIG_BLK_DEV_DM: enabled
    - CONFIG_DM_THIN_PROVISIONING: enabled (as module)
  - "overlay":
    - CONFIG_OVERLAY_FS: missing
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000


Looking at https://cateee.net/lkddb/web-lkddb/OVERLAYFS_FS.html and https://cateee.net/lkddb/web-lkddb/OVERLAY_FS.html it appears the macro was renamed before final release (i.e. OVERLAYFS_FS was only used in 3.18-rc+HEAD).

I don't think the docker daemon actually looks for the definition, so I'm not sure why it fails.
mkroman
 
Posts: 4
Joined: Tue Apr 10, 2018 6:42 am
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby mkroman » Thu Apr 19, 2018 6:00 am

The function used to check whether the host supports the overlay driver is located here

It looks for the presence of the string "nodev\toverlay" in /proc/filesystems, while the overlay driver in the ODROID kernel is registered as overlayfs.

I found the commit where the filesystem was renamed.

The backported driver seems a bit too outdated unfortunately.
mkroman
 
Posts: 4
Joined: Tue Apr 10, 2018 6:42 am
languages_spoken: english
ODROIDs: ODROID C2

Re: [OS] Debian Jessie (arm64)

Unread postby odroid » Thu Apr 19, 2018 10:01 am

So you might need a higher Kernel version.
Try the latest 4.17 if you don't need the GPU/VPU HW acceleration.
viewtopic.php?f=135&t=22717&start=800#p221555
User avatar
odroid
Site Admin
 
Posts: 28622
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: [OS] Debian Jessie

Unread postby jenja_c2 » Thu Jun 28, 2018 5:21 am

Hi All,
Apologies if this is a duplicate. Basically, I just came across an issue trying to update my system

# /etc/apt/sources.list.d# uname -a
Linux orion 3.16.56+ #1 SMP PREEMPT Wed Apr 18 16:59:34 CEST 2018 aarch64 GNU/Linux

# /etc/apt/sources.list.d# cat /etc/*release*
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

# apt update -y && apt upgrade -y && apt dist-upgrade -y
<skipped>
W: Failed to fetch http://security.debian.org/dists/jessie ... /InRelease Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.


Any idea what happened recently? It looks like the entry did disappear from InRelease
jenja_c2
 
Posts: 38
Joined: Sat Dec 17, 2016 6:53 pm
languages_spoken: english
ODROIDs: Odroid C2

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Thu Jun 28, 2018 5:30 am

First of all, I moved your Post from the ODROID XU4 forum to the ODROID C2 forum, as these are different boards.

Second, Debian Jessie never fully supported arm64 and now it seems they removed arm64 support from some repositories completely.
I highly recommend using Debian Stretch instead or try an upgrade from Jessie to Stretch.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby jenja_c2 » Fri Jun 29, 2018 7:37 pm

Apologies for posting in the wrong forum for the second time - time to learn. I shall try upgrading to Stretch (hope it is similar to the desktop version and the above issue is not a show stopprt)
the other thing I have just come across was:
# apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-headers-3.16.56+ linux-image-3.16.56+
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 108 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 63238 files and directories currently installed.)
Removing linux-headers-3.16.56+ (3.16.56-20180531-C2) ...
Removing linux-image-3.16.56+ (3.16.56-20180531-C2) ...
dpkg: error processing package linux-image-3.16.56+ (--remove):
subprocess installed pre-removal script returned error exit status 1
Errors were encountered while processing:
linux-image-3.16.56+
E: Sub-process /usr/bin/dpkg returned an error code (1)

my gut feeling it might be a parsing issue with /etc/kernel/postinst.d/apt-auto-removal? Any glues? Thanks!
jenja_c2
 
Posts: 38
Joined: Sat Dec 17, 2016 6:53 pm
languages_spoken: english
ODROIDs: Odroid C2

Re: [OS] Debian Jessie (arm64)

Unread postby jenja_c2 » Fri Jun 29, 2018 7:57 pm

All,
disregard please - the auto-remove went smoothly after the second attempt
jenja_c2
 
Posts: 38
Joined: Sat Dec 17, 2016 6:53 pm
languages_spoken: english
ODROIDs: Odroid C2

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Fri Jun 29, 2018 8:47 pm

did you encounter any other issues with the update to Debian Stretch?
I sometimes had an issue that apt-get update did no longer work after I updated from Jessie to Stretch, but it could be fixed easily.
Also have you changes the repository entries under /etc/apt/sources.list.d/ from jessie to stretch?
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby jenja_c2 » Sat Jun 30, 2018 7:38 am

I have not yet started, really. I shall share my experience if there is anything worth mentioning.
jenja_c2
 
Posts: 38
Joined: Sat Dec 17, 2016 6:53 pm
languages_spoken: english
ODROIDs: Odroid C2

Re: [OS] Debian Jessie (arm64)

Unread postby lele » Wed Aug 08, 2018 11:19 pm

Hello,
sorry if this seems out-of-context with the last messages but it is relevant with Debian Jessie on C2.

I need an ARM platform with secure boot and full disk encryption, at least on the eMMC root drive. I currently use a XU4 (ARMv7) which works perfectly but does not have support for secure boot, so I looked into the C2 (ARMv8) which should be suitable for this, hardware-wise.

Is this actually feasible on C2 using this Debian image? Or maybe is there a software way to do this on the XU4? That would be even better.

I have no experience in secure boot and FDE on Linux so if you have any suggestions would be very helpful

Thanks a lot!
lele
 
Posts: 17
Joined: Wed Dec 23, 2015 2:46 am
languages_spoken: english
ODROIDs: XU4

Re: [OS] Debian Jessie (arm64)

Unread postby mad_ady » Wed Aug 08, 2018 11:23 pm

Can't say about secure boot, but there was an article in the magazine about encrypted rootfs.
User avatar
mad_ady
 
Posts: 4477
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Wed Aug 08, 2018 11:33 pm

First I highly recommend using Debian Stretch not Debian Jessie.
Second I have no clue about secure boot, disk encryption for the rootfs seems to be the logical step.
In fact, I would boot from an external source, USB thumb-driver or HDD instead of eMMC/SD Card.
That way the SD/eMMC is only for handling the encryption of the HDD and the HDD itself can not be used without the SD/eMMC. Means, booting ODROID with eMMC/SD card does not work as it has no rootfs.
Accessing the external HDD on any other system does not work, as it's encrypted (at least not without the key or pass-phrase you use). So one does not boot/work without the other, probably the most secure option to boot your ODROID and secure your data.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby lele » Thu Aug 09, 2018 7:30 am

Thanks Meveric

any particular reasons for recommending Stretch over Debian (also on XU4) other than for the new features? Are there stability issues found in the last Debian images, e.g. on XU4? Any significant performance advantage? I run a headless server and performance is important in my case.

As for encryption, thanks for the info. I can just do it straight on XU4 then. No need to migrate to C2 if trustZone in ArmV8 is not directly implemented.

Thanks
lele
 
Posts: 17
Joined: Wed Dec 23, 2015 2:46 am
languages_spoken: english
ODROIDs: XU4

Re: [OS] Debian Jessie (arm64)

Unread postby meveric » Thu Aug 09, 2018 1:36 pm

lele wrote:Any particular reasons for recommending Stretch over Debian (also on XU4) other than for the new features? Are there stability issues found in the last Debian images, e.g. on XU4? Any significant performance advantage? I run a headless server and performance is important in my case.

I was referring to Debian Jessie on arm64 (ODROID C2).
ARM64 support is still rather new and not very good, and Debian Jessie as an operating system is not even fully aware that "arm64" exists.
Different programs do not recognize arm64 as an architecture, for example if you try to compile a Kernel under arm64 with make-kpkg (make Kernel Package) the make-kpkg tool doesn't know the architecture type aarch64/arm64 and you have to use the packages from Debian Stretch to build packages on Debian Jessie. Other packages also were never ported to Debian Jessie, as the configurations for these software are not aware of arm64 architectures.
Different developers dropped Debian Jessie arm64 support all together, for example deb-multimedia removed all Debian Jessie arm64 packages.
I also recently stopped publishing new packages for Debian Jessie for arm64 while I still continue this for armhf.

That is the main reason why I say use Debian Stretch. It had nothing to do with XU4, features, performance or whatever.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.
User avatar
meveric
 
Posts: 9075
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1

Re: [OS] Debian Jessie (arm64)

Unread postby lele » Thu Aug 09, 2018 6:15 pm

Thanks for the clarification!
lele
 
Posts: 17
Joined: Wed Dec 23, 2015 2:46 am
languages_spoken: english
ODROIDs: XU4

Previous

Return to Other OS

Who is online

Users browsing this forum: No registered users and 3 guests