Hi;
I have a DVB usb based in RTL2832u Chipset and i would like use it in my Raspberry Pi, anybody can help me?
thanks in advance
Have you tried setting it up with TVHeadend so far?
Yes, my dmesg not recognize it,
[ 2.670238] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
[ 2.781241] usb 1-1.5: New USB device found, idVendor=1b80, idProduct=d398
[ 2.781282] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.781303] usb 1-1.5: Product: usbtv
[ 2.781319] usb 1-1.5: Manufacturer: realtek
[ 2.845470] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[ 3.020228] usb 1-1.3: new high-speed USB device number 6 using dwc_otg
[ 3.095390] fuse init (API version 7.23)
[ 3.121428] usb 1-1.3: New USB device found, idVendor=18a5, idProduct=0400
[ 3.121501] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.121520] usb 1-1.3: Product: USB 3.0 Desktop HD
[ 3.121536] usb 1-1.3: Manufacturer: Verbatim
[ 3.121553] usb 1-1.3: SerialNumber: 306247043850
[ 3.135167] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[
Suspect we need to add firmware for that. I’ll try get it in for the next release.
Sam
thanks for all
I would like to have the option to switch between using the DVBT dongle both as a Tv receiver and as a RTL-SDR device, I think that requires 2 different drivers!?
@sam_nazarko
usb 1-1: New USB device found, idVendor=1b80, idProduct=d398
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: usbtv
usb 1-1: Manufacturer: realtek
Here is driver for Realtek.
Or
Compiling for Raspbmc
BBerski
Looked at this
rtl28xx module is enabled in our kernel, so perhaps a new vendor ID needs to be patched in.
Sam
Perfect @sam_nazarko
Can you patch with these ID
#define USB_PID_KWORLD2_TURBOX_USB2_DVB_T 0xd398
and recompile .
Can I test if it works
BBerski
Which file does this need to be added to? The driver files seem to be:
./drivers/media/usb/em28xx/em28xx-reg.h
./drivers/media/usb/em28xx/em28xx-cards.c
./drivers/media/usb/em28xx/em28xx-v4l.h
./drivers/media/usb/em28xx/em28xx-i2c.c
./drivers/media/usb/em28xx/em28xx-core.c
./drivers/media/usb/em28xx/em28xx-audio.c
./drivers/media/usb/em28xx/Makefile
./drivers/media/usb/em28xx/em28xx-camera.c
./drivers/media/usb/em28xx/em28xx.h
./drivers/media/usb/em28xx/em28xx-vbi.c
./drivers/media/usb/em28xx/em28xx-input.c
./drivers/media/usb/em28xx/Kconfig
./drivers/media/usb/em28xx/em28xx-dvb.c
./drivers/media/usb/em28xx/em28xx-video.c
./drivers/media/usb/dvb-usb-v2/rtl28xxu.h
./drivers/media/usb/dvb-usb-v2/rtl28xxu.c
linux/drivers/media/dvb-core/dvb-usb-ids.h
@388
#define USB_PID_KWORLD2_TURBOX_USB2_DVB_T 0xd398
------------
linux/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
@1652
{ DVB_USB_DEVICE(USB_VID_KWORLD_2, 0xd398,
&rtl2832u_props, “Realtek 2832U USB DVB-T Stick RC”, NULL) },
I will merge this for Alpha 4 and would appreciate it if you could update this thread when it is released and let me know if it worked.
BBerski
Hi
This will be in Alpha 4 which should come soon
Sam
Yes @sam_nazarko
Works perfectly. I have 2 DVB-T (cheap) Realtek.
osmc@osmc:~$ uname -a
Linux osmc 3.18.3-7-osmc #1 PREEMPT Sat Jan 24 17:27:24 UTC 2015 armv6l GNU/Linux
osmc@osmc:~$ lsusb
Bus 001 Device 008: ID 1b80:d398 Afatech DVB-T receiver [RTL2832U]
Bus 001 Device 007: ID 1b80:d398 Afatech DVB-T receiver [RTL2832U]
osmc@osmc:~$ ls -alh /dev/dvb/adapter*
/dev/dvb/adapter0:
totalt 0
drwxr-xr-x 2 root root 120 jan 1 1970 .
drwxr-xr-x 4 root root 80 jan 1 1970 …
crw-rw---- 1 root video 212, 4 jan 1 1970 demux0
crw-rw---- 1 root video 212, 5 jan 1 1970 dvr0
crw-rw---- 1 root video 212, 3 jan 1 1970 frontend0
crw-rw---- 1 root video 212, 7 jan 1 1970 net0
/dev/dvb/adapter1:
totalt 0
drwxr-xr-x 2 root root 120 jan 1 1970 .
drwxr-xr-x 4 root root 80 jan 1 1970 …
crw-rw---- 1 root video 212, 68 jan 1 1970 demux0
crw-rw---- 1 root video 212, 69 jan 1 1970 dvr0
crw-rw---- 1 root video 212, 67 jan 1 1970 frontend0
crw-rw---- 1 root video 212, 71 jan 1 1970 net0
osmc@osmc:~$ sudo journalctl -xn 10000 |grep mpegts
jan 25 10:11:56 osmc tvheadend[1282]: mpegts: 642MHz in DVB-T - tuning on Realtek RTL2832 (DVB-T) : DVB-T #1
jan 25 10:11:56 osmc tvheadend[1282]: mpegts: 490MHz in DVB-T - tuning on Realtek RTL2832 (DVB-T) : DVB-T #0
osmc@osmc:~$ lsmod |grep rtl
dvb_usb_rtl28xxu 20165 14
rtl2830 10674 1 dvb_usb_rtl28xxu
rtl2832 11555 3 dvb_usb_rtl28xxu
i2c_mux 2459 1 rtl2832
dvb_usb_v2 16993 1 dvb_usb_rtl28xxu
dvb_core 106775 3 rtl2830,rtl2832,dvb_usb_v2
rc_core 25875 15 ir_sharp_decoder,ir_xmp_decoder,lirc_dev,ir_lirc_codec,dvb_usb_rtl28xxu,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,ir_mce_kbd_decoder,ir_jvc_decoder,dvb_usb_v2,ir_rc6_decoder,ir_sanyo_decoder
BBerski
Great,
I can use my DBV usb stick now.
Thanks ,
The Alpha 4 release is imminent and will have this included.
Hi
I have a QNAP DVB USB receiver based on Realtek RTL2832u chipset.
This is my dmesg at connect:
[175901.335815] usb 1-1.3.4: new high-speed USB device number 7 using dwc_otg
[175901.454890] usb 1-1.3.4: New USB device found, idVendor=1b80, idProduct=d3a4
[175901.454935] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[175901.454953] usb 1-1.3.4: Product: Rtl2832UDVB
[175901.454969] usb 1-1.3.4: Manufacturer: Realtek
No new DVB events in dmesg for this receiver.
I have another receiver connected (AVerMedia HD Volar (A867)) that works and store dmesg DVB events:
[ 8.954584] usb 1-1.3.1: dvb_usb_af9035: prechip_version=00 chip_version=03 chip_type=3802
[ 8.955057] usb 1-1.3.1: dvb_usb_v2: found a ‘AVerMedia HD Volar (A867)’ in cold state
[ 8.977301] usb 1-1.3.1: dvb_usb_v2: downloading firmware from file ‘dvb-usb-af9035-02.fw’
[ 9.293022] usb 1-1.3.1: dvb_usb_af9035: firmware version=12.13.15.0
[ 9.293101] usb 1-1.3.1: dvb_usb_v2: found a ‘AVerMedia HD Volar (A867)’ in warm state
[ 9.313051] usb 1-1.3.1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 9.831326] usb 1-1.3.1: dvb_usb_v2: schedule remote query interval to 500 msecs
[ 9.831355] usb 1-1.3.1: dvb_usb_v2: ‘AVerMedia HD Volar (A867)’ successfully initialized and connected
[ 9.835519] usbcore: registered new interface driver dvb_usb_af9035
May be the idVendor=1b80, idProduct=d3a4 of my QNAP-Realtek not yet patched in alpha4 release ?
Can you help me ?
Thank for all
Paolo
Hi everybody, same problem here.
I’ve bought a Hamlet XDVBT900BK, which has the same chipset, idVendor and idProduct as @sampeiilpescatore’s receiver. I’ve noticed that idProduct=d3a4 has already been added in module sources from LinuxTV.org, so I tried to build the module by myself, but I get this error during building process on RPI 1:
In file included from ./arch/arm/include/asm/page.h:163:0,
from ./arch/arm/include/asm/thread_info.h:17,
from include/linux/thread_info.h:54,
from include/asm-generic/preempt.h:4,
from arch/arm/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:18,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:35,
from include/linux/time.h:5,
from include/linux/input.h:11,
from /home/osmc/LinuxDriver/Linux/Linux/v4l/compat.h:9,
from :0:
./arch/arm/include/asm/memory.h:24:25: fatal error: mach/memory.h: No such file or directory
#include <mach/memory.h>
and a similar error, related to missing file mach/barriers.h, if I try to build on RPI 2.
Any suggestion/fix for this problem ? Alternatively, can anybody indicate a dvb-t usb tuner proven to work out-of-the-box with OSMC ?
Thank you very much
Giuseppe
Hello is this working as yet?
I have a RPI2 with the latest image and RTL2832u based dongle talking to OSMC via TVHeadend. TV Headend sees the dongle but it does not function…
Many thanks.