Beiträge von majordidge

OK, I'm happy with that.

MD.

Hi Helmut,

I tried Wirbels suggestion and the firmware was loaded once as expected, but no picture.

I have noticed that when things work the firmware appears to be loaded twice in quick succession on first frontend access, and then once only each time I switch back to the satellite frontend. The following dmesg is from starting VDR and selecting the satellite channel and then shutting down immediately. The driver seems to reload the firmware within a second of the first load. I dont know if this throws any more light on whats going on.

root@Nutrigrain:/home/digitalTV# dmesg | grep "cx24116"

[29257.040177] cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...

[29257.068106] cx24116_firmware_ondemand: Waiting for firmware upload(2)...

[29262.364806] cx24116_load_firmware: FW version 1.26.90.0

[29262.364833] cx24116_firmware_ondemand: Firmware upload complete

[29263.564171] cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...

[29263.564348] cx24116_firmware_ondemand: Waiting for firmware upload(2)...

[29268.826493] cx24116_load_firmware: FW version 1.26.90.0

[29268.826521] cx24116_firmware_ondemand: Firmware upload complete

root@Nutrigrain:/home/digitalTV#

I must say that I appreciate your perseverance in getting to the bottom of this but it is not a problem for me as my system now does what I want it to do. Waiting for 5 seconds when switching to a satellite channel is not a concern for me and i'm happy with the way things are. That said, i'm happy to work with you to get to the bottom of this if you so desire.

Thanks,

MD.

Hi Helmut,

I am using stock 5.11.6. This is the Kernel version that has worked consistently with the card now that the channels.conf entry has been corrected. I'll stich with this for now as I know it works, unless you suggest otherwise.

MD.

Hmm, removing the patch still leaves me with KCSAN reports in dmesg so that may be a red herring.

Notwithstanding that the patch still does not work, i.e. no firmware is loaded.

MD.

Hi Helmut,

Apologies for the delay in responding re the firmware patch. Unfortunately it does not work and the firmware never gets loaded. It also has an unfortunate side effect of causing some sort of race condition in the kernel:

[ 9.748915] cx88_dvb: cx2388x dvb driver version 1.0.0 loaded

[ 9.758082] cx8802: registering cx8802 driver, type: dvb access: shared

[ 9.811086] cx8800: registered device video0 [v4l2]

[ 9.830324] ==================================================================

[ 9.834653] BUG: KCSAN: data-race in mutex_spin_on_owner+0x56/0x110

[ 9.843218] race at unknown origin, with read to 0xffff95be81830d74 of 4 bytes by task 523 on cpu 0:

[ 9.847558] mutex_spin_on_owner+0x56/0x110

[ 9.851869] __mutex_lock.constprop.0+0x105/0x800

[ 9.856141] __mutex_lock_slowpath+0xf/0x10

[ 9.858619] cx8802: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68]

[ 9.860388] mutex_lock+0x93/0xa0

[ 9.874595] kernfs_dop_revalidate+0x4e/0x170

[ 9.878950] lookup_fast+0x18e/0x250

[ 9.883243] walk_component+0x52/0x290

[ 9.887488] path_lookupat+0xcd/0x350

[ 9.891747] filename_lookup+0x121/0x2b0

[ 9.895947] user_path_at_empty+0x6d/0x90

[ 9.900131] do_readlinkat+0x6c/0x190

[ 9.904210] __x64_sys_readlink+0x42/0x50

[ 9.908270] do_syscall_64+0x3a/0x90

[ 9.912328] entry_SYSCALL_64_after_hwframe+0x44/0xa9

[ 9.920452] Reported by Kernel Concurrency Sanitizer on:

[ 9.924475] CPU: 0 PID: 523 Comm: udevd Not tainted 5.11.6-Build #1

[ 9.928562] Hardware name: System manufacturer System Product Name/P5KPL-CM, BIOS 0512 05/19/2008

[ 9.932490] ==================================================================

Your thoughts?

Thanks,

MD.

Hi guys,

Thanks again for your prompt replies.

One word - Success !!!

I tried the new firmware but no joy with dvbv5-scan so I was not confident that vdr would work with the modified transponder parameters. But it did. I then switched back to my previous firmware to pinpoint what fixed things and the old firmware also worked. So it was as simple as an incorrect channels.conf entry. Interestingly my technotrend card with two SAA716x FF (STV090x Multistandard) frontends is happy to lock on to the transponder with the old transponder parameters so I just assumed that they were OK.

Helmut, your patch works very well. I am able to repetitively switch between the S and T frontends on the card without issue. The switch back from the Terrestrial frontend does take a little longer as the cx24116 firmware is reloaded each time. Is this to be expected or should the firmware be loaded once only? Its not an issue or concern, just something i noticed looking through dmesg.

Thank you both for your assistance in getting to the bottom of this.

Regards,

MD.

Hi Helmut and Wirbel, thanks for your prompt replies.

wirbel: Thanks for your suggestions.

I'm using version 1.26.90.0 downloaded from hauppauge as suggested in your link. The md5sum for the unzipped hcw88bda.sys is 3f685a2ca6d1dae35b10c06f3a538d82 which checks out, and the md5sum for the extracted /lib/firmware/dvb-fe-cx24116-1.26.90.0.fw is 6755898e8f8s479bfba07fc85d647079 which you might like to confirm.

I am using dvbv5-scan to test the card outside of VDR, see below.

@Helmut: Channels.conf extract follows:

:@100 Terestrial TV

7 Melbourne;Seven Network:177500:B7C34D0G16M64S0T8Y0:T:27500:769=2:770=eng@3:772:2:1328:4115:1283:0

:@300 Satellite TV

Al Jazeera;Foxtel:12136:VM2O0P0S1:S156.0E:27800:1121=2:1122=eng@4:1126:3:32012:4096:32:0

Output from dvbv5-scan using the DVB-S2 frontend on the troublesome card:

dvbv5-scan -a 1 -f 0 -l L10700 /discs/sdc/sdc3/configs/dvb/dtv-scan-tables/dvb-s/Optus-D310-156.0E

Using LNBf L10700

L10700

Freqs : 11750 to 12750 MHz, LO: 10700 MHz

WARNING Ignoring device /dev/dvb/adapter2/osd0

ERROR command BANDWIDTH_HZ (5) not found during retrieve

Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable (yet).

Scanning frequency #1 11762000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #2 11804000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #3 11804000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #4 11845000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #5 11845000 (0x00) Signal= 91.90% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #6 11886000 (0x00) Signal= 91.11% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #7 11886000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #8 11928000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #9 11928000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

.

.

.

Scanning frequency #32 12598000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #33 12638000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #34 12647000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #35 12707000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #36 12718000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

Scanning frequency #37 12727000 (0x00) Signal= 91.51% C/N= 0.00% UCB= 0 postBER= 0

root@Nutrigrain:/home#

The same scan works (locks transponders) when i use it on one of the technotrend fe's attached to the same LNB.

Thoughts?

MD.

Hi Helmut,

An update: So the card is NOT broken after all. I ran Windows / Prog-DVB on the same machine and it was able to see and successfully use both frontends.

So on to the firmware and drivers. The firmware seems to be loading and reporting itself correctly:

cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...

cx24116_firmware_ondemand: Waiting for firmware upload(2)...

cx24116_load_firmware: FW version 1.26.90.0

cx24116_firmware_ondemand: Firmware upload complete

As for the drivers I am using kernel 5.11.0 so I downloaded, built and installed the latest drivers from the v4l-dvb backport tree. I noted the the size of the new cx24116 driver was different to my old driver so I was hopeful that things might now work but alas the behavior was the same. I am now contemplating updating my kernel to the latest and greatest but before I do I thought id ask if you (or anyone else) has any other suggestions as to what I might try or look at.

Meanwhile I can report that your patch appears to be working in that I can successfully switch back and forth between both front ends on VDR and the femon plugin is correctly reporting the connected frontend in each case, but just without a lock on the Conexant cx24116/cx24118 DVB-S2 frontend.

Any suggestions much appreciated.

Thanks,

MD.

Hi Helmut,

After a lot of experimentation with and without your patch it appears that the DVB-S2 side of the card is broken . It has definitely worked in the past but I cant get it to work now, even on a legacy set up from some 10 years ago when I last used the card.

However, I have managed to source an identical second hand replacement card at a good price and I am waiting for it to arrive. This may take a few weeks but I am still very keen to use this card so will be in touch again when it arrives, hopefully with some better news.

Thanks,

MD.

Hi Helmut,

With your patch applied the DVB-T frontend (frontend1) is now visible to VDR and works, while the DVB-S2 front end (frontend0) is also visible but does not work. According to femon a strong signal is present but there is no signal quality. If I attach the LNB to one of the STV090x frontends i get a picture so it should/can work

.

My adapter arrangement is as follows:

  dmesg | grep "registering adapter"

  budget dvb 0000:03:01.0: DVB: registering adapter 0 frontend 0 (LSI L64781 DVB-T)...
  cx88-mpeg driver manager 0000:03:00.2: DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)...
  cx88-mpeg driver manager 0000:03:00.2: DVB: registering adapter 1 frontend 1 (Conexant CX22702 DVB-T)...
  SAA716x FF 0000:02:00.0: DVB: registering adapter 2 frontend 0 (STV090x Multistandard)...
  SAA716x FF 0000:02:00.0: DVB: registering adapter 3 frontend 0 (STV090x Multistandard)...

The DVB-T and DVB-S channels in channels.conf used for the test both used CA 2.

Any ideas?

Thanks,

MD.

Thanks Helmut, I'll try the patch tomorrow and let you know how I get on.

MD.

On further investigation i discovered the following code in dvbdevice.c

// Check for multiple frontends:
if (frontend == 0) {
   for (int i = 1; ; i++) {
      if (access(DvbName(DEV_DVB_FRONTEND, adapter, i), F_OK) == 0) {
         if (access(DvbName(DEV_DVB_DEMUX, adapter, i), F_OK) != 0) {
            fe = new cDvbFrontend(adapter, i);
            dvbFrontends.Append(fe);
            numDeliverySystems += fe->NumDeliverySystems();
            //numModulations += fe->NumModulations(); // looks like in multi frontend devices all frontends report the same modulations
            FrontendNumbers = cString::sprintf("%s+%d", *FrontendNumbers, i);
            }
         }
      else
         break;
      }
   }

This appears to look for a second frontend on an adapter but then ignore it if a corresponding demux is also present, which is the case with the Hauppauge Win TV-HVR-4000 card. The /dev/dvb/adapter(n) folder for the card actually contains: frontend0, demux0, net0, dvr0, frontend1, demux1, net1 and dvr1.

That is about as far as I can go with this as my dvb knowledge is limited but can anyone suggest why the presence of a second demux on an adapter should preclude the use of a second frontend in VDR?

Thanks,

MD.

Hello, I have a Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid card which supports both DVB/S2 and DVB/T streams. The hardware driver provides access to frontend0 and frontend1 through one adapter. These can be accessed independently using the v4l apps however VDR only detects frontend0. I note that some work was done back in 2018 to build support for multiple frontend cards but this does not appear to support this card. Can this be addressed?

Pertinent dmesg output:

cx88xx: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected], frontend(s): 2

cx88xx: i2c init: enabling analog demod on HVR1300/3000/4000 tuner

tda9887 10-0043: creating new instance

tda9887 10-0043: tda988[5/6/7] found

tuner: 10-0043: Tuner 74 found with type(s) Radio TV.

tuner: 10-0061: Tuner -1 found with type(s) Radio TV.

tveeprom: Hauppauge model 69009, rev B2D3, serial# 4029845100

tveeprom: MAC address is 00:0d:fe:32:8e:6c

tveeprom: tuner model is Philips FMD1216MEX (idx 133, type 78)

tveeprom: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4)

tveeprom: audio processor is CX882 (idx 33)

tveeprom: decoder processor is CX882 (idx 25)

tveeprom: has radio, has IR receiver, has no IR transmitter

cx88xx: hauppauge eeprom: model=69009

tuner-simple 10-0061: creating new instance

tuner-simple 10-0061: type set to 78 (Philips FMD1216MEX MK3 Hybrid Tuner)

Registered IR keymap rc-hauppauge

IR RC5(x/sz) protocol handler initialized

rc rc0: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:03:00.2/rc/rc0

rc rc0: lirc_dev: driver cx88xx registered at minor = 0, raw IR receiver, no transmitter

input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:03:00.2/rc/rc0/input12

cx8802: cx2388x 8802 Driver Manager

cx8802: found at 0000:03:00.2, rev: 5, irq: 19, latency: 64, mmio: 0xfc000000

cx8800: found at 0000:03:00.0, rev: 5, irq: 19, latency: 64, mmio: 0xfa000000

cx88_alsa: cx88[0]: alsa: CX88x/0: ALSA support for cx2388x boards

wm8775 10-001b: chip found @ 0x36 (cx88[0])

cx88_dvb: cx2388x dvb driver version 1.0.0 loaded

cx8802: registering cx8802 driver, type: dvb access: shared

cx8802: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68]

cx8800: registered device video0 [v4l2]

cx8800: registered device vbi0

cx8800: registered device radio0

cx88_dvb: cx2388x based DVB/ATSC card

cx88_dvb: cx8802_alloc_frontends: allocating 2 frontend(s)

tuner-simple 10-0061: attaching existing instance

tuner-simple 10-0061: couldn't set type to 63. Using 78 (Philips FMD1216MEX MK3 Hybrid Tuner) instead

dvbdev: DVB: registering new adapter (cx88[0])

cx88-mpeg driver manager 0000:03:00.2: DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)...

cx88-mpeg driver manager 0000:03:00.2: DVB: registering adapter 1 frontend 1 (Conexant CX22702 DVB-T)...

cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...

cx24116_firmware_ondemand: Waiting for firmware upload(2)...

cx24116_load_firmware: FW version 1.26.90.0

cx24116_firmware_ondemand: Firmware upload complete

Thanks,

MD.

Hi Methodus,

Further to my last post - I also have a mediagate MG 800 HD. It can also see the VDR upnp server and can play back all recordings OK but also has problems with live TV.
I'd like to get that going too but my preference is to sort the Blu Ray player out first.

MD.

Zitat von methodus

Could you please send me your metadata.db. I wanted to fix the size issue, but... humm.. there isn't one. Every call to getSize has long int, I don't know, why it returns a negative number. There are two possibilities: 1.: the provider stores the wrongly calculated size (then, it must be wrong in the database) or 2.: the creation of the result set returns the wrong size (then, there must not be any negative number in the DB). Could you please verify that?

Zitat von methodus

Could you please send me your metadata.db. I wanted to fix the size issue, but... humm.. there isn't one. Every call to getSize has long int, I don't know, why it returns a negative number. There are two possibilities: 1.: the provider stores the wrongly calculated size (then, it must be wrong in the database) or 2.: the creation of the result set returns the wrong size (then, there must not be any negative number in the DB). Could you please verify that?

metadata.db as requested.

Not sure how to answer your question 2, but perhaps you can.

(Sorry its a bit "overquoted" , still getting the hang of things)

MD

Hi Methodus,
I have been able to run the test this evening and have attached two wireshark captures.
The first is an attempt to select my live TV group "Favourites" in 'VDR Live-TV' which returns 'There is no playable file'.
The second is an attempt to select 'VDR Recordings' which also returns 'There is no playable file'.
The VDR target is 192.168.0.18 and the Blu Ray player is at 192.168.0.20.
MD

Hi Methodus,
FYI I have just tried the streamdev header patch to no avail - I still get 'No playable file found" when selecting a channel group.
I will run with wireshark trace tomorrow and provide traces for both 'live TV' and 'VDR recordings'.
MD.

Hi, I have been following with interest the thread with Rofafor regarding Sony Blu Ray players. I also have a Sony blue ray player and using the latest git release (HEAD is now at a2ed1e7... Added installation of the channelTitle.conf to Makefile) still cannot get it to play back recordings or live TV. I can navigate the live TV structure from my channels.conf but if I select a channel group i am told "No playable file found". I get the same message when selecting VDR Recordings. Any ideas?
Thanks,
MD.