official image yes, but not if you update with "apt-get dist-upgrade)" there is 4.9.24.
i can try with rpi-update as well... but as i said for me the raspbian build works fine...
Please confirm what "uname -a" reports when working fine and try rpi-update to see if it changes things.
Your results and metaron's results don't match so it would be good to understand the discrepancy.
Display MoreI've just tried with Raspbian Pixel jessie (official image):
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux
pi@raspberrypi:~ $ apt-cache show kodi
Package: kodi
Version: 2:17.1-1~jessie
pi@raspberrypi:~ $ apt-cache show tvheadend
Package: tvheadend
Version: 4.0.8~jessie
no problem at all, DVB-S with DVB-Sky960CI running smoothly, no artefacts visible!
Can anyone else reproduce this? It seems a very significant result, but surprising, so more confirmation would be good.
This can be done without kernel modifications. See:
Raspberry Pi • View topic - Controlling LAN LEDs individually
As compiling on LE is tricky, here is a build I did on raspbian that works fine on LE.
wget -O llctl "https://drive.google.com/uc?id=0B-6zmEDJwxZEbmJkU3g2MlhMQWs&export=download"
chmod +x llctlYou can now turn off LEDS with
./llctl f0 l0 d0and turn them on with
./llctl f1 l1 d1Are you able to measure the voltage on the Pi0 (between 5V and GND on gpio header)?
That would be one likely reason for this issue.
Is this when in GUI or only when playing video?
I'll give it a try, any suggestions?
I wanted to try the new video player updates from FernetMenta
That doesn't require ffmpeg 3.3.
Last night's milhouse build includes the vpupdates commits (without bumping ffmpeg).
I have the following setup: Raspberry Pi Zero W with LibreELEC 8.01, a Samsung TV (LE40B530) and a Logitech Z-5500 surround set.I cannot get audio to work. Tried different settings, with or without passthrough - it just will not play sound. Even if i put my TV back to internal speakers it will not play any sound.
Can anyone assist me with this?
Can you start with posting a debug log?
My colleague Phil has testes the pwm-2chan overlay on a Pi0W and it is working.
Can you try removing "audio_pwm_mode=2"?
I don't think that is the problem, but it is a non-standard option that should be ruled out.
Can you try running raspi-gpio. Here is version from raspbian that should work on LE
uc?id=0B-6zmEDJwxZEY1RXb0ZpNi04VEU&export=download
Report output of "./raspi-gpio get" with the pwm-2chan overlay present.
aplay will output to the default device, which will be hdmi if a hdmi display supporting audio is attached (is it?)
You can force pwm output with:
amixer cset numid=3 1Can you just confirm that you have selected analogue audio output (rather than hdmi) in system/audio settings?
Netflix (and Amazon Prime) will work on Pi. I've had 720p video with 5.1 audio working perfectly on mine.
Not released yet and will require a Kodi 18 build. See:
Plugin brings Netflix to Kodi Media Center (unofficially, but without breaking DRM) - Liliputing
Kodi Is Getting A Proper Netflix Plugin - Phoronix
But you'll have to wait until it is released.
Just to clarify, passthrough of DTS-HD and TrueHD is not supported on any Pi.
The Pi (at least Pi2 and Pi3) can decode those formats and output them through HDMI as 8 channel PCM.
That is likely to sound identical to the passed through version. (The decoders are bit exact).
Kodi will always open every archive file (zip/rar) in the same directory as the video file to look for subtitles.
Having very large archives in the directory can make kodi very slow and possibly crash.
Try to keep your directories clean and tidy.
Can you try switching deinterlace method from automatic to bob.
I will. However I am very disappointed. So far I thought RPi is very capable for a HTPC with DVB receiving capability. Now I can see it is on the edge when wathcing a single HD channel. I assume paralel recording or timeshifting can be completely forgotten.
Just select deinterlace to Bob (x2) and then set as default for all videos and the problem is gone.
Note, Bob (x2) was the default on Jarvis so you haven't lost anything.
Currently advanced deinterlace is not compatible with some dvb dongles running on the same Pi.
I'd like to know this myself. I noticed the inferior performance of kernel 4.9 back in December with Milhouse build #1215. The issue is easy to reproduce as long as you have a DVB tuner connected to the Pi and PVR server/client are on the same Pi. The difference in performance is huge, with kernel 4.8 I can run this setup without a single issue (with Advanced deinterlacing enabled). With kernel 4.9 I absolutely have to disable Advanced deinterlacing (even increasing arm_uc doesn't help).
I'll need to dig in to see exactly what changed between 4.8 and 4.9.
4.9 kernel uses more upstream drivers, including the upstream interrupt controller. 4.8 may have still been using the downstream one (I'd have to check).
That could mean either a difference in speed to dispatching the ISR (I would have thought that difference would be small) or a difference in precedence
(i.e. if a USB and a timer ISR are both pending which gets dispatched first) which may have more of an effect.
There is also a FIQ driver that USB uses.
Can you point sakos at your build to see if it helps his issue too?
Use an older, pre-kernel 4.9 build (or my custom 7.95.2 build) + "arm_uc 12 0" and the errors should be gone.
Which kernel does your custom build use?
I can't think of a reason why an older kernel would work better, but if it does I'd like to know why.
There have been some libcec changes and some firmware changes between Jarvis and Krypton.
If you are having trouble with CEC on Pi, you can try reverting the firmware back. Download the following two file:
start.elf?raw=true
fixup.dat?raw=true
and replace the ones on the sdcard (take a copy of the old files in case you want to switch back after testing).
These files should be visible when the sdcard is inserted into a PC with an sdcard reader (assuming a direct LibreELEC install, rather than a NOOBS install).
Power off the TV from mains for a minute. Check you are seeing a problem. Revert the firmware. Power off the TV from mains for a minute. Report if any difference in behaviour.