temporary

Hi,

You have right. It have to be problem in code with slot assigment because i see that 8 adapters was detected but only one slot assigned .

parts from debug:

...
found 8 adapter, 8 frontends(8 sim) and 8 demux, boxtype 6
...
LNB
sec config cleared
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr VTUNER, need rotorworkaround No, enabled Yes, DVB-S2 Yes

Regards,
temporary

Hi,

@Betacentauri: Thanks for adding of my humble contribution into the source tree.

@dev,

About the multiple tuner configuration problem mentioned by temporary here is perhaps an explanation.

On a standard E2 system (DMM & compatible), the multiple tuner are handled this way:

/dev/dvb/adapter0/frontend0 (tuner A)
/dev/dvb/adapter0/frontend1 (tuner
/dev/dvb/adapter0/frontend2 (tuner C)
/dev/dvb/adapter0/frontend3 (tuner D)

as you see every tuner is attached behind adapter0.

On a PC system this is not the case, each physical tuner have its own /dev/dvb/adapterX/frontend0 (or 1).

So in the temporary log, we saw that it is trying to access the frontend1 (if the log is right) but on its system there is no interface with frontend1, so I guess that it should normally access the /dev/dvb/adaptor1/frontend0.
So can be interesting to check in the source code for this log message and see if frontend1 means in fact /dev/adapter1/frontend0 or if it really tries to access /dev/adapter0/frontend1 which is wrong since it doesn't exist on its system.

So perhaps that there is still somewhere in the source code a place where multiple tuners are not properly converted from standard E2 way of handling multiple tuner into the "nim_sockets" way.

Pr2

P.S.: I refer to this error message:

3.
scan: allocating raw channel (on frontend 1) failed!

Hi all,

I already post problem with multiple tuners. When I try use other tuner than first tunning of channel fails. I used also tool "create_nim_sockets" for create sockets file, but with same results.

Bellow you can find generated nim_sockets file(1), list of my /dev/dvb(2), error in console when tunning fail(3) and some screens from gui. I tested both branches again without sucess. Is it anybody who have idea what could be cause of this behaviour?

Thank you.


1.
[root@e2 bin]# cat ../etc/tuxbox/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: TurboSight TBS 6984 DVBS/S2 frontend
Has_Outputs: no
Frontend_Device: 0

NIM Socket 1:
Type: DVB-S2
Name: TurboSight TBS 6984 DVBS/S2 frontend
Has_Outputs: no
Frontend_Device: 0

NIM Socket 2:
Type: DVB-S2
Name: TurboSight TBS 6984 DVBS/S2 frontend
Has_Outputs: no
Frontend_Device: 0

NIM Socket 3:
Type: DVB-S2
Name: TurboSight TBS 6984 DVBS/S2 frontend
Has_Outputs: no
Frontend_Device: 0

2.
[root@e2 bin]# find /dev/dvb/
/dev/dvb/
/dev/dvb/adapter3
/dev/dvb/adapter3/ca0
/dev/dvb/adapter3/frontend0
/dev/dvb/adapter3/net0
/dev/dvb/adapter3/dvr0
/dev/dvb/adapter3/demux0
/dev/dvb/adapter2
/dev/dvb/adapter2/ca0
/dev/dvb/adapter2/frontend0
/dev/dvb/adapter2/net0
/dev/dvb/adapter2/dvr0
/dev/dvb/adapter2/demux0
/dev/dvb/adapter1
/dev/dvb/adapter1/ca0
/dev/dvb/adapter1/frontend0
/dev/dvb/adapter1/net0
/dev/dvb/adapter1/dvr0
/dev/dvb/adapter1/demux0
/dev/dvb/adapter0
/dev/dvb/adapter0/ca0
/dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/net0
/dev/dvb/adapter0/dvr0
/dev/dvb/adapter0/demux0
3.
scan: allocating raw channel (on frontend 1) failed!

4.

Same situation with "Frontend_Device: 0" or numbered by tuner. I have not any other ideas to get work.

Me too. Hope that someone else can help.

Does the card work with other software(kaffeine, vdr,...)?

Sorry for delay, but I waited for new posts assigment
Yes, all tuners works okay in vlc or in tools szap, scan-s2.

Do you have any ideas why is not working? At the moment I'm waiting for quad DVB-T/T2 card TBS6284. I will check if this card will be same behaviour.

Same situation with "Frontend_Device: 0" or numbered by tuner. I have not any other ideas to get work.

NIM Socket 0:
Type: DVB-S2
Name: Tuner A
Has_Outputs: no
Frontend_Device: 0

NIM Socket 1:
Type: DVB-S2
Name: Tuner B
Has_Outputs: no
Frontend_Device: 0

NIM Socket 2:
Type: DVB-S2
Name: Tuner C
Has_Outputs: no
Frontend_Device: 0

NIM Socket 3:
Type: DVB-S2
Name: Tuner D
Has_Outputs: no
Frontend_Device: 0

Same errors like before.

"Error failed to scan" and in console "scan: allocating raw channel (on frontend 1) failed!"

I think that there is the problem. Why all four tuners using same name and config?

setSlotInfo for dvb frontend 0 to slotid 0, descr Tuner A, need rotorworkaround No, enabled No, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr Tuner A, need rotorworkaround No, enabled No, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr Tuner A, need rotorworkaround No, enabled No, DVB-S2 Yes
setSlotInfo for dvb frontend 0 to slotid 0, descr Tuner A, need rotorworkaround No, enabled No, DVB-S2 Yes