Talk:Realtek RTL2831U
Possible new ID 1f4d:b803
Greetings, I just recently acquired an USB tuner from the company "NPG" model "Real DVB-T F PLUS" (but the most common vendor/model with this ID is Lifeview LV5TDLX), looking for a suitable driver using the USB ID, I found multiple references pointing to use this driver. Trying the tarballs available from those sources, none of then could compile as I am using a "recent" kernel version (2.6.35). None of the Mercurial branches pointed in the wiki page detects the USB device as the ID is not listed in any of then. Here I paste the information dumped from the device just in case it can be added to the supported device list:
# lsusb Bus 001 Device 002: ID 1f4d:b803
# lsusb -v -d 1f4d:b803
Bus 001 Device 002: ID 1f4d:b803
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1f4d
idProduct 0xb803
bcdDevice 1.00
iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDIR
iSerial 3 00000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4 USB2.0-Bulk&Iso
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 Bulk-In, Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 Bulk-In, Interface
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 2
Device Status: 0x0000
(Bus Powered)
I have not melded with the IDs myself just in case I brick the stick, but if you thinks it is safe, I can replace the ids of one of the supported sticks and tell you about the results. Sources:
http://www.turnovfree.net/~stybla/linux/v4l-dvb/lv5tdlx/readme.lv5tdlx.txt
http://aur.archlinux.org/packages.php?ID=36746&comments=all
http://www.spinics.net/lists/linux-media/msg23229.html
http://www.abclinuxu.cz/poradna/hardware/show/302823
https://usb-ids.gowdy.us/read/UD/1f4d
Hello, I have a possible new stick as well
PEAK Peak 102569AGPK with USB ID 1b80:d395. It shows up as Afatech but has the Realtech chip... :
Bus 001 Device 004: ID 1b80:d395 Afatech
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1b80 Afatech
idProduct 0xd395
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
The circuit board is stamped HU394-T and has a Realtek RTL2832U chip on it.
Appears to be working for somone under the same source as above: