If the NUC has LSPCON it makes sense that DP-1 is seen as connected, althoug it's a bit of a mystery why HDMI-1 is not active at the same time since (in theory?) it's the active output. Have you tried an LE11 nightly image? .. newer drivers might give different results (grasping at straws in the dark).
Posts by chewitt
-
-
-
Kodi only searches for the active DRM device at startup, so if you connect (or power on) the monitor afterwards the kernel will detect it and reconfigure itself for the new active connection but Kodi will remain fixed on whatever it saw at boot. And it looks like the DP-1 port is seen to be active when HDMI is not connected.
The getedid script should work, but you will need to ensure HDMI is connected and the monitor powered on before you power on the NUC, else the script will probably find the DP-1 device active and then you get the EDID for the DP-1 port, maybe?
It's also possible to set "video=HDMI-A-1:1920x1080M@60" in kernel boot params, which should force output to the HDMI connector with some standard timings. Other random thoughts are to disable the DP ports in BIOS, if that's possible?
-
it does not continue loading and the error appears at the top right of the screen as already explained
And what does the error say? (snap a pic on a phone or take a slowmo video it's quick)
-
Bump to the LE11 nightly, because if anything is fixed that's great, and if not fixed it's a current kernel to investigate from wheras the 5.10.x kernel used in LE10 releases is recent but also ageing .. Linux 5.16 was released last Sunday.
-
Urgh.. I didn't notice that
-
A95X F3 Air (S905X3)..has anyone had any success booting with one of these?
If Armbian boot scripts work, LE scripts should work too as the Armbian ones were plaiguarised from LE in the first place. Project stats show a few active installs so I assume it worked for someone somewhere (no guarantees your box is the same though as there are 20+ box vendors shipping 'Air' boxes that look identical).
-
Anyway, may I ask, what is the harm in shipping an improved driver with multiple bug fixes?
Test an LE11 nightly from https://test.libreelec.net/ and you will be using the latest LTS kernel driver that Intel has contributed fixes to. If we switched from the in-kernel driver frequently maintained by Intel to some forgotten out-of-tree kernel driver that Intel has not touched in two years; you can expect more breakage than fixage.
-
-
Users with a problem Ethernet connection are not unheard of, but I'd start with changes to Cables and Switches before pointing the finger at the kernel driver. LE uses the upstream in-kernel driver - which is also used by 10's of millions of other Intel devices. It's not impossible for the driver to have an issue, but if you do want to point the finger in that direction you will need to convince us by sharing some proper technical evidence of it being the source of problems! NB: In all cases we will not update to the not-in-kernel vendor driver, it would be a bad move.
-
There is no change. Put Kodi in debug mode and reboot, then check to see if something is logged?
-
If you use cards on their own, they both work. If you use the adapter, one of the cards does not work. The non-working card changes when you swap them around (i.e. the slot is bad, not the card). Thus .. either the adapter is bad (as one of the slots will always be non-working) or that kind of adapter simply isn't supported. In either case, I'm not seeing an LE problem here. You could use PINN or NOOBS if you want to have multiple OS booting from the same card.
-
The AMLGX "box" image here https://test.libreelec.tv/ has a device-treee for the A95XF3 box, but SM1 (S905X2/D2/Y2) boards currently have no support for 10-bit HEVC (and playing it wiill crash the board) so you won't get a better experience. You'd be better off with CE images that use the legacy vendor kernel.
-
Add "ssh" to kernel boot params in syslinux.conf or extlinux.conf (not sure which is used these days) and the daemon is forced to start.
-
Ok, thanks for nothing than. You can keep your buggy software. Several people got lipsync issues. It is surely not related. And besides this "anti" piracy aspect is purely dishonest. Why do even anybody need Kodi? For sure not for streaming DRM proofed like Netflix or his own ripped BluRay content...
Our project. Our rules. And the rules state support will be refused to users with pirate add-ons installed. It's something we take seriously and regardless of the merits of the problem reported. NB: Pirates always assume that everyone else is also a pirate [wrong] so they ignore the legion of Kodi users with DVB cards watching Satellite and Terrestrial broadcasts, and people with kids who rip discs into Kodi to avoid them being trodden on, and people who listen to global radio stations and watch catchup tv servies, and many other not-pirate use-cases for an open-source media app .. Zzzz we could go on.
Show us a clean box and we'll happily look at the problem.
-
You can rename /storage/.kodi to /storage/.kodi-old or such and reboot to start over .. it makes copying working config back easier
-
Nothing stands out, but the most common cause of unexplained crashes is add-ons. So start with a clean install and add things back in small changes until either everything works or you can pinpoint the change that introduces the problem.
-
Settings > Playback > Sync Playback to Display (should be off by default, and we'd recommend it to be off so that Kodi uses the media clock)
