Posts by Rataplan626

And here is question number one. I cloned the linux kernel (git clone https://git.kernel.org/pub/scm/linux/…valds/linux.git) which worked fine on it's own. However when I go into that dir, and do

rataplan_@ubuntu01:~/linux$ git bisect start
rataplan_@ubuntu01:~/linux$ git bisect bad d23900f974e0fb995b36ef47283a5aa74ca25f51
fatal: Bad rev input (not a commit): d23900f974e0fb995b36ef47283a5aa74ca25f51

Same for the good 61fd484b2cf6bc8022e8e5ea6f693a9991740ac2. So that leads me to think I cloned from the wrong repository? Anyway, a push in the right direction is needed By the way, the initial LE build I did to test works fine (apart from the tuner of course) so that's a win already

Wow, yes indeed, the initial build took 54 minutes on my laptop... this will sure take some time Anyway, I'm on it and will report when I have news (or questions).

Smells like a complex thing if you've never done it. It'll take me some time to work through that, but I will test.

And... Is that something I can do or help with? I can work with Linux and am a MS systems and storage engineer, but building kernels would be new for me

I was trying to, but it seems https://ix.io/ is 'taking a break'. Seems that service is down. 11.0.3 uses that, so can't paste that log (or can I upload it somewhere, you are very clear I shouldn't upload it here). For now, because of that I'll allow myself to paste a few lines that I think matter. By the way, I tried with 11.0.5 but also no TV adapter available anymore it seems.

11.0.3:

LibreELEC:~ # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1c73:861f AMT Anysee E30 USB 2.0 DVB-T Receiver
Bus 001 Device 003: ID 1915:1028 Nordic Semiconductor ASA Smart Control
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg output:

[ 2.598648] usb 1-1.2: New USB device found, idVendor=1c73, idProduct=861f, bcdDevice= 1.00
[ 2.598661] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.598672] usb 1-1.2: Product: anysee-FA(LP)
[ 2.598681] usb 1-1.2: Manufacturer: AMT.CO.KR
[ 5.468386] usb 1-1.2: dvb_usb_v2: found a 'Anysee' in warm state
[ 5.471744] usb 1-1.2: dvb_usb_anysee: firmware version 1.2 hardware id 15
[ 5.472160] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 5.472281] dvbdev: DVB: registering new adapter (Anysee)
[ 5.472295] usb 1-1.2: media controller created

in 11.0.5 pastekodi DOES work: https://paste.libreelec.tv/enabling-vervet.log

As far as lsusb and dmesg go, they show the same. So I guess the driver is still there. However, TVHeadend Server (which seems to run fine on 11.0.4 / 11.0.5) show no adapters in the config-screen, and obviously when I switch to a TV channel, Kodi says something like 'no free adapter'.

Quote from CvH

there are no drivers for TBS and "Digital Devices (that is the actual name)" devices
everything else is still there

Then I assume those are brands of TV adapters or something? I am not familiar with those. Anyway, I'm using DVB-C, which means I am using a Philips TDA10023, and using 11.0.3 it identifies as such too (at least in TVHeadend). Is that related to this TBS and "Digital Devices"?

Hi. I'm running a Pi4, with 11.0.3. I have an Anysee DVB tuner connected, which feeds TVHeadend also running on the same PI. When I update to 11.0.4, no DVR drivers seem to be present for the Anysee. TVHeadend runs just fine, but it sees no attached TV adapters.

I've searched the forum but couldn't find anything specific, and looked at the release notes, which states

DVB ADD-ONS

DVB Add-Ons are currently deactivated. Digital Devices and TBS have currently no support for recent kernels so we are out of options. If you require support for those devices please stay at LE10.

I', actually not sure what that means. I run TVHeadend client and server, both of which are installed from Kodi itself. So I guess that's not related. Also it shows the same message for previous releases, but still up to 11.0.3 my DVB adapter works fine, in 11.0.4 it does not. The Anysee E30 consists of two USB tuners:

Zarlink ZL10353 DVB-T
Philips TDA10023 DVB-C

Both are not working. Is this to be expected in 11.0.4? When typing this post I see 11.0.5 is just released, would that include the drivers again?

Fixed with getedid create. Sometimes it's so simple if you know it.

Hi. For as long as I have this Rpi4 2GB, I'm struggling with this issue. Whenever the Pi reboots (kodi crashes from time to time, most probably because of TVHeadend), and the receiver it's connected to is NOT powered on, it hangs during boot on 'waiting on Network to come online'. However, network is already functional at that point. I use UTP network (WiFi disabled) with a static IPv4 address. And all is up and running. IP is there, SSH is running, even the samba share I mount using a system.d mount script is already there. Kodi is running, but it's like it forgot to switch to the GUI. When I use my remote, I actually can hear the menu 'click' sound, although it's extremely distorted, like 1/10th of a second of loud white noise. I have 'wait for network before kodi starts' enabled with 10 seconds, but that doesn't help. The network isn't the actual issue here I think as that's up just fine. I think it's just Kodi not switching from console-output to graphics output or something.

Before Pi4 I used a Odroid-C2, which never had this issue. I've read through the logs, and in dmesg I see several lines like this:

[ 13.217600] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19

If the receiver IS on, I see the same message, but not as often, only twice or so.

Not sure if that has anything to do with it. I tried forcing a resolution in cmdline.txt, which worked on its own (ie. if I set it to 720p for example it booted in that) but that only affects booting I think before Kodi kicks in. When it hangs at that message and I kill kodi.bin, Kodi restarts automatically, and then it works just fine.

I've narrowed down a bit; when I enable 'HDMI control' in my old Denon AVR3808 receiver, it works. However, then it doesn't switch off the HDMI circuits drawing a whopping 89.5 watts when powered off. Not feasible. Now I took the receiver out. And I think everyone can reproduce this; When the Pi is booted WITHOUT the HDMI cable connected, the same issue occurs. When it's booted and then I plug it directly in the TV (bypassing receiver completely) the issue is the same, it shows the 'waiting on network' message, which is in fact Kodi already running with network and all up and running. my config.txt only has hdmi_ignore_cec_init=1 in it and gpu_mem=76. Rest is commented out.

In other words, can we force kodi in a specific resolution or output or something when it wasn't connected during boot?

[edit]

hdmi_force_hotplug=1 in config.txt doesn't help, hdmi_ignore_edid=0xa5000080 doesn't work either.

I realised as I'm using LE 10.0.2 config.txt settings for HDMI don't work anymore. However, setting video=HDMI-A-1:1920x1080M@50 in cmdline.txt doesn't help a bit either.

just to report back, the older Widevine version fixed all my streaming problems

Thanks for that! So far it seems to be working. I'll report after a few days. This will surely inrease the WAF for Kodi in my house

Sorry, I didn't have notifications setup yet.

perf top when the issue is there:

top H when the issue is there:

after killing kodi.bin, perf top without the issue:

top H without the issue:

It seems videoplayer consumes a bit less CPU after killing kodi. I can mostly trigger the issue, as said by turning of the TV and receiver. It seems it doesn't like the HDMI reset or something.

[edit]

by the way, bcmstat.sh shows my Pi is not throttling at all, even when videoplayer is using high cpu. As reported CPU load is relative to the CPU speed at that time (at least as far as I know) I thought it would be throttling, but it's not. Temps are fine too, between 50 and 55 celcius.

Hi,

for a while I have had this issue, I even think ever since I switched to Pi4. I have a 2GB Pi4, which was recommended me (in terms of 2GB vs 4GB) to be more than enough for Kodi use. I'm running LE 10.0.2 now, but I've had this issue with 10.0.1 and some nightlies as well.

When the Pi is just booted, everything is fine. I have TVHeadend running on the Pi, with an Anysee DVB-C tuner (just free-to-air channels) and everything works fine. However, I also use the RetroSpect add-in, as well as the Dutch Ziggo plugin, both stream h264 streams (both live TV and playback). When the Pi is just booted, everything is fine, and the streams run perfectly smooth, for as long as I want to watch. Then at night I shutdown the AV receiver the Pi is connected to, and the TV itself. Then in the morning, when turning all on again the following happens:

The Kodi interface is choppy. h264 streams from RetroSpecs and the Ziggo plugin are extremely choppy and constantly need to re-buffer after a few seconds of playback. I constantly have one CPU core at 100%. DVD playback (ISO format) works fine, tvheadend streams are fine as well. I forgot to test h264 content from my NAS. When I run top from shell, I can see kodi.bin running at between 110% and 150% when doing choppy streams. When I use the debug stats in Kodi itself (with 'o' during playback) I can see one CPU core being at 100% all the time.

Rebooting LE fixes this. However, I also tried killing just kodi.bin from shell and that fixes it too. So it seems something within Kodi seems to bug.

Now I still have an old JVC 1280x720 tv, and it defaults to 1080i instead of 720p that I want. So in my cmdline.txt I have:

boot=UUID=3010-5350 disk=UUID=a8e8a687-3b0f-472c-a2e4-3e8c903fd088 quiet video=HDMI-A-1:1280x720M@50

to get Kodi to boot up in 720p. Kodi itself is set to 720p as well. Not sure if it has anything to do with it, but it might, as it only happens when I have turned off the receiver and tv for a longer time (ie a night or a few hours during daytime). When I enable debug logginf grom kodi and tail the kodi.log, I don't see ANY event though when I turn of the receiver / tv at all.

How should I debug this, or what logs would you need?

Thanks!

Quote from Shoog

DVD playback has been flacky in Kodi for years at this stage, it has not got attention for years because the people who maintain Kodi do not have any interest in supporting it properly. Its effectively a dead technology.

Shoog

Sure, but in LE 9.0.2 and all versions before it all worked perfectly fine, as do the recent Windows builds. So why doesn't it work properly on C2 anymore? Kodi itself works fine for other builds. DVD might be a dead horse, but people have hundreds of them in their collection...

Just updated to the latest (as of yet) Odroid C2 build. But I still have the same issues I've reported before, but as noone responded at all I'll do again:

Image is installed on SD, not eMMC. It boots fine, but when I reboot Kodi, it halts. The OS shuts down nicely though, it seems to do a shutdown -h rather than a shutdown -r.

DVD menu's aren't working. I have all my DVD's ripped to ISO. Doesn't matter if I play them from NAS or the local SD card. DVD trailer starts playing, but the menu is blank (black) with only the cursor showing. When I enter a few times something usually starts playing, and when I then go back to the dvd menu, it works fine. Initially it doesn't though.

Are this bugs to be reported at this time, and if so what logs would you like? The usual kodi debug logs?

9-11 Odroid C2 build freshly installed on a brand new SD (for now I run CoreElec on an EMMC to keep the girls happy). It works rather well, but it halts when I do a reboot. The OS seems to be completely shutdown, the heartbeat led stops flashing, SSH of course is down at that point too (so I can't log anything), but it won't reboot, or at least it doesn't actually start booting.

Passthrough audio not working well (I think that's to be expected at this point). DVD menu's (running from DVD ISO's) are not working properly. The studio-trailers run fine, but as soon as an interactive menu should show up, it's either blank, or sometimes the menu shows but the 'cursor' is flashing. Then, when for example I choose 'select episode' I get to the episode menu, but then there's no selector at all.

I'm new to these test builds. Having read trough most of the posts in this thread, I'm not really sure if you guys want logs for these kind of issues, or it's too soon to iron these out?

Anyway I want to applaud you guys in how far you've already come and how well this is already running on a recent kernel!

Hi. Stupid question probably, but reading through most of the thread I couldn't find an answer. Why is it that the Odroid C2 needs, or at least has, it's own image, while it's based on the S905?

Hi! I'm new with Odroid C2. Initially I installed HardKernels own LibreElec build - and for LibreElec that works perfectly fine. However, I want to run RetroArch as well. I quickly found that that needs 32bit libraries / binaries. Now I did get it running using JoKeRz repository and addons, but I was assuming Raybuntu's build would make 32bit packages 'just work' (to some degree of course).

So I flashed LibreELEC-Odroid_C2.arm-8.2-rb-krypton17.img, and then installed RetroArch from Gamestarter: Retrogaming add-ons (RPi/Generic). It installs just fine (as it did with HardKernels build) but starting it shows the splash screen and then quits back to Kodi.

I've searched this thread but RetroArch doesn't even come up. Is this support to work, and does anyone have some more info for me?

Thanks!