yes , works without problems
No, it does NOT !!!
Tested the above device ~2 weeks ago on last LE release and on some vanilla/distro kernels on Fedora 27 (x64_86)
ID 0b48:3011 TechnoTrend AG TT-connect S2-4600
=> BUG: unable to handle kernel NULL pointer dereference
see => BUG: unable to handle kernel NULL pointer dereference
same Bugs in
- DVBSky S960
- TerraTec Cinergy S2 Rev.4 (ID 0ccd:0105)
Technotrend and TerraTec was tested by me
esp. Technotrend I got an additional error message sort of "overcurrent on usb port xyz"
not so on TerraTec ...
If they would work I would go for a TerraTec again
worked for me O_o
not saying there is no bug, but no problems so far
This tuner works for me too on rpi3.
Hello,
So I have a Raspberry Pi 3 now connected to the TT Connect s2-4600 with the official power supply and a 16GB microSD Card with latest Noobs installed on it and I have now a dual boot with Raspbian and Librelec.
On Libreelec I have managed to Install Tvheadend 4.2 and Tvheadend HTSP Client and then Rebooted the system.
After that I made sure the the PSU of the tuner is working by checking it using voltmeter. and I have checked /lib/firmware and I have found the three files that are related to the device installed already
1- dvb-fe-ds300x.fw
2- dvb-fe-ds3103.fw
3- dvb-demod-m88ds3103.fw
Display MoreNo, it does NOT !!!
Tested the above device ~2 weeks ago on last LE release and on some vanilla/distro kernels on Fedora 27 (x64_86)
ID 0b48:3011 TechnoTrend AG TT-connect S2-4600
=> BUG: unable to handle kernel NULL pointer dereference
see => BUG: unable to handle kernel NULL pointer dereference
same Bugs in
- DVBSky S960
- TerraTec Cinergy S2 Rev.4 (ID 0ccd:0105)
Technotrend and TerraTec was tested by me
esp. Technotrend I got an additional error message sort of "overcurrent on usb port xyz"
not so on TerraTec ...
If they would work I would go for a TerraTec again
And the result is : The device "does not" work, it has not been detected by tvheadend when I accessed it using mozilla Firefox from windows. Tvheadend worked but I did not find the device listed under DVB Inputs. Same case with Raspbian+tvheadend
So I have tried to install the drivers myself (I have installed linux headers and found build essentials already installed)
sudo apt-get install raspberrypi-kernel-headersbut: "s2-TT4600-linux-20120815" and "liplianin-s2-liplianin-v37-67ce08afdbe7" and "liplianin-s2-liplianin-v39-4c01a16b6237" did not work. I am not an expert in Linux but I think these Drivers have been made for older Kernels.
worked for me O_o
not saying there is no bug, but no problems so far
How did you install the driver. Was it plug and play?
Here are some INFO using PuTTY during SSH with the Pi. Any ideas. Thanks to everyone.
htpc:~ # cat /etc/release
RPi2.arm-8.2.1
htpc:~ # uname -a
Linux htpc 4.9.59 #1 SMP Thu Nov 16 08:35:17 GMT 2017 armv7l GNU/Linux
htpc:~ # lsusb
Bus 001 Device 004: ID 0b48:3011 TechnoTrend AG TT-connect S2-4600
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
htpc:~ # lsmod
Module Size Used by
hci_uart 15605 1
btbcm 5315 1 hci_uart
bluetooth 292114 3 hci_uart,btbcm
8021q 16771 0
m88ds3103 10903 1
i2c_mux 4067 1 m88ds3103
ds3000 9679 0
brcmfmac 184596 0
brcmutil 4893 1 brcmfmac
cfg80211 247930 1 brcmfmac
dvb_usb_dw2102 46407 1
dvb_usb 15211 1 dvb_usb_dw2102
rfkill 13757 4 bluetooth,cfg80211
dvb_core 76172 3 m88ds3103,dvb_usb,dvb_usb_dw2102
bcm2835_gpiomem 2652 0
rc_core 20369 2 dvb_usb,dvb_usb_dw2102
fixed 2407 0
htpc:~ # dmesg | grep -i dvb
[ 2.125337] usb 1-1.5: Product: dvb-s2
[ 4.583956] dvb-usb: found a 'TechnoTrend TT-connect S2-4600' in warm state.
[ 4.584394] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 4.584509] dvbdev: DVB: registering new adapter (TechnoTrend TT-connect S2-4600)
[ 4.588994] dvb-usb: MAC address: ##:##:##:##:##:##
[ 5.068200] Modules linked in: m88ds3103(O) i2c_mux ds3000(O) brcmfmac brcmutil cfg80211 dvb_usb_dw2102(O+) dvb_usb(O) rfkill dvb_core(O) bcm2835_gpiomem rc_core(O) fixed
[ 5.068316] LR is at su3000_frontend_attach+0x360/0x4d4 [dvb_usb_dw2102]
[ 5.069448] [<7f04e220>] (su3000_frontend_attach [dvb_usb_dw2102]) from [<7f0455c0>] (dvb_usb_adapter_frontend_init+0x104/0x1e0 [dvb_usb])
[ 5.069507] [<7f0454bc>] (dvb_usb_adapter_frontend_init [dvb_usb]) from [<7f044998>] (dvb_usb_device_init+0x4f0/0x684 [dvb_usb])
[ 5.069595] [<7f0444a8>] (dvb_usb_device_init [dvb_usb]) from [<7f04c578>] (dw2102_probe+0x36c/0x44c [dvb_usb_dw2102])
[ 5.069689] [<7f04c20c>] (dw2102_probe [dvb_usb_dw2102]) from [<80504f3c>] (usb_probe_interface+0x10c/0x264)
[ 5.070125] [<80503a28>] (usb_register_driver) from [<7f059024>] (dw2102_driver_init+0x24/0x2c [dvb_usb_dw2102])
[ 5.070214] [<7f059000>] (dw2102_driver_init [dvb_usb_dw2102]) from [<8010179c>] (do_one_initcall+0x4c/0x174)please do a
dmesg|grep -iEw 'bug|conflict|corrupted|error|fail|fault|fatal|Lock|NULL|segfault|stack|trace|warn'
or attach the lines between [ 4.588994] and [ 5.068200]
or the whole dmesg output
Btw pls test a milhouse build if it works there, if there is a kernel bug it won't get fixed anymore as LE9 is already at the "corner".
Btw pls test a milhouse build if it works there, if there is a kernel bug it won't get fixed anymore as LE9 is already at the "corner".
'can't test against above driver related bugs cause the devices were send back to the seller.
But I can test - and actually do - with another x86_64 box with an DVB PCI card !
Btw pls test a milhouse build if it works there, if there is a kernel bug it won't get fixed anymore as LE9 is already at the "corner".
Same result. It "did not work". I have downloaded the latest OpenELEC Img file, installed it, copied the milhouse build to the update folder, rebooted, installed tvheadend, and checked DVB Inputs in Tvheadend. It was not detected before and after installing milhouse build.
So please can you tell me how did you get the s2-4600 to work? what does dmesg tells you?
please do a
dmesg|grep -iEw 'bug|conflict|corrupted|error|fail|fault|fatal|Lock|NULL|segfault|stack|trace|warn'
or attach the lines between [ 4.588994] and [ 5.068200]
or the whole dmesg output
Here is the output:
LibreELEC:~ # dmesg|grep -iEw 'bug|conflict|corrupted|error|fail|fault|fatal|Lock|NULL|segfault|stack|trace|warn'
[ 0.822575] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xaf904000 dma = 0xef904000 len=9024
[ 0.822655] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x80687ed4
[ 0.822665] WARN::hcd_init_fiq:460: FIQ ASM at 0x80688230 length 36
[ 0.822676] WARN::hcd_init_fiq:486: MPHI regs_base at 0xb0879000
[ 2.525313] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 5.244832] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 5.244856] Internal error: Oops: 80000005 [#1] SMP ARM
[ 5.244943] task: adfd0c80 task.stack: ae26e000
[ 5.245065] Process systemd-udevd (pid: 262, stack limit = 0xae26e210)
[ 5.245077] Stack: (0xae26fb20 to 0xae270000)
[ 5.246430] ---[ end trace 08fb7c55c37e2981 ]---Pls do an dmesg | paste at ssh and post the generated link here.
Pls do an dmesg | paste at ssh and post the generated link here.
Here you go: RJf
yea the driver crashs, could you pls disable the hauppauge DVB driver addon (choose LE standard driver) and try again ? (and post dmesg | paste )
yea the driver crashs, could you pls disable the hauppauge DVB driver addon (choose LE standard driver) and try again ? (and post dmesg | paste )
Here it is: RLw
It's a bug. The driver crashes in tt_s2_4600_frontend_attach() when there is no external 12V attached or the fuse is blown on the PCB.
As you did check the PSU I'm afraid it is the latter case.
Sure ?
IIRC, in my tests (technotrend, Terratec on x86_64) the driver crashes *with* external 12V attached too.
maybe here comes a fix for kernel 4.16:
