266 replies to this topic

[hemertje]

wij hebben geen kennis van een of andere meeting...

[Pimsat]

Basically the problem is in /lib/modules/3.1.1/extra/dvb-bcm7335.ko

So even though as usual, 'the problems only occur with the PLi image', it seems we are not causing them

the affected modules are within the Pli image, however since you are not in charge of those modules you're not the one causing it of course. In order to check if the modules are different within the VTI image someone can run following command on the console:

$ md5sum /lib/modules/*/extra/dvb-bcm7335.ko 2d9b809fb7590d33c1a2ba5cbb696f84 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

(without $ sign) The hash 2d9b... will probably be a different one this shows up that different drivers are used in both images (VTI / Pli) We'll try to contact VU+ within the next days and try to sort it out with them directly.

@Sundtek: Thanks for all your help and support!

And also thanks to Ronh for helping to solve this problem.

I'm running VTi 4.1 now and I ran the command 'md5sum /lib/modules/*/extra/dvb-bcm7335.ko' on my Vu+ duo and I get this result:

root@vuduo:~# md5sum /lib/modules/*/extra/dvb-bcm7335.ko
c57df29a964e95ef3dd6df3412c320f8 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

So it's a different driver used by VTi ?

Edited by Pimsat, 1 April 2012 - 00:03.

[prishara]

Ik raad aan een kabel tuner te kiezen die door linux ondersteund wordt.
Veel goedkoper, en betere drivers.

welke tuners bijvoorbeeld? En hoeveel goedkoper. De sundtek kostte mij 95,- euro incl. verzending.
Ook ik krijg de sundtek kabel tuner niet werkend onder PLi. Maar met de Vix image op Xtrend 9000 draait ie wel.

Dus als de kabel tuner maar een paar tientjes kost is het misschien het overwegen waard???
Heb je een link?

[Pimsat]

Hier staat een lijst:

http://linuxtv.org/w...B-C_USB_Devices

[sundtek]

$ md5sum /lib/modules/*/extra/dvb-bcm7335.ko 2d9b809fb7590d33c1a2ba5cbb696f84 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

(without $ sign) The hash 2d9b... will probably be a different one this shows up that different drivers are used in both images (VTI / Pli) We'll try to contact VU+ within the next days and try to sort it out with them directly.

@Sundtek: Thanks for all your help and support!

And also thanks to Ronh for helping to solve this problem.

I'm running VTi 4.1 now and I ran the command 'md5sum /lib/modules/*/extra/dvb-bcm7335.ko' on my Vu+ duo and I get this result:

root@vuduo:~# md5sum /lib/modules/*/extra/dvb-bcm7335.ko
c57df29a964e95ef3dd6df3412c320f8 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

So it's a different driver used by VTi ?

that causes the different experience for you with VTI, all those issues are in the VU+ broadcom drivers. We will try to help them to fix it.
After investigating the issues with Ronh the issues are not caused by our drivers.

Edited by sundtek, 1 April 2012 - 15:42.

[littlesat]

So in short we can currently verify/confirm that it is VU-driver related?

Thanks for your help here!

Unless this is a dutch thread it switched to English so Sundtek can read with us

Edited by littlesat, 1 April 2012 - 15:45.

[sundtek]

So in short we can currently verify/confirm that it is VU-driver related?

Thanks for your help here!

Unless this is a dutch thread it switched to English so Sundtek can read with us

It seems like the broadcom drivers which are used with openpli cause some memory corruptions with external tuners and finally result in non-working En*gma2.

Driver used in openpli which crashes:
md5sum /lib/modules/*/extra/dvb-bcm7335.ko 2d9b809fb7590d33c1a2ba5cbb696f84 /lib/modules/3.1.1/extra/dvb-bcm7335.ko
Driver used in VTI which seems to have a better behavior:
md5sum /lib/modules/*/extra/dvb-bcm7335.ko c57df29a964e95ef3dd6df3412c320f8 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

Those drivers provide the virtual tuner interface

Edited by sundtek, 1 April 2012 - 16:12.

[sundtek]

It seems like the broadcom drivers which are used with openpli cause some memory corruptions with external tuners and finally result in non-working En*gma2.

Driver used in openpli which crashes:
md5sum /lib/modules/*/extra/dvb-bcm7335.ko 2d9b809fb7590d33c1a2ba5cbb696f84 /lib/modules/3.1.1/extra/dvb-bcm7335.ko
Driver used in VTI which seems to have a better behavior:
md5sum /lib/modules/*/extra/dvb-bcm7335.ko c57df29a964e95ef3dd6df3412c320f8 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

Those drivers provide the virtual tuner interface

Update:
we are in contact with vuplus finally and try to visit them in order to fix those broadcom virtual tuner issues (that's one step further now). We'll try to keep this up to date, also in case if it does not work out as expected.

Edited by sundtek, 3 April 2012 - 04:54.

[sundtek]

It seems like the broadcom drivers which are used with openpli cause some memory corruptions with external tuners and finally result in non-working En*gma2.

Driver used in openpli which crashes:
md5sum /lib/modules/*/extra/dvb-bcm7335.ko 2d9b809fb7590d33c1a2ba5cbb696f84 /lib/modules/3.1.1/extra/dvb-bcm7335.ko
Driver used in VTI which seems to have a better behavior:
md5sum /lib/modules/*/extra/dvb-bcm7335.ko c57df29a964e95ef3dd6df3412c320f8 /lib/modules/3.1.1/extra/dvb-bcm7335.ko

Those drivers provide the virtual tuner interface

Update:
we are in contact with vuplus finally and try to visit them in order to fix those broadcom virtual tuner issues (that's one step further now). We'll try to keep this up to date, also in case if it does not work out as expected.

As per advice, openpli does not seem to use the latest broadcom drivers with some systems.
Dreambox users also reported issues with OpenPli, it would be nice if OpenPli developers could document which drivers they are using (from which date or release version).

First of all in order to solve some issues OpenPli has to update the broadcom drivers.

littlesat, can you give us some information about that on your side?

VU+ is also testing the tuners again - but they are using the latest drivers on their side and don't see some of those issues actually.

Edited by sundtek, 4 April 2012 - 10:18.

[littlesat]

First of all in order to solve some issues OpenPli has to update the broadcom drivers.

How do you conclude this. Can you point us to the drivers we need to use? Do you mean DMM only - did they fixed stuff for sundtek in their drivers from last month - indeed this is still not committed)...

For what we use.... everything is here: http://openpli.git.s...itweb-index.cgi

Edited by littlesat, 4 April 2012 - 11:01.

[sundtek]

First of all in order to solve some issues OpenPli has to update the broadcom drivers.

How do you conclude this. Can you point us to the drivers we need to use? Do you mean DMM only - did they fixed stuff for sundtek in their drivers from last month - indeed this is still not committed)...

For what we use.... everything is here: http://openpli.git.s...itweb-index.cgi

DMM is working on new stuff which seems to improve kind of everything on their side but I'm not sure how much OpenPli can benefit from that in the future.

For VU+ I just doublechecked, you are indeed using the latest drivers - VU+ is just testing right now and keep updating me with their results.

The relevant part for the issues are the broadcom drivers as mentioned (since you're using the latest ones right now nothing you can do here..).
http://archive.vuplu...wnload/drivers/

Hopefully we can nail down the root cause of all that soon.

[ronh]

Good to hear that's there is progression. And I hope there will be a working update soon!

@SundTek: If you need access to my VU+Duo to test new drivers, give me a call.

[sundtek]

Some news from VU+ about the broadcom drivers:

We figured out the problem in 3rd party image.
It will be fixed in the upcoming driver update.(hopefully next week).

Edited by sundtek, 6 April 2012 - 03:15.

[littlesat]

Indeed good news!!! Thanks!!

[ronh]

@SundTek: Any progress?
I don't know what you've changed in my box, but I have a lot of crashes lately. Just by changing channels, I'll get the feared "Gears", and only a powercycle will get me back!!

[Jimmy1987]

Hey ronh,

Heb je pas een driverupdate gedaan ? want ik heb nog steeds dezelfde drivers al 2 weken geleden in gebruik.

Ik heb sinds vorige week een 2e sundtektuner erbij en heb ze intern ingebouwd met behulp van een kleine usb-hub.
Ik draai nog steeds Blackhole, en het werkt eigenlijk tot nu toe helemaal perfect, geen vastlopers enzo, heb elke avond nog opnames gehad, dus ook elke avond de 2 tuners actief staan.
Als je wil kan ik je eventueel een backup van mijn image sturen, met de hoop dat het bij jou dan ook (tijdelijk totdat de problemen met openpli opgelost zijn) goed werkt...
groetjes Jimmy

[robbedoeske]

@jimmy1987

Heb hier ook de Sundtek stick werkend met VTI,maar heb wel dat na verloop van tijd (een dag) het beeld begint te haperen,en brokkelen.Na een reboot is het dan weer een hele tijd goed,hier geen last mee met Blackhole? Heb evt wel interesse in een backup van je image.

[Jimmy1987]

@robbedoeske, je hebt pb

[ronh]

@jimmy1987: Ik begin nu pas OpenPli een beetje door te krijgen (zoek nog een goede manual voor de commandline), en weet niet goed wat je bedoeld met de BlackHole variant.
Maar ik heb, buiten de "hangers", ook af en toe het probleem zoals robbedoeske beschrijft. Dus, ja, ik ben zeer geinteresseerd in jouw image.
(Waarom werkt de email notification trouwens niet van dit forum? Ik zie de post nu pas...)

[sundtek]

@SundTek: Any progress?
I don't know what you've changed in my box, but I have a lot of crashes lately. Just by changing channels, I'll get the feared "Gears", and only a powercycle will get me back!!

VU+ is on it they found a bug in their broadcom drivers.
We are going to visit them at the end of this months to go through remaining issues (if there are still some left).