Posts by chewitt

Hardware (and/or Windows) supporting DV is not equal to Linux supporting DV. As DV is proprietary closed-source magic there is not really any support for it outside of ARM device vendor kernels that depend upon more closed-source DV blobs to work.

..but should be supported in newer kernels, so the nightly will probably work.

I'd guess that u-boot has been corrupted or overwritten with an incompatible version. Assuming the eMMC didn't die the easiest way to get things working again would be to use Amlogic burning tool to restore the correct factory image for the box (from XDA forums or similar) so that the box boots (Android). Once it boots again, it's simple to boot an LE image. Alternatively you need to connect a UART cable to the box so we can see the early boot output - but this involves the box being opened and UART cable attaching, which may (or may not) require the UART pins to be soldered to the board first. From the level of technical detail in your posts, I'd suggest the restore-Android approach.

You cannot install drivers in LE, they need to be embededded (baked into) the image. You need to us the WiFi chipset and/or make/model of the WiFi card in the box. From there we can investigate.

There are multiple issues with the current 'update' functionality, and rearranging of files on the test server is not the most important bit that we need to resolve. Once the other pieces are done, easier updates for nightlies will be possible. There is no timeline - people have lives and families and things will be done as/when developers have time. Until then folks can update manually using .img.gz files (not .tar files) which has been supported since 2015.

S905X boxes should work quite well, S905X2 less so (unless hardware decode disabled) .. "but nothing" doesn't really describe a problem that would could respond to

Test with a current nightly, as that will have newer kernel, drivers and firmwares.

(
sleep 3
xrandr --newmode "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync
xrandr --addmode HDMI1 "3840x2160_60.00"
xrandr --output HDMI1 --mode "3840x2160_60.00"
)&

^ Try that. It runs the commands in the background after waiting 3 secs for X11 to start. Even if 4K60 is working in nightles your issue is the EDID data read from HDMI does not provide that modeline, so you'll still need to add it.

You can put the commands in a simple script and then order the execution using a systemd service file in /storage/.config/system.d/ .. it's been a decade since I used LE on x86_64 hardware with X11 services so I have no idea which services you need in the after criteria, but this is the only way to say "after X11 services start, before kodi.target starts"

NVMe will be faster and more reliable than a USB stick.

No (unless using a test build with HDR patches), No (because DoVi is closed-source garbage), Yes (assuming the hardware supports it).

Same, using Estuary. So it's a skin thing.

AVG is garbage. End of lesson.

Press pause and the OSD appears. There should be a cog icon on the right side, which brings up video settings. Is that what you mean?

Quote from poeBaer

I'm not at all familiar with ALSA, outside of being a simple end user, but is that something that could eventually be auto-configed/make it's way into the GUI (assuming a proper arrangement can be figured out/found)?

Kodi has a GUI option to upmix 2.0 to the current speaker configuration, e.g. 5.1, so IMHO the best approach would be a similar Kodi feature that upmixes mono to either stereo (default) or a centre channel in a multi-channel configuration where FC exists. Fiddling with alsa confs is probably do-able but not something I'd ever want to adopt for distro features as it won't be replicable to all devices (alsa confs are device-specific).

Please share the whole dmesg log (via pastebin). It's not clear which LE image you are using.

Kodi has a function to change resolution (which is poorly documented and may not work) but the design assumption is that you either leave the refresh rate at the 'desktop' frequency of 60Hz and let Kodi adapt the content for best output, or let Kodi switch to resolutions that match the media playing (which is better). You can manually set the desktop refresh rate but there's no function to hot-swap/force a specific rate.

It's not the first time someone reports an issue with Denon AVR

It should be a Kodi feature we inherit and not something specific to LE, hence there's not much ambition among staff.