Jump to content


Photo

External tuner info

External tuner kernel

  • Please log in to reply
19 replies to this topic

#1 plasticassius

  • Member
  • 16 posts

0
Neutral

Posted 23 January 2019 - 13:49

Hello, I'm interested in using an external tuner with my Zgemma H5 box. If it's possible, would someone please point out some information about how I can pursue it?
 
In the "External Device Support" list on the wiki, I can see "Hauppauge pctv nanoStick T2 290e (DM8000)." Should I interpret that to mean it should work on my box as well?
 
I happen to have a "Hauppauge WinTV-soloHD (DVB-T,T2,C)" that I use on a Raspberry Pi with Tvheadend:
#uname -a

Linux raspberrypi 4.14.52+ #1123 Wed Jun 27 17:05:32 BST 2018 armv6l GNU/Linux

#cat /etc/debian_version 
9.4

#lsusb
Bus 001 Device 011: ID 2040:8268 Hauppauge

#dmesg
[1179392.896682] usb 1-1.3: new high-speed USB device number 11 using dwc_otg
[1179393.028314] usb 1-1.3: New USB device found, idVendor=2040, idProduct=8268
[1179393.028372] usb 1-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[1179393.028384] usb 1-1.3: Product: soloHD
[1179393.028394] usb 1-1.3: Manufacturer: HCW
[1179393.028403] usb 1-1.3: SerialNumber: 0014048643
[1179393.035771] em28xx 1-1.3:1.0: New device HCW soloHD @ 480 Mbps (2040:8268, interface 0, class 0)
[1179393.035800] em28xx 1-1.3:1.0: DVB interface 0 found: bulk
[1179393.046820] em28xx 1-1.3:1.0: chip ID is em28178
[1179395.188841] em28xx 1-1.3:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x69cec080
[1179395.188866] em28xx 1-1.3:1.0: EEPROM info:
[1179395.188880] em28xx 1-1.3:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[1179395.202792] em28xx 1-1.3:1.0:  AC97 audio (5 sample rates)
[1179395.202810] em28xx 1-1.3:1.0:  500mA max power
[1179395.202834] em28xx 1-1.3:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[1179395.205443] em28xx 1-1.3:1.0: Identified as PCTV tripleStick (292e) (card=94)
[1179395.205473] em28xx 1-1.3:1.0: dvb set to bulk mode.
[1179395.208677] em28xx 1-1.3:1.0: Binding DVB extension
[1179395.266131] i2c i2c-4: Added multiplexed i2c bus 5
[1179395.266160] si2168 4-0064: Silicon Labs Si2168-B40 successfully identified
[1179395.266172] si2168 4-0064: firmware version: B 4.0.2
[1179395.297061] si2157 5-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[1179395.297219] dvbdev: DVB: registering new adapter (1-1.3:1.0)
[1179395.297245] em28xx 1-1.3:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[1179395.299821] em28xx 1-1.3:1.0: DVB extension successfully initialized
[1179395.299850] em28xx 1-1.3:1.0: Registering input extension
[1179395.314075] Registered IR keymap rc-pinnacle-pctv-hd
[1179395.315090] rc rc0: 1-1.3:1.0 IR as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/rc/rc0
[1179395.315437] input: 1-1.3:1.0 IR as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/rc/rc0/input2
[1179395.315906] em28xx 1-1.3:1.0: Input extension successfully initialized
[1179395.609450] si2168 4-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[1179396.695891] si2168 4-0064: firmware version: B 4.0.25
[1179396.709348] si2157 5-0060: found a 'Silicon Labs Si2157-A30'
[1179396.760894] si2157 5-0060: firmware version: 3.0.5
[1179396.761004] em28xx 1-1.3:1.0: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000)

However, when I put it into the Zgemma H5 with Openpli 6.2, it doesn't seem to be recognized at all:
#cat /etc/version 
20181112154844

#uname -a
Linux STB 4.10.12 #1 SMP Thu May 17 07:36:43 CEST 2018 mips GNU/Linux

#lsusb -v
Bus 001 Device 004: ID 2040:8268

#dmesg
[1178935.643000] usb 1-1: new high-speed USB device number 4 using ehci-brcm

While writing, I came across a post from the Tvheadend boards: https://tvheadend.or.../4/topics/29460 Apparently the kernel needs some help to recognize the id of this tuner:
modprobe em28xx card=94
echo "2040 8268" > /sys/bus/usb/drivers/em28xx/new_id

So, now it seems that the module em28xx is not in the 4.10 kernel:

#modprobe em28xx card=94
modprobe: FATAL: Module em28xx not found in directory /lib/modules/4.10.12
 

I guess that the next thing I'll look into is whether the em28xx module is in the kernel that comes with Openpli 7.0. Looks like I have a reason to upgrade my firmware.


Edited by plasticassius, 23 January 2019 - 13:52.


Re: External tuner info #2 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 23 January 2019 - 14:34

If it comes with OpenPLi 7 you will have to install it first, we don't install anything by default that is not needed.

 

You can check with

opkg list | grep em28xx

if a kernel module exists that can be installed.


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.


Re: External tuner info #3 plasticassius

  • Member
  • 16 posts

0
Neutral

Posted 23 January 2019 - 14:59

Great! It looks like it's in 6.2. I installed it with

opkg install enigma2-plugin-drivers-dvb-usb-em28xx

Then, after

modprobe em28xx card=94
echo "2040 8268" > /sys/bus/usb/drivers/em28xx/new_id

it seems that the tuner is recognized:

[1192509.605000] usb 1-1: new high-speed USB device number 5 using ehci-brcm
[1192539.354000] usbcore: registered new interface driver em28xx
[1192573.747000] em28xx 1-1:1.0: New device HCW soloHD @ 480 Mbps (2040:8268, interface 0, class 0)
[1192573.747000] em28xx 1-1:1.0: DVB interface 0 found: bulk
[1192573.747000] em28xx 1-1:1.0: chip ID is em28178
[1192575.700000] em28xx 1-1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x69cec080
[1192575.700000] em28xx 1-1:1.0: EEPROM info:
[1192575.700000] em28xx 1-1:1.0: 	microcode start address = 0x0004, boot configuration = 0x01
[1192575.711000] em28xx 1-1:1.0: 	AC97 audio (5 sample rates)
[1192575.711000] em28xx 1-1:1.0: 	500mA max power
[1192575.711000] em28xx 1-1:1.0: 	Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[1192575.712000] em28xx 1-1:1.0: Identified as PCTV tripleStick (292e) (card=94)
[1192575.712000] em28xx 1-1:1.0: dvb set to bulk mode.
[1192575.748000] em28xx 1-1:1.0: Binding DVB extension
[1192575.748000] em28xx 1-1:1.0: no endpoint for DVB mode and transfer type 1
[1192575.748000] em28xx 1-1:1.0: failed to pre-allocate USB transfer buffers for DVB.
[1192575.748000] em28xx: Registered (Em28xx dvb Extension) extension

That seemed good, but Openpli doesn't list the tuner. Do you think it would be possible to use the external tuner along with the existing internal one?



Re: External tuner info #4 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 23 January 2019 - 15:35

If it works it should register itself as a tuner.

 

This doesn't look good:

[1192575.748000] em28xx 1-1:1.0: failed to pre-allocate USB transfer buffers for DVB.

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.


Re: External tuner info #5 ColinB

  • Senior Member
  • 743 posts

+28
Good

Posted 23 January 2019 - 22:08

I see on OATV forum

 

opkg install firmware-dvb-fe-si2168


Xtrend et8000 7.1-Release

2 x 8/1 DiSEqC  30w 13e 19e 23e 28e   

Astrometa USB Tuner Working DVB-T2 now on Kernel 4.10+  ;)

WD10EARX 1TB

Sandisk 32GB USB for AFB, EPG, Picons & Timeshift

 

ZGemma Star S 7.0-Release

4/1 DiSEqC  30w 13e 19e 28e

Sandisk 8GB USB for AFB, EPG, Picons & Timeshift

 

LG 49UH610V UHD-HDR

UHF/Cable/Sat

 

E-Channelizer

 

 

 


Re: External tuner info #6 ColinB

  • Senior Member
  • 743 posts

+28
Good

Posted 23 January 2019 - 22:12

More of the same from OATV

 

Installing the drivers ct2-dvb-usb-pctv292e was the crucial hint!
Now the stick is recognized as tuner C: Silicon Labs Si2168.
It can be switched between DVB-T2 and DVB-C.


Xtrend et8000 7.1-Release

2 x 8/1 DiSEqC  30w 13e 19e 23e 28e   

Astrometa USB Tuner Working DVB-T2 now on Kernel 4.10+  ;)

WD10EARX 1TB

Sandisk 32GB USB for AFB, EPG, Picons & Timeshift

 

ZGemma Star S 7.0-Release

4/1 DiSEqC  30w 13e 19e 28e

Sandisk 8GB USB for AFB, EPG, Picons & Timeshift

 

LG 49UH610V UHD-HDR

UHF/Cable/Sat

 

E-Channelizer

 

 

 


Re: External tuner info #7 plasticassius

  • Member
  • 16 posts

0
Neutral

Posted 23 January 2019 - 22:28

# opkg install firmware-dvb-fe-si2168
Collected errors:
 * opkg_prepare_url_for_install: Couldn't find anything to satisfy 'firmware-dvb-fe-si2168'.



Re: External tuner info #8 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 23 January 2019 - 22:48

I'll have a look.


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.


Re: External tuner info #9 plasticassius

  • Member
  • 16 posts

0
Neutral

Posted 23 January 2019 - 23:05

# opkg install firmware-dvb-demod-si2168-b40
Installing firmware-dvb-demod-si2168-b40 (1.1+git292+25f936b) on root.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/all/firmware-dvb-demod-si2168-b40_1.1+git292+25f936b-r0.3_all.ipk.
Configuring firmware-dvb-demod-si2168-b40.

# opkg install firmware-dvb-tuner-si2158-a20
Installing firmware-dvb-tuner-si2158-a20 (1.1+git292+25f936b) on root.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/all/firmware-dvb-tuner-si2158-a20_1.1+git292+25f936b-r0.1_all.ipk.
Configuring firmware-dvb-tuner-si2158-a20.

Neither of these packages helped.

 

I noticed that Openpli 6.2 has kernel 4.10, and my Raspbian image has kernel 4.14. So, I have the feeling that a more recent kernel has driver fixes for this. Now I think that trying Openpli 7.0 has some logic to it since it must have a more recent kernel. (Is that true?)



Re: External tuner info #10 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 23 January 2019 - 23:29

We can’t change the kernel version. Manufacturer delivers drivers for specific kernel version. So we have to use this version.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: External tuner info #11 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 23 January 2019 - 23:54

I'll have a look.


I'll add firmware-dvb-fe-si2168 to develop, and see if it builds. If it does, I'll backport it to 7.0-release, after which it will be in next Monday's image.


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.


Re: External tuner info #12 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 24 January 2019 - 00:22

In the meantime, what you can do is download https://github.com/o...58.zip?raw=true, and install it's contents on the box in /lib/firmware, and restart the box.

 

Please let me know if it works, so I don't do my work for nothing... ;)


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.


Re: External tuner info #13 plasticassius

  • Member
  • 16 posts

0
Neutral

Posted 24 January 2019 - 05:01

Sorry if I'm creating work for you, but of course I don't want you to do work for nothing...

 

I tried the firmware but, I'm afraid there's another problem:

modprobe em28xx card=94
echo "2040 8268" > /sys/bus/usb/drivers/em28xx/new_id

[  128.599000] usbcore: registered new interface driver em28xx
[  146.493000] em28xx 1-1:1.0: New device HCW soloHD @ 480 Mbps (2040:8268, interface 0, class 0)
[  146.493000] em28xx 1-1:1.0: DVB interface 0 found: bulk
[  146.493000] em28xx 1-1:1.0: chip ID is em28178
[  148.503000] em28xx 1-1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x69cec080
[  148.503000] em28xx 1-1:1.0: EEPROM info:
[  148.503000] em28xx 1-1:1.0: 	microcode start address = 0x0004, boot configuration = 0x01
[  148.516000] em28xx 1-1:1.0: 	AC97 audio (5 sample rates)
[  148.516000] em28xx 1-1:1.0: 	500mA max power
[  148.516000] em28xx 1-1:1.0: 	Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[  148.517000] em28xx 1-1:1.0: Identified as PCTV tripleStick (292e) (card=94)
[  148.517000] em28xx 1-1:1.0: dvb set to isoc mode.
[  148.586000] em28xx 1-1:1.0: Binding DVB extension
[  148.587000] ------------[ cut here ]------------
[  148.587000] WARNING: CPU: 1 PID: 556 at /openpli/oe/release-6.2/build/tmp/work-shared/h5/kernel-source/mm/page_alloc.c:3541 __alloc_pages_nodemask+0x3a8/0xc6c
[  148.587000] Modules linked in: em28xx_dvb(+) em28xx tveeprom nfsd ipv6 h5(FO) h5_3(O) h5_2(O) h5_1(O)
[  148.587000] CPU: 1 PID: 556 Comm: modprobe Tainted: GF          O    4.10.12 #1
[  148.587000] Stack : 00000000 00000000 809c7d9a 00000043 00000000 809c7d98 808ac520 00000009
[  148.587000]         aee83064 8092f167 8087201c 00000001 0000022c 809c384c 00010000 ac8889d8
[  148.587000]         aca5a800 80080374 00000000 0000000a 809c7d9a 00000000 80878d44 aca7f994
[  148.587000]         00000003 800cbd34 00000009 00000dd5 00000021 00000000 aca7f994 aee82d00
[  148.587000]         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  148.587000]         ...
[  148.587000] Call Trace:
[  148.587000] [<8000f91c>] show_stack+0x88/0xa4
[  148.587000] [<803b8e78>] dump_stack+0xd8/0x110
[  148.587000] [<80028464>] __warn+0x104/0x118
[  148.587000] [<80028508>] warn_slowpath_null+0x1c/0x34
[  148.587000] [<800d972c>] __alloc_pages_nodemask+0x3a8/0xc6c
[  148.587000] [<80017ca4>] mips_dma_alloc_coherent+0xd0/0x2ac
[  148.587000] [<8051cda4>] hcd_buffer_alloc+0xb8/0x1a0
[  148.587000] [<e1fd7d3c>] em28xx_alloc_urbs+0x214/0x4d0 [em28xx]
[  148.588000] [<e1ffd888>] em28xx_dvb_init.part.3+0xb4/0x30bc [em28xx_dvb]
[  148.588000] [<e1fd625c>] em28xx_register_extension+0x6c/0xc0 [em28xx]
[  148.588000] [<800015d8>] do_one_initcall+0x44/0x18c
[  148.588000] [<800cc080>] do_init_module+0x74/0x1d4
[  148.588000] [<800b3648>] load_module+0x2450/0x26f8
[  148.588000] [<800b3b7c>] SyS_finit_module+0xc8/0xe8
[  148.588000] [<80015d84>] syscall_common+0x34/0x58
[  148.588000] ---[ end trace fe1801519c563a90 ]---
[  148.588000] em28xx 1-1:1.0: unable to allocate 654573568 bytes for transfer buffer 0
[  148.590000] em28xx 1-1:1.0: failed to pre-allocate USB transfer buffers for DVB.
[  148.590000] em28xx: Registered (Em28xx dvb Extension) extension



Re: External tuner info #14 tappari

  • Senior Member
  • 121 posts

+2
Neutral

Posted 24 January 2019 - 08:27

I have this same problem with pctv 290e tuner in my VU+ Uno 4K SE. It works in VTI 14.0.1 image, but it has em28xx-dbv 1:4.1.20-r1.8 vti05 driver.


Edited by tappari, 24 January 2019 - 08:29.


Re: External tuner info #15 tappari

  • Senior Member
  • 121 posts

+2
Neutral

Posted 24 January 2019 - 11:49

This is how you see pctv 290e with VTi image:

 

Attached Files

  • Attached File  VTi.png   370.6KB   3 downloads


Re: External tuner info #16 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 24 January 2019 - 14:46

I have this same problem with pctv 290e tuner in my VU+ Uno 4K SE. It works in VTI 14.0.1 image, but it has em28xx-dbv 1:4.1.20-r1.8 vti05 driver.

 

Unfortunately that doesn't help much, VTI keeps their source closed, so we can't see what they do.

 

The em28xx driver is a kernel driver, so the kernel used dictates the version used, we build it as-is. If they added a different version, or patched it, we don't have access to it.

 

Can you check with "lsmod" what VTI has actually loaded, and then with "opkg info" what versions?


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.


Re: External tuner info #17 tappari

  • Senior Member
  • 121 posts

+2
Neutral

Posted 24 January 2019 - 15:14

  root@vuuno4kse:~# lsmod                                   
Module                  Size  Used by                     
ipv6                  282198  32                          
cxd2820r               22713  1                           
em28xx_dvb             19707  3                           
em28xx                 59779  1 em28xx_dvb                
tveeprom               11888  1 em28xx                    
brcmfb                  1475  3                           
dvb_bcm7252sse       2265016  31 brcmfb                   
dvb_base             5475486  7 dvb_bcm7252sse            
bcm_event               2907  5 dvb_bcm7252sse            
procmk                  1686  2 bcm_event,dvb_bcm7252sse  
root@vuuno4kse:~# ^C                                      
root@vuuno4kse:~#                                         



Re: External tuner info #18 WanWizard

  • PLi® Core member
  • 70,371 posts

+1,807
Excellent

Posted 24 January 2019 - 15:22

These are the modules used by the stick:

cxd2820r               22713  1                           
em28xx_dvb             19707  3                           
em28xx                 59779  1 em28xx_dvb                
tveeprom               11888  1 em28xx     

You can check with

opkg list | grep <driver>

for each of the drivers if there is a package for it, and if so, what version it is (replace "<driver>" with the name of the driver).

 

You can also check what OpenPLi loads and compare, to see if something is 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.


Re: External tuner info #19 tappari

  • Senior Member
  • 121 posts

+2
Neutral

Posted 24 January 2019 - 15:25

opkg info:

 

Attached Files



Re: External tuner info #20 plasticassius

  • Member
  • 16 posts

0
Neutral

Posted 25 January 2019 - 11:01

Version 7.0 20190121054719 behaves the same way as 6.2





Also tagged with one or more of these keywords: External tuner, kernel

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users