Re: RTL2831U wont compile against 2.6.38
I already resolved the symbol thing. Your lsusb explains a lot, you have a RTl2832, while I have the RTL2831 which seem to be Revision 4 of the RTL2830. However, there seem to be big similarities between all those chips. It might be not that hard for the contributors of this driver to add support for the early chips as well. Maybe Jan can shade some light on it, since he wrote the initial RTL2831 driver. In any case I may help with testing it. Sascha Wüstemann wrote: Thomas Holzeisen wrote: Unknown symbol means, there is unresolved dependencies at your kernel or false dependencies in the module. My stick works with those google hosted new driver sources and I have no use for lirc, so nothing about it at the following lines, they are stripped, too: ~ # lsusb -v Bus 001 Device 021: ID 1d19:1101 Dexatek Technology Ltd. DK DVB-T Dongle Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1d19 Dexatek Technology Ltd. idProduct 0x1101 DK DVB-T Dongle bcdDevice1.00 iManufacturer 1 Realtek iProduct2 Rtl2832UDVB iSerial 3 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 USB2.0-BulkIso bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 2 Device Status: 0x (Bus Powered) ~ # lsmod | grep dvb dvb_usb_rtl2832u 190302 0 dvb_usb17272 1 dvb_usb_rtl2832u dvb_core 69295 1 dvb_usb rc_core15790 2 dvb_usb ~ # dmesg usb 1-6: new high speed USB device number 20 using ehci_hcd hub 1-6:1.0: USB hub found hub 1-6:1.0: 4 ports detected usb 1-6.3: new high speed USB device number 21 using ehci_hcd dvb-usb: found a 'DK DVBT DONGLE' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DK DVBT DONGLE) DVB: registering adapter 0 frontend 0 (Realtek DVB-T RTL2832)... dvb-usb: DK DVBT DONGLE successfully initialized and connected. dvb-usb: found a 'DK DVBT DONGLE' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DK DVBT DONGLE) DVB: registering adapter 1 frontend 0 (Realtek DVB-T RTL2832)... dvb-usb: DK DVBT DONGLE successfully initialized and connected. Yes, works at no powered four port USB-2.0 mini hub without problems. ~ # uname -a Linux killerghost 2.6.39-gentoo-r1 #1 SMP Fri Jun 10 12:16:38 CEST 2011 x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel GNU/Linux Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U wont compile against 2.6.38
On 06/18/2011 03:44 PM, Thomas Holzeisen wrote: I already resolved the symbol thing. Your lsusb explains a lot, you have a RTl2832, while I have the RTL2831 which seem to be Revision 4 of the RTL2830. However, there seem to be big similarities between all those chips. It might be not that hard for the contributors of this driver to add support for the early chips as well. Maybe Jan can shade some light on it, since he wrote the initial RTL2831 driver. In any case I may help with testing it. I think there is no such revision 4 RTL2830 which is RTL2831. I think you misunderstand. There is DVB-T demods RTL2830 and RTL2832. Then there is USB-bridge let's call it RTL28xxU. When you put USB-bridge and demod together you get chips called RTL2831U (USB-bridge + RTL2830 demod) and RTL2832U (USB-bridge + RTL2832 demod). Also many other Realtek demods exits which uses same USB-bridge. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U wont compile against 2.6.38
Hi Sascha, this solution is not working for me. When compiling and installing the media_build, it works fine. Here in combination with a Digivox Duo Stick: Bus 002 Device 002: ID 1462:8801 Micro Star International # lsmod | grep dvb dvb_usb_af9015 21067 5 dvb_usb22011 1 dvb_usb_af9015 dvb_core 67624 1 dvb_usb rc_core17813 12 dvb_usb_af9015,ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,dvb_usb,ir_rc5_decoder,rc_imon_pad,ir_nec_decoder,imon i2c_core 18989 6 mxl5005s,af9013,nvidia,dvb_usb_af9015,dvb_usb,i2c_nforce2 usbcore99058 11 lirc_imon,dvb_usb_af9015,dvb_usb,usbhid,imon,usb_storage,uas,ohci_hcd,ehci_hcd One very strange behavior is, when theres no dvb-adapter at all, the system loads dvb_ttpci, but no such card is installed, nor gets any /dev/dvb/ created or anything logged in dmsg: # lsmod | grep dvb dvb_ttpci 71007 0 dvb_core 67624 1 dvb_ttpci saa7146_vv 39558 1 dvb_ttpci saa714617148 2 dvb_ttpci,saa7146_vv ttpci_eeprom 12344 1 dvb_ttpci i2c_core 18989 5 dvb_ttpci,videodev,ttpci_eeprom,nvidia,i2c_nforce2 Building and installing new_build as suggested, ends up with # dmesg | grep dvb [ 26.828625] dvb_ttpci: Unknown symbol dvb_net_init (err 0) [ 26.830730] dvb_ttpci: Unknown symbol dvb_net_release (err 0) Here no dvb-adapter was attached, now insert the rtl2831u ... [ 161.752088] usb 1-2: new high speed USB device using ehci_hcd and address 4 [ 161.886020] usb 1-2: New USB device found, idVendor=14aa, idProduct=0160 [ 161.886030] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 161.886036] usb 1-2: Product: DTV Receiver [ 161.886041] usb 1-2: Manufacturer: DTV Receiver [ 161.886046] usb 1-2: SerialNumber: 00067936 ... device got identified, but no module was loaded at all, doing it by hand ... # modprobe -v dvb-usb-rtl2832u WARNING: All config files need .conf: /etc/modprobe.d/usbhid, it will be ignored in a future release. insmod /lib/modules/2.6.38-bpo.2-686/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko WARNING: Error inserting dvb_usb (/lib/modules/2.6.38-bpo.2-686/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko): Invalid argument FATAL: Error inserting dvb_usb_rtl2832u (/lib/modules/2.6.38-bpo.2-686/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl2832u.ko): Invalid argument lets ignore the usbhid warning, its made out of comments anyway, checking dmsg ... [ 296.652984] dvb_usb: disagrees about version of symbol rc_register_device [ 296.652997] dvb_usb: Unknown symbol rc_register_device (err -22) [ 296.654001] dvb_usb: disagrees about version of symbol rc_free_device [ 296.654007] dvb_usb: Unknown symbol rc_free_device (err -22) [ 296.654823] dvb_usb: disagrees about version of symbol rc_allocate_device [ 296.654828] dvb_usb: Unknown symbol rc_allocate_device (err -22) [ 296.656427] dvb_usb: disagrees about version of symbol rc_unregister_device [ 296.656440] dvb_usb: Unknown symbol rc_unregister_device (err -22) From there on, those errors appear attaching any dvb-usb adapter i have, there seem to be a problem. The rtl2831u adapter identifies as following and is labeled Digitus DA-70781-B/A1 and worked fine with Jan Hoogenraads driver under 2.6.32. lsusb -v -s 001:004 Bus 001 Device 004: ID 14aa:0160 WideView Technology Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x14aa WideView Technology Inc. idProduct 0x0160 bcdDevice1.00 iManufacturer 1 DTV Receiver iProduct2 DTV Receiver iSerial 3 00067936 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 USB2.0-BulkIso bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize
Re: RTL2831U wont compile against 2.6.38
Thomas Holzeisen wrote: Unknown symbol means, there is unresolved dependencies at your kernel or false dependencies in the module. My stick works with those google hosted new driver sources and I have no use for lirc, so nothing about it at the following lines, they are stripped, too: ~ # lsusb -v Bus 001 Device 021: ID 1d19:1101 Dexatek Technology Ltd. DK DVB-T Dongle Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1d19 Dexatek Technology Ltd. idProduct 0x1101 DK DVB-T Dongle bcdDevice1.00 iManufacturer 1 Realtek iProduct2 Rtl2832UDVB iSerial 3 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 USB2.0-BulkIso bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 2 Device Status: 0x (Bus Powered) ~ # lsmod | grep dvb dvb_usb_rtl2832u 190302 0 dvb_usb17272 1 dvb_usb_rtl2832u dvb_core 69295 1 dvb_usb rc_core15790 2 dvb_usb ~ # dmesg usb 1-6: new high speed USB device number 20 using ehci_hcd hub 1-6:1.0: USB hub found hub 1-6:1.0: 4 ports detected usb 1-6.3: new high speed USB device number 21 using ehci_hcd dvb-usb: found a 'DK DVBT DONGLE' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DK DVBT DONGLE) DVB: registering adapter 0 frontend 0 (Realtek DVB-T RTL2832)... dvb-usb: DK DVBT DONGLE successfully initialized and connected. dvb-usb: found a 'DK DVBT DONGLE' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DK DVBT DONGLE) DVB: registering adapter 1 frontend 0 (Realtek DVB-T RTL2832)... dvb-usb: DK DVBT DONGLE successfully initialized and connected. Yes, works at no powered four port USB-2.0 mini hub without problems. ~ # uname -a Linux killerghost 2.6.39-gentoo-r1 #1 SMP Fri Jun 10 12:16:38 CEST 2011 x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel GNU/Linux Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RTL2831U wont compile against 2.6.38
Hi there, I tried to get an RTL2831U dvb-t usb-stick running with a more recent kernel (2.6.38) and failed. The hg respository ~jhoogenraad/rtl2831-r2 aborts on countless drivers, the rc coding seem have to changed a lot since it got touched the last time. The hg respository ~anttip/rtl2831u wont compile as well, since its even older. The recent git respositories for media_tree and anttip dont contain drivers for the rtl2831u. Has this device been abandoned, or is anyone working on it? greetings, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U wont compile against 2.6.38
Thomas Holzeisen wrote: Hi there, I tried to get an RTL2831U dvb-t usb-stick running with a more recent kernel (2.6.38) and failed. The hg respository ~jhoogenraad/rtl2831-r2 aborts on countless drivers, the rc coding seem have to changed a lot since it got touched the last time. The hg respository ~anttip/rtl2831u wont compile as well, since its even older. The recent git respositories for media_tree and anttip dont contain drivers for the rtl2831u. Has this device been abandoned, or is anyone working on it? greetings, Thomas There are still people working on it and there is new sources, e.g. look at http://www.spinics.net/lists/linux-media/msg24890.html at the very bottom. Worked like a charm at my system with kernel 2.6.39. I think, there will be announcements later at http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
