Please run "lsmod | sort | paste" and share the URL, thanks.
Posts by chewitt
-
-
Now you have a working image we need to rebuild/test with different BlueZ versions. To guide the process we will download sources for BlueZ and start a "bisect" process in the BlueZ source directory by marking known-good (v5.72) and known-bad (v5.73) release commits (using the commit githashes):
Codecd ~/ git clone https://github.com/bluez/bluez cd bluez git bisect good 770ad5614e7e8074133e6f563495ce4822f63fe4 git bisect bad 19f8fcdc2084048bebe5bd9ea4fb97f7ece16df0 git bisect startBisect will now suggest a githash to test. Change to the LE buildsystem (open another tab in Terminal to make copy/pasting easier) and edit packages/network/bluez/package.mk and make changes:
Diff
Display More--- a/packages/network/bluez/package.mk +++ b/packages/network/bluez/package.mk @@ -3,11 +3,11 @@ # Copyright (C) 2019-present Team LibreELEC (https://libreelec.tv) PKG_NAME="bluez" -PKG_VERSION="5.73" -PKG_SHA256="257e9075ce05c70d48c5defd254e78c418416f7584b45f9dddc884ff88e3fc53" +PKG_VERSION="770ad5614e7e8074133e6f563495ce4822f63fe4" +PKG_SHA256="" PKG_LICENSE="GPL" PKG_SITE="http://www.bluez.org/" -PKG_URL="https://www.kernel.org/pub/linux/bluetooth/${PKG_NAME}-${PKG_VERSION}.tar.xz" +PKG_URL="https://github.com/bluez/bluez/archive/${PKG_VERSION}.tar.gz" PKG_DEPENDS_TARGET="toolchain dbus glib readline systemd" PKG_LONGDESC="Bluetooth Tools and System Daemons for Linux." PKG_TOOLCHAIN="autotools"^ We change PKG_VERSION to use whatever githash bisect is asking to test (change this each time). We also null PKG_SHA256 so it is ignored (to make testing easier). We also change PKG_URL to download from the BlueZ mirror on GitHub instead of the normal repo as this supports downloading at any githash in the repo (the kernel repo only has release versions).
Once package.mk is modified, run the "PROJECT=xxx ARCH=xxx" image build command again and the buildsystem will detect the BlueZ package changed and it will rebuild that package and create a new image. You can then transfer (e.g. scp) the built image (.img.gz or .tar file) to /storage/.update/ on your test device and reboot to see if the image works?
If the image is good run "git bisect good" in the BlueZ source dir, and if bad run "git bisect bad" and bisect will suggest another githash to test. Keep repeating this process (edit githash, rebuild, test, mark good/bad) until bisect tells you the first bad (breaking) commit. Then report back here with that info.
Good luck

-
how do I create an image of the SD card that can be useful for later use with multitool on the TV box?
Sorry.. no idea and subzero interest in investigating the topic further. As a rule backup/restore of /storage contents is always easier and faster than trying to "full-image" devices so I'd recommend learning some basic tar/untar commands.
-
Banned add-ons are installed. Your problem is not our problem.
-
OpenVPN works fine here so it's something related to your configuration or a third-party add-on that needs updating not the OS image.
-
I really hope there's a way to get the wifi working
Not happening. The SSV6501P chip has no driver that works on Amlogic hardware and upstream kernels. Some Armbian devs have wrangled the rather horrific vendor code to use on Rockchip boards, but in the process of simplifying the code for their Rockchip needs they removed support for the Amlogic chip implementation. You'll need to use an external USB dongle for WiFi.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Put Kodi in debug mode and reboot, then share the URL generated by "pastekodi"
-
No log(s) provided.
-
Please provide/share some media samples that Pi devs can have a look at.
-
If the upstream kernel only shows normal 720p; that's what's supported. The better option would be using the HDMI input no the TV and having normal 1080p available.
-
Enable persistent logging in LE settings. Enable debug logging in Kodi. Reboot to generate clean logs. Then connect a USB drive and copy logs from the following locations to the USB drive using the Kodi file manager:
/storage/.cache/log/journal/*
/storage/.kodi/temp/kodi.log
Use the LE12 image as the LE11 codebase is now EOL and will not receive fixes (only add-on bumps).
-
Would you mind adding a ffmpeg plugin with the 4.4.x ffmpeg version as a alternative?
There's no info on your hardware/codecs/configuaration or Tvheadend configuration, and no debug logs ..

So assuming there is a real problem (not related to client-side drivers) the issue should be reported to Tvheadend devs so it can be investigated. If the problem is in Tvheadend (as you suggest) that's where a fix is required; we have no interest in packaging retro ffmpeg versions for workarounds.
-
Use connmanctl to join a WiFi network ^
Code<advancedsettings version="1.0"> <!-- enable debug logging --> <loglevel hide="false">1</loglevel> </advancedsettings>Then create /storage/.kodi/userdata/advancedsettings.xml with ^ that content and reboot so Kodi is in debug mode. Then run "pastekodi" and share the URL generated so I can see the system log and Kodi log.
-
Not sure how you are running Transmission (nor do we care to know) .. but it wasn't provided by LE so it's not something you will receive support on in this forum. Go read forum rules again.
-
-
-
dhomas Have you tried a clean install vs. upgrade? (or stop Kodi and rename /storage/.kodi to sidestep all current config). I ran a boot test on LE12 to look at alleged audio issues with an ageing Xtreamer Ultra2 (ION) board a couple of weeks ago (first boot in nearly a decade) and audio was working for me.