Please share a debug log that demonstrates the problem. Thanks.
Not sure what to log I chose "video" and "video and audio timing" in "components" list. I just tried to start playing the file (which was 4K HEVC mov created by me) and when the playback started and it was obvious it was wrong I stopped it. Then I stopped the logging.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Under the years i have used Pi4 with LE and LG Oled something similar happened only once and it went away when i replaced the HDMIcable.
There is one tricky thing I did not fully realize - I am using Argon case with SSD port. I had to originally replace the board with HDMI convertors because one did not work. Then I read here that Argon cases are not very reliable with respect to HDMI. So I wonder if this might be a culprit.
So far my reasoning about this not being the cable (or the HDMI output itself) is that apparently the TV switches into right res (4K), but for some reason Kodi turns on the downsampling anyway. I would expect if the hw negotiation of 4K mode fails, it would not switch into it in the first place.
Now, when playing 4K content (SDR, HEVC) the TV switches into 4K mode, but the movie is rendered in what seems to be a Full HD res (1920x1080) into the first quadrant. If I un-whitelist the 4K modes, the TV does not switch into 4K mode and the movie is again rendered in Full HD res correctly (and upsampled to 4K by TV). So it looks, like for some reason Kodi downsamples the content regardless the mode the TV is in.
This is how it looks:
I could have missed something fundamental in Kodi settings, but after several reviews I am still clueless. Anyone has any insight?
risa2000 Interesting. Nice to see the errors are gone. The log also shows Broadcom WiFi is now missing but I suspect that's due to another change I made. Can you update to https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar and share the boot log to confirm (it should be fixed if I'm right)?
I noticed wifi was missing, was thinking it was because I had already wired connection :). The new build fixes that. Here is dmesg log, there are some video errors at the end, but I am not sure if they are relevant (I observed some instability when watching TV or TV recordings from TVHeadend backend).
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
I also noticed that in this build kodi run correctly 1920x1200p@60Hz.
Purely for kicks can you update to the latest https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar and share a new dmesg log please. I've described all SD card modes in device-tree and increased the max SD card speed. On most hardware i'd expect this to cause problems, but I'm curious to see what impact/influence it has (not sure it can make things worse).
The latest build from today seems to work fine with Samsung SD card (I flashed the image anew, to avoid risking having corrupted fs from the previous run). Here is the dmesg:
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
There is actually nothing particular about kodi start in the log. Only, after starting kodi I have connected Air Mouse which is registered at the end of dmesg.
Amlogic mmc controller issues normally exhibit with high-speed card modes and faster speeds and the current/upstream U9-H device-tree is already defeatured to run at a minimum level. The usual way to rule out those issues with modern cards (that have fancy modes and such) is to test with an old, slow, low-capacity card. I have some 2GB cards which aren't much use for an install but are reliable for that kind of testing. Most vendor firmware will power-up the USB section in u-boot automatically which will make the AMLGX boot media discoverable and useable there too, so perhaps try with a USB stick instead of SD card.
I got my hands on another Minix Neo U9-H, and run it with your latest test build and observed the same behavior. It booted alright in textmode and then got stuck with a lot filesystem errors when I started kodi.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Which at least ruled out that my original box had some hardware/power supply problem.
I have a hunch this is a power problem, but figuring it out might be a challenge. When you start Kodi the GPU is used for the first time which increases power demand on the system. The current assumption is that the box follows the Q200 reference design (the legacy device-tree suggests this: https://github.com/LibreELEC/devi…inix_neo_u9.dts) but there are probably differenes. I do have the schematics for the box, but I'm not the greatest reader of them.
FWIW CoreElec 9.2.8 which I run currently claims to use dt-id: gxm_q200_2g_minix_neo_u9 which I would assume is the same device tree LE is using. I have checked the power supply, it gives 5V, looks solid. My hunch about overclocking might as well be undervolting though. I tried looking into any hint from comparing dmesg outputs from LE and CE, but these differ so much that I am clueless.
The last thing I wonder if might be an issue is the SD card and its potential incompatibility with the Minix. For LE I am using a different SD card (32GB Samsung) from the one I am using with CE (16GB Transcend).
chewitt Ok, I will check your builds. Meanwhile I was able to boot into the box, using textmode. It turned out that everything runs fine (without kodi), so I could get dmesg, edid etc.
Once I tried to start kodi (systemctl start kodi) it did not start but led to a quite a lot of filesystem errors in dmesg. I wonder if there is some HW incompatibility between the card and the box. The other suspicious detail is that when LE is starting there is a short moment where the screen looks corrupted (with snowing and vertical lines). I guess it could be related to the gfx init, but I alse wonder if it could be because my box is overclocked (not intentionally, but maybe the default LE freq is too much)?
dmesg output follows (around 512 sec time the errors begin - the time when I started kodi)
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Images are based on LE12 which has newer everything including a more recent kernel. The amount of change in the Amlogic kernel is low but that also means it's low risk to use (nothing is likely to be fixed or more broken) but we remove the doubt.
Just booted your image (LibreELEC-AMLGX.aarch64-11.80.0-box.img.gz), using ssh textmode kernel boot args.
The behavior is the same as with LE11 - without kodi everything starts up correctly. Once I start kodi from commandline (systemctl start kodi) the kernel log starts to fill with filesystem errors.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
NB: If anyone has a second/spare U9-H box I'd be interested in acquiring it for testing. I've attempted to pick one up on eBay a few times, but I've either been outbid on the item (which is crazy) or sellers have refused to entertain shipping the device to the UAE.
I might be able to get one locally on the second hand site and send it to you, but was not able to contact you over PM. Let me know, if you are interested.
I was just trying to run the latest 11.0.4 on Minix Neo U9-H.
First, booting the default config without any changes gets me into LE screen, then it gets shortly into Kodi screen, then again into LE screen and then gets stuck. It looks like it gets stuck at a point where another poster here got kernel panic. I do not though.
Second, enabling the log into console and sshd (following the advice from RE: My Old Minix Neo U9-H Can Be Updated?) showed that LE gets quite far in the boot process (see the attached pics).
Setting the video mode to suggested video=HDMI-A-1:1920x1080M@60 did not work though, I did not get any video output at all. Setting no explicit video or using video=HDMI-A-1:1280x720M@50 seems to work equally well - TV identifies the mode as 720p and shows the aforementioned screens. This is strange because the TV should support 1920x1080p@60Hz (and it indeed does when running the venerable CoreElec version).
What is also strange is when it gets stuck I cannot connect to sshd, but I can ping the box, even though it looks like sshd started correctly, which is confirmed both in the console log and also in a "postmortem analysis" of the SD card, where I can see that the ssh started and the keys were correctly generated in both the log and in /storage/.cache/ssh. But despite the positive indications the box does not respond to ssh request. From /storage/.cache/conman files I can deduct that the wired network was correctly configured by DHCP (also confirmed by ping), so some part of the network stack is running correctly.
When booting with log enabled it also looks like there is a moment (possibly around starting kodi) where it looks like LE/Kodi is trying switching the video mode but failing and continuing with 720p.
After several attempts I manage to record a log from kodi (/storage/.kodi/temp) but it does not seem to indicate anything out of ordinary (
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
).
I was thinking about booting LE without starting the kodi, so I can look around more, but to enable that I only find methods which either involve already running LE, or modifying the ext4 filesystem (which I cannot do, as I have only Windows machine at the moment, and only read-only access tool for ext4). Is there a way to disable kodi by modifying uEnv.ini or something else on FAT partition?
Thanks for the tips! It seemed stuck for a long time and the kodi log got created so I would hope it reached userspace (unless the kodi runs in some other mode). The video might be a problem as the TV is an old Panasonic plasma with native res 1280x720 ("HD ready"), it should be able to run Full HD (1920x1080) up to 60Hz but the EDID might not be "up to date".
Coming to the repetitive reboot with power button down, do you if it is an expected behavior? For example if the power button is mapped to "reset" on LE and activates at the very first moment?
On CoreElec when booting with the power button down, it flashes the Minix screen shortly but then goes directly into CE boot and remains there until it fully boots, regardless how long I keep the button pressed.
I was trying to breath the new life to my venerable Minix Neo U9-H with the latest LibreElec. So far the thing was running CoreElec 9.2.8 without problems, so I have good reason to believe that the hardware is fine.
First thing I noticed when trying to boot LE from an SD card was that in order to be able to switch to the new SD card (by booting while keeping power button) the device had to be shut down properly before. Which is possible either from the native Android or from the CE by using some menu commands, but does not work if I just power cycled the device in sleep mode. I do not remember if it was a normal behavior, but since I did not know (or did not remember) I thought that maybe my SD card install is not correct, or the power button trick did not work anymore - anyway it scared me especially since it started to behave the same way even for the old SD card with CE install.
The recovery was to remove SD card, boot the original Firmware, use the menu command to shut it down properly then disconnect the power, put the SD card in, push the power button and plug the power.
The second thing I am not sure was right, while booting the card with LE and still keeping the power button down, it looked like the boot was locked in a loop. The first LE screen showed up, then the screen blacked out, then again as long as I kept the button down. Once I released the button, it showed the LE screen with the text LibreElec and version at the top left corner, then Kodi booting screen showed up and then it got stuck.
Since I read about some extensive booting time mentioned by OP here, I left it conservatively for maybe 10 minutes, but it did not budge from the Kodi screen.
The problem is that I do not have the device at my place and have typically just limited time for playing with it, so I need to prepare myself in advance. I have checked the both filesystems on the card (FAT and Ext4) but did not find any log (`.kodi/temp/kodi.log apparently got created but is empty).
Is there a way to instrument the boot to get any diagnostics either into console or recorded onto SD card?
Well, it seems I can answer that myself. After downgrading back to 10.0.4 and noticing the same behavior, and checking thoroughly the sound settings, I noticed that the option "keep the audio source active" was unset. I guess I had it set originally to "Always", but it did get into an undefined state after an upgrade to 11.0.1 and remained after the downgrade as well.
I have been running LE 10.0.4 on RPi 4, with LG TV (OLED C11) and Sonos Beam v2 without any problems. After an update to 11.0.1, the Kodi UI sounds started to behave erratically. They play fine for a while (when navigating through menus) then stop and after few silent actions, a chirp comes out (as if disconneting/reconnection speakers).
I did not change anything after the update, and the actual TV channel sound seems to be fine (no chirps, or drop outs).
I tried to change different sound settings for the sound in general, but it did not help, neither toggling Kodi UI sound settings for different options.
I am currently trying to figure out, if there is a way to make dualHD WinTV tuner work on RPi 3B+.
First I took CvH image, but it does not boot on RPi 3B+. I made a naive attempt by copying 3B+ dtd file from Raspbian Stretch, but I guess this was too naive...
Then I noticed that LE9 image may include CvH drivers by default. The problem was I did not find any LE9 images except the ones built by milhouse, and those, while booting fine on RPi 3B+, also support only one tuner.
Does anyone know, what is the expected resolution to this problem? Will LE9 add additional drivers as in CvH's image? Will this be eventually added to milhouse's build? Or will LE9 wait until the support is in the kernel and until the kernel is accepted in LE?
