Posts by chewitt

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.

Done

Quote from vobs

I would have to rename them like 'Movie.Year.3D.SBS.mkv' – it seems that the letter 'F' is preventing the 3D recognition.

First world problems

echo "127.0.0.1 update.libreelec.tv releases.libreelec.tv" >> /storage/.config/hosts.conf
reboot

Run that ^ over SSH

The fix will be in nightlies within 24h of this being merged: https://github.com/LibreELEC/LibreELEC.tv/pull/11756

You'll need to ask questions on the design intent in the Kodi forum; the author CrystalP is active there.

Quote from atoulmin

I noticed in the nightly builds that output for AMD radeon has shifted from YUV to RGB. Are we able to change that back? or at least offer a setting to switch?

AMD/Intel/nVidia cards *should* output in their native RGB format, and this is not a problem as long as the correct conversions are used; which are all broadcast standards. The change is that Kodi now implements and handles colour things correctly instead of not-handling them at all resulting in wrong output.

Make sure you have the GUI in expert mode.

Quote from plez

Any clue what's causing this ?

Linux 5.15+ removed support for NTLM: https://git.kernel.org/pub/scm/linux/…782eb68f61a179c

There was some discussion about reverting the change but Linus rejected the idea https://lore.kernel.org/all/CAHk-=wjSB…mail.gmail.com/ and a simple git revert no longer works due to surrounding code change in the kernel.

Some workarounds are mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=216682; AFPS support via FUSE is probably the right direction to move in. The original AFPS project looks to be quite dead but https://github.com/Netatalk/netatalk-client seems to be current and might be something we can package into an installable add-on similar to NTFS-3G.

I still have a TimeCapsule in a box somewhere, but I'm travelling and it will be a ~week before I can investigate further.