SONY CXD2837ER recognized as Panasonic MN88473 in TVH

ly chen

My TVheadend is running on rPi2, with a white case DVB-C stick (rtl2832p, Panasonic MN88473, R828D chipset). Recently, I bought a new DVB-C stick, it has the same white case as the old one, but the demod chip is SONY CXD2837ER, I built the driver following this tutorial: http://blog.vmsplice.net/2018/01/how-to-modify-kernel-modules-without.html, and using this patch: https://github.com/torvalds/linux/pull/567. After installing the ko module, the CXD2837ER is succesfully recognized in dmesg, but in TVheadend webui, it is recognized as Panasonic MN88473, the wierd thing is, this stick is working normally!
For now, I don't know wheather the driver patch or TVH has a bug.

Here are the dmesg output.

[ 6997.240771] usb 1-1.2: new high-speed USB device number 6 using dwc_otg
[ 6997.381083] usb 1-1.2: New USB device found, idVendor=15f4, idProduct=0131
[ 6997.381103] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6997.381113] usb 1-1.2: Product: dvbt2
[ 6997.381124] usb 1-1.2: Manufacturer: astrometadvbt2
[ 6997.389180] usb 1-1.2: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
[ 6997.464133] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 6997.464213] dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
[ 6997.473604] i2c i2c-3: Added multiplexed i2c bus 4
[ 6997.473625] rtl2832 3-0010: Realtek RTL2832 successfully attached
[ 6997.473749] i2c i2c-3: cxd2841er_attach(): I2C adapter b9637070 SLVX addr 6e SLVT addr 6c
[ 6997.478088] i2c i2c-3: cxd2841er_attach(): attaching CXD2837ER DVB-C/T/T2 frontend
[ 6997.478104] i2c i2c-3: cxd2841er_attach(): chip ID 0xb1 OK.
[ 6997.478126] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
[ 6997.478466] usb 1-1.2: DVB: registering adapter 0 frontend 1 (Sony CXD2837ER DVB-T/T2/C demodulator)...
[ 6997.478735] r820t 4-003a: creating new instance
[ 6997.486627] r820t 4-003a: Rafael Micro r820t successfully identified
[ 6997.486671] r820t 4-003a: attaching existing instance
[ 6997.504730] r820t 4-003a: Rafael Micro r820t successfully identified
[ 6997.522717] Registered IR keymap rc-empty
[ 6997.522910] rc rc0: Astrometa DVB-T2 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0
[ 6997.523176] input: Astrometa DVB-T2 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0/input4
[ 6997.524037] input: MCE IR Keyboard/Mouse (dvb_usb_rtl28xxu) as /devices/virtual/input/input5
[ 6997.524712] rc rc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
[ 6997.524736] usb 1-1.2: dvb_usb_v2: schedule remote query interval to 200 msecs

[ 6997.541967] usb 1-1.2: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected

mpmc

TVH only displays what it's told by the kernel/driver. You might have a new version of the stick that uses the exact same product info as an older version, the driver is likely detecting this and passing it to another module.

ly chen

Mark Clarkstone wrote:

> TVH only displays what it's told by the kernel/driver. You might have a new version of the stick that uses the exact same product info as an older version, the driver is likely detecting this and passing it to another module.

Yeah, they use the same VID and PID.

Ronald Kager

Hi,

i expect you're facing exactly this problem with "2018 revision"

https://linuxtv.org/wiki/index.php/Astrometa_DVB-T2

here is the thread for updating the driver in kernel,
also with discussion and fixing some additional problems (reinit after host reboot wenn stick is in warm state)

https://github.com/torvalds/linux/pull/567

br Ron

ly chen

Thanks Kager,
I applied the patch you mentioned, in my case, after system installition, if the MN88473 is the first stick plugged, and then plug the CXD2837ER, the CXD2837ER is recognised as MN884783. Otherwise, if plug the CXD2837ER first, and then plug the MN88473, the MN88473 is recognised as CXD2837ER. Maybe the reason is they share the same VID and PID, TVH thinks that they are the same device. But the correct driver is loaded, so they can work normally even they are misrecognised.

Ronald Kager

Question: if you use only one of both (especially the CXD2837ER) everything works fine?

ly chen

Everything works fine, and they can work together flawlessly.