Er zijn 49 reacties in dit onderwerp

[malakudi]

I updated today my ET9X00 box to the latest kernel. My USB DVB-T stick Hauppauge WinTV-Nova-TD does not work anymore. I removed usbtunerhelper manually.
driver seems to load ok, /dev/dvb/adapter1/frontend0 and /dev/dvb/adapter2/frontend0 are created, vtuner interfaces are created, /proc/bus/nim_sockets display the two DVB-T tuners, enigma2 recognize them, but when I try to tune to a channel or scan, in dmesg I get I2C errors.

dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...
DiB0070: successfully identified
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
DVB: registering adapter 2 frontend 0 (DiBcom 7000PC)...
DiB0070: successfully identified
Registered IR keymap rc-dib0700-rc5
input: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.0/usb1/1-1/1-1.2/rc/rc0/input3
rc0: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.0/usb1/1-1/1-1.2/rc/rc0
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: Hauppauge Nova-TD Stick (52009) successfully initialized and connected.
dib0700: rc submit urb failed
 
...
 
DVB: registering adapter 0 frontend 2 (vtuner)...
DVB: registering adapter 0 frontend 3 (vtuner)...
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C write failed
DiB0070 I2C read failed
DiB0070 I2C write failed
...

[littlesat]

I suggest have the same here....

opkg install usbtunerhelper

and restart the box was what helped for me as work-a-round.

[malakudi]

Indeed, reinstalling usbtunerhelper fixes the issue. So something is not handled correctly in the new implementation. Please let me know if I can help debugging.

[littlesat]

i do not know how to help... but at least i2C failed is the issue.... so it cannot tune...???

[malakudi]

After today's update (which removed usbtunerhelper again), I no longer have I2C errors. I rebooted box 4-5 times, in one boot I got some weird message that frontend3 does not specify frequency limits. When this happened, DVB-T tuners didn't work. I haven't kept log since it only happened once. All other boot sessions were OK and DVB-T tuners work (both of them).
What fixed the I2C errors? Maybe this? http://openpli.git.s...a3c3e5ce2426a2a

[littlesat]

That was not the fix (that fix was to get recordings viewable)....

But it is not stable without usbtunerhelper.... sometimes the USB stick is working and sometimes not with the 0700 drivers....

[pieterg]

I think the i2c errors will be back.
It seems some startup issue, perhaps timing related immediately after opening the frontend.

With the old usbtunerhelper setup, the frontend was opened for at least 15s before the first i2c requests started.

[littlesat]

With several atempts to kill enigma2 via the console and start it via the console I was also able to get tuning ussues....

When it happens the SNR gives back 1%... usually this value is always 0% when it was correct..... (the SNR value was never correct before - it was more a tuning failed/OK flag)...

Veranderd door littlesat, 11 april 2012 - 09:14

[malakudi]

Reported SNR is OK in later versions of DIB0700 chipsets, like the one used in my Hauppauge Nova TD. However, it is reported as dB and not as percentage scaled to 65535. For example, a decimal value of 258 means 25.8 dB . I don't know how this has to be handled in order to be shown correctly as dB in enigma2. enigma2 thinks this is a percentage scale, so 258/65535 is 0.

Will try to check if I2C issues return.

[littlesat]

Interestinng that 258/65536..... I'll check this and try if I can make at least a fix for this....

Veranderd door littlesat, 11 april 2012 - 09:52

[littlesat]

Zou dit het kunnen zijn?

http://patchwork.lin...rg/patch/10328/

[pieterg]

...no...

[malakudi]

Indeed, I2C errors back again after some reboots. It seems to be completely random.
Sometimes it loads without I2C errors, but doesn't deliver TS and in dmesg I get this:

DVB: registering adapter 0 frontend 2 (vtuner)...
DVB: registering adapter 0 frontend 3 (vtuner)...
DVB: adapter 0 frontend 3 frequency limits undefined - fix the driver
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0

I can no longer install usbtunerhelper with any --force options. I installed it by extracting data.tar.gz manually

[Gennar1]

Interestinng that 258/65536..... I'll check this and try if I can make at least a fix for this....

Something like the attached patch should fix it, if I picked up the correct source file (there are 2 similar frontends: 7000p and 7000m).

Bijgevoegde Bestanden

•  dib7000p-output-full-scale-SNR.patch.zip   935bytes   21 Aantal bijlagen

Veranderd door Gennar1, 11 april 2012 - 11:48

[malakudi]

Interestinng that 258/65536..... I'll check this and try if I can make at least a fix for this....

Something like the attached patch should fix it, if I picked up the correct source file (there are 2 similar frontends: 7000p and 7000m).

 
+ case 0:
+ /* QPSK */
+ max_snr = 230;
+ break;
+ case 1:
+ /* QAM_16 */
+ max_snr = 260;
+ break;
+ case 2:
+ default:
+ /* QAM_64 */
+ max_snr = 290;
+ break;

I think I've seen higher values than 260 in QAM16. Have to check again though to be sure.

Anyway, this will display SNR as percentage. I would prefer to be able to see it in enigma2 as dB, as it happens with ET9X00 DVB-S2 tuners.

Veranderd door malakudi, 11 april 2012 - 11:47

[Gennar1]

Something like the attached patch should fix it, if I picked up the correct source file (there are 2 similar frontends: 7000p and 7000m).

I think I've seen higher values than 260 in QAM16. Have to check again though to be sure.

Anyway, this will display SNR as percentage. I would prefer to be able to see it in enigma2 as dB, as it happens with ET9X00 DVB-S2 tuners.

You can have even infinite SNR
The point here is that we should fix a reasonable max value that indicates optimal reception (if we want to display a 0-100% quality bar). This values are taken from the af9015 driver and they seem to give a decent idea of the reception quality with several sticks.

If you prefer to see the dB value in Enigma2, you can do the inverse conversion directly in the skin. I already modified several drivers in the same way above, so it would benefit all of them.

Veranderd door Gennar1, 11 april 2012 - 11:58

[littlesat]

Not like that patch... that patch makes a % again.... I suggest to put this in E2.

[malakudi]

I suggest displaying as dB in enigma2 if the tuner supports it and convert to percentage in software inside enigma2, in case this is possible. If it is not, gannar1 patch is OK. However, rounding once in the driver and then again in the enigma2 code is loosing detail.

Anyway this is just a beautification, the real issue is the I2C problems.

Veranderd door malakudi, 11 april 2012 - 12:06

[littlesat]

If you do it correctly both should be possible.... % and dB....

[Gennar1]

Not like that patch... that patch makes a % again.... I suggest to put this in E2.

We just have to agree to a common standard. I started modding the drivers in the way above, as it was easier (no Enigma2 modification required to have a working SNR bar). But recent drivers (at least the well-written ones) usually output SNR in 0.1 dB units (like the dib7000), so it makes sense to adopt that format in Enigma2. Non-conforming drivers can be converted to that format too, and there is even a remote chance that the patches may be accepted in the kernel.