Posts by chewitt

If the driver doesn't support suspend then it's nVidia's problem because it's their driver, all we did is package their driver into our distro image.

It's not possible to install .deb packages but it is possible to unpack them to see what's inside:

ar x package.deb
mkdir /storage/deb
tar -xf control.tar.xz -C /storage/deb
tar -xf data.tar.xz -C /storage/deb

If the tool(s) are a single binary, inspect it with ldd to see if it's a static binary or linked against shared libraries. Manufacturers tend to compile this type of tool as a static binary to make it self-contained and more portable across a larger group of distros; and if true, you can probably just copy the binary and run it on LE with some supporting scripts and a systemd service.

If the tools are a whole suite of binaries etc. then it's probably a dead end.

I gave support advice. You chose to ignore it. Your problem is not our problem.

This is the alsa conf that LE12.2 uses, it is focussed on HDMI output and the 3.5mm Jack output is unlikely to work:

WIP: add confs for gx-sound-card and axg-sound-card · chewitt/alsa-lib@5b81165

github.com

I am reworking audio support for LE13 to hopefully to get pass-through HDMI audio working. I might play with analogue later, but it's not a priority for LE users so not a priority for me either. I have no interest in trying to support other distros like Debian - which has a forum where you can ask for help from people that understand its packaging and requirements.

LE13 dev images support installation of browsers via flatpak. There are test images here: https://chewitt.libreelec.tv/testing/ although the latest ones posted have some major improvements for video decoding and I have not tested them on S905X3 (SM1) hardware yet. Testing is $free though.

In future posts please use line-breaks in your text instead of posting one huge wall of text.

Test an LE13 image. You will need to cross-grade to Generic as Generic Legacy no longer exists. Clone your Kodi folder before to give a downgrade route. Any addons that depend on OpenGL should be removed first; leave settings and reinstall OpenGLES versions afterwards. There’s no guarantee this improves anything but LE12.2 is no longer being developed so best to test v.next.

Download an appropriate picons set from https://openpicons.com/?dir=full-motor-utf8snp/hardlink to /storage/picons/tvh and then reset the icons in the Tvheadend GUI so they are picked up. I've found that I needed to delete /storage/picons/tvh and then move/rename the unpacked folder to that location.

Done

I found https://discourse.osmc.tv/t/solved-my-rf…di-v17/22118/46 from a Google search on the USB device IDs. I'm not sure it's the same problem, and it would be interesting to see journalctl | paste output from the system before and after the following udev rule is created in /storage/.config/udev.rules.d/51-not-a-joystick-rm.rules .. beware the line-wrapping in the forum, it should be two lines:

# /storage/.config/udev.rules.d/51-not-a-joystick-rm.rules
# based on: https://github.com/denilsonsa/udev-joystick-blacklist

SUBSYSTEM=="input", ATTRS{idVendor}=="25a7", ATTRS{idProduct}=="2402", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="25a7", ATTRS{idProduct}=="2402", KERNEL=="js[0-9]*", RUN+="/usr/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""

EDIT: linking https://github.com/raspberrypi/firmware/issues/1189 too; which looks to be a different issue that mentions the same devices ID's, but might somehow be relevant since we use RPi kernel and not mainline kernel sources for RPi images so the change will be present in our kernel.

Disable the internal screen first then so there's a single device, then it will run.

Once complexity reaches a certain point it's time to look for a Docker container that a) has everything needed, b) is attentively maintained by someone else

I’d build the module with =y so it’s always present and doesn’t need to be loaded. Use two services for the apps if you need to manage start order. Or do in one if they can start more in parallel. Or use one and put whatever sequence you need in a script and execute that from a service. Lots of options; probably no wrong or right and to the question

Run getedid create from the console with HDMI connected and the kernel will always see the TV as connected:

https://wiki.libreelec.tv/configuration/edid

You can also hard-disable the internal screen:

Laptops | LibreELEC.wiki

How to disable the internal screen and force external HDMI/DP/VGA output

wiki.libreelec.tv

If the issue is something deeper in how the laptop hardware or firmware works, there is nothing we can do. We don't fix laptop firmware

thomaz https://github.com/tvheadend/tvheadend/pull/2233 and changes should be in the .13 addon in our repo along with some dark-mode theme changes that I pushed last week. Some cleanup might be needed https://github.com/tvheadend/tvheadend/pull/2247 but the scan should complete now.

"User error: please replace user"

Are you running the latest nightly?

config SND_ALOOP                                                                          
        tristate "Generic loopback driver (PCM)"                                          
        select SND_PCM                                                                    
        select SND_TIMER                                                                  
        help                                                                              
          Say 'Y' or 'M' to include support for the PCM loopback device.                  
          This module returns played samples back to the user space using                 
          the standard ALSA PCM device. The devices are routed 0->1 and                   
          1->0, where first number is the playback PCM device and second                  
          number is the capture device. Module creates two PCM devices and                
          configured number of substreams (see the pcm_substreams module                  
          parameter).                                                                     
                                                                                          
          The loopback device allows time synchronization with an external                
          timing source using the time shift universal control (+-20%                     
          of system time).                                                                
                                                                                          
          To compile this driver as a module, choose M here: the module                   
          will be called snd-aloop.

No mention of SND_DRIVERS there ^ so looks like a kernel bug to report and submit a fix for

Honestly no idea and I'm neck-deep in debugging something so not going to spend time looking.

I bumped Kodi four days ago: https://github.com/LibreELEC/Libr…94747d2db405f63

So update to the latest nightly and it should be there.

If you have a working default image building, edit projects/RPi/devices/RPi4/linux/linux.aarch64.conf to enable the module then rebuild the image and it will rebuild the kernel and update the image.

At least that's the theory. It doesn't work for me on an Amlogic image with linux-7.3-rc2 kernel either, and diff comparing the edited conf and .config file from the kernel build folder shows the kernel has unset CONFIG_SND_ALOOP=m when processing the config; hence nothing gets built.

I will task Claude to investigate the problem once I take a break from some other debugging. I suspect some kind of upstream kernel issue and not something on our side.