121 replies to this topic

[DrAk3]

in addition i try to use the kernel-module-dvb-usb-a867 module (in substitution of the AF9035) and the systm did not start (the system is unreachable).

 

D.

[DrAk3]

this is the e2 log while the system appears to be stalled:

 

 
PYTHONPATH: /usr/lib/enigma2/python
+ (1) Background File Eraser
+ (5) Tuxtxt
+ (8) graphics acceleration manager
+ (9) GFBDC
24300k video mem
 - double buffering available!
17100kB available for acceleration surfaces.
resolution: 1280 x 720 x 32 (stride: 5120)
+ (9) gLCDDC
found OLED display!
lcd buffer 0x7f17b8 8448 bytes, stride 132
LCD resolution: 132 x 64 x 8 (stride: 132)
+ (9) Font Render Class
[FONT] initializing lib...
[FONT] loading fonts...
[FONT] Intializing font cache, using max. 4MB...
+ (10) gRC
RC thread created successfully
+ (15) eWindowStyleManager
+ (20) DVB-CI UI
+ (20) UHF Modulator
couldnt open /dev/rfmod0!!!!
+ (20) RC Input layer
+ (20) misc options
+ (20) AVSwitch Driver
couldnt open /dev/dbox/fp0 to monitor vcr scart slow blanking changed!
+ (21) input device driver
Input device "dreambox remote control (native)" is a remotecontrol
Input device "dreambox advanced remote control (native)" is a remotecontrol
Input device "front panel" is a remotecontrol
Input device "AVerMedia HD Volar (A867)" is a remotecontrol
Found 4 input devices.
+ (22) Hdmi CEC driver
eHdmiCEC: detected physical address change: 1000 --> 1100
eHdmiCEC: send message 84 11 00 01 
+ (30) eActionMap
+ (35) CI Slots
scanning for common interfaces..
CI Slot 0 setSource(0)
CI Slot 1 setSource(0)
eDVBCIInterfaces->setInputSource(0, 0)
eDVBCIInterfaces->setInputSource(1, 1)
cannot open /proc/stb/tsmux/input2
cannot open /proc/stb/tsmux/input3
done, found 2 common interface slots
+ (35) CA handler
+ (36) Stream server
+ (40) eServiceCenter
settings instance.
+ (41) eServiceFactoryDVD
+ (41) eServiceFactoryM2TS
+ (41) eServiceFactoryMP3
+ (41) eServiceFactoryFS
+ (41) eServiceFactoryDVB
reached rl 70
---- opening lame channel db
reading services (version 4)
loaded 2555 services
linking adapter1/frontend0 to vtuner0
scanning for frontends..
opening frontend 0
close frontend 0
opening frontend 1
close frontend 1
opening frontend 2
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!

[Pr2]

Hi,

 

Can you fix the bug to be able to set back Multi EPG graphique on the Guide button? This is an important woman acceptance factor for this "new version". :-)

 

Thanks,

 

Pr2

 

Hi,

 

I just find that I have Multi EPG graphique assigned to the i key instead of the guide key.

Is it a bug in the new RC driver, do they invert i key and guide key?

 

Why isn't it possible possible to assign Multi EPG graphique to the guide key (like it was possible to do before)?

 

Pr2

Edited by Pr2, 12 May 2013 - 09:04.

[WTE]

Hi,

 

Can you fix the bug to be able to set back Multi EPG graphique on the Guide button? This is an important woman acceptance factor for this "new version". :-)

 

Thanks,

 

Pr2

 

Hi,

 

I just find that I have Multi EPG graphique assigned to the i key instead of the guide key.

Is it a bug in the new RC driver, do they invert i key and guide key?

 

Why isn't it possible possible to assign Multi EPG graphique to the guide key (like it was possible to do before)?

 

Pr2

 

You can change it in keymap.xml by rename showEventInfoSingleEPG to showEventInfoMultiEPG and advance is you can assign to info button another event.

It seems that info and EPG were identical button and need to been devide.

 

Hopefully a simular selection can been add for EPG and color buttons

[Pr2]

Hi WTE,

 

Thanks for the tip but if you do a long press on the Guide key (for example) last option is:  Select the default EPG type...

There I select Multi EPG Graphique but this doesn't work, so there is a bug with this option in the new image.  

That's what I want to point out here, it is no longer possible to change the default EPG on the Guide button with a long key press.

 

Same long press option is available for the i too.

 

Pr2

[Pr2]

Hi,

 

I test the tip given by WTE but it is not the EPG that I am talking about, it is not Multi EPG but Multi EPG Graphique (which looks like CoolTVguide).

 

I am using this EPG:

 

opkg install enigma2-plugin-extensions-graphmultiepg

 

Pr2

[pieterg]

in addition i try to use the kernel-module-dvb-usb-a867 module (in substitution of the AF9035) and the systm did not start (the system is unreachable).

this might fix it:

http://sourceforge.n...cf0716cc8b1992/

[Dimitrij]

this might fix it:

http://sourceforge.n...cf0716cc8b1992/

It works, thanks.

Edited by Dima73, 15 May 2013 - 05:51.

[DrAk3]

in addition i try to use the kernel-module-dvb-usb-a867 module (in substitution of the AF9035) and the systm did not start (the system is unreachable).

this might fix it: http://sourceforge.n...cf0716cc8b1992/

Tonight i'll test it! It will works also for the 9035 module or only for the a867? Regards D.

[pieterg]

only one way to find out
I don't have those devices myself.

[DrAk3]

only one way to find out
I don't have those devices myself.

 

i can confirm that it works! i use the 9035 kernel module and the system boot regulary

 

D.

[jpuigs]

What do you do with this file dvb.cpp ? Where do you upload to ?

[betacentauri]

@jpuigs: Nothing. Do only a normal software update via menu.

Edited by betacentauri, 15 May 2013 - 20:59.

[pieterg]

only one way to find out
I don't have those devices myself.

 
i can confirm that it works! i use the 9035 kernel module and the system boot regulary
 
D.

ok, thanks for the confirmation.

That means this has been the solution for most (hopefully all) recent dvb-usb related issues.

[jpuigs]

OK. Thanks.  I've updated and it works again !.

 

Now, I think I could delete packets I've dowloaded those days to test....

 

kernel-module-af9013

kernel-module-af9033

kernel-module-dvb-usb

kernel-module-dvb-usb-af9015

kernel-module-dvb-usb-af9035

kernel-module-dvb-usb-v2

 

Which one could I delete ?

reading dmesg, I don't see clearly which one I need,

 

DVB: registering new adapter (dvb0)
platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
platform dvb0.0: DVB: registering adapter 0 frontend 1 (DVB-S2)...
input: front panel as /devices/virtual/input/input2
NET: Registered protocol family 10
usb 1-1: dvb_usb_v2: found a 'AVerMedia AVerTV Volar HD/PRO (A835)' in warm state
usbcore: registered new interface driver dvb_usb_af9035
usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (AVerMedia AVerTV Volar HD/PRO (A835))
i2c i2c-4: af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1
usb 1-1: DVB: registering adapter 1 frontend 0 (Afatech AF9033 (DVB-T))...
i2c i2c-4: tda18218: NXP TDA18218HN successfully identified
Registered IR keymap rc-empty
input: AVerMedia AVerTV Volar HD/PRO (A835) as /devices/platform/ehci-brcm.0/usb1/1-1/rc/rc0/input3
rc0: AVerMedia AVerTV Volar HD/PRO (A835) as /devices/platform/ehci-brcm.0/usb1/1-1/rc/rc0
usb 1-1: dvb_usb_v2: schedule remote query interval to 500 msecs
usb 1-1: dvb_usb_v2: 'AVerMedia AVerTV Volar HD/PRO (A835)' successfully initialized and connected
Console: switching to colour dummy device 80x25
platform dvb0.0: DVB: registering adapter 0 frontend 2 (vtuner)...

 

Which Tuner do I have ? 9015, 9033, 9035 ???

[betacentauri]

The packages do not harm. They only take some space in your flash. So if it is no problem you don't need to remove them.

[jpuigs]

OK thank You.

[Gennar1]

OK. Thanks.  I've updated and it works again !.

 

Now, I think I could delete packets I've dowloaded those days to test....

 

kernel-module-af9013

kernel-module-af9033

kernel-module-dvb-usb

kernel-module-dvb-usb-af9015

kernel-module-dvb-usb-af9035

kernel-module-dvb-usb-v2

 

Which one could I delete ?

reading dmesg, I don't see clearly which one I need,

 

 

DVB: registering new adapter (dvb0)
platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
platform dvb0.0: DVB: registering adapter 0 frontend 1 (DVB-S2)...
input: front panel as /devices/virtual/input/input2
NET: Registered protocol family 10
usb 1-1: dvb_usb_v2: found a 'AVerMedia AVerTV Volar HD/PRO (A835)' in warm state
usbcore: registered new interface driver dvb_usb_af9035
usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (AVerMedia AVerTV Volar HD/PRO (A835))
i2c i2c-4: af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1
usb 1-1: DVB: registering adapter 1 frontend 0 (Afatech AF9033 (DVB-T))...
i2c i2c-4: tda18218: NXP TDA18218HN successfully identified
Registered IR keymap rc-empty
input: AVerMedia AVerTV Volar HD/PRO (A835) as /devices/platform/ehci-brcm.0/usb1/1-1/rc/rc0/input3
rc0: AVerMedia AVerTV Volar HD/PRO (A835) as /devices/platform/ehci-brcm.0/usb1/1-1/rc/rc0
usb 1-1: dvb_usb_v2: schedule remote query interval to 500 msecs
usb 1-1: dvb_usb_v2: 'AVerMedia AVerTV Volar HD/PRO (A835)' successfully initialized and connected
Console: switching to colour dummy device 80x25
platform dvb0.0: DVB: registering adapter 0 frontend 2 (vtuner)...

 

Which Tuner do I have ? 9015, 9033, 9035 ???

 

The A835 needs usb-dvb-v2, af9033, af9035,  tda18218 and the af9033 firmware. You can remove anything else.

[Gennar1]

 

only one way to find out
I don't have those devices myself.

 
i can confirm that it works! i use the 9035 kernel module and the system boot regulary
 
D.

 

ok, thanks for the confirmation.

That means this has been the solution for most (hopefully all) recent dvb-usb related issues.

 

Thanks Pieterg. Right now I'm travelling for work, but this week-end I will test several USB tuners to make sure all issues are fixed.

[j.puig]

The A835 needs usb-dvb-v2, af9033, af9035,  tda18218 and the af9033 firmware. You can remove anything else.

 

 

Thanks.