Posts by chewitt

add "systemd.debug_shell=ttyS0" to the APPEND line

dd on macOS uses =1m, on Linux it's =1M .. I always forget. Note that /dev/device does not exist, you need to swap that for the /dev/mmcblk? device that corresponds to the emmc. If you're booted from one of my images the output of "emmctool" will tell you what the /dev/device is.

Boot an LE image. Connect a 16GB (or larger) USB stick, formatted EXT4. Run "dd if=/dev/device of=/var/mount/USB/backup.img bs=1m" to clone the contents of emmc to a file on the USB drive. The /dev/device will be something like /dev/mmcblk0 .. whatever the internal emmc is, and where USB is the disk label for the USB drive. You'll have to figure out what these are. Once the backup is complete (it will take time) .. "dd if=/dev/zero of=/dev/device bs=1m" will erase the emmc. Once emmc is erased (and vendor u-boot is gone) the WP2 will find mainline u-boot on the SD card and use it.

It prevents spam posts from bots advertising miracle tablets that claim to help you lose <banned word> .. and we value the blocking (and resulting admin time saving) over the ocasional user inconvenience.

Official:Forum rules/Banned add-ons - Official Kodi Wiki <= no further support while you have banned add-ons installed. You will need to provide logs showing a clean system before anything else happens.

There is no further development on LE 9.2 so best thing would be to switch to LE10 nightly images. They are quite stable for RPi4 now. The video driver stack is completely different so you might find new and exciting issues, but if you do, they may be fixed (unlike LE9.2 where they won't be).

See if the currently RPi4 nightly images improve things for you. There will be no further development on MMAL support in Kodi (we removed it) or the LE 9.2 codebase (no further releases). At least if you see issues with the nightly images it's something that can be worked on.

Recent focus has been on getting RPi4 working as in many areas this is more complex and provides a superset of the functionality needed for older Pi models. Now that many of the big-ticket issues are resolved or have progressed (and the dynamics of the all-new code are starting to be much better understood) the attention can shift back towards RPi2/3 devices where changes are needed. There is desire/intent to make HEVC work on the new stack too, but it's entirely new code and it works very differently to the older stack, and people forget that it took several years of progressive tinkering to get it as good as it currently is on the older stack. NB: There's nothing to stop you (and many other RPi3 users) continuing to use LE 9.2.

I'm not sure what the issue is, but modern Kodi isn't going to run well on something that old, and while LE is lightweight we focus on the latest chips not older stuff so even if you get past the boot problem I wouldn't guarantee video output let alone hardware acceleration. If you're able to boot a desktop distro like Ubuntu that might be a better option. If you really want to run LE, any generation of Raspberry Pi board will trump the current archaeological exercise by a wide mile.

Default settings .. 1 min, and send low volume noise enabled. Neither of those settings will have anything to do with resume delays though.

[v3,1/1] Bluetooth: btrtl: Add support for RTL8761B - Patchwork

LE 9.2 uses a 5.1 kernel (quite old) and ^ the same change was applied to the Linux kernel last August, so update to a current LE10 nightly image (using a much newer kernel) and it will probably work. You can also drop/remove the config file change as the patch clearly shows this is optional not mandatory.

Settings > Media > Library > Manage Sources > Videos

Define (separate) source folders for Movies and TVshows, then you set the content type for each source and the scraper settings. Then (only then) do you scan the souurce to scrape content into the library views.

The Kodi wiki has good tutorials on scraping.

I run an RPi4 as the family daily driver and never see delays on resume, unless using WiFi which is the cause. Are you using Ethernet?

We don't have an issue booting in EFI or legacy BIOS modes (in fact BIOS is easier). What CPU and GPU are in the box?

levitsky86 Settings > System > Input > Peripherals > CEC Adapter

@reboot /usr/bin/bash /storage/path/to/script

^ see if adding the path to bash helps, and do the the same for the second line in crontab

mkdir -p /storage/.config/firmware/rtl_bt
echo "55ab 2387 0000 " > /storage/.config/firmware/rtl_bt/rtl8761a_config.bin
reboot

The "firmware" file is just a text file in the vendor driver package, so ^ should create it with the same content. No guarantee it works, but.. no harm in trying..

[   60.143680] Bluetooth: Core ver 2.22
[   60.143693] NET: Registered protocol family 31
[   60.143694] Bluetooth: HCI device and connection manager initialized
[   60.143698] Bluetooth: HCI socket layer initialized
[   60.143699] Bluetooth: L2CAP socket layer initialized
[   60.143702] Bluetooth: SCO socket layer initialized
[   60.148528] usbcore: registered new interface driver btusb
[   60.158058] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[   60.159228] Bluetooth: hci0: RTL: rom_version status=0 version=1
[   60.159230] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8761a_fw.bin
[   60.159952] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8761a_config.bin
[   60.159968] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761a_config.bin failed with error -2
[   60.159973] Bluetooth: hci0: RTL: cfg_sz -2, total sz 20204
[   60.183360] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   60.183362] Bluetooth: BNEP filters: protocol multicast
[   60.183366] Bluetooth: BNEP socket layer initialized
[   62.428020] Bluetooth: hci0: command 0xfc20 tx timeout
[   70.321349] Bluetooth: hci0: RTL: download fw command failed (-110)

^ looks like rtl8761a_fw.bin exists but rtl8761a_config.bin is missing .. although I don't see it in the upstream linux-firmware repo:

rtl_bt - kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel

I'm not sure what the story is .. but should give you something to go looking for. If you can find the firmware file, put it in /storage/.config/firmware/rtl_bt/ and reboot and it will be overlayed onto /usr/lib/firmware/rtl_bt where it needs to be.