[VU+ Duo2] Missing Dvb-T2 driver for the Vu+ Duo2 dub-t2 model

[tappari]

I promised to send only one, and that is on it`s way to Andy.

 

[tappari]

Coming back to this original issue. I`m not a Linux person (had to be some other Finn to start it), but here is some diifferencies between Ultimo and Duo2:
Welcome to OpenViX for vuultimo
openvix Zeus vuultimo


vuultimo login: root
Last login: Mon Apr 7 09:39:00 +0300 2014 on /dev/pts/0.
root@vuultimo:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 1
I2C_Device: 3
NIM Socket 2:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 2
I2C_Device: 1
Duo2:
Welcome to OpenViX for vuduo2
openvix Zeus vuduo2


vuduo2 login: root
Last login: Mon Apr 7 07:47:09 +0300 2014 on /dev/pts/0.
root@vuduo2:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 1
I2C_Device: 3
So, as you can see, there is a difference.

 

[andyblac]

Coming back to this original issue. I`m not a Linux person (had to be some other Finn to start it), but here is some diifferencies between Ultimo and Duo2:
Welcome to OpenViX for vuultimo
openvix Zeus vuultimo


vuultimo login: root
Last login: Mon Apr 7 09:39:00 +0300 2014 on /dev/pts/0.
root@vuultimo:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 1
I2C_Device: 3
NIM Socket 2:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 2
I2C_Device: 1
Duo2:
Welcome to OpenViX for vuduo2
openvix Zeus vuduo2


vuduo2 login: root
Last login: Mon Apr 7 07:47:09 +0300 2014 on /dev/pts/0.
root@vuduo2:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-T2
Name: Vuplus DVB-T NIM(SSH108)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 1
I2C_Device: 3
So, as you can see, there is a difference.

thanks for the Tuner, those proc entries are control via the drivers, so imo the duo2 driver is not telling e2 it is infact a T2, i'll pass this info on to VuPlus drier dev thanks.

 

[tappari]

thanks for the Tuner, those proc entries are control via the drivers, so imo the duo2 driver is not telling e2 it is infact a T2, i'll pass this info on to VuPlus drier dev thanks.

But still the thing remains, that BlackHole image does recognize this tuner as T2 in Duo2. So does OpenVix with Ultimo.

 

[tappari]

It seems this problem is again VU+ driverproblem. So let`s see for the fix from their side.

 

[IAmATeaf]

Maybe BH are using different or even older drivers?

It might be worth grabbing the drivers from BH when the tuner is correctly recognised and comparing them to the drivers in ViX, if only to report that they are different as this might explain the differing behaviour between the images.

 

[tappari]

Maybe BH are using different or even older drivers?

It might be worth grabbing the drivers from BH when the tuner is correctly recognised and comparing them to the drivers in ViX, if only to report that they are different as this might explain the differing behaviour between the images.

No, they don`t. Copy/paste from OpenPLi site:


Senior Member
2,737 posts



+70
Good

Posted Yesterday, 07:36

atm the DUO2 driver doesn't support the internal DVB-T2 tuner for other than OI-based images.
VU+ promised that this will be fixed in the next driver update.
In the UNO & Ultimo the tuner works fine.

 

[Rob van der Does]

I've said it over and over again: all images use the same drivers.

And when drivers work in Windows XP that doesn't mean they work in Windows 8......

 

[Larry-G]

Maybe BH are using different or even older drivers?

It might be worth grabbing the drivers from BH when the tuner is correctly recognised and comparing them to the drivers in ViX, if only to report that they are different as this might explain the differing behaviour between the images.

There is no difference at all between the drivers BH use as opposed to any other image, This was pointed out in another thread a few days ago.

 

[tappari]

I've said it over and over again: all images use the same drivers.

And when drivers work in Windows XP that doesn't mean they work in Windows 8......

So right you Rob are.

 

[andyblac]

had word back from Vu, it seems they do not check what the TUNE supports, they just assume it does T2, (BH use same code as VU), in vix, i read the Driver to see what the TUNER support, in the ultimo the driver is correct in saying it is DVB-C / DVB-T2, but in Duo2 driver only says it is DVB-C / DVB-T, vuplus have told me they will fix this in next driver update.

Andy.

 

[tappari]

had word back from Vu, it seems they do not check what the TUNE supports, they just assume it does T2, (BH use same code as VU), in vix, i read the Driver to see what the TUNER support, in the ultimo the driver is correct in saying it is DVB-C / DVB-T2, but in Duo2 driver only says it is DVB-C / DVB-T, vuplus have told me they will fix this in next driver update.

Andy.

So, did you receive the tuner I sent?

 

[andyblac]

So, did you receive the tuner I sent?

just arrived 10mins ago Thanks. i'll post back once issue is confirmed fixed .

 

[tappari]

just arrived 10mins ago Thanks. i'll post back once issue is confirmed fixed .

Andy, please don`t send it back to me. I can easily buy a new one from local distributer in Finland. Let me support you this way for all your efforts.

 

[andyblac]

Andy, please don`t send it back to me. I can easily buy a new one from local distributer in Finland. Let me support you this way for all your efforts.

still waiting on new driver to test, but i can confirm it is a driver issue, thank you very much for your donation. i will get your status changed.

 

[tappari]

still waiting on new driver to test, but i can confirm it is a driver issue, thank you very much for your donation. i will get your status changed.

No problem Andy. I love your work you have done.

 

[tappari]

With VU+ drivers dated today, ssh108 tuner is recognized as T2.

 

[Rob van der Does]

It looks like VU has fix:
update driver
20140418
- Fix DVB-S2 Single(AVL6211) tuner problem(duo2, ultimo)
- Change nim_sockets of DVB-T2 tuner(duo2, needs a E2 update)

Although it says ''needs E2 update' it is possible that this is only applicable to OI. So those of you who have a T2-internal tuner could try to use the drivers from

http://archive.vuplus.com/download/drivers/

and see if it works.
But please backup your image for chances are that it doesn't work at all.

 

[tappari]

It looks like VU has fix:
update driver
20140418
- Fix DVB-S2 Single(AVL6211) tuner problem(duo2, ultimo)
- Change nim_sockets of DVB-T2 tuner(duo2, needs a E2 update)

Although it says ''needs E2 update' it is possible that this is only applicable to OI. So those of you who have a T2-internal tuner could try to use the drivers from

http://archive.vuplus.com/download/drivers/

and see if it works.
But please backup your image for chances are that it doesn't work at all.

It does work with Zeus 023 just replacing four files in /lib/modules/3.3.8-2.0/extra. But only with manual service scan. So all multiplexies having T2 broadcasts have to be scanned one by one.

 

[Rob van der Does]

OK, anyway it is working, so now Andy might be able to improve things.