Just to explain my suggestion: Here is a user, who had no audio after suspend, and firmware update was the fix:
Posts by Da Flex
-
-
Make sure your firmware (especially BIOS and HDMI) is up-to-date. This might require Windows.
CodeMar 22 18:46:11.274800 LibreELEC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS01], AE_NOT_FOUND (20230628/dswload2-162) Mar 22 18:46:11.274809 LibreELEC kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220) Mar 22 18:46:11.274817 LibreELEC kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010) Mar 22 18:46:11.274826 LibreELEC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS02], AE_NOT_FOUND (20230628/dswload2-162) Mar 22 18:46:11.274834 LibreELEC kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220) -
Wrong logs.
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 -
-
I see no reason to consider running Kodi as a dedicated OS if you have Shield. LibreELEC or CoreELEC won't improve anything.I agree. The Shield is the big exception on the market of Android boxes. nVidia has the money to deliver updates over a long time span. Owners of cheaper Android boxes love the option to install an OS like ours.
-
Running Kodi 21 RC2 on my Shield Pro, it plays Dolby Vision.
That's an app, not an independent OS, right?
-
If your TV supports DV then I recommend to get a DV TV box. I have Nvidia Shield tube(32bit) along with another ~15 different android TV boxes and the Shield is the only one I use because of DV.
DV is AMAZING!Dolby Vision needs a device with a dedicated license. To my knowledge, only one device has such a license, and can run Kodi as an independent OS, and that's on CoreELEC (go to CoreELEC forum for details).
-
Fine. Your electromagnetic environment might be the cause. If the issue appears again, try a 4K cable (HDMI 2.0 or 2.1 standard). Those cables have better shielding.
-
From what you say, it could be a hardware defect at HDMI-0. That's why you should try RPi OS on another microSD.
If you use a 4K display, make sure to use an HDMI 2.0 or 2.1 cable. Sometimes a slightly higher data rate leads to HDMI interruption due to a bad cable.
-
HDMI-1 doesn't support CEC by design. A/V should work on both ports without special configuration.
Did HDMI-0 ever worked with another OS? If LE is your first OS on RPi4, try RPi OS.
-
I've separated ION posts to provide more clarity, and more attention to this topic.
At your ALSA device list three devices have the same display name "HDA NVidia" (Analog, S/PDIF and HDMI). Seems like you or the system (naming confusion) have picked the wrong device:
Code2024-02-10 19:42:37.553 T:924 debug <general>: CActiveAESink::OpenSink - ALSA Initialized: 2024-02-10 19:42:37.553 T:924 debug <general>: Output Device : HDA NVidia 2024-02-10 19:42:37.553 T:924 debug <general>: Sample Rate : 44100 2024-02-10 19:42:37.553 T:924 debug <general>: Sample Format : AE_FMT_S32NE 2024-02-10 19:42:37.553 T:924 debug <general>: Channel Count : 2 2024-02-10 19:42:37.553 T:924 debug <general>: Channel Layout: FL, FR 2024-02-10 19:42:37.553 T:924 debug <general>: Frames : 464 2024-02-10 19:42:37.553 T:924 debug <general>: Frame Size : 8 -
Which output options do you have at LE's audio settings? Maybe the wrong output device is currently selected.
-
Make sure that all your firmware is up-to-date. This can be challenging, because you probably need Windows for that.
-
How do you script a daily graceful shutdown schedule in LE ?
LE has cron service. Use our search function (magnifier icon) for details.
-
So you own an Acer AspireRevo R3610. Specs say it's an nVidia MCP7A-ION. I think that's the "audio chip" in this case.
Thanks, and wait for chewitt now.
-
Sadly, in my case the audio problem continues to present itself with no resolution.
Can you say something about your audio chip? Or open the box, and make a hi-res photo with all chips. So you and chewitt could compare ION hardware.
To me it looks like the driver doesn't offer any usable sample rate:
CodeFeb 10 19:42:50.883122 LibreELEC kernel: perf: interrupt took too long (2730 > 2500), lowering kernel.perf_event_max_sample_rate to 73200 Feb 10 19:42:51.643620 LibreELEC iwd[412]: wiphy_estimate_data_rate() failed Feb 10 19:42:51.645612 LibreELEC iwd[412]: wiphy_estimate_data_rate() failed Feb 10 19:42:51.645612 LibreELEC iwd[412]: wiphy_estimate_data_rate() failed Feb 10 19:42:51.645612 LibreELEC iwd[412]: wiphy_estimate_data_rate() failed Feb 10 19:43:08.987290 LibreELEC kernel: perf: interrupt took too long (3798 > 3412), lowering kernel.perf_event_max_sample_rate to 52500 Feb 10 19:43:45.921340 LibreELEC kernel: perf: interrupt took too long (4876 > 4747), lowering kernel.perf_event_max_sample_rate to 40800chewitt Which sample rate is in use on your setup? Maybe your setup can play an unusual sample rate (40800Hz, see log snippet), but the setup of paperbackwriter can't.
-
Code
2024-03-18 17:52:36.351 T:1284 error <general>: ffmpeg[0x4634568]: [hevc] frame_post_process: Decode fail 2024-03-18 17:52:36.352 T:1284 debug <general>: CDVDVideoCodecDRMPRIME::Reset - flush buffersTry LE 12 Beta. If the issue persists, try without DRM Prime (gear icon menu at playback bar).
-
I'm running LE 11.0.6 on Raspi 4. Does this procedure works with the current version ?
Yes. Eventually you have to overclock for higher resolutions.
