[OS] Debian Stretch

Nelars · Post by **Nelars** » Mon Mar 18, 2019 12:59 am

Hi Meveric,

Any chance you could update OpenVPN to 2.4.7 in your repository?
It still is at 2.4.0.
Thank you!

meveric · Post by **meveric** » Mon Mar 18, 2019 1:57 am

first of all openvpn does not come from "my" repository but from official Debian Stretch repository, it's not touched by me.
secondly, aside from the 2.4.0 which is the standard for Debian Stretch 2.4.7 is available from stretch-backports:

Code: Select all

apt-cache policy openvpn
openvpn:
  Installed: (none)
  Candidate: 2.4.0-6+deb9u3
  Version table:
     2.4.7-1~bpo9+1 100
        100 http://ftp.debian.org/debian stretch-backports/main armhf Packages
     2.4.0-6+deb9u3 500
        500 http://ftp.debian.org/debian stretch/main armhf Packages
     2.4.0-6+deb9u1 500
        500 http://security.debian.org/debian-security stretch/updates/main armhf Packages

so there is no need for me to port anything, as it's already available in official Debian Stretch repositories.

nn_m · Post by **nn_m** » Tue Mar 19, 2019 2:43 am

I'm having to reinstall to a new uSD card. There doesn't seem to be anything obviously wrong with the old uSD card. I can mount and view all the files and logfiles on another linux computer, and don't see any crash imfo. There is plenty of free space on the disk. When I start up with this crashed uSD card, I never get a beeping blue light, it just stays steady on (or not all, the last time I tried, I think!) . Oh well ;- )

Now that I'm reinstalling, I'm going with the XFCE desktop, and have watched the installer run for 1/2 hour or so.

How long should I expect this install to take?

Also, Is there a preferred TERM value I should be using on my local ssh client (not putty). The current TERM value (vt100) is displaying the graphic chars for the menu/installer as a triple-wide char, for example, `öΓöé` are the chars that form the border at the left margin of the status window. That is from a copy/paste. On the screen, they look like `hPhr` but the r is not a standard US char.

Ah, now I noticed that because of my buggy border, the status messages like `Preparing libperl5.24 (armhf)` are hidden in the funky border. AND I notice that the green status bar is changing to grey and moving to the right some more. I am **making progress** ;- ) .

I guess this is more of a feedback message, rather than anything requiring help.

Cheers!

Update : ~ 4 hrs later, Stuck on Preparing python3-pil (armhf) and progress show 51%.

Code: Select all

/usr/bin/perl -w /usr/share/debconf/frontend /usr/bin/debconf-apt-progress ....

among others, shows up at the top of htop output.

Just going to let it keep running

Update : - 5 mins later. Now we're at 89%. I guess it knew I was writing about it ;- )

meveric · Post by **meveric** » Tue Mar 19, 2019 6:47 am

nn_m wrote: ↑
Tue Mar 19, 2019 2:43 am
I'm having to reinstall to a new uSD card. There doesn't seem to be anything obviously wrong with the old uSD card. I can mount and view all the files and logfiles on another linux computer, and don't see any crash imfo. There is plenty of free space on the disk. When I start up with this crashed uSD card, I never get a beeping blue light, it just stays steady on (or not all, the last time I tried, I think!) . Oh well ;- )

solid blue led normally means that it did not load the kernel correctly.
using a UART is the best way to debug this.

nn_m wrote: ↑
Tue Mar 19, 2019 2:43 am
Now that I'm reinstalling, I'm going with the XFCE desktop, and have watched the installer run for 1/2 hour or so.

Not sure how good XFCE will perform, but let me know how it turns out.

nn_m wrote: ↑
Tue Mar 19, 2019 2:43 am
How long should I expect this install to take?

this highly depends on the quality of the media, eMMC can be quite fast and an installation could be done within 15~25min.
SD card can be a lot slower, depending on the write speed it can take several hours

I often move the OS to an HDD before I start doing serious stuff with it.

nn_m wrote: ↑
Tue Mar 19, 2019 2:43 am
Also, Is there a preferred TERM value I should be using on my local ssh client (not putty). The current TERM value (vt100) is displaying the graphic chars for the menu/installer as a triple-wide char, for example, `öΓöé` are the chars that form the border at the left margin of the status window. That is from a copy/paste. On the screen, they look like `hPhr` but the r is not a standard US char.

hmm not sure never had an issue with that. on putty I had to change the defaults to get correct boarders, but I haven't much experience with other SSH clients, cygwin maybe but that should work out of the box.
I normally use my Linux Laptop for everything, so SSH is Linux to Linux, never had to change anything on the settings.

nn_m wrote: ↑
Tue Mar 19, 2019 2:43 am
Ah, now I noticed that because of my buggy border, the status messages like `Preparing libperl5.24 (armhf)` are hidden in the funky border. AND I notice that the green status bar is changing to grey and moving to the right some more. I am **making progress** ;- ) .

I guess this is more of a feedback message, rather than anything requiring help.

Cheers!

Update : ~ 4 hrs later, Stuck on Preparing python3-pil (armhf) and progress show 51%.
Code: Select all
/usr/bin/perl -w /usr/share/debconf/frontend /usr/bin/debconf-apt-progress ....
among others, shows up at the top of htop output.

Just going to let it keep running

Update : - 5 mins later. Now we're at 89%. I guess it knew I was writing about it ;- )

Hope it finished by now

Yes SD card can be painfully slow.

pdobrien3 · Post by **pdobrien3** » Sun Mar 24, 2019 10:00 pm

I am getting this error when I try to update/upgrade. Any help greatly appreciated. Also getting an error of the desktop about no room left. I have a 32 g emmc.

Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130) ...
ln: failed to create hard link '/boot/initrd.img-4.14.107+.dpkg-bak' => '/boot/initrd.img-4.14.107+': Operation not permitted
cp: error writing '/boot/initrd.img-4.14.107+.dpkg-bak': No space left on device
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

meveric · Post by **meveric** » Sun Mar 24, 2019 10:15 pm

That is the important part.

pdobrien3 wrote: ↑
Sun Mar 24, 2019 10:00 pm
cp: error writing '/boot/initrd.img-4.14.107+.dpkg-bak': No space left on device

You boot partition ran full. Check /boot for old files that have not 107+ in their name and delete them.

pdobrien3 · Post by **pdobrien3** » Sun Mar 24, 2019 10:37 pm

Edit: Ok, I think I figured it out. I cd to /boot and removed files with 102+

After an apt-get update/upgrade, I got this error:

ln: failed to create hard link '/boot/initrd.img-4.14.107+.dpkg-bak' => '/boot/initrd.img-4.14.107+': Operation not permit

It looks like it did in fact complete though?

Thanks

meveric · Post by **meveric** » Mon Mar 25, 2019 5:28 am

pdobrien3 wrote: ↑
Sun Mar 24, 2019 10:37 pm
ln: failed to create hard link '/boot/initrd.img-4.14.107+.dpkg-bak' => '/boot/initrd.img-4.14.107+': Operation not permit

This error can be ignored, it tries to create a backup, but that's not possible since the boot partition is a fat32 partition so it can be accessed from Windows to allow changes to boot.ini and other things.
And since fat32 does not support linux hard links this operation fails.
It's no big deal and can be ignored.

Nelars · Post by **Nelars** » Thu Apr 04, 2019 10:13 pm

meveric wrote: ↑
Mon Mar 18, 2019 1:57 am
first of all openvpn does not come from "my" repository but from official Debian Stretch repository, it's not touched by me.
secondly, aside from the 2.4.0 which is the standard for Debian Stretch 2.4.7 is available from stretch-backports:
Code: Select all
...
so there is no need for me to port anything, as it's already available in official Debian Stretch repositories.

Meveric, thank you for the tip!

Bernini · Post by **Bernini** » Fri Apr 05, 2019 2:50 am

meveric wrote: ↑
Mon Mar 25, 2019 5:28 am

pdobrien3 wrote: ↑
Sun Mar 24, 2019 10:37 pm
ln: failed to create hard link '/boot/initrd.img-4.14.107+.dpkg-bak' => '/boot/initrd.img-4.14.107+': Operation not permit
This error can be ignored, it tries to create a backup, but that's not possible since the boot partition is a fat32 partition so it can be accessed from Windows to allow changes to boot.ini and other things.
And since fat32 does not support linux hard links this operation fails.
It's no big deal and can be ignored.

I thought there was a technical reason for /boot being FAT32. So I could e.g. turn it into an EXT4 partition without any issues (besides the need to update UUIDs and whatnot)?

meveric · Post by **meveric** » Fri Apr 05, 2019 2:58 am

Bernini wrote: ↑
Fri Apr 05, 2019 2:50 am
I thought there was a technical reason for /boot being FAT32. So I could e.g. turn it into an EXT4 partition without any issues (besides the need to update UUIDs and whatnot)?

I'm not sure about this, as the uboot must support booting from ext4 as well, and since i'm using the uboot from hardkernel I can not tell if ext4 boot is supported from uboot or not.

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 4:14 am

Hi @Meveric,

After the latest update (the one where 'setup-odroid' package was updated), I noticed there were some errors. It seemed to relate to my /boot directory being full, so I used 'sudo apt autoremove --purge' to declutter, and then the update executed successfully. At the time I didn't reboot.

A week or so later, I needed to reboot and now my system is broken.

I am presented with Control-D message to enter maintenance mode, and I'm getting errors relating to:

"Direct firmware load for s5p-mfc-v8.fw failed with error -2"

...and:

"Firmware is not present in the /lib/firmware directory nor compiled in the kernel"

I am typing this out manually, as I am unable to copy and paste the exact error log at this moment in time.

Can you advise?

The odroid on which Debian is installed needs to be on 24/7, and it's currently down.

This site seems to suggest I need to put s5p-mfc*.fw files into /lib/firmware/s5p-mfc/ folder:

https://github.com/voidlinux/void-packages/issues/810

Thank you, as ever.

meveric · Post by **meveric** » Fri Apr 05, 2019 4:22 am

First of all, ignore all errors about "sp5-mfc" do not try to fix any of this as you are more likely to break anything.
It's only required for hardware decoding videos anyway, so if you don't use Kodi you can ignore it all together.

The real issue probably is/was the message about the full /boot partition... autoremove --purge doesn't help that often, and it's likely that you might not actually have succeeded with the update afterall.
It's normally easier to delete the file in /boot manually that are not for the current version of the kernel, as they are not needed. that way you free space and the update procedure can continue.
It's hard to tell what's the current state or issue.

Can you show me the content of the /boot partition? Maybe from a different system?
I'd need to see the file names and sizes (in byte) to give an estimation on what could be the issue.

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 4:31 am

I can get in from root, so I'm typing this out:

/boot# ls

boot.ini
config-4.14.102+
config-4.14.107+
exynos5422-odroidhc1.dtb
exynos5422-odroidxu3.dtb
exynos5422-odroidxu3-lite.dtb
exynos5422-odroidxu4.dtb
exynos5422-odroidxu4-kvm.dtb
initrd.img-4.14.102+
initrd.img-4.14.107+
System.map-4.14.102+
System.map-4.14.107+
uInitrd
uInitrd-4.14.102+
uInitrd-4.14.107+
uInitrd-4.14.94+
vmlinuz-4.14.102+
vmlinuz-4.14.107+
zImage

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 4:35 am

Sorry, half a job...more to follow (sizes).

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 4:39 am

/boot# ls

9959 boot.ini
150961 config-4.14.102+
150961 config-4.14.107+
56387 exynos5422-odroidhc1.dtb
63513 exynos5422-odroidxu3.dtb
62458 exynos5422-odroidxu3-lite.dtb
63484 exynos5422-odroidxu4.dtb
63628 exynos5422-odroidxu4-kvm.dtb
5983698 initrd.img-4.14.102+
5983825 initrd.img-4.14.107+
2698865 System.map-4.14.102+
2699227 System.map-4.14.107+
5983762 uInitrd
5983762 uInitrd-4.14.102+
5983806 uInitrd-4.14.107+
5983811 uInitrd-4.14.94+
5683040 vmlinuz-4.14.102+
5684968 vmlinuz-4.14.107+
5684968 zImage

<bytes> <filename>

Does that help?

meveric · Post by **meveric** » Fri Apr 05, 2019 4:55 am

ok, from the sizes you can see the update was not completed:
5983762 uInitrd
5983762 uInitrd-4.14.102+
5983806 uInitrd-4.14.107+
So uInitrd is still 4.14.102+

5683040 vmlinuz-4.14.102+
5684968 vmlinuz-4.14.107+
5684968 zImage
while zImage has the size of 4.14.107, so the Kernel and the initramdisk do not match.

As it's more likely that the 107 is not working correctly, I'd suggest copy the vmlinuz-4.14.102+ over zImage (it's the same file just renamed)
and the system should be able to boot again. After that try to install the Kernel again.
In worst case do a apt install --reinstall linux-image-4.14.107+

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 5:06 am

Thank you for the prompt assitance!

I did:

cp vmlinuz-4.14.102+ zImage

...and can now verify file sizes for these two files are identical. About to reboot!

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 5:12 am

Unfortunately, that didn't work, even after hard-reboot.

So:

apt install --reinstall linux-image-4.14.107+

...and reboot.

Sadly, that did not work either.

meveric · Post by **meveric** » Fri Apr 05, 2019 5:17 am

The reinstall only works if the system is able to boot again.
I'm confused why this shouldn't work.
All files are in place and the system should be able to work, unless the rootfs is somehow damaged.
The bootfs seems fine though, only boot.ini uInitrd and zImage are used for booting, as well as the dtb file of your system (most likely xu4).
So since all of this is in place I wonder if the rootfs is somehow damaged.

Are you able to access the rootfs as well?
If so can you check under /lib/modules if there's a folder for 4.14.102+ and/or 4.14.107+ ?

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 5:23 am

Actuallly, my bad! It works fine now.

I had some external USB drives in my fstab, which were no longer connected to the odroid, so once I'd commented them out and rebooted again the odroid kicked back into life.

Thanks Meveric. You are a great help as always.

So, now I want rid of everything not '4.14.107+' from /boot, can I just delete all the '4.14.102+' items?

Naturally I'd like to be able to avoid a full /boot in future, so I can do some preventative maintenance.

meveric · Post by **meveric** » Fri Apr 05, 2019 5:32 am

yes you can delete everything that has 4.14.102+ in the name if you're now running on 107+

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 5:36 am

Awesome sauce! Thanks.

Yes, uname -r reports I'm running 107+, so I'll get deleting.

For anyone else who might read this:

cd /boot
ls *102+ <--Good safety test
sudo rm *102+ <--Deletes everything ending in 102+

Thanks again.

meveric · Post by **meveric** » Fri Apr 05, 2019 5:46 am

glad everything is working again for you

tedrogers · Post by **tedrogers** » Fri Apr 05, 2019 5:47 am

You've cheered me right up! Spreading your joy, as you have done. Can't thank you enough.

All the best.

MichaIng · Post by **MichaIng** » Wed Apr 10, 2019 5:00 am

@meveric
We recognized your server + repo is currently down. I guess you are already on that, however just wanted to mention.

Since we switch to our European mirror on DietPi images, we only recognized since one APT sources drop-in was not added as https:// but http://:
- On this Odroid XU4 Stretch image /etc/apt/sources.list.d/meveric-all.list contains "deb http://oph.mdrjr.net/meveric all main testing" where I think it was intended to be https:// like the others? No harm at all, just a tiny one to perhaps adjust on next image update

.

Many thanks for the great work and happy sunny days.

meveric · Post by **meveric** » Wed Apr 10, 2019 5:13 am

MichaIng wrote: ↑
Wed Apr 10, 2019 5:00 am
@meveric
We recognized your server + repo is currently down. I guess you are already on that, however just wanted to mention.

Actually it's not my server but the server of @mdrjr and I hope he will have it fixed soon.

MichaIng wrote: ↑
Wed Apr 10, 2019 5:00 am
Since we switch to our European mirror on DietPi images, we only recognized since one APT sources drop-in was not added as https:// but http://:
- On this Odroid XU4 Stretch image /etc/apt/sources.list.d/meveric-all.list contains "deb http://oph.mdrjr.net/meveric all main testing" where I think it was intended to be https:// like the others? No harm at all, just a tiny one to perhaps adjust on next image update .

Many thanks for the great work and happy sunny days.

Thanks for the note about http vs https, although it doesn't makes much of a difference as there is a permanent redirect from http to https, but I guess when changing the sources with a sed command, it's easy to miss that one that is still having http in it's list.
I'll probably add it on the next update of setup-odroid to make sure http://oph.mdrjr.net is replaced with https://oph.mdrjr.net in case I missed it somewhere else.
Thanks for the info!

Post by **odroid** » Wed Apr 10, 2019 9:24 am

Really sorry about that.
We need another 50 hours to fix our server issue.

jenja_c2 · Post by **jenja_c2** » Wed Apr 10, 2019 5:12 pm

Hi,
I've been seeing this during last two days:

et:35 http://ftp.debian.org/debian stretch-backports/main Translation-en 2019-04-09-2011.39.pdiff [33 B]
Err:36 http://oph.mdrjr.net/meveric all InRelease
Could not connect to oph.mdrjr.net:80 (216.155.157.42), connection timed out
Err:37 http://oph.mdrjr.net/meveric stretch InRelease
Unable to connect to oph.mdrjr.net:http:

Does anyone know whether oph.mdrjr.net has moved?

Post by **odroid** » Wed Apr 10, 2019 5:40 pm

The server has some issues.
We need another 40~50 hours to fix our server problem.

aberrio · Post by **aberrio** » Wed Apr 10, 2019 10:17 pm

aberrio wrote: ↑
Fri Jan 04, 2019 2:11 am
Hi,

The old image on the system works fine no problem booting from HDD but as long I upgrade the image cause the problem, looks that the upgraded image did not wait until HDD is ready but adding the rootdelay fix the problem.

One more question , editing boot.ini in another system should work fine? or I need to update the UUI and boot from sd and do the process again without formatting HDD to preserve data on it?

Thx for you reply

HI,

I back to this issue, the rootdelay works fine on XU4 but does not work on HC2 boards. I just tried the Ubuntu image and work fine after update/upgrade/distupgrade.

What log file do you need information from to solve Debian problem?

Regards,

Al

meveric · Post by **meveric** » Thu Apr 11, 2019 3:17 am

Good question... the best log would be the output of UART when you boot the image. That's the only log that includes all information about the boot process.
I'm afraid every other log only works after the image was booted from HDD. So there's no log that will hold the issue of the HDD not booting correctly, as that log would be placed on the HDD.

stevedev · Post by **stevedev** » Fri Apr 12, 2019 9:37 am

Mev, your site down or move? Can't pull updates at this time. Been really appreciative of this image and hope things are still running.. Thx.

Code: Select all

8 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch https://oph.mdrjr.net/meveric/dists/all/InRelease  Connection timed out after 120000 milliseconds
W: Failed to fetch https://oph.mdrjr.net/meveric/dists/stretch/InRelease  Connection timed out after 120001 milliseconds

aberrio · Post by **aberrio** » Fri Apr 12, 2019 11:26 am

meveric wrote: ↑
Thu Apr 11, 2019 3:17 am
Good question... the best log would be the output of UART when you boot the image. That's the only log that includes all information about the boot process.
I'm afraid every other log only works after the image was booted from HDD. So there's no log that will hold the issue of the HDD not booting correctly, as that log would be placed on the HDD.

This mean that we are not able to have the UART's output unless is created on the SD card?

Regards,

meveric · Post by **meveric** » Fri Apr 12, 2019 2:20 pm

stevedev wrote: ↑
Fri Apr 12, 2019 9:37 am
Mev, your site down or move? Can't pull updates at this time. Been really appreciative of this image and hope things are still running.. Thx.
Code: Select all
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch https://oph.mdrjr.net/meveric/dists/all/InRelease  Connection timed out after 120000 milliseconds
W: Failed to fetch https://oph.mdrjr.net/meveric/dists/stretch/InRelease  Connection timed out after 120001 milliseconds

If you check i few posts higher you'll see that the server is currently under maintenance, there's nothing I can do about it:
viewtopic.php?p=251816#p251816

aberrio wrote: ↑
Fri Apr 12, 2019 11:26 am
This mean that we are not able to have the UART's output unless is created on the SD card?

Regards,

UART is a external debugging cable, it has nothing to do with SD card:
https://www.hardkernel.com/shop/usb-uart-module-kit/

You connect it to the debugging port (UART) on the ODROID and another PC, and it will show detailed logs of the boot process... it is not "written" anywhere, you have to save the output yourself.
But it's not called a debugging port for nothing

odro-volti · Post by **odro-volti** » Fri Apr 12, 2019 4:40 pm

Hi!
I'm new to Odroid, bought my first one some days ago. From the berry universe I have a UART-USB bridge, comparable to this here:

https://shop.pimoroni.com/products/usb- ... sole-cable

Can I use this one with my Odroid XU4?

Many thanks in advance

volti

meaz · Post by **meaz** » Fri Apr 12, 2019 6:01 pm

Hi Meveric,

I'm a brand new XU4 odroid user. I was used to work with Raspberry

Anyway, I wanted to install kodi. I used setup-odroid to do so (by the way, why can't I just use Kodi package from Stretch?). But Kodi doesn't work.
Here is the crash log I have.

[pastebin] https://pastebin.com/1SQ74DiF [/pastebin]

thanks a lot for your help!

meaz

meveric · Post by **meveric** » Fri Apr 12, 2019 7:48 pm

odro-volti wrote: ↑
Fri Apr 12, 2019 4:40 pm
Hi!
I'm new to Odroid, bought my first one some days ago. From the berry universe I have a UART-USB bridge, comparable to this here:

https://shop.pimoroni.com/products/usb- ... sole-cable

Can I use this one with my Odroid XU4?

Many thanks in advance

volti

probably not and you shouldn't try as you can damage the board.
The XU4 (and other ODROIDs) use 1.8V UART port, most other have 3.3V and therefore you can easily damage the board.
The UART from hardkernel has a converter from 3.3V to 1.8V to make sure everything works correctly.

meveric · Post by **meveric** » Fri Apr 12, 2019 8:07 pm

meaz wrote: ↑
Fri Apr 12, 2019 6:01 pm
Anyway, I wanted to install kodi. I used setup-odroid to do so (by the way, why can't I just use Kodi package from Stretch?). But Kodi doesn't work.

The reason why you can't use the version from Stretch is simple. The VPU of the XU4 is (like with most ARM boards) a very specific version that is most of the time not included in "standard" Debian packages.
Therefore a Kodi need to be compiled in a specific way to make the Hardware acceleration working.
You "could" use standard Kodi, but in that case you would have no hardware acceleration for video decoding.

meaz wrote: ↑
Fri Apr 12, 2019 6:01 pm
Here is the crash log I have.

[pastebin] https://pastebin.com/1SQ74DiF [/pastebin]

thanks a lot for your help!

meaz

Yes there's another issue with this. Kodi is compiled against X11 libraries, so you need a running X11 session to make it work. Either you install X11 libraries and start it with "startx kodi" or something like that, or the easier way is to simply install a Desktop such as MATE.

odro-volti · Post by **odro-volti** » Fri Apr 12, 2019 9:44 pm

meveric wrote: ↑
Fri Apr 12, 2019 7:48 pm

probably not and you shouldn't try as you can damage the board.
The XU4 (and other ODROIDs) use 1.8V UART port, most other have 3.3V and therefore you can easily damage the board.
The UART from hardkernel has a converter from 3.3V to 1.8V to make sure everything works correctly.

That sounds reasonable, thanks! First project is a NAS (tired of the USB2/100 Mbit networking on the berries), but for some tinkering later with additional Odroids I will keep in mind.

Should not be a problem to have a software RAID 1 (MD) on Stretch for the XU4, or?

meveric · Post by **meveric** » Sat Apr 13, 2019 12:48 am

nope software raid should be fine

meaz · Post by **meaz** » Sat Apr 13, 2019 3:32 am

meveric wrote: ↑
Fri Apr 12, 2019 8:07 pm
Yes there's another issue with this. Kodi is compiled against X11 libraries, so you need a running X11 session to make it work. Either you install X11 libraries and start it with "startx kodi" or something like that, or the easier way is to simply install a Desktop such as MATE.

I use my XU4 as a print server, as a prosody server also. So I would prefer not to install a Desktop. Do you know what exact X11 libraries I need for Stretch? When i search info about X11 on the web, there are just too many things!

meveric · Post by **meveric** » Sat Apr 13, 2019 4:04 am

hmm I'm not 100% sure, but I know it's normall started through "startx" which itself is a program provided by the package "xinit" so installing "xinit" should be enough to have a working X11 environment.

But I think you will have to do some manual steps to get hardware acceleration working.
Try the follinging (no guarantee it will work, never tried it):

Code: Select all

apt install xinit malit628-odroid xf86-video-armsoc-odroid
cp /usr/local/share/setup-odroid/xorg/exynos/xorg.conf /etc/X11/

If you're lucky that's already enough and you can run kodi with:

Code: Select all

startx kodi --

meaz · Post by **meaz** » Sat Apr 13, 2019 4:14 am

Thanks a lot, I will try!

Also, how could I enable CEC? I've just tried apt install cec-utils but CEC still doesn"t work

meveric · Post by **meveric** » Sat Apr 13, 2019 4:27 am

you all and your damn CEC

cec-utils has nothing to do with cec.
You need to make sure /boot/boot.ini has CEC enabled (it's disabled by default)
make sure you have write permission to /dev/CEC
Also make sure your ODROID is connected to HDMI-1 as in the past no other port worked.
And make sure you have installed libcec4.
You might actually have to rebuild libcec4, not sure if I compiled a new version for Debian Stretch, as per Default Exynos support is disabled in libcec and has to be enabled to work.
I remember I did this in the past for Debian Jessie, but I don't remember if I did the same for Debian Stretch.. check the version of libcec4 see if it comes from my repo or from Debian.. Debian won't work, if it's my repo it might work

meaz · Post by **meaz** » Sat Apr 13, 2019 5:05 am

I bought the XU4 also for a smooth experience with Kodi, and for the all family. So the CEC feature is really important to me as I have young kids. It works just fine on raspberry, I thought that would be the same XU4 (I'm not blaming anyone, just a bit sad about that)

/boot/boot.ini has CEC enabled: setenv cecenable "true"
make sure you have write permission to /dev/CEC: I don't have /dev/CEC but /dev/cec0, I don't know if it is the same. It belongs to root and is 602.
make sure your ODROID is connected to HDMI-1: done
make sure you have installed libcec4: done

check the version of libcec4 see if it comes from my repo or from Debian: it comes from Debian. So I tried to rebuild it. I followed that: https://wiki.odroid.com/odroid-xu4/soft ... rom_source But when I get to "make -j 8" from the part called " Clone libCEC from the Github repository then build/install that." I get an error: libcec/src/libcec/adapter/Linux/LinuxCECAdapterCommunication.cpp:46:23: fatal error: linux/cec.h: No file or folder
#include <linux/cec.h>
^
compilation terminated.

You're my only hope

meveric · Post by **meveric** » Sat Apr 13, 2019 5:25 am

meaz wrote: ↑
Sat Apr 13, 2019 5:05 am
I bought the XU4 also for a smooth experience with Kodi, and for the all family. So the CEC feature is really important to me as I have young kids. It works just fine on raspberry, I thought that would be the same XU4 (I'm not blaming anyone, just a bit sad about that)

I got my parents a special remote for that purpose.. a remote that can be used as a "remote" like for a tv, but also as an Air-Mouse and has a keyboard on the back... much more convenient than CEC and normal remote.
Something like this: https://www.amazon.com/dp/B07GWVKLFL/
Please note, there are MANY different devices like this and you have tons of options to choose from, that particular one is just an example after a 10sec search on amazon

meaz wrote: ↑
Sat Apr 13, 2019 5:05 am
/boot/boot.ini has CEC enabled: setenv cecenable "true"
make sure you have write permission to /dev/CEC: I don't have /dev/CEC but /dev/cec0, I don't know if it is the same.

Should be fine.. I think it depends on the Kernel version or board... but as long as you have a CEC device you should be fine.

meaz wrote: ↑
Sat Apr 13, 2019 5:05 am
It belongs to root and is 602.

Could be an issue if you run Kodi as non-root user, then you will have to add for example a udev rule to set it to 666 or something like that.

meaz wrote: ↑
Sat Apr 13, 2019 5:05 am
check the version of libcec4 see if it comes from my repo or from Debian: it comes from Debian. So I tried to rebuild it. I followed that: https://wiki.odroid.com/odroid-xu4/soft ... rom_source But when I get to "make -j 8" from the part called " Clone libCEC from the Github repository then build/install that." I get an error: libcec/src/libcec/adapter/Linux/LinuxCECAdapterCommunication.cpp:46:23: fatal error: linux/cec.h: No file or folder
#include <linux/cec.h>

Don't use that guide!
If it's available on Debian, rebuild the Debian package, not an "foreign" source.
Make sure you have deb-src entries in /etc/apt/sources.list
after that just do something like:

Code: Select all

apt update
mkdir sources
cd sources
apt source libcec4
cd libcec-4.0.1+dfsg1
apt build-dep libcec4

next open debian/rulses and add -DHAVE_EXYNOS_API=1 after -DBUILD_SHARED_LIBS=1 so the line looks like this:

Code: Select all

        dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 -DHAVE_EXYNOS_API=1 -DCMAKE_INSTALL_LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH)

after that you can build the package with:

Code: Select all

dpkg-buildpackage -b

After that you end up with a new .deb file that you can install instead of the old one (if everything works fine).

And as this is fun and easy to do.. I just created my own package of libcec4 for Debian Stretch and will upload it in a few minutes

meaz · Post by **meaz** » Sat Apr 13, 2019 6:02 am

Thanks a lot for the guidelines. THat is much easier!
I did succeed in building it this way. I've installed the built .deb.
I've rebooted, just in case it was needed.
I've lauched kodi as root, to avoid permission issue, just to see.
However, I still don't have any CEC peripherals that appears in kodi settings/syste/input ...

odro-volti · Post by **odro-volti** » Sat Apr 13, 2019 6:28 am

Sorry for the noob question, but I read the forum thread on eMMC recovery

viewtopic.php?f=53&t=6173

and the manual on burning eMMC with SD-card/USB adapter.

I bought an eMMC (16 GB) with the XU4, what is the official way to get stretch on this eMMC?

Many thanks!

meaz · Post by **meaz** » Sat Apr 13, 2019 6:41 am

Alright I quit. I'm kind of disappointed. I've tried some video with kodi, it was so slow, and the image quality not that great. I'm just getting back on my rpi2, it worked just fine. Thanks a lot meveric for the time you took to help out !