2740 replies to this topic

[ftp21_]

I read the commits to another branch from afl1:

https://github.com/a...l/commits/r848a

 

Anyone able to compile this version?

[moham96]

I had the proc entry stb/frontend/0/mode to enable multitype tuner

 

http://www.mediafire...q/procfs.tar.gz

 

Now enigma can switch the mode but i cannot scan (now i can scan only dvb-t) for this error:

[eDVBFrontend] opening frontend 0
[eDVBChannel] getDemux cap=00
[eDVBResourceManager] allocate demux cap=00
[eDVBResourceManager] allocating demux adapter=0, demux=0, source=-1 fesource=0
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBDemux] DMX_SET_SOURCE Frontend0 failed: Invalid argument
[eDVBFrontend] (0)tune
[eDVBFrontend] tune setting type to 2 from 0
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend] startTuneTimeout 5000
[eDVBFrontend] setVoltage 0
[eDVBFrontend] setFrontend 1
[eDVBFrontend] setting frontend 0
FE_SET_PROPERTY failed: Bad address

I suspect a wrong demux allocation and it can crash FE_SET_PROPERTY

so, we're back to square one, the "FE_SET_PROPERTY failed: Bad address" needs somone who understand the avl6862 driver

[ftp21_]

 

I had the proc entry stb/frontend/0/mode to enable multitype tuner

 

http://www.mediafire...q/procfs.tar.gz

 

Now enigma can switch the mode but i cannot scan (now i can scan only dvb-t) for this error:

[eDVBFrontend] opening frontend 0
[eDVBChannel] getDemux cap=00
[eDVBResourceManager] allocate demux cap=00
[eDVBResourceManager] allocating demux adapter=0, demux=0, source=-1 fesource=0
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBDemux] DMX_SET_SOURCE Frontend0 failed: Invalid argument
[eDVBFrontend] (0)tune
[eDVBFrontend] tune setting type to 2 from 0
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend] startTuneTimeout 5000
[eDVBFrontend] setVoltage 0
[eDVBFrontend] setFrontend 1
[eDVBFrontend] setting frontend 0
FE_SET_PROPERTY failed: Bad address

I suspect a wrong demux allocation and it can crash FE_SET_PROPERTY

so, we're back to square one, the "FE_SET_PROPERTY failed: Bad address" needs somone who understand the avl6862 driver

 

 

 

I can't understand why same driver on "True Linux distribution" work well with tvheadend.

I read a commit with "set property fix" message on branch r484a

[moham96]

 

 

I had the proc entry stb/frontend/0/mode to enable multitype tuner

 

http://www.mediafire...q/procfs.tar.gz

 

Now enigma can switch the mode but i cannot scan (now i can scan only dvb-t) for this error:

[eDVBFrontend] opening frontend 0
[eDVBChannel] getDemux cap=00
[eDVBResourceManager] allocate demux cap=00
[eDVBResourceManager] allocating demux adapter=0, demux=0, source=-1 fesource=0
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBDemux] DMX_SET_SOURCE Frontend0 failed: Invalid argument
[eDVBFrontend] (0)tune
[eDVBFrontend] tune setting type to 2 from 0
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend] startTuneTimeout 5000
[eDVBFrontend] setVoltage 0
[eDVBFrontend] setFrontend 1
[eDVBFrontend] setting frontend 0
FE_SET_PROPERTY failed: Bad address

I suspect a wrong demux allocation and it can crash FE_SET_PROPERTY

so, we're back to square one, the "FE_SET_PROPERTY failed: Bad address" needs somone who understand the avl6862 driver

 

 

 

I can't understand why same driver on "True Linux distribution" work well with tvheadend.

I read a commit with "set property fix" message on branch r484a

 

Well actually it doesn't work with tvheadend either, I think if you build tvheadend from the official repo, then tvheadend won't detect the card ( I could be wrong though, I tried it once a long time ago).

I think afl1 also patched the tvheadend version that is shipped with the coreelec to work with the avl6862

 

I'm trying now to build the driver with previous commits by afl1

[ftp21_]

Well actually it doesn't work with tvheadend either, I think if you build tvheadend from the official repo, then tvheadend won't detect the card ( I could be wrong though, I tried it once a long time ago).

 

 

I think afl1 also patched the tvheadend version that is shipped with the coreelec to work with the avl6862

 

I'm trying now to build the driver with previous commits by afl1

 

 

This is the thread where are the tvheadend modify:

https://tvheadend.org/issues/4278

[ftp21_]

 

Well actually it doesn't work with tvheadend either, I think if you build tvheadend from the official repo, then tvheadend won't detect the card ( I could be wrong though, I tried it once a long time ago).

 

 

I think afl1 also patched the tvheadend version that is shipped with the coreelec to work with the avl6862

 

I'm trying now to build the driver with previous commits by afl1

 

 

This is the thread where are the tvheadend modify:

https://tvheadend.org/issues/4278

 

 

We also have this feature on dvb.cpp

https://github.com/O...vb/dvb.cpp#L967

[engineerkhan15]

I compiled the image for K1 Pro using recipe of K2 Pro (old) and CoreELEC kernel. Box is booting well, PLi FullHD skin working (no need to change skin). Drivers for AVL6862 loaded and displaying as DVB-S/DVB-T tuner. But scan on DVB-S detected no channels.

[frankviana]

I compiled the image for K1 Pro using recipe of K2 Pro (old) and CoreELEC kernel. Box is booting well, PLi FullHD skin working (no need to change skin). Drivers for AVL6862 loaded and displaying as DVB-S/DVB-T tuner. But scan on DVB-S detected no channels.

 

Please post the link for some tests.

 

Thank you.

[engineerkhan15]

http://www.mediafire...sdcard.zip/file

[erbas]

http://www.mediafire...sdcard.zip/file

Well, thank you very much.

[Persian Prince]

Update pli-extras with "update.sh" and compile again

[moham96]

Anyone with k2pro (s905d soc) make an update and build and image using k2pro_s905D as a  MACHINE, I've used the same device tree as the k1 pro because I don't know which device tree belongs to the k2 pro  so you might lose LAN connection or have less ram?

If you do know which of these device trees is the right for k2 pro s904d please tell

https://github.com/C...-trees-amlogic/

[igorg11]

 k2pro (s905d soc) 

gxl_p231_2g_dvb

[thmls]

http://www.mediafire...sdcard.zip/file

for my no boot stock on mecool logo

i have last firmware android 7.1.2

Edited by thmls, 23 July 2018 - 21:44.

[algdu83]

For me Is boot with gxl_p230_k1_pro.dtb

all work without dvb

I have test with my favoris but dvb not work

But thnks

Edited by algdu83, 23 July 2018 - 21:51.

[thmls]

For me Is boot with gxl_p230_k1_pro.dtb

all work without dvb

I have test with my favoris but dvb not work

But thnks

where put the file gxl_p230_k1_pro.dtb?

i have 4 files

kernel.itb

image-version-info

first-boot

aml_autoscript

 

I would have to start without changing anything

Edited by thmls, 23 July 2018 - 22:06.

[thmls]

finaly start up with

 

gxl_p230_k1_pro.dtb

[erbas]

finaly start up with

 

gxl_p230_k1_pro.dtb

How did you do, friend?

Can you post the image?

What a change!

[algdu83]

 

finaly start up with

 

gxl_p230_k1_pro.dtb

How did you do, friend?

Can you post the image?

What a change!

 

http://www.mediafire...sdcard.zip/file

and after add

https://kszaq.libree...p230_k1_pro.dtb

[moham96]

 k2pro (s905d soc) 

gxl_p231_2g_dvb

I suspected that file too but are you sure ?

please do the following:

place the gxl_p231_2g_dvb.dts file in the k2pro_s905D directory

and change this line https://github.com/P...o_s905D.conf#L9

from

KERNEL_DEVICETREE = "gxl_p230_k1_pro.dtb"

to

KERNEL_DEVICETREE = "gxl_p230_2g_dvb.dtb"

then test the following:

1-you have LAN working (got ip).

2- the amount of allocated ram is correct.

3- you have dvb nodes.

note that currently enigma2 doesn't work with afl1 dvb drivers so to test for dvb just make sure you have dvb nodes as such

➜  ~ ls -la /dev/dvb/adapter0
total 0
drwxr-xr-x  2 root root      240 Jul 24 06:30 .
drwxr-xr-x  3 root root       60 Jul 24 06:30 ..
crw-rw----+ 1 root video 212,  4 Jul 24 06:30 demux0
crw-rw----+ 1 root video 212, 20 Jul 24 06:30 demux1
crw-rw----+ 1 root video 212, 36 Jul 24 06:30 demux2
crw-rw----+ 1 root video 212,  5 Jul 24 06:30 dvr0
crw-rw----+ 1 root video 212, 21 Jul 24 06:30 dvr1
crw-rw----+ 1 root video 212, 37 Jul 24 06:30 dvr2
crw-rw----+ 1 root video 212,  3 Jul 24 06:30 frontend0
crw-rw----+ 1 root video 212,  7 Jul 24 06:30 net0
crw-rw----+ 1 root video 212, 23 Jul 24 06:30 net1
crw-rw----+ 1 root video 212, 39 Jul 24 06:30 net2

if you have frontend0 device then you're good to go, all we need is driver patch to support enigma2.

You could go a bit further and test the DVB using command line tools but it's unnecessary.

Please report back if your tests are positive so I can change the dtb file in the repo.

 

thanks