Help with Realtek RTL2838UHIDIR DVB stick

I have a Realtek RTL2838UHIDIR DVB stick, which I have not been able to get working. I have downloaded and successfully compiled a few different drivers from the web but to no avail.

dmesg |grep -i realtek
27.083940] usb 2-1.1: Manufacturer: Realtek

dmesg |grep -i rtl
27.083939] usb 2-1.1: Product: RTL2838UHIDIR
27.321432] dvb_usb_rtl2832u: no symbol version for module_layout
27.321435] dvb_usb_rtl2832u: no symbol version for module_layout

dmesg |grep -i dvb
11.545396] e97a5d893fdf45c20799b72a1c11dca3b282c89c [media] fs/compat_ioctl: it needs to see the DVBv3 compat stuff
11.545397] 53c91373bdd74f7e11d2726046a90b986c1ed650 dvb: remove the extra parameter on get_frontend
11.546302] e97a5d893fdf45c20799b72a1c11dca3b282c89c fs/compat_ioctl: it needs to see the DVBv3 compat stuff
11.546303] 53c91373bdd74f7e11d2726046a90b986c1ed650 dvb: remove the extra parameter on get_frontend
22.311984] tveeprom 17-0000: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L’) PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
22.576627] DVB: registering new adapter (saa7164)
22.576631] DVB: registering adapter 0 frontend 0 (NXP TDA10048HN DVB-T)…
24.997706] DVB: registering new adapter (saa7164)
24.997709] DVB: registering adapter 1 frontend 0 (NXP TDA10048HN DVB-T)…
27.155968] e97a5d893fdf45c20799b72a1c11dca3b282c89c fs/compat_ioctl: it needs to see the DVBv3 compat stuff
27.155969] 53c91373bdd74f7e11d2726046a90b986c1ed650 dvb: remove the extra parameter on get_frontend
27.321432] dvb_usb_rtl2832u: no symbol version for module_layout
27.321435] dvb_usb_rtl2832u: no symbol version for module_layout
35.836989] tveeprom 20-0000: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L’) PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
36.101783] DVB: registering new adapter (saa7164)
36.101787] DVB: registering adapter 2 frontend 0 (NXP TDA10048HN DVB-T)…
38.555834] DVB: registering new adapter (saa7164)
38.555837] DVB: registering adapter 3 frontend 0 (NXP TDA10048HN DVB-T)…
172.284681] tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)…
177.424224] tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)…
187.132179] tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)…
199.794739] dvb_usb_rtl2832u: no symbol version for module_layout
199.797176] dvb_usb_rtl2832u: no symbol version for module_layout

As you can see, I have other dvb devices working, but not the RTLs

All ideas would be appreciated

Cheers

Dave

On 01/08/2012 06:26 AM, dmbgo wrote:
> waiting for firmware upload (dvb-fe-tda10048-1.0.fw)

have you installed that firmware?


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

Yes It is installed and working fine. The tda10048 firmware is for the Hauppauge cards. I don’t think the Realtek USB card needs a firmware?
I should redo the dmesg post to keep things clear. Here you are:

dmesg |grep -i dvb
11.545396] e97a5d893fdf45c20799b72a1c11dca3b282c89c [media] fs/compat_ioctl: it needs to see the DVBv3 compat stuff
11.545397] 53c91373bdd74f7e11d2726046a90b986c1ed650 dvb: remove the extra parameter on get_frontend
11.546302] e97a5d893fdf45c20799b72a1c11dca3b282c89c fs/compat_ioctl: it needs to see the DVBv3 compat stuff
11.546303] 53c91373bdd74f7e11d2726046a90b986c1ed650 dvb: remove the extra parameter on get_frontend
199.794739] dvb_usb_rtl2832u: no symbol version for module_layout
199.797176] dvb_usb_rtl2832u: no symbol version for module_layout

I’m not sure if the errors at the start of the dmesg |grep dvb output are related to the rtl USBs or to the other cards.

Keep the suggestions coming!

BTW what does this message in dmesg mean? “dvb_usb_rtl2832u: no symbol version for module_layout”

Cheers

Dave

Hmm Am I posting my question in the wrong forum, or did I do something to upset people?

Non I don’t think so, most are probably like me - they don’t know the answer to your problem with the driver for this usb dvb stick.

As to the “no symbol version for module_layout” problem, this generally indicates a mismatch between the driver and your machine.
Some headers etc are wrong. Try something like

“zypper in kernel-default-devel” to make sure you have the correct header etc, and recompile.

HTH

Lenwolf