Posted 15 August 2023 - 11:50
Think I've found the issue, it should be in the develop feed after the current build run is finished.
thank you very much. excited for the resut.
By the way, is there any way for a user to browse through different feeds? like I can do with debian or rpm repositories?
Posted 15 August 2023 - 12:27
Yep, just add the wanted repositories in /etc/apt/sources.d
Posted 15 August 2023 - 17:07
By the way, is there any way for a user to browse through different feeds? like I can do with debian or rpm repositories?
No, we don't have the index online (has historical reasons, thanks to other non-behaving developers).
Yep, just add the wanted repositories in /etc/apt/sources.d
apt? On a box? Or a box feed on a desktop linux?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 16 August 2023 - 10:07
Think I've found the issue, it should be in the develop feed after the current build run is finished.
something went wrong again, I assume.
Don't see it
Posted 16 August 2023 - 15:00
The problem seems to be the code that tries to determine the KERNEL_VERSION. It is needed to see if the package can be build or not (i.e. if the current kernel version supports it).
The build log says
run.sysroot_stage_all.2239032:export KERNEL_VERSION=""
which is not good.
I presume this is because it needs kernel files for this, but those don't exist if the kernel isn't rebuild in the same build run (which is hardly ever the case).
Back to the drawing board.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 16 August 2023 - 15:40
Just tested on the rc (can't n develop as it is running):
# $KERNEL_VERSION [2 operations]
# exported /openpli/oe/rc-9.0/meta-openpli/recipes-openpli/enigma2-dvb-drivers/dvb-usb-drivers-meta.bb:9
# [export] "1"
# set /openpli/oe/rc-9.0/meta-openpli/recipes-openpli/enigma2-dvb-drivers/dvb-usb-drivers-meta.bb:9
# "${@oe.utils.read_file('${STAGING_KERNEL_BUILDDIR}/kernel-abiversion')}"
# pre-expansion value:
# "${@oe.utils.read_file('${STAGING_KERNEL_BUILDDIR}/kernel-abiversion')}"
export KERNEL_VERSION=""
STAGING_KERNEL_BUILDDIR is "openpli/oe/rc-9.0/build/tmp/work-shared/vuduo4kse/kernel-build-artifacts", but
[build@buildserver3] $ ls -l /openpli/oe/rc-9.0/build/tmp/work-shared/vuduo4kse/kernel-build-artifacts ls: cannot access '/openpli/oe/rc-9.0/build/tmp/work-shared/vuduo4kse/kernel-build-artifacts': No such file or directory
But I found
[build@buildserver3] $ ls -l /openpli/oe/rc-9.0/build/tmp/pkgdata/vuduo4kse/kernel-depmod/ -rw-r--r-- 2 build build 12 Jul 31 23:38 kernel-abiversion -rw-r--r-- 2 build build 1779349 Jul 31 23:38 System.map-4.1.45-1.17
which has what we need
[build@buildserver3] $ cat /openpli/oe/rc-9.0/build/tmp/pkgdata/vuduo4kse/kernel-depmod/kernel-abiversion 4.1.45-1.17
New build is running, fingeres crossed.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 August 2023 - 08:46
seem to have worked.
installed enigma2-plugin-drivers-ct2-usb-dvbsky-t330
but. still no tuner.
root@stb1:~# opkg list-installed | grep -i usb-dvb enigma2-plugin-drivers-ct2-usb-dvbsky-t330 - 1.0-r0.1 root@stb1:~# lsmod Module Size Used by bluetooth 397033 4 ipv6 289640 76 brcmfb 1467 2 dvb_bcm7444 2002616 29 brcmfb dvb_base 5478453 5 dvb_bcm7444 bcm_event 2899 5 dvb_bcm7444 procmk 2104 2 dvb_bcm7444,bcm_event sr_mod 11676 0 cdrom 42256 1 sr_mod fuse 75343 1 root@stb1:~# lsusb Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 003: ID 0a5c:2045 Broadcom Corp. Bluetooth Controller Bus 005 Device 004: ID 0a5c:bd27 Broadcom Corp. Remote Download Wireless Adapter Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0572:0320 Conexant Systems (Rockwell), Inc. DVBSky T330 DVB-T2/C tuner Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 13fd:0840 Initio Corporation INIC-1618L SATA Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
maybe something wrong with the ipk:
root@stb1:~# opkg files enigma2-plugin-drivers-ct2-usb-dvbsky-t330 Package enigma2-plugin-drivers-ct2-usb-dvbsky-t330 (1.0-r0.1) is installed on root and has the following files:
?
Posted 17 August 2023 - 09:46
You have rebooted after installation I presume?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 August 2023 - 10:09
You have rebooted after installation I presume?
of course
I also tried hot plugging without success:
root@stb1:~# echo -n "usb4" > /sys/bus/usb/drivers/usb/unbind root@stb1:~# lsusb Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 003: ID 0a5c:2045 Broadcom Corp. Bluetooth Controller Bus 005 Device 004: ID 0a5c:bd27 Broadcom Corp. Remote Download Wireless Adapter Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 13fd:0840 Initio Corporation INIC-1618L SATA Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@stb1:~# echo -n "usb4" > /sys/bus/usb/drivers/usb/bind root@stb1:~# lsusb Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 003: ID 0a5c:2045 Broadcom Corp. Bluetooth Controller Bus 005 Device 004: ID 0a5c:bd27 Broadcom Corp. Remote Download Wireless Adapter Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 004: ID 0572:0320 Conexant Systems (Rockwell), Inc. DVBSky T330 DVB-T2/C tuner Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 13fd:0840 Initio Corporation INIC-1618L SATA Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@stb1:~# dmesg | tail -n10 [ 4926.143189] >>cid=1, sid=0 r=2 s=0 [ 4935.562163] >>cid=1, sid=0 r=2 s=0 [ 5356.946816] usb 4-1: USB disconnect, device number 2 [ 5367.033457] hub 4-0:1.0: USB hub found [ 5367.037492] hub 4-0:1.0: 1 port detected [ 5368.244264] usb 4-1: new high-speed USB device number 3 using ehci-brcm [ 5387.196908] usb 4-1: USB disconnect, device number 3 [ 5397.098388] hub 4-0:1.0: USB hub found [ 5397.102289] hub 4-0:1.0: 1 port detected [ 5398.309207] usb 4-1: new high-speed USB device number 4 using ehci-brcm root@stb1:~# lsmod Module Size Used by bluetooth 397033 4 ipv6 289640 76 brcmfb 1467 2 dvb_bcm7444 2002616 34 brcmfb dvb_base 5478453 5 dvb_bcm7444 bcm_event 2899 5 dvb_bcm7444 procmk 2104 2 dvb_bcm7444,bcm_event sr_mod 11676 0 cdrom 42256 1 sr_mod fuse 75343 1 root@stb1:~#
inspected the ipk:
root@stb1:~# curl -o enigma2-plugin-drivers-ct2-usb-dvbsky-t330_1.0-r0.1_vuduo4kse.ipk http://downloads.openpli.org/feeds/openpli-develop/vuduo4kse/enigma2-plugin-drivers-ct2-usb-dvbsky-t330_1.0-r0.1_vuduo4kse.ipk
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 694 100 694 0 0 7010 0 --:--:-- --:--:-- --:--:-- 7229
root@stb1:~# file enigma2-plugin-drivers-ct2-usb-dvbsky-t330_1.0-r0.1_vuduo4kse.ipk
enigma2-plugin-drivers-ct2-usb-dvbsky-t330_1.0-r0.1_vuduo4kse.ipk: Debian binary package (format 2.0), with control.tar.gz, data compression xz
root@stb1:~# ar t enigma2-plugin-drivers-ct2-usb-dvbsky-t330_1.0-r0.1_vuduo4kse.ipk
debian-binary
control.tar.gz
data.tar.xz
root@stb1:~# ar x enigma2-plugin-drivers-ct2-usb-dvbsky-t330_1.0-r0.1_vuduo4kse.ipk
root@stb1:~# tar -tJvf data.tar.xz
root@stb1:~# tar -tzvf control.tar.gz
-rw-r--r-- 0/0 533 2023-05-26 23:01:45 ./control
only the control file (metadata?) is present, no files in package
Edited by paneologist, 17 August 2023 - 10:15.
Posted 17 August 2023 - 10:32
It is a meta package (check the control file).
It should install as dependency
so perhaps one of those is still missing?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 August 2023 - 10:45
ok. not that familiar with those packages. I am more familiar with rpm.
so, yes there's something missing:
root@stb1:/media/hdd# opkg list-installed | grep -iE "(kernel-module-dvb-usb-dvbsky|kernel-module-si2157|kernel-module-si2168|firmware-dvb-demod-si2168-b40)" firmware-dvb-demod-si2168-b40 - 1.1+git296+4b2b151-r0.6 kernel-module-si2157-4.1.45-1.17 - 4.1.45-r0.1.3.2 kernel-module-si2168-4.1.45-1.17 - 4.1.45-r0.1.3.2
hm..:
root@stb1:/media/hdd# opkg verify root@stb1:/media/hdd# echo $? 0 root@stb1:/media/hdd# opkg install kernel-module-dvb-usb-dvbsky No packages installed or removed. root@stb1:/media/hdd# opkg list-installed | grep kernel-module-dvb-usb-dvbsky root@stb1:/media/hdd# opkg list | grep kernel-module-dvb-usb-dvbsky
seems that package is missing. but opkg doesn't complain.
the control file says "Recommends: firmware-dvb-demod-si2168-b40, kernel-module-dvb-usb-dvbsky, kernel-module-si2157, kernel-module-si2168" - shouldn't it be required?
Posted 17 August 2023 - 14:42
Limitation of bitbake.
If you change recommends by depends in the build, it won't build at all, because there are no build recipes for those kernel modules, they are a product of building the linux kernel.
I'll have to check if kernel-module-dvb-usb-dvbsky is enabled in the kernel defconfig for the Duo 4K SE, but I wouldn't know why not if it worked in 8.3-release, defconfigs usually don't change.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 August 2023 - 15:02
Limitation of bitbake.
If you change recommends by depends in the build, it won't build at all, because there are no build recipes for those kernel modules, they are a product of building the linux kernel.
I'll have to check if kernel-module-dvb-usb-dvbsky is enabled in the kernel defconfig for the Duo 4K SE, but I wouldn't know why not if it worked in 8.3-release, defconfigs usually don't change.
iirc, there wasn't a ...-t330 driver in the release, just the ...-s960 (with that installed a kernel module "dvb_usb_dvbsky" has been loaded - but still hadn't a tuner)
Posted 17 August 2023 - 20:49
Here's the problem, as I expected:
./meta-vuplus/recipes-bsp/linux/linux-vuduo4k-4.1.45/vuduo4k_defconfig:# CONFIG_DVB_USB_DVBSKY is not set ./meta-vuplus/recipes-bsp/linux/linux-vuduo4kse-4.1.45/vuduo4kse_defconfig:# CONFIG_DVB_USB_DVBSKY is not set ./meta-vuplus/recipes-bsp/linux/linux-vuuno4kse-4.1.20/vuuno4kse_defconfig:# CONFIG_DVB_USB_DVBSKY is not set ./meta-vuplus/recipes-bsp/linux/linux-vuzero4k-4.1.20/vuzero4k_defconfig:# CONFIG_DVB_USB_DVBSKY is not set
( all other VU+ boxes have a kernel version that is too old for this driver).
I've updated the BSP, should be in develop sometime tomorrow.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 19 August 2023 - 09:12
not there yet :-(
Posted 19 August 2023 - 10:28
( all other VU+ boxes have a kernel version that is too old for this driver).
Not true in fact… I own a VU+SoloSE v2 and one of the last ever updates from VU+ enabled exactly this device! Even being a MIPSEL box. In fact, when I bought this TurboSE v2 tuner it was the ONLY box it worked on!
They had backported the drivers for this kernel…
On OpenPli it took much longer and worked only on >=3.18 kernels..
Posted 19 August 2023 - 17:06
Backporting drivers is always an option, if you have the source, the skills and the time.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 19 August 2023 - 17:12
not there yet :-(
It doesn't compile, due to a conflict with another driver in the BSP:
NOTE: recipe hmp-usb-dvb-t2-c-arm-V160430-r1: task do_packagedata: Started
ERROR: hmp-usb-dvb-t2-c-arm-V160430-r1 do_packagedata: The recipe hmp-usb-dvb-t2-c-arm is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/data/openpli/pli-oe/develop/build/tmp/pkgdata/vuduo4k/runtime/kernel-module-dvb-usb-dvbsky-4.1.45-1.17
(matched in manifest-vuduo4k-linux-vuduo4k.packagedata)
Please verify which recipe should provide the above files.
The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
so probably switched off by VU+ for a reason...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 19 August 2023 - 17:22
just an assumption:
enigma2-plugin-drivers-ct2-usb-dvbsky-t330 also provided a kernel module "dvb_usb_dvbsky" (in release 8.3)
Posted 19 August 2023 - 17:27
This by the way also means the kernel-module-dvb-usb-dvbsky is already build as part of that package, so you need to install hmp-usb-dvb-t2-c-arm.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
0 members, 3 guests, 0 anonymous users
