![]() When I re-plugged my USB adapter and checked dmesg, I saw it picks up the file. I accessed the supervisor container, created /data/firmware/ and copied a missing firmware file into it ( v4l-cx231xx-avcore-01.fw), and saw the symlink was no longer broken. As I was poking around and found my way into the host filesystem, I saw there was a broken symlink at /lib/firmware/updates which points to /mnt/data/supervisor/firmware/. On other systems (RaspberyPi OS or Kodi) works I've seen your struggles around the different issue trackers/forums as I have been fighting this myself. 08:11:38.552 START: HTS Tvheadend version 4.2.8 started, running as PID:368 UID:0 GID:0, CWD:/run/s6/services/tvheadend CNF:/config/tvheadend 08:11:38.551 epgdb: gzip format detected, inflating (ratio 72.3% deflated size 138) 08:11:38.547 epggrab: module xmltv created 08:11:38.547 epggrab: module pyepg created 08:11:38.545 epggrab: module opentv-ausat created 08:11:38.545 epggrab: module opentv-skynz created 08:11:38.544 epggrab: module opentv-skyuk created 08:11:38.541 epggrab: module opentv-skyit created 08:11:38.527 epggrab: module psip created 08:11:38.527 epggrab: module Bulsatcom_39E created 08:11:38.527 epggrab: module viasat_baltic created 08:11:38.526 epggrab: module nz_freeview created 08:11:38.526 epggrab: module uk_freeview created ![]() 08:11:38.526 epggrab: module uk_freesat created 08:11:38.526 epggrab: module eit created 08:11:38.526 descrambler: adding CAID 2600 as constant crypto-word (BISS) 08:11:38.525 csa: Using 32bit parallel descrambling 08:11:38.520 dvr: Creating new configuration '' 08:11:37.004 scanfile: ISDB-T - loaded 2 regions with 1297 networks 08:11:37.004 scanfile: ATSC-C - loaded 1 regions with 5 networks 08:11:37.004 scanfile: ATSC-T - loaded 2 regions with 12 networks 08:11:37.004 scanfile: DVB-C - loaded 19 regions with 64 networks 08:11:37.004 scanfile: DVB-T - loaded 44 regions with 1124 networks 08:11:37.004 scanfile: DVB-S - loaded 1 regions with 115 networks 08:11:36.491 config: scanfile (re)initialization with path Or support in, e.g., GitHub, forums or the Discord chat. Please, share the above information when looking for help ![]() System: Home Assistant OS 9.4 (aarch64 / raspberrypi4-64) You are running the latest version of this add-on. executing container initialization scripts. ensuring user provided files have correct perms.exited 0. making user provided files available at /var/run/s6/etc.exited 0. brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 cxd2880 spi0.0: DVB: registering adapter 0 frontend 0 (Sony CXD2880). dvbdev: DVB: registering new adapter (CXD2880) Looks for me like it is unable to either start a driver or detect the right firmware. usbcore: registered new interface driver btusb` usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-2.1: New USB device found, idVendor=9022, idProduct=d660, bcdDevice= 0.01 `dmesg | egrep "firmware|dvb|frontend|usb" If you use the COMMUNITY SSH & Terminal AddOn you can issue "dmesg" and get your kernel logs. I´m digging the same thing with a USB DVB-S2 device. Thanks for pointing me into the right direction! :) So far, I cannot setup the Tvheadend add-on with the DVB-C/T/T2 stick, as nothing is shown in the WebGUI config under the DVB inputs/TV adapters. If they were, where should I store them, and would the Tvheadend add-on and/or the HA OS recognize them at all? Therefore, I do not know, if some firmware file(s) is/are missing. However, on HA OS (despite reading various docu & FAQs), I could not find a way to see anything when plugging the stick in. On plain Raspberry Pi OS, this would be tail -f /var/log/messages. First, I would like to know how I can "tail -f" when pluggin it in to see what happens. However, when I use Home Assistant OS and your Tvheadend add-on, the stick is not recognized. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |