AC3/DTS 5.1 is transported over 2.0 PCM channels.
Posts by mglae
-
-
Good to hear that it is working.
I ended up putting a copy of both mt7662.bin and mt7662_rom_patch.bin (without the u, just renamed the original files), in firmware, the ones WITH u's in mediatek:
/storage/.config/firmware
/storage/.config/firmware/mediatek/
I'm not sure which one got it going but it worked. I got the idea for the two different sets from this post ASUS USB-N53 B1: failed to load ROM patch · Issue #232 · openwrt/mt76 · GitHub (LorenzoBianconi, really who seems to know what he is doing, unlike me ).The files in firmware/mediatek/ are used by the kernel 4.19.36 driver (shown in your modinfo post).
The kernel 5.1.1 driver is looking for them firmware/ with different name - please don't ask me why
For future reference, the FOUR files I used, I found in kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel, in the latest gz file. It's a 78M file with ALL the firmware, my file name was linux-firmware-20190514.tar.gz. I extracted it with Z-Zip, found the files in:
You can copy only the needed files directly from the linux-firmware git tree using the plain links.
-
For DTS and/or AC3 only configuration you have to set 2.0 channels.
For the records: start with the Audio quickstart guide - Official Kodi Wiki when configuring audio.
-
Please check file name again.
-
Put mt7662_rom_patch.bin into /storage/.config/firmware and reboot. It will be automatically linked to /var/lib/firmware.
You may have to rename mt7662u_rom_patch.bin from linux-firmware if there is no other firmware file.
-
Please type journalctl|paste and post the link after a fresh reboot and authentication try.
-
-
Audio quickstart guide - Official Kodi Wiki
Use TV (AC3) and add DTS.
-
yubby Meganiekje Sorry, wrong thread. LE 8.2.5/Kodi 17 do not support VAAPI on AMD.
-
Add the radeon.lockup_timeout=xxxxx kernel parameter, see this post.
-
To create a USB stick installation just type "run" on first boot of the installer image (or select the grub menu entry on EFI32 devices).
-
I expect a Grub boot menu.
But the shift key detection is not implemented in LE, my fault.
With the BIOS being activated by <esc> finding the right timing for pressing the key may be difficult.
Creating a LE 9 installation stick and booting from USB looks like the easiest test environment to use. -
I see. timeout=0, the boot menu is not visible by default. Try to hold the <shift> key at boot or press the <Esc> key to activate it.
Navigate to the boot entry and press <e> to edit. The changes are not stored.
Or create an installation stick and boot from USB.
-
So it looks as though the code in this commit has been removed at some point and for some reason.
The code is still there.
Furthermore the update does not alter the existing boot configuration. You can try to <e>dit the boot entry from the grub boot menu and replace "quiet" with "debug textmode" to see boot messages.
-
-
Please use your favorite web search, it's long ago that I did use one of these tools.
-
Try the *zap* tools from dvb-tools addon matching your DVB system.
-
Code
Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: lzo decompression failed, data probably corrupt Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: squashfs_read_data failed to read block 0x73a23cf Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: lzo decompression failed, data probably corrupt Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: squashfs_read_data failed to read block 0x73a23cf Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: lzo decompression failed, data probably corrupt Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: squashfs_read_data failed to read block 0x73a23cf
Exchange your SD card.