Posts by chewitt

Quote from Da Flex

I would say yes. Hopefully this bug will be fixed in the next stable release. Developers are informed.

There is no bug .. auto-update has not been enabled yet.

All S905X boards use the same Ethernet configuration so that should simply work in all S905X device-trees. Most devices are derivatives of the P212 reference design with few changes so all the core perhiperals will the same. The only major changes are buttons/LEDs .. and sometimes the SDIO WiFi/BT module.

There is no support in the upstream kernel for the RTL8189ETV chip, and I (and rest of the team) have no interest in adding more downstream Realtek drivers (https://github.com/jwrdegoede/rtl8189ES_linux) to the distro image - they're low quality and a pain to maintain. You could attempt a custom build with that driver included. The WiFi part of the SDIO module should probe; SDIO is a bus so connected devices are auto-discovered and wifi@1 reference in device-tree for broadcom chips will also work for Realtek. The BT part of the module will need things to be described correctly in device-tree.

I suggest you build in a Docker container to avoid all the hoop jumping with build environments.

I've recently pushed a change to LE master branch which enables (allows) Ethernet tethering in ConnMan. It works the same as WiFi tethering but in reverse (share the WiFi connection over Ethernet). This makes it fairly simple to connect the LE device to Hotel WiFI and then connect a laptop (behind a NAT connection) to negotiate the logon process. Next step is to make changes to the LE settings app to support the current Hotspot being rebranced as connection sharing and to support switching between WiFi and Ethernet. I suck at Python and have low time right now so that might take a year or two.

Quote from RavenRA

Can't make the wifi work on this box. DTBs from other S905Xes work. I am also very curious to install it to internal flash

I've never managed to get the RTL8189ETV to probe correctly but it's been a while since one came along. Start with expaining which dtb you are using to boot the device (which dtb has best overal fit for board features). NB: LE does not support installing to internal emmc on TV box devices; only SBC boards with dedicated images and upstream u-boot support. If you attempt using old scripts and forum posts I guarantee that it goes wrong and I guarantee zero sympathy and support for unbricking things.

You need to create multiple .config files (fr.config, ch.config, be.config, etc.) instead of putting multiple configs in one file.

You've erased u-boot. Your best hope/option going forwards is to find an Amlogic burning tool image on freaktab or similar. We have no real expertise or interest in Android images, and that's what you need to restore a working boot environment.

Quote from jamm

Is it actually the OS like the sbc versions?

Does it support a mouse or touch screen or does it need a dedicated remote?

It's exactly the same OS, only compiled for x86_64 CPU architecure and with different GPU drivers to suit "PC" hardware. It supports a mouse the same as the ARM/SBC releases. It could support a touchscreen; depending on the exact/specific hardware having drivers in the kernel or can be enabled in the kernel. Most users will attach some kind of remote; either the 'wireless' keyboard type, or an IR sensor like flirc.tv with a spare IR remote, or a BT remote. Unlike ARM devices, CEC is rarely supported in the PC world.

Add-on:SFTP support - Official Kodi Wiki

Quote from Origin

My setting is 1080/50 but the WIKI recommendation is 4096x2160 @ 60Hz (highest supported resolution of my TV) or not?

1080@60 (and whitelists for 4K modes, as you've done) would be our recommendation. The skin is 720p or 1080p (not sure which) so the TV does a better job of scaling an already rendered image to 4K than Kodi does using CPU to scale the content to render. Few people have HTPC devices with the CPU to handle 4K GUI smoothly.

I'm wondering if there's a restriction on switching to something lower than the GUI resolution (1080p). The logs will show more I think.

I can see that "720x576 @ 50.000000 Hz" is in the whitelist. Please ensure "adjust refresh" is enabled then reboot (to create a clean log) and play something that should be switched to that resolution, then share the log URL.

2023-01-21 12:57:25.898 T:751      info <general>: Found resolution 720x576 with 720x576 @ 50.000000 Hz
2023-01-21 12:57:25.898 T:751      info <general>: Found resolution 720x480 with 720x480 @ 59.940063 Hz

^ the 4:3 modes are present.

Quote from Origin

On the Vero 4K+ (Linux OSMC) I'll have to look later.

The Amlogic vendor kernel might work, but it is definitely not a reference 'Linux' implementation

What did you update from? (LE9, LE10, another LE11 nightly). Share logs:

Quote from _emanuel_

there is no playback at the moment for v4l/panfrost?

What about the avl tuners or other usb tuners/demods in LE nigthly - also no playback ?

Panfrost/Lima render the Kodi GUI (2D) and nothing more, they have nothing to do with video decoding. There are hardware video decode (and software decode) drivers using GBM/V4L2. However you still need something to take the transport stream from the tuner/demod and demux it into a supported video and audio format for playback. I've started poking around with other demod/tuner drivers and have some that compile, but none probe hardware yet (the code needs amending for upstream GPIO) and none are in nightlies. Even if we can get them to probe hardware there is still the same "missing demux" issue.

Do you actually have any media outside of 576@25 (PAL) and [email protected] (NTSC) .. because ye olde analogue broadcast standards certainly don't include those refresh rates; which is prob. why Linux doesn't invent/expose them.