[OS] Debian Stretch

[prein]

Running on the C2 with the latest update/upgrade/dist-upgrade I encounter USB problems. Devices seem to disappear/reappear causing all sorts of problems

Here is part of /var/log/messages:

Code: Select all

Nov 20 21:14:31 localhost kernel: [11350.014624] usb 1-1.2: USB disconnect, device number 29
Nov 20 21:14:31 localhost kernel: [11350.019740] usb 1-1.2.1: USB disconnect, device number 30
Nov 20 21:14:31 localhost kernel: [11350.026359] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
Nov 20 21:14:31 localhost kernel: [11350.041205] ftdi_sio 1-1.2.1:1.0: device disconnected
Nov 20 21:14:31 localhost kernel: [11350.046575] usb 1-1.2.3: USB disconnect, device number 31
Nov 20 21:14:31 localhost kernel: [11350.051530] usb 1-1.2.3.1: USB disconnect, device number 32
Nov 20 21:14:32 localhost kernel: [11350.296419] usb 1-1.2: new full-speed USB device number 33 using dwc_otg
Nov 20 21:14:32 localhost kernel: [11350.396656] usb 1-1.2: not running at top speed; connect to a high speed hub
Nov 20 21:14:32 localhost kernel: [11350.404254] hub 1-1.2:1.0: USB hub found
Nov 20 21:14:32 localhost kernel: [11350.409677] hub 1-1.2:1.0: 4 ports detected
Nov 20 21:14:32 localhost kernel: [11350.786411] usb 1-1.2.1: new full-speed USB device number 34 using dwc_otg
Nov 20 21:14:32 localhost kernel: [11351.015256] ftdi_sio 1-1.2.1:1.0: FTDI USB Serial Device converter detected
Nov 20 21:14:32 localhost kernel: [11351.021628] usb 1-1.2.1: Detected FT232RL
Nov 20 21:14:32 localhost kernel: [11351.026554] usb 1-1.2.1: Number of endpoints 2
Nov 20 21:14:32 localhost kernel: [11351.031377] usb 1-1.2.1: Endpoint 1 MaxPacketSize 64
Nov 20 21:14:32 localhost kernel: [11351.036091] usb 1-1.2.1: Endpoint 2 MaxPacketSize 64
Nov 20 21:14:32 localhost kernel: [11351.040799] usb 1-1.2.1: Setting MaxPacketSize 64
Nov 20 21:14:32 localhost kernel: [11351.045842] usb 1-1.2.1: FTDI USB Serial Device converter now attached to ttyUSB1
Nov 20 21:14:33 localhost kernel: [11351.246362] usb 1-1.2.3: new full-speed USB device number 35 using dwc_otg
Nov 20 21:14:33 localhost kernel: [11351.466688] usb 1-1.2.3: not running at top speed; connect to a high speed hub
Nov 20 21:14:33 localhost kernel: [11351.474030] hub 1-1.2.3:1.0: USB hub found
Nov 20 21:14:33 localhost kernel: [11351.478957] hub 1-1.2.3:1.0: 4 ports detected
Nov 20 21:14:33 localhost kernel: [11351.876338] usb 1-1.2.3.1: new full-speed USB device number 36 using dwc_otg
Nov 20 21:14:34 localhost kernel: [11352.105689] cdc_acm 1-1.2.3.1:1.0: ttyACM1: USB ACM device

How can I debug the problem?

[LucGIS]

My apt seems to be stuck on an kernel error. Anyone knows how to solve this?

Code: Select all

# apt-get update 
Ign:1 http://ftp.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease
Hit:3 http://ftp.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.debian.org/debian stretch-backports InRelease
Hit:5 http://ftp.debian.org/debian stretch-proposed-updates InRelease
Hit:6 http://ftp.debian.org/debian stretch Release                               
Hit:9 https://download.docker.com/linux/debian stretch InRelease                 
Hit:7 https://oph.mdrjr.net/meveric all InRelease
Hit:8 https://oph.mdrjr.net/meveric stretch InRelease
Reading package lists... Done

# apt-get upgrade 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_TIME = "en_GB.utf8",
	LC_MONETARY = "en_GB.utf8",
	LC_MEASUREMENT = "en_GB.utf8",
	LC_NUMERIC = "en_GB.utf8",
	LC_PAPER = "en_GB.utf8",
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
Setting up linux-image-3.16.75+ (3.16.75-20191021-C2) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/Image 3.16.75+ /boot/vmlinuz-3.16.75+
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.75+ /boot/vmlinuz-3.16.75+
run-parts: executing /etc/kernel/postinst.d/copy_dtb 3.16.75+ /boot/vmlinuz-3.16.75+
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.16.75+ /boot/vmlinuz-3.16.75+
update-initramfs: Generating /boot/initrd.img-3.16.75+
E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.16.75+ with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.75+.postinst line 391.
dpkg: error processing package linux-image-3.16.75+ (--configure):
 subprocess installed post-installation script returned error exit status 2
Setting up linux-image-3.16.82+ (3.16.82-20200317-C2) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/Image 3.16.82+ /boot/vmlinuz-3.16.82+
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.82+ /boot/vmlinuz-3.16.82+
run-parts: executing /etc/kernel/postinst.d/copy_dtb 3.16.82+ /boot/vmlinuz-3.16.82+
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.16.82+ /boot/vmlinuz-3.16.82+
update-initramfs: Generating /boot/initrd.img-3.16.82+
E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.16.82+ with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.82+.postinst line 391.
dpkg: error processing package linux-image-3.16.82+ (--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.82+; however:
  Package linux-image-3.16.82+ 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.75+
 linux-image-3.16.82+
 linux-image-arm64-odroid-c2
E: Sub-process /usr/bin/dpkg returned an error code (1)

[meveric]

not sure why, but it seems the script is somehow broken now, but I don't know why.
You can fix it manually if you change the file:

/usr/share/initramfs-tools/hooks/zz-busybox-initramfs

and exchange:
BB_BIN=/bin/busybox
to
BB_BIN=/usr/lib/initramfs-tools/bin/busybox

this should fix it.
Why it's suddenly broken, I don't know.
I'll see if I can fix the package without breaking anything else.

[LucGIS]

I did something really stupid, because I was trying to fix it myself too :s

Now my ODROID won't boot. Is there any chance on fixing it when mounted on a laptop Linux OS? I can see the boot partition, it has the following files:

Code: Select all

-rw-r--r--  1     6833 May 12 21:53 boot.ini
-rw-r--r--  1     2696 Jan  1  1980 boot.ini~
-rw-r--r--  1     6807 Nov 22 15:32 boot.ini.orig
-rw-r--r--  1      315 Jun 19  2017 boot.ini.rej
-rw-r--r--  1   114064 Oct 21  2019 config-3.16.75+
-rw-r--r--  1   114065 Mar 17 18:23 config-3.16.82+
drwxr-xr-x  2     2048 Nov 18  2016 .fseventsd
-rw-r--r--  1 13810608 May 12 22:42 Image
-rw-r--r--  1  4605034 May 12 22:42 initrd.img-3.16.75+
-rw-r--r--  1  4605239 May 12 22:42 initrd.img-3.16.82+
-rw-r--r--  1    30004 Mar 17 18:52 meson64_odroidc2.dtb
drwxr-xr-x  4     2048 Nov 18  2016 .Spotlight-V100
-rw-r--r--  1  3094852 Oct 21  2019 System.map-3.16.75+
-rw-r--r--  1  3095343 Mar 17 18:51 System.map-3.16.82+
-rw-r--r--  1  4605303 May 12 22:42 uInitrd
-rw-r--r--  1  4018339 Mar 18  2018 uInitrd-3.14.79+
-rw-r--r--  1  4024629 May  3  2018 uInitrd-3.16.55+
-rw-r--r--  1  4605098 May 12 22:42 uInitrd-3.16.75+
-rw-r--r--  1  4605303 May 12 22:42 uInitrd-3.16.82+
-rw-r--r--  1 13794224 Oct 21  2019 vmlinuz-3.16.75+
-rw-r--r--  1 13810608 Mar 17 18:51 vmlinuz-3.16.82+

[meveric]

I think it's missing the Image.gz file and instead has just the Image file.
I think you can just do a gzip -9 Image and it should boot again.
rest seems to be fine.

[LucGIS]

Hi meveric,

Thanks for your quick replies.

I did as you told and gzipped the Image.
Connected the emmc on the ODROID C2
Powered on, but it seems to hang again.
I tried to connect the ODROID to an external monitor, so I can have some more insight on what is going on and where it might have a problem during boot.

I was trying to check the /var/log/boot.log but the file is not there.

Any more ideas on how to check what is going on, so I (we) can fix it ?

[meveric]

/var/log/syslog should be more helpful but I'm not sure if it's already mounted at that boot stage.

I can probably pack and upload the content of my bootfs somewhere so you can replace what's on yours hopefully that will fix it.

[LucGIS]

Hi,

That would be great!

Cheers

[LucGIS]

/var/log/syslog should be more helpful but I'm not sure if it's already mounted at that boot stage.

I can probably pack and upload the content of my bootfs somewhere so you can replace what's on yours hopefully that will fix it.

Hi meveric,

I hope you are still willing to help me out here

Cheers

[meveric]

Hi LucGIS
sorry it took me so long but I've uploaded the files:
https://oph.mdrjr.net/meveric/other/C2/boot.tar.xz

They look very similar the what you have so I wonder if that's really the issue here.
I still suggest making a backup of your files first, just in case.

[LucGIS]

Hi meveric,

It worked. My ODROID C2 booted and Dockers started running again

Thank!

Cheers,

Luc

[LucGIS]

But my hwclock is not working Dokcer is running for years it says on docker ps

# date
Wed May 20 17:06:51 CEST 2020

# hwclock --show
hwclock: ioctl(RTC_RD_TIME) to /dev/rtc to read the time failed: Input/output error

# hwclock --systohc
hwclock: ioctl(RTC_RD_TIME) to /dev/rtc to read the time failed: Input/output error
hwclock: ioctl(RTC_SET_TIME) to /dev/rtc to set the time failed.: Input/output error

Any thoughts?

[meveric]

You probably have to activate clock again, as it needs to add some stuff on the Kernel, which I did not on my image.
Use the setup-odroid tool to activate RTC, not sure if it works it's been a while since I tested it.

[nas27]

Hi Meveric,

Is there any prospect of a Buster image for the C2?

Now I've got the C4 working really well as a desktop with your help, I'd like to repurpose my old C2, but exactly what it ends up doing depends on whether it can stay up to date for a while.

Just thought I'd ask...
Thanks and regards,
Nick

[meveric]

most of the stuff for Debian Buster should already be available.

I have to check on fbturbo for X11 and Kodi which will be the most complicated.
Generelly it should be possible to use C2 with Buster as well, although the Kernel is rather old and might cause issues.
I have to test this.

[nas27]

Ah, thank you, that sounds hopeful then.

Regards,
Nick

[rondnelson]

I'm working on setting up a server that also plays media with kodi on my C2. I was using your Jessie image previously but since Jessie is unsupported now I needed to upgrade, and I thought I would just start over with this image. Before, I had a MATE installation that Kodi just automatically ran on top of, but I figure a better method would be to just have a minimal X11 server that kodi would run on. Is this easy to do? Of course the "install desktop" option in setup-odroid has to install an entire desktop, and skipping that and just using "install kodi" resulted in an instance of kodi that failed to start. I assume that's because Kodi requires X11 or some other thing that "install desktop" installs. I imagine I would just need to install a few of your packages to get a "minimal" kodi working, but I have to clue where to start.
Thanks,
Ron

[meveric]

if you installed Kodi via setup-odroid most of the tasks are done already, you only need to setup the DDX and install the X-Server itself if I remember correctly:

Code: Select all

apt-get install -y xf86-video-fbturbo-odroid libump-odroid xinit sudo
cp /usr/local/share/setup-odroid/xorg/c2/fbturbo/xorg.conf /etc/X11

You should also create a user and not using root directly as this may cause issues with Kodi and is also less secure.

Once everything is installed it "should" work with:

Code: Select all

sudo xinit /bin/sh -c "sudo -u odroid /usr/local/bin/kodi"

assuming your regular user is called "odroid", else replace it with whatever user you created.

[rondnelson]

Maybe I'm wrong but I think there's something going wrong with the "install kodi" button in setup-odroid. When I run it, it doesn't actually install kodi-odroid, although it does install some other things. it also throws out this: /usr/local/sbin/setup-odroid: line 506: [: -ne: unary operator expected Looking the the script, I can see why a typo there could make it skip installing kodi, but I have no idea how to fix it.

Installing kodi-odroid with apt results in this error from xinit:

Code: Select all

xinit: unable to run server "X": No such file or directory
Use the -- option, or make sure that /usr/bin is in your path and
that "X" is a program or a link to the right type of server
for your display.  Possible server names include:

    Xorg        Common X server for most displays
    Xvfb        Virtual frame buffer
    Xfake       kdrive-based virtual frame buffer
    Xnest       X server nested in a window on another X server
    Xephyr      kdrive-based nested X server
    Xvnc        X server accessed over VNC's RFB protocol
    Xdmx        Distributed Multi-head X server

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

I then tried installing xserver-xorg-core. I'm not sure if that was the right thing to do or not. Then the xinit error changed to this:

Code: Select all

X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-8-arm64 aarch64 Debian
Current Operating System: Linux odroid-stretch64 3.16.85+ #1 SMP PREEMPT Tue Jun 30 19:02:35 CEST 2020 aarch64
Kernel command line: coherent_pool=2M root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro consoleblank=0 console=ttyS0,115200n8 console=tty0 no_console_suspend  hdmimode=1080p60hz m_bpp=32 vout= fsck.repair=yes elevator=noop disablehpd=true  max_freq=1536 maxcpus=4 monitor_onoff=false disableuhs=false mmc_removable=true usbmulticam=false usbhid.quirks=0x0eef:0x0005:0x0004 net.ifnames=0
Build Date: 03 November 2018  03:03:37AM
xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug  4 16:14:54 2020
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module mali_drm not found in directory /lib/modules/3.16.85+
xinit: Unable to run program "xterm": No such file or directory
Specify a program on the command line or make sure that /usr/bin
is in your path.

xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

I imagine all these errors are the result of setup-odroid skipping the installation of some of these packages. Is that the case?
Thanks for being so helpful!

[meveric]

I checked the code and it's just checking if the fbdev variable is 1 or not, problem here is that it may not be set, but I can easily fix that.
Still in worst case it only does not install kodi-odroid itself, that is not a big deal, if you install it later on.
So the install and setup process still continues.
So no, this is not the result of the setup tool not installing some packages.

Overall the program complains about the command you give with xinit:

Code: Select all

xinit: Unable to run program "xterm": No such file or directory
Specify a program on the command line or make sure that /usr/bin
is in your path.

Here it says you tried to run the program "xterm" which is not installed.
So My guess is you are using the wrong command line option to run xinit.
But since you did not include the command that you typed to start xinit or kodi, there is very little that I can say what you might have done wrong.

Edit:
I just tested it on my C2 and could start it with:

Code: Select all

sudo xinit /bin/sh -c "sudo -u odroid /usr/local/bin/kodi"

Can you try that again please?

[rondnelson]

Thanks! I was able to get Kodi to start and audio was working, so that's great. However, when hardware decoding is turned on, I was getting that black screen issue I've seen talked about here before. The video I was trying to watch was 480p in MPEG4 format which by default had hardware acceleration disabled. This worked okay but it had screen tearing issues that I'd like to avoid if possible. I assumed it was off by default because it would work well enough on most PCs in software, but if it's because it causes issues with the amlogic decoder that's understandable. Earlier I tried installing MATE through setup-odroid before installing Kodi and it had the same issue, so it doesn't seem to be caused by the whole no desktop environment thing. You said a few pages ago that you used some alpha-blending hack hardkernel made to fix that. Is that fix published?

[meveric]

it should be part of the kodi starting script.
If you check /usr/local/bin/kodi it should have some lines at the beginning that does the Alpha Hack.
I "only" tested a H265 video with hardware decoder when I tried to start without desktop.. that went fine without issues, no tearing or anything.

I'm also not aware of any issues with MPEG4 format and hardware decoder... basically MPEG4/H264 and H265 are the only ones that are really supported.
Others like MPEG2 may cause issues, but I thought MPEG4 was pretty much stable with hardware decoder.

[rondnelson]

Thanks for your patience with me. I tried the 1080p60 H.264 sample from https://kodi.wiki/view/Samples and it had the exact same issue: black screen, can be solved by disabling hardware acceleration in kodi settings, but that causes skipped frames and tearing of course. One other thing I noticed was that when in the slightly transparent menu the video was ever-so-slightly visible in the background. Ridiculously faint, fainter than it was supposed to be, but definitely there. I could only notice it because of the simple, high-contrast white-on-black bars in the sample video, but once I knew it was there, I could see it on the other MPEG4 video too. The fact that it was revealed by transparent items on top of the video seems to suggest that it might be related to the alpha hack but It's not like I would have any idea. I can confirm that the hack is in /usr/local/bin/kodi and the if statement is getting triggered (I tried putting an echo to the console in there, and it showed up.) At this point if you have anything else you think might help I'd love to try it but it seems like you're unable to reproduce any issues. It seems really odd to me though. I can't imagine how my install could differ much from yours. Do you think a different SD card could make a difference?

[adelias]

I'm trying to compile mpd and have run into the following:
fatal error: string_view: No such file or directory

Any idea how to get past this?

[meveric]

string_view seems to be part of the boost package.
I suggest installing libboost-all-dev and try again.

[adelias]

Thanks, but I'm still getting that error after installing libboost-all-dev.

I just noticed that the mpd requirements state:
a C++14 compiler (e.g. GCC 8 or clang 5)

[adelias]

Any news on a Buster image for the C2?

[meveric]

Currently not I'm not sure the default Kernel 3.16 can handle buster... I have to test could be the Kernel is too old.
You can try Armbian which comes with newer Kernel, but may not have all hardware support as the default Kernel has.

[domoggvad]

Hello I have 3 Odroid C2, but by burning a buster, all three have the same mac address, would you have a solution to modify this problem?
thank you

[meveric]

well since that Debian Buster is not from me, I don't know exactly what is the issue, as on my image with Kernel 3.16 each device has it's own mac address.
Check the boot.ini or whatever you use and see if it has an entry for MAC address... if you make sure that you set different for each board.

Some of the newer Kernel offer the ability to set your own MAC rather than using the one from the actual adapter. If your image does this, than you have to manually modify it.

But once again, not related to my work.

[domoggvad]

Is your image that of the first post?
thank you

[meveric]

yes it is, but please keep in mind it's Debian 9 (Stretch) not Debian Buster.
It should be possible to upgrade to Buster though.

[domoggvad]

Hello
I just did it with your image, but weird, I still have the same mac address on my 3 C2s, yet I made a diskpart, clean to empty the emmc card, and it's identical the same MAC address 00 : 1E: 06: 33: d5: 59
Thank you

[meveric]

let me check what the MAC of my C2 looks like.. if it's the same, then it might be an issue.

Edit: nope I can not confirm that. The MAC on my C2 is a different one, so it shouldn't be an issue with the image.
Either your ODROIDs really have the same MAC (which would be odd) or it's some leftover of the other image you were using.. maybe something with the u-boot.

[domoggvad]

thank you for your investigation