[OS] Debian Jessie

Moderators: mdrjr, odroid

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jan 21, 2018 12:53 am

Hello,

little question for unserstanding. So far I run my XU4 server with Debian Jessie and kernel 3.10. Some modules like php are already from Debain Stretch. I wonder now, if it is recommendet to switch to a newer kernel version and/or Debian Stretch completely. Debian Jessie has security support till May 2018 and LTS till 2020, about the kernels I have no idea. Therefore I guess it would make sense, or?

Have a nice day!
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Jan 21, 2018 1:09 am

Kernel is independent from the OS, as it not comes from Debian but from HardKernel/me directly. So Debian Stretch has the same Kernel as Debian Jessie.
3.10 is the official Kernel from Samsung, but 4.14 is also available for both Debian Jessie and Debian 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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jan 21, 2018 1:30 am

So I should update at least Debian and can stay with the kernel? Where is the benefit of staying or updating the kernel?
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Jan 21, 2018 1:38 am

Currently under Debian Stretch there are fewer programs/games available than under Debian Jessie (at least when it comes to the software I port to ODROIDs), but yes Debian Stretch has newer programs/drivers that come directly from Debian.
So You have to choose what you prefer. More available programs/games for ODROIDs, or newer programs/drivers from Debian directly (not necessarily for ODROIDs at all).

Kernel 3.10 has most "stable" support, means the ODROID probably runs with less issues, some programs/games run better under Kernel 3.10, even some drivers work better.
Kernel 4.14 is newer and supports newer hardware, it also allows the use of hardware decoder/encoder for ffmpeg and gstreamer on ODROID XU4 and G2D hardware acceleration on the desktop, but it has some issues with drivers and hardware that was previously working fine on Kernel 3.10.

Sooner or later I guess Kernel 4.14 will be the default for everyone, as the benefits probably outweigh the downsides and patches may fix the issues that we still see under 4.14.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jan 21, 2018 2:35 am

Sounds like a kernel update is not necessary for me. Just because I am cursious, to update I have to execute following statements:
Code: Select all
apt-get update && apt-get upgrade && apt-get dist-upgrade
apt-get install linux-image-4.14-armhf-odroid-xu3 linux-headers-4.14-armhf-odroid-xu3


To update Debian I have to edit the file /etc/apt/sources.list and the ones in /etc/apt/sources.list.d and replace jessie with stretch and then again
Code: Select all
apt-get update && apt-get upgrade && apt-get dist-upgrade


is that right?
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Jan 21, 2018 3:00 am

one correction:
Code: Select all
apt-get install linux-image-4.14-armhf-odroid-xu4 linux-headers-4.14-armhf-odroid-xu4

xu4 instead of xu3.. it's still for both XU3 and XU4 though.

The rest you wrote is correct.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jan 21, 2018 8:25 am

The debian update worked but now I get an error when i try to shutdown:
Code: Select all
shutdown -r
Failed to connect to bus: No such file or directory
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Jan 21, 2018 8:29 am

not sure.. try reboot, or just turn it hard off.. shouldn't be an issue.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jan 21, 2018 8:31 am

I did the hard turn off. But would prefer to do it a better way in long term.
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Jan 21, 2018 8:35 am

Well if it doesn't work at all then maybe something else is broken.
After the update it can happen that something is not working.. but after a reboot it should be fine again.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jan 21, 2018 10:09 am

Seems like the dbus was not (properly) installed, apt-get solved this issue.
Thanks meveric!
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby lufkinOrange » Thu Feb 01, 2018 12:40 pm

Hello all,
I have done some research to install debian strech instead of jessaie. meveric said that it was working fine, but fewer programs were available for it vs the current jessaie.
I wanted to know what was these packages, so I ended up checking the package list from what happears to be his repository.
https://oph.mdrjr.net/meveric/dists/jessie/main/binary-armhf/Packages
https://oph.mdrjr.net/meveric/dists/stretch/main/binary-armhf/Packages
Indeed there are a lot less programs in the stretch. The list of software from his jessy repo is very impressive. His repo seems to consist mosly on games and emulator. There are some desktop related application like chrominium with video plugins, kodi, a todo app, image-analyzer, moonlight, mpv, seafile, synergy to name a few popular one. Thanks for his dedication, all packages have a description and this helped a lot.
I am am now the owner of a odroid-hc2, which I will use as a remote backup location, most of these games software or graphical software will not be useful to me, so I'll try to take his base jessie image and upgrade it to stretch see how it goes, like other users did. Just wanted to share an input and how to visualize the list of package before installing the distro.

on a side note, I am not completly sure on the debian vs ubuntu choice. Usually I take debian because of how the react with the community vs cannonical fiasco (never upstream code, rythmnbox paid song, mir, unity bug gnome, upstart, mark always vs people), but I do recognise that ubuntu is the default choice and I might have less issue with it - for a server build. so sorry for stealing the thread, but if someone might have an opinion thank you for sharing it.

edit : unlike what is said in the first page, the sshd_config file allow root to connect with interractive password. this is useful for the hc1-2 machine. Be sure to install your public key and apply "permitRootLogin without-password" as soon as possible.
also, for those that wish to edit the image before flashing it, decompress it with unxz, then use losetup -fP image to set it to /dev/loop* and create the p2 partition which is now mountable.
lufkinOrange
 
Posts: 21
Joined: Mon Jan 22, 2018 7:50 am
languages_spoken: english, français

Re: [OS] Debian Jessie

Unread postby dominic » Thu Mar 01, 2018 12:30 pm

Hello,

I updated the kernel to 4.10 and now my odroid does not want to talk with me anymore. The update itself worked without any problems but since the restart I cannot create a connection via putty, the fan is spinning at maximum and no signal over HDMI.

Earlier this thread someone else had also problem after updating the kernels. The solution was to adjust the boot.ini, see https://forum.odroid.com/viewtopic.php?f=96&t=17542&start=550#p205135 The content of my boot.ini is slightly different to the one maveric posted and even more curious, it mentions Ubuntu? See below. I adjusted the file according to meverics suggestion but that didn't change anything. Played arround with the contained settings but no success. Then I replaced my boot.ini completely with the one from the latest image from meveric, first post. This time I could see something via HDMI and the fan was normal again, but still no connection via putty. In the boot.ini I adjusted then 'fatload mmc 0:1 0x44000000 exynos5422-odroidxu3.dtb' to 'fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb' but no big difference.

Currently the last lines on the monitor are:
Give root password for maintenance
(or press Control-D to continue):


But I have no USB keyboard right now and can't proceed here. Besides that I have the feeling that the boot.ini was changed with the kernel updates and should be different now. In my backup the file looks different to the one posted below.

Has anyone an idea how to get my little friend back on track?

Code: Select all
ODROIDXU-UBOOT-CONFIG

# U-Boot Parameters
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"

# Mac address configuration
setenv macaddr "00:1e:06:61:7a:85

#------------------------------------------------------------------------------------------------------
# Basic Ubuntu Setup. Don't touch unless you know what you are doing.
# --------------------------------
setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes"

# boot commands
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x42000000 uInitrd; if test "${board_name}" = "xu4"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb; setenv fdtloaded "true"; fi
if test "${board_name}" = "xu3"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu3.dtb; setenv fdtloaded "true"; fi
if test "${board_name}" = "xu3l"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu3-lite.dtb; setenv fdtloaded "true"; fi
#failsafe
if test "x${board_name}" = "x"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb; fi; bootz 0x40008000 0x42000000 0x44000000"

# --- Screen Configuration for HDMI --- #
# ---------------------------------------
# Uncomment only ONE line! Leave all commented for automatic selection.
# Uncomment only the setenv line!
# ---------------------------------------
# ODROID-VU forced resolution
# setenv videoconfig "video=HDMI-A-1:1280x800@60"
# -----------------------------------------------
# ODROID-VU forced EDID
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x800.bin"
# -----------------------------------------------
# 1920x1080 (1080P) with monitor provided EDID information. (1080p-edid)
# setenv videoconfig "video=HDMI-A-1:1920x1080@60"
# -----------------------------------------------
# 1920x1080 (1080P) without monitor data using generic information (1080p-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080.bin"
# -----------------------------------------------
# 1920x1080 50hz (1080P) with monitor provided EDID information. (1080p 50hz-edid)
# setenv videoconfig "video=HDMI-A-1:1920x1080@50"
# -----------------------------------------------
# 1920x1080 50hz (1080P) without monitor data using generic information (1080p 50hz-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080_50hz.bin"
# -----------------------------------------------
# 1440x900 with monitor provided EDID information.
# setenv videoconfig "video=HDMI-A-1:1440x900@60"
# -----------------------------------------------
# 1440x900 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1440x900.bin"
# -----------------------------------------------
# 1280x720 (720P) with monitor provided EDID information. (720p-edid)
# setenv videoconfig "video=HDMI-A-1:1280x720@60"
# -----------------------------------------------
# 1280x720 (720P) without monitor data using generic information (720p-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x720.bin"
# -----------------------------------------------
# 1024x768 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin"
# -----------------------------------------------
# 800x600 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/800x600.bin"
# -----------------------------------------------
# 800x480 without monitor data using generic information (ODROID 7")
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/800x480.bin"
# -----------------------------------------------
# 720x576 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/720x576.bin"
# -----------------------------------------------
# 720x480 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/720x480.bin"
# -----------------------------------------------
# 640x480 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/640x480.bin"

# Disable video system (not sure it it works for XU4
# https://wiki.archlinux.org/index.php/ODROID
setenv nographics "1"


# --- HDMI / DVI Mode Selection ---
# ------------------------------------------
# - HDMI Mode
setenv vout "hdmi"
# - DVI Mode (disables sound over HDMI as per DVI compat)
# setenv vout "dvi"


# --- CPU Governor Setup ---
# Uncomment only one line. New governor is set after 90secs after boot.
# ------------------------------------------
# - Performance (Keep all the CPU's at Maximum frequency)
setenv governor "performance"
# ------------------------------------------
# - Ondemand
# setenv governor "ondemand"
# ------------------------------------------
# - Interactive (Pretty much just like ondemand with more possible customization via sysfs.)
# setenv governor "interactive"
# ------------------------------------------
# - Conservative (Like ondemand, but do the frequency transitions more slowly, great for battery powered applications)
# setenv governor "conservative"
# ------------------------------------------
# - Powersave (Keeps the CPU's to the lowest possible temps)
# setenv governor "powersave"


#------------------------------------------------------------------------------
#
# HDMI-PHY Parameter Control
#
#------------------------------------------------------------------------------
#------------------------------------------------------------------------------
#
# HDMI Hot Plug detection
#
#------------------------------------------------------------------------------
#
# Forces the HDMI subsystem to ignore the check if the cable is connected or
# not.
# false : disable the detection and force it as connected.
# true : let cable, board and monitor decide the connection status.
#
# default: true
#
#------------------------------------------------------------------------------
setenv HPD "true"

#------------------------------------------------------------------------------
#
#  TMDS data amplitude control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  tx_amp_lvl : 0 = 760 mVdiff(Min), 31 = 1380 mVdiff(Max)
#
#  Hardkernel default hdmi_tx_amp_lvl = 31(1380 mVdiff);
#------------------------------------------------------------------------------
setenv hdmi_tx_amp_lvl  "31"

#------------------------------------------------------------------------------
#
#  TMDS data amplitude fine control for each channel.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  tx_lvl : 0 = 0 mVdiff(Min), 3 = 60 mVdiff(Max)
#
#  Hardkernel default
#      hdmi_tx_lvl_ch0 = 3, hdmi_tx_lvl_ch1 = 3, hdmi_tx_lvl_ch2 = 3,
#------------------------------------------------------------------------------
setenv hdmi_tx_lvl_ch0      "3"
setenv hdmi_tx_lvl_ch1      "3"
setenv hdmi_tx_lvl_ch2      "3"

#------------------------------------------------------------------------------
#
#  TMDS data pre-emphasis level control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to -0.45dB emphasis level except for 1
#  tx_emp_lvl : 0 = 0 db(Min), 1 = -0.25 db, 2 = 0.7 db, 15 = -7.45 db(Max)
#
#  Hardkernel default hdmi_tx_emp_lvl = 6 (-2.50 db);
#------------------------------------------------------------------------------
setenv hdmi_tx_emp_lvl      "6"

#------------------------------------------------------------------------------
#
#  TMDS clock amplitude control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  clk_amp_lvl : 0 = 790 mVdiff(Min), 31 = 1410 mVdiff(Max)
#
#  Hardkernel default hdmi_clk_amp_lvl = 31 (1410 mVdiff)
#------------------------------------------------------------------------------
setenv hdmi_clk_amp_lvl     "31"

#------------------------------------------------------------------------------
#
#  TMDS data source termination resistor control.
#
#------------------------------------------------------------------------------
#
#  tx_res :
#      0 = Source Termination OFF(Min), 1 = 200 ohm, 2 = 300 ohm, 3 = 120 ohm(Max)
#
#  Hardkernrel default hdmi_tx_res = 0 (Source Termination OFF)
#------------------------------------------------------------------------------
setenv hdmi_tx_res      "0"

#------------------------------------------------------------------------------

setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}"

# final boot args
setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control}"
# drm.debug=0xff
# Boot the board
boot
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Thu Mar 01, 2018 2:43 pm

The boot.ini you posted is the correct one it doesn't need to be changed, as the failsafe mode should already be correct (assuming you have an ODROID XU4).

Can you check all files in the bootfs? Are the dtb files present?

Do you have an UART to debug the boot process?
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby lufkinOrange » Fri Mar 02, 2018 2:26 am

@dominic,
Code: Select all
Give root password for maintenance
(or press Control-D to continue):

this looks like a standard linux issue/maybe not something directly related to debian and boot.init. You system can properly boot, but somewhere when the system boot, it fail and systemd ask the root password for maintenance. Your ssh is not started as it would be started late in the boot process, but your error is early.

For example, if one add to /etc/fstab to mount a hard disk, this mount is now mandatory for the system to boot. If you shut down the computer, remove the disk and reboot, you will have the same systemd message (give root password for maintenance) because a disk is missing. There are a lot of workafound for this, you can follow odroid wiki to show you how to make the disk optionnal by configuring autofs manually, using nofail and systemd-timeout in fstab etc.

So in this case I would suggest to connect a uart to see early boot message and interract with the system to see what's wrong. Optionnally you might simply boot it and crash it, and then look at systemd logs (on another computer by mounting the file system) of what happen in the last boot.
lufkinOrange
 
Posts: 21
Joined: Mon Jan 22, 2018 7:50 am
languages_spoken: english, français

Re: [OS] Debian Jessie

Unread postby dominic » Fri Mar 02, 2018 11:59 am

Yes, I have a XU4.
The boot folder content can be seen in the attached screenshot.
No, I sadly don't have an UART
I mounted the storage and looked at the logs but could not find anything (but I also don't know what to look for). Will delete all logs and try again tomorrow.

The boot.ini is ok? Multiple statements in one line are ok then?
Attachments
files.png
files.png (21.82 KiB) Viewed 2284 times
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby lufkinOrange » Fri Mar 02, 2018 12:35 pm

It's probably not related to boot.ini.
the hardware executed boot.ini and started the kernel. the kernel unpacked the initramfs and started it's init. Your problem is either in systemd in the initramfs or in the real root. There is not magic, you will need to investigate logs. Ifyou were able to see systemd maintenance prompt, it means that you have console access. With this you don't need the uart as you have a screen and keyboard working.
lufkinOrange
 
Posts: 21
Joined: Mon Jan 22, 2018 7:50 am
languages_spoken: english, français

Re: [OS] Debian Jessie

Unread postby meveric » Fri Mar 02, 2018 3:55 pm

dominic wrote:The boot.ini is ok? Multiple statements in one line are ok then?

The file in the boot folder look fine, but you're right, I took a closer look at that boot.ini of yours and it looks off.
Although multiple commands in the same line should not be an issue, the lines are at the wrong place and bootcmd is not used anywhere so this seems to be broken.
Can you try the following:
Code: Select all
ODROIDXU-UBOOT-CONFIG

# U-Boot Parameters
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"

# Mac address configuration
setenv macaddr "00:1e:06:61:7a:26"

#------------------------------------------------------------------------------------------------------
# Basic Ubuntu Setup. Don't touch unless you know what you are doing.
# --------------------------------
setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=/dev/mapper/hdd-root rootwait ro fsck.repair=yes net.ifnames=0"

# --- Screen Configuration for HDMI --- #
# ---------------------------------------
# Uncomment only ONE line! Leave all commented for automatic selection.
# Uncomment only the setenv line!
# ---------------------------------------
# ODROID-VU forced resolution
# setenv videoconfig "video=HDMI-A-1:1280x800@60"
# -----------------------------------------------
# ODROID-VU forced EDID
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x800.bin"
# -----------------------------------------------
# 1920x1080 (1080P) with monitor provided EDID information. (1080p-edid)
# setenv videoconfig "video=HDMI-A-1:1920x1080@60"
# -----------------------------------------------
# 1920x1080 (1080P) without monitor data using generic information (1080p-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080.bin"
# -----------------------------------------------
# 1920x1080 50hz (1080P) with monitor provided EDID information. (1080p 50hz-edid)
# setenv videoconfig "video=HDMI-A-1:1920x1080@50"
# -----------------------------------------------
# 1920x1080 50hz (1080P) without monitor data using generic information (1080p 50hz-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080_50hz.bin"
# -----------------------------------------------
# 1440x900 with monitor provided EDID information.
# setenv videoconfig "video=HDMI-A-1:1440x900@60"
# -----------------------------------------------
# 1440x900 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1440x900.bin"
# -----------------------------------------------
# 1280x1024 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x1024.bin"
# -----------------------------------------------
# 1280x720 (720P) with monitor provided EDID information. (720p-edid)
# setenv videoconfig "video=HDMI-A-1:1280x720@60"
# -----------------------------------------------
# 1280x720 (720P) without monitor data using generic information (720p-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x720.bin"
# -----------------------------------------------
# 1024x768 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin"
# -----------------------------------------------
# 1024x600 without monitor data using generic information (ODROID VU7+)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x600.bin"
# -----------------------------------------------
# 800x600 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/800x600.bin"
# -----------------------------------------------
# 800x480 without monitor data using generic information (ODROID 7")
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/800x480.bin"
# -----------------------------------------------
# 720x576 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/720x576.bin"
# -----------------------------------------------
# 720x480 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/720x480.bin"
# -----------------------------------------------
# 640x480 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/640x480.bin"


# --- HDMI / DVI Mode Selection ---
# ------------------------------------------
# - HDMI Mode
setenv vout "hdmi"
# - DVI Mode (disables sound over HDMI as per DVI compat)
# setenv vout "dvi"


# --- HDMI CEC Configuration ---
# ------------------------------------------
setenv cecenable "false" # false or true
# set to true to enable HDMI CEC


# --- CPU Governor Setup ---
# Uncomment only one line. New governor is set after 90secs after boot.
# ------------------------------------------
# - Performance (Keep all the CPU's at Maximum frequency)
setenv governor "performance"
# ------------------------------------------
# - Ondemand
# setenv governor "ondemand"
# ------------------------------------------
# - Interactive (Pretty much just like ondemand with more possible customization via sysfs.)
# setenv governor "interactive"
# ------------------------------------------
# - Conservative (Like ondemand, but do the frequency transitions more slowly, great for battery powered applications)
# setenv governor "conservative"
# ------------------------------------------
# - Powersave (Keeps the CPU's to the lowest possible temps)
# setenv governor "powersave"


#------------------------------------------------------------------------------
#
# HDMI-PHY Parameter Control
#
#------------------------------------------------------------------------------
#------------------------------------------------------------------------------
#
# HDMI Hot Plug detection
#
#------------------------------------------------------------------------------
#
# Forces the HDMI subsystem to ignore the check if the cable is connected or
# not.
# false : disable the detection and force it as connected.
# true : let cable, board and monitor decide the connection status.
#
# default: true
#
#------------------------------------------------------------------------------
setenv HPD "true"

#------------------------------------------------------------------------------
#
#  TMDS data amplitude control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  tx_amp_lvl : 0 = 760 mVdiff(Min), 31 = 1380 mVdiff(Max)
#
#  Hardkernel default hdmi_tx_amp_lvl = 31(1380 mVdiff);
#------------------------------------------------------------------------------
setenv hdmi_tx_amp_lvl  "31"

#------------------------------------------------------------------------------
#
#  TMDS data amplitude fine control for each channel.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  tx_lvl : 0 = 0 mVdiff(Min), 3 = 60 mVdiff(Max)
#
#  Hardkernel default
#      hdmi_tx_lvl_ch0 = 3, hdmi_tx_lvl_ch1 = 3, hdmi_tx_lvl_ch2 = 3,
#------------------------------------------------------------------------------
setenv hdmi_tx_lvl_ch0      "3"
setenv hdmi_tx_lvl_ch1      "3"
setenv hdmi_tx_lvl_ch2      "3"

#------------------------------------------------------------------------------
#
#  TMDS data pre-emphasis level control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to -0.45dB emphasis level except for 1
#  tx_emp_lvl : 0 = 0 db(Min), 1 = -0.25 db, 2 = 0.7 db, 15 = -7.45 db(Max)
#
#  Hardkernel default hdmi_tx_emp_lvl = 6 (-2.50 db);
#------------------------------------------------------------------------------
setenv hdmi_tx_emp_lvl      "6"

#------------------------------------------------------------------------------
#
#  TMDS clock amplitude control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  clk_amp_lvl : 0 = 790 mVdiff(Min), 31 = 1410 mVdiff(Max)
#
#  Hardkernel default hdmi_clk_amp_lvl = 31 (1410 mVdiff)
#------------------------------------------------------------------------------
setenv hdmi_clk_amp_lvl     "31"

#------------------------------------------------------------------------------
#
#  TMDS data source termination resistor control.
#
#------------------------------------------------------------------------------
#
#  tx_res :
#      0 = Source Termination OFF(Min), 1 = 200 ohm, 2 = 300 ohm, 3 = 120 ohm(Max)
#
#  Hardkernrel default hdmi_tx_res = 0 (Source Termination OFF)
#------------------------------------------------------------------------------
setenv hdmi_tx_res      "0"

#------------------------------------------------------------------------------

setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}"

# Load kernel, initrd and dtb in that sequence
fatload mmc 0:1 0x40008000 zImage
fatload mmc 0:1 0x42000000 uInitrd
if test "${board_name}" = "xu4"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb; setenv fdtloaded "true"; fi
if test "${board_name}" = "xu3"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu3.dtb; setenv fdtloaded "true"; fi
if test "${board_name}" = "xu3l"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu3-lite.dtb; setenv fdtloaded "true"; fi
#failsafe
if test "x${board_name}" = "x"; then fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb; fi

# set FDT address
fdt addr 0x44000000

if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi


# final boot args
setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} board=${board_name} ${hdmi_phy_control}"
# drm.debug=0xff
# Boot the board
bootz 0x40008000 0x42000000 0x44000000


You should also be able to use the following boot.ini: https://github.com/mdrjr/5422_bootini/b ... 4/boot.ini
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sat Mar 03, 2018 8:25 am

I tried meverics boot.ini first
HDMI worked, fan worked. But odroid did not boot correctly. On the monitor is an entry "Failed to create component debugfs" - see picture.
No logs in /var/log at all

Then I tried the boot.ini from github
HDMI worked, fan worked. More text had been printed on monitor but still the odroid did not boot correctly. On the monitor is an entry 'Firmware is not present in the /lib/firmware directory...' - see pictures.
The log folder contained an empty btmp file and a wtmp file with a little data but not realy text.

The only thing I did both times was to adjust the mac to have the old value.
It should be possible to migrate from kernel 3.10 to 4.14 directly, right?
Attachments
git2.jpg
git2.jpg (228.09 KiB) Viewed 2243 times
git1.jpg
git1.jpg (492.05 KiB) Viewed 2243 times
meveric.jpg
meveric.jpg (365.56 KiB) Viewed 2243 times
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sat Mar 03, 2018 8:54 am

dominic wrote:The only thing I did both times was to adjust the mac to have the old value.
It should be possible to migrate from kernel 3.10 to 4.14 directly, right?

Yes normally that should work fine I've done it a couple of times.
Except for some issues if you boot from HDD rather than SD/eMMC then it seems you have to adjust the rootfs in the boot.ini as well.

The missing firmware is no big deal, it's used only if you want to use hardware decoder in Kodi and other video applications (not required on a server image).

Still I don't see why the system is "parked" for so long nearly a minute.
I wonder if something earlier in the boot process goes wrong which we can't see in the pictures. The pictures do not show any issues as far as I can tell.

Just to show you that it looks pretty similar to my bootlog just that I don't have such a big timeout after random: crng init done I think that is when it normally would initialize the filesystem and mount rootfs.
Code: Select all
Jan  1 00:00:26 loki kernel: [    4.277594] ALSA device list:
Jan  1 00:00:26 loki kernel: [    4.279079]   #0: Odroid-XU4
Jan  1 00:00:26 loki kernel: [    4.282987] Freeing unused kernel memory: 1024K
Jan  1 00:00:26 loki kernel: [    4.383990] usb 3-1: new high-speed USB device number 2 using xhci-hcd
Jan  1 00:00:26 loki kernel: [    4.571711] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
Jan  1 00:00:26 loki kernel: [    4.577004] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  1 00:00:26 loki kernel: [    4.584502] usb 3-1: Product: USB2.0 Hub
Jan  1 00:00:26 loki kernel: [    4.587995] usb 3-1: Manufacturer: GenesysLogic
Jan  1 00:00:26 loki kernel: [    4.597092] hub 3-1:1.0: USB hub found
Jan  1 00:00:26 loki kernel: [    4.599708] hub 3-1:1.0: 2 ports detected
Jan  1 00:00:26 loki kernel: [    4.696055] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
Jan  1 00:00:26 loki kernel: [    4.722783] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
Jan  1 00:00:26 loki kernel: [    4.728032] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  1 00:00:26 loki kernel: [    4.735135] usb 4-1: Product: USB3.0 Hub
Jan  1 00:00:26 loki kernel: [    4.739030] usb 4-1: Manufacturer: GenesysLogic
Jan  1 00:00:26 loki kernel: [    4.757241] hub 4-1:1.0: USB hub found
Jan  1 00:00:26 loki kernel: [    4.759835] hub 4-1:1.0: 2 ports detected
Jan  1 00:00:26 loki kernel: [    5.052123] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
Jan  1 00:00:26 loki kernel: [    5.078874] usb 4-1.1: New USB device found, idVendor=05e3, idProduct=0735
Jan  1 00:00:26 loki kernel: [    5.084294] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  1 00:00:26 loki kernel: [    5.091568] usb 4-1.1: Product: USB3.0 SATA Bridge
Jan  1 00:00:26 loki kernel: [    5.096332] usb 4-1.1: Manufacturer: USB Storage
Jan  1 00:00:26 loki kernel: [    5.100924] usb 4-1.1: SerialNumber: 0000000000000033
Jan  1 00:00:26 loki kernel: [    5.106628] usb-storage 4-1.1:1.0: USB Mass Storage device detected
Jan  1 00:00:26 loki kernel: [    5.112462] scsi host0: usb-storage 4-1.1:1.0
Jan  1 00:00:26 loki kernel: [    5.118285] usbcore: registered new interface driver uas
Jan  1 00:00:26 loki kernel: [    5.244025] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
Jan  1 00:00:26 loki kernel: [    5.268827] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
Jan  1 00:00:26 loki kernel: [    5.274078] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Jan  1 00:00:26 loki kernel: [    5.281183] usb 6-1: Product: USB 10/100/1000 LAN
Jan  1 00:00:26 loki kernel: [    5.285862] usb 6-1: Manufacturer: Realtek
Jan  1 00:00:26 loki kernel: [    5.289932] usb 6-1: SerialNumber: 000001000000
Jan  1 00:00:26 loki kernel: [    5.459097] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
Jan  1 00:00:26 loki kernel: [    5.524909] r8152 6-1:1.0 eth0: v1.09.9
Jan  1 00:00:26 loki kernel: [    6.306126] scsi 0:0:0:0: Direct-Access     Genesys  USB3/SATA Bridge 1003 PQ: 0 ANSI: 6
Jan  1 00:00:26 loki kernel: [    6.313316] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan  1 00:00:26 loki kernel: [    7.983754] sd 0:0:0:0: [sda] Spinning up disk...
Jan  1 00:00:26 loki kernel: [    8.995925] .
Jan  1 00:00:26 loki kernel: [    8.996106] ready
Jan  1 00:00:26 loki kernel: [    8.998361] sd 0:0:0:0: [sda] 3907029152 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan  1 00:00:26 loki kernel: [    9.006498] sd 0:0:0:0: [sda] Write Protect is off
Jan  1 00:00:26 loki kernel: [    9.010625] sd 0:0:0:0: [sda] Mode Sense: 5f 00 10 08
Jan  1 00:00:26 loki kernel: [    9.011272] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan  1 00:00:26 loki kernel: [    9.046603]  sda: sda1
Jan  1 00:00:26 loki kernel: [    9.049482] sd 0:0:0:0: [sda] Attached SCSI disk
Jan  1 00:00:26 loki kernel: [   11.044887] random: crng init done
Jan  1 00:00:26 loki kernel: [   11.418573] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 00:00:26 loki kernel: [   13.617224] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
Jan  1 00:00:26 loki kernel: [   15.122617] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan  1 00:00:26 loki kernel: [   16.354948] EXT4-fs (dm-3): recovery complete
Jan  1 00:00:26 loki kernel: [   16.383480] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 00:00:26 loki kernel: [   16.441982] Adding 4194300k swap on /dev/mapper/hdd-swap.  Priority:-2 extents:1 across:4194300k
Jan  1 00:00:26 loki kernel: [   18.042296] EXT4-fs (dm-1): recovery complete
Jan  1 00:00:26 loki kernel: [   18.048572] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 00:00:26 loki systemd[1]: Started getty on tty2-tty6 if dbus and logind are not available.
Jan  1 00:00:26 loki systemd[1]: Starting Login Service...
Jan  1 00:00:26 loki systemd[1]: Starting Permit User Sessions...
Jan  1 00:00:26 loki systemd[1]: Starting LSB: Start NTP daemon...
Jan  1 00:00:26 loki systemd[1]: Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
Jan  1 00:00:26 loki systemd[1]: Starting LSB: controls zram devices...
Jan  1 00:00:26 loki systemd[1]: Started System Logging Service.


Have you changed /etc/fstab in any way? Or moved the rootfs to HDD?
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sat Mar 03, 2018 9:35 am

meveric wrote:Have you changed /etc/fstab in any way? Or moved the rootfs to HDD?


Yes, I have a small external HDD connected via USB which is mounted in fstab. It was not connected when I took the pictures. With HDD the log on minitor is mention it successfully and the stops again. The only difference is, that the 'random: crng init done' message appears earlier.

The fstab was not touched by me in a long time and so far I had never problems. Is that file changed during kernel update? Then I'll go and check it.

EDIT:
I removed the entry from fstab and unplugged the HDD, then restarted the odroid a couple of times. Sometimes there was more log, sometimes less. The picture is the one with most log entries.
The only weird thing is the header banner. When I got the odroid I played a little with various distributions, maybe OGST was one of it. But why is it partly still there as I always flashed the emmec propperly?
Attachments
20180302_195429.jpg
20180302_195429.jpg (306.17 KiB) Viewed 2243 times
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sat Mar 03, 2018 6:12 pm

dominic wrote:Yes, I have a small external HDD connected via USB which is mounted in fstab. It was not connected when I took the pictures.

Linux sometimes hangs if there's an entry in the fstab to a device that is not available.
Also a wrong UUID or a wrong device (for example for the rootfs /dev/mmcblk0p2 vs. /dev/mmcblk1p2) in the fstab can prevent the system from booting properly.

dominic wrote:The fstab was not touched by me in a long time and so far I had never problems. Is that file changed during kernel update? Then I'll go and check it.

No it's not touched by the update, BUT while in Kernel 3.10 the first boot device no matter of eMMC or SD card is always /dev/mmcblk0 under Kernel 4.14 the eMMC is /dev/mmcblk0 and SD is /dev/mmcblk1 even if it's the only boot device.
If your fstab used /dev/mmcblk* instead of UUIDs that could be an issue.

dominic wrote:The only weird thing is the header banner. When I got the odroid I played a little with various distributions, maybe OGST was one of it. But why is it partly still there as I always flashed the emmec propperly?

That's normal, just means it's one of my Kernels. It's a symbol in the Kernel itself and the Kernel is the same for the OGST images and the regular Debian images, so you can ignore that.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby elatllat » Sat Mar 03, 2018 11:10 pm

be sure to end the removable fstab entries in
Code: Select all
defaults,nofail 0 0
elatllat
 
Posts: 1047
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1

Re: [OS] Debian Jessie

Unread postby dominic » Sun Mar 04, 2018 5:54 am

The current entries in fstab is:
Code: Select all
UUID=e139ce78-9841-40fe-8833-96a304a09859   /   ext4   errors=remount-ro,noatime   0   1
/dev/mmcblk0p1                /boot    vfat   noatime          0    2


I checked the UUID and that fits to the emmec.
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Mar 04, 2018 6:19 am

but the second one for boot might not fit.
can you change: /dev/mmcblk0p1 to UUID=96C3-9298 just to be sure?
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Mar 04, 2018 8:33 am

meveric wrote:can you change: /dev/mmcblk0p1 to UUID=96C3-9298 just to be sure?


I did but nothing changed. That the boot is mounted second is no problem? Where does that UUID come?
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Mar 04, 2018 8:36 am

no it does not matter that it's mounted second.

You can find the UUID of all devices under ls -la /dev/disk/by-uuid/
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Mar 04, 2018 8:53 am

The UUID is correct. Any other ideas? Is there any change to turn on some (debug) logging to file?

Is it maybe possible to scroll in the logs that is shown via HDMI? Have no USB keyboard back home and that not tested yet so far.
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Mar 04, 2018 9:01 am

normally it should write the log to /var/log/syslog...
if no log is written then my guess it that it doesn't mount the rootfs properly during boot process.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Mar 04, 2018 9:46 am

No, nothing sadly. But shouldn't the boot fail a lot earlier if the mounting failed? As everything is on the boot or the main partition.
Does maybe an important system task (systemd) not start?
Does it make sence to flash a backup and try again? Maybe with the 4.10 instead of 4.14 kernel version?
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Sun Mar 04, 2018 5:27 pm

dominic wrote:No, nothing sadly. But shouldn't the boot fail a lot earlier if the mounting failed? As everything is on the boot or the main partition.

Not necessarily. Kernel is booted directly from bootfs, only the modules are on the rootfs.
Also the rootfs is part of the boot.ini and it might be able to use it until fstab tells it otherwise.
dominic wrote:Does maybe an important system task (systemd) not start?

In that case you should at least see "something" in the log.
4 seconds on the boot process is quite long, it shoud have started logging long time before that.
dominic wrote:Does it make sence to flash a backup and try again?

Yes, this might help. If you don't have any important data on it yet, download a new image, and try updating to Kernel 4.14 directly.
dominic wrote:Maybe with the 4.10 instead of 4.14 kernel version?

Kernel 4.10 is not supported, only 4.9 and 4.14 but 4.9 wasn't updated for quite some time.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Mon Mar 05, 2018 5:49 am

Good news, it is working now with kernel 4.14.

I did a few changes before installing the kernel, don't know if that helped.
* Changed fstab to use UUID
* Replaced boot.ini with the one from your image in post 1 (i think the macaddr statement is missing a closing " char)
* emptied log folder
* Only installed the kernel and no headers as I don't think I'll need them

Worked with the first try :)
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Mon Mar 05, 2018 7:23 am

Glad it's working now :)
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby Mr.Poopy » Wed Mar 28, 2018 9:54 pm

Someone managed to use the WiringPi library (https://github.com/hardkernel/wiringPi) on this image?
After I executed "./build", I can use the gpio command. Unfortunalety, nothing happens...
Is it possible to fix this?

"./build" output:
Code: Select all
wiringPi Build script
=====================


WiringPi Library
[UnInstall]
[Compile] wiringPi.c
wiringPi.c: In function ‘analogRead’:
wiringPi.c:2290:20: warning: pointer targets in passing argument 1 of ‘atoi’ differ in signedness [-Wpointer-sign]
       return  atoi(value);
                    ^
In file included from /usr/include/features.h:374:0,
                 from /usr/include/stdio.h:27,
                 from wiringPi.c:54:
/usr/include/stdlib.h:278:1: note: expected ‘const char *’ but argument is of type ‘unsigned char *’
 __NTH (atoi (const char *__nptr))
 ^
wiringPi.c: In function ‘digitalWriteByte_XU’:
wiringPi.c:2424:19: warning: overflow in implicit constant conversion [-Woverflow]
  gpx1.bits.bit2 = (value & 0x80);
                   ^
wiringPi.c: In function ‘digitalWriteByte_C’:
wiringPi.c:2454:20: warning: overflow in implicit constant conversion [-Woverflow]
  gpioy.bits.bit3 = (value & 0x80);
                    ^
wiringPi.c: In function ‘digitalWriteByte_C2’:
wiringPi.c:2481:21: warning: overflow in implicit constant conversion [-Woverflow]
  gpiox.bits.bit21 = (value & 0x80);
                     ^
wiringPi.c: In function ‘waitForInterrupt’:
wiringPi.c:2559:1: warning: label ‘wait’ defined but not used [-Wunused-label]
 wait:
 ^
wiringPi.c: In function ‘wiringPiSetupSys’:
wiringPi.c:3071:12: warning: unused variable ‘offset’ [-Wunused-variable]
   int pin, offset;
            ^
wiringPi.c:3069:7: warning: unused variable ‘boardRev’ [-Wunused-variable]
   int boardRev ;
       ^
wiringPi.c: At top level:
wiringPi.c:687:12: warning: ‘sysFdData’ defined but not used [-Wunused-variable]
 static int sysFdData [64] = {
            ^
wiringPi.c:730:13: warning: ‘gpioFdOffsetXU34’ defined but not used [-Wunused-function]
 static int  gpioFdOffsetXU34(int pin)
             ^
[Compile] wiringSerial.c
[Compile] wiringShift.c
[Compile] piHiPri.c
[Compile] piThread.c
[Compile] wiringPiSPI.c
[Compile] wiringPiI2C.c
[Compile] softPwm.c
[Compile] softTone.c
[Compile] mcp23008.c
[Compile] mcp23016.c
[Compile] mcp23017.c
[Compile] mcp23s08.c
[Compile] mcp23s17.c
[Compile] sr595.c
[Compile] pcf8574.c
[Compile] pcf8591.c
[Compile] mcp3002.c
[Compile] mcp3004.c
[Compile] mcp4802.c
[Compile] mcp3422.c
[Compile] max31855.c
[Compile] max5322.c
[Compile] sn3218.c
[Compile] drcSerial.c
[Link (Dynamic)]
[Install Headers]
[Install Dynamic Lib]

WiringPi Devices Library
[UnInstall]
[Compile] ds1302.c
[Compile] maxdetect.c
[Compile] piNes.c
[Compile] gertboard.c
[Compile] piFace.c
[Compile] lcd128x64.c
[Compile] lcd.c
[Compile] piGlow.c
[Link (Dynamic)]
[Install Headers]
[Install Dynamic Lib]

GPIO Utility
[Compile] gpio.c
gpio.c: In function ‘doEdge’:
gpio.c:571:3: warning: implicit declaration of function ‘doUnexport’ [-Wimplicit-function-declaration]
   doUnexport(3, argv);      // unexport argc == 3
   ^
gpio.c: At top level:
gpio.c:644:6: warning: conflicting types for ‘doUnexport’
 void doUnexport (int argc, char *argv [])
      ^
gpio.c:571:3: note: previous implicit declaration of ‘doUnexport’ was here
   doUnexport(3, argv);      // unexport argc == 3
   ^
[Compile] extensions.c
[Compile] readall.c
[Compile] pins.c
[Link]
[Install]

All Done.

NOTE: To compile programs with wiringPi, you need to add:
    -lwiringPi
  to your compile line(s) To use the Gertboard, MaxDetect, etc.
  code (the devLib), you need to also add:
    -lwiringPiDev
  to your compile line(s).
Mr.Poopy
 
Posts: 1
Joined: Wed Mar 28, 2018 9:28 pm
languages_spoken: english, dutch
ODROIDs: C2, XU4

Re: [OS] Debian Jessie

Unread postby meveric » Wed Mar 28, 2018 10:03 pm

As the Kernel is the one that controlling GPIOs and the Kernel is the same for Ubuntu and Debian it should behave the same on this image as on any other image.
There are different versions of the Kernel available Kernel 3.10 is pre-installed, but you can also use Kernel 4.14.
I guess depending on what Kernel you use the behavior of wiringPi can be different.

From what I could read in the code it's suppose to work with all Kernel versions, but I've never tried 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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby skyfly555 » Thu Mar 29, 2018 11:51 pm

Hello, Meveric and other guys here.

I'm happy with this Debian version, now trying to compile SoftEther, and getting errors.

When I "make", I get this:
Code: Select all
make[1]: Entering directory '/root/vpnserver'
Preparing SoftEther VPN Server...
ranlib lib/libcharset.a
ranlib lib/libcrypto.a
ranlib lib/libedit.a
ranlib lib/libiconv.a
ranlib lib/libncurses.a
ranlib lib/libssl.a
ranlib lib/libz.a
ranlib code/vpnserver.a
gcc code/vpnserver.a -O2 -fsigned-char -lm -ldl -lrt -Wl,--no-warn-mismatch -lpthread -L./ lib/libssl.a lib/libcrypto.a lib/libiconv.a lib/libcharset.a lib/libedit.a lib/libncurses.a lib/libz.a -o vpnserver
code/vpnserver.a: error adding symbols: File in wrong format
collect2: error: ld returned 1 exit status
Makefile:18: recipe for target 'i_read_and_agree_the_license_agreement' failed
make[1]: *** [i_read_and_agree_the_license_agreement] Error 1
make[1]: Leaving directory '/root/vpnserver'


Searching an answer, I found people saying the problem is I'm on ARM64 and the SoftEther code is ARM 32 bits. https://www.linuxquestions.org/questions/slackware-14/i-keep-getting-this-error-file-in-wrong-format-4175439373/

Is there any way to tell it to compile in 32 bits mode?

Or other type of solution?

Thank you!
skyfly555
 
Posts: 19
Joined: Sun Nov 15, 2015 8:44 am
languages_spoken: english
ODROIDs: None yet

Re: [OS] Debian Jessie

Unread postby meveric » Fri Mar 30, 2018 12:54 am

This is the section for ODROID XU3/XU4 which is a 32bit board and it automatically compiles for 32bit boards.

I've checked the code and both armhf (32bit) and arm64 (64bit) ARE supported, so it wouldn't even matter on which board you compile.
I needed to change one thing for arm64 and remove the -m64 option from the compiler options, aside from that everything was already there ready to be used.

In fact it was so simple to compile I already created packages for Debian Jessie and Debian Stretch both for armhf and arm64 which is now available on this and all my other images via apt-get install: viewtopic.php?p=219920#p219920
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby skyfly555 » Fri Mar 30, 2018 3:47 am

Meveric, thank you very much, you are amazing, I'm so impressed.

Thank you, and thank you again :)
skyfly555
 
Posts: 19
Joined: Sun Nov 15, 2015 8:44 am
languages_spoken: english
ODROIDs: None yet

Re: [OS] Debian Jessie

Unread postby jenja_c2 » Fri Apr 06, 2018 4:54 am

Hi all,
I am seeing issues, when updating (it is C2):
Code: Select all
root@orion:~# uname -a
Linux orion 3.14.79+ #1 SMP PREEMPT Sun Jul 23 00:04:44 CEST 2017 aarch64 GNU/Linux

root@orion:~# 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/"

root@orion:~# apt update -y && apt upgrade -y && apt dist-upgrade -y
<skipped>
Setting up linux-image-3.16.56+ (3.16.56-20180403-C2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/Image 3.16.56+ /boot/vmlinuz-3.16.56+
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.56+ /boot/vmlinuz-3.16.56+
run-parts: executing /etc/kernel/postinst.d/copy_dtb 3.16.56+ /boot/vmlinuz-3.16.56+
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.16.56+ /boot/vmlinuz-3.16.56+
update-initramfs: Generating /boot/initrd.img-3.16.56+
/etc/initramfs-tools/scripts/local-top/c2_init.sh: 25: /etc/initramfs-tools/scripts/local-top/c2_init.sh: fbset: not found
/etc/initramfs-tools/scripts/local-top/c2_init.sh: 26: /etc/initramfs-tools/scripts/local-top/c2_init.sh: fbset: not found
run-parts: executing /etc/kernel/postinst.d/rtc 3.16.56+ /boot/vmlinuz-3.16.56+
run-parts: failed to exec /etc/kernel/postinst.d/rtc: Exec format error
run-parts: /etc/kernel/postinst.d/rtc exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.56+.postinst line 391.
dpkg: error processing package linux-image-3.16.56+ (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-image-arm64-odroid-c2:
 linux-image-arm64-odroid-c2 depends on linux-image-3.16.56+; however:
  Package linux-image-3.16.56+ is not configured yet.

dpkg: error processing package linux-image-arm64-odroid-c2 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-3.16.56+
 linux-image-arm64-odroid-c2
E: Sub-process /usr/bin/dpkg returned an error code (1)

It looks like an issue with 3.14 -> 3.16 update. What is the workaround, please?
jenja_c2
 
Posts: 38
Joined: Sat Dec 17, 2016 6:53 pm
languages_spoken: english
ODROIDs: Odroid C2

Re: [OS] Debian Jessie

Unread postby jenja_c2 » Fri Apr 06, 2018 5:17 am

Hi again,
/etc/kernel/postinst.d/rtc was missing #!/bin/sh - added manually and apt went smoothly
jenja_c2
 
Posts: 38
Joined: Sat Dec 17, 2016 6:53 pm
languages_spoken: english
ODROIDs: Odroid C2

Re: [OS] Debian Jessie

Unread postby meveric » Fri Apr 06, 2018 6:36 am

glad you could solve the issue..
I'll check if I can fix the install script for that.
Please make sure to post in the C2 forum next time.
This is the forum for ODROID XU3/XU4-Series of ODROIDs which are very different from the C2.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby faragalla » Thu May 10, 2018 9:39 am

Image works great except that whenever I do an "apt-get update" I get the errors:

Err https://oph.mdrjr.net all/xu3 armhf Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Failed to fetch https://oph.mdrjr.net/meveric/dists/all ... f/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

I've tried "apt-get install -y ca-certificates git ufw apt-transport-https" but that did not resolve the problem. Anyone run into this error and has been able to solve it?
faragalla
 
Posts: 10
Joined: Sat Nov 28, 2015 9:51 am
languages_spoken: english
ODROIDs: XU4

Re: [OS] Debian Jessie

Unread postby meveric » Thu May 10, 2018 1:37 pm

In the past the above error only happened if time server was not working.. the certificates have validity date and if you do not have the correct time the server thinks the certificates are not valid.
Check the output of date to see if your date is correct. If the date is correct the certificate check should work fine.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby springs » Thu Jun 07, 2018 7:44 pm

hi all,

i'm aware that this version has been superseded by the new stretch version that meveric has released but i'm trying to get handbrake-cli installed if it's at all possible.

installing it through apt doesn't work for me and there doesn't seem to be a deb file for it?
springs
 
Posts: 13
Joined: Wed Jan 24, 2018 4:31 pm
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby meveric » Thu Jun 07, 2018 11:09 pm

sadly handbreak is not available on Debian Jessie, I've build it myself some time in the past, but never bothered uploading it.
On Debian Stretch though it's part of deb-multimedia and can be installed there.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby springs » Thu Jun 07, 2018 11:50 pm

ok thanks. I'll have to look at upgrading then soon
springs
 
Posts: 13
Joined: Wed Jan 24, 2018 4:31 pm
languages_spoken: english

Re: [OS] Debian Jessie

Unread postby mad_ady » Fri Jun 08, 2018 1:37 am

I have build instructions and packages for ubuntu on this thread: viewtopic.php?t=16863
User avatar
mad_ady
 
Posts: 4599
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1

Re: [OS] Debian Jessie

Unread postby jeastman53 » Sat Jul 28, 2018 1:48 pm

Thank you meveric, as a newbie I find this very hard.
I did download your file, uncompressed it (483mb vs 472), flashed it to my 16gb SD card, plugged into my -xu4 and nothing on the screen.
The odroid double blinks like it is running but nothing on screen especially no login.
What did I do wrong?
I realize I may be a year and a half out of sync but I would be interested to find out how to do this, anyone may comment.
Thanks,
Jeff
p.s. Ultimately, I want to put Q4OS on it and try Chrome browser to run Cryptotab and see if it works while I am learning this.
It runs Ubuntu but Cryptotab says it does not support Linux at this time.
So I keep running into brick walls with everything I try.
Just wondering if your software will get me there?
Many thanks,
jeastman53
 
Posts: 1
Joined: Sat Mar 03, 2018 2:41 pm
Location: Yelm WA
languages_spoken: english
ODROIDs: odroid-xu4

Re: [OS] Debian Jessie

Unread postby meveric » Sat Jul 28, 2018 3:38 pm

If the system is up and running (blue light blinking) it's probably an issue with the monitor/tv or the way you connected to it.
There are several options in the boot.ini file of the image to select different resolution that might be supported by your TV/Monitor or select an option if you're using a HDMI to DVI/VGA adapter.
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: 9200
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, N1, Go

Re: [OS] Debian Jessie

Unread postby dominic » Sun Jul 29, 2018 5:44 am

Hello,

tried to install php-imagick, but that failed with following message:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
php-imagick : Depends: libmagickcore-6.q16-3 (>= 8:6.9.6.8) but it is not going to be installed
Depends: libmagickwand-6.q16-3 (>= 8:6.9.6.8) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


I am on debian stretch. apt-get -f install shows no problems. When I try to install the depenendencies I just get the same error with their dependencies. Anyone an idea how to fix that?
dominic
 
Posts: 25
Joined: Thu Jul 20, 2017 12:16 am
languages_spoken: english

PreviousNext

Return to Other OS

Who is online

Users browsing this forum: No registered users and 1 guest