2740 replies to this topic

[algdu83]

I think we can contact magicsees and talk to them about the project, it's a benefit for them too

http://www.magicsees...aspx?FId=n7:7:7

asking them for functional drivers

because they use AVL6862 for all their DVB boxes

they are more open than videostrong

let's try ....

Edited by algdu83, 27 July 2018 - 07:38.

[moham96]

I think we can contact magicsees and talk to them about the project, it's a benefit for them too

http://www.magicsees...aspx?FId=n7:7:7

asking them for functional drivers

because they use AVL6862 for all their DVB boxes

they are more open than videostrong

let's try ....

I don't think there is any benefit for them since we don't have their device and can't create a meta layer for it 

as for the avl6862 I think they will provide the same drivers as the ones on the avlogic github(they probably will refuse because they might have signed an NDA with avalink )

Also do you know the exact model names of their devices that have AVL6862/r848 demod/tuner combo?

[ftp21_]

Hello,

I can't understand how can work a driver if enigma try to FE_SET_PROPERTY and avl6862.c have a bad implementation of this ioctl

 

I'm working on avl6862.c to make a working FE_SET_PROPERTY implementation

[engineerkhan15]

 

Ok can you try these images and tell me which one works and which one doesn't ?(these are k1 pro images)

https://drive.google...DtRaQt2tpO7ZVUE

 

Hi moham96,

I am sorry I was busy yesterday so could not find time to test those images. Today, I tested and here are the results:

 

File: 8b3dbcd4058b77b2b0c0480bd6909c9bb420f713
Boot: No
Display: Blank and message on LED screen "Mode not supported"
Telnet: No connectivity
-------------------------------------------------------------
File: 901cfac8b226d69f4c2ac3747aaea8676fa6bfad
Boot: Yes
Display: "Please wait: booting ..." message, then spinner and then Language Selection Screen
WebIF: Working
Telnet: Working
FTP: Working
Skin: Full HD working
Remote: Not working
DVB Driver: Detected
DVB-S Scan: Started, scanned all frequencies but completed without finding any channel
-------------------------------------------------------------
File: 6367ca2f66dd8dfebf4a4b15374a17a9dc7b6b52
Boot: Yes
Display: "Please wait: booting ..." message, then spinner and then Language Selection Screen
WebIF: Working
Telnet: Working
FTP: Working
Skin: Full HD working
Remote: Not working
DVB Driver: Detected
DVB-S Scan: Started, scanned all frequencies but completed without finding any channel
-------------------------------------------------------------
File: f032c1d95676121adafbad860ac76a52679b370f
Boot: Yes
Display: "Please wait: booting ..." message, then spinner and then Language Selection Screen
WebIF: Working
Telnet: Working
FTP: Working
Skin: Full HD working
Remote: Not working
DVB Driver: Detected
DVB-S Scan: Started, scanned all frequencies but completed without finding any channel

--------------------------------------------------------------

 

I am also attaching dmesg logs of all images except the first (because of no FTP connectivity in that case).

Attached Files

•  KI Pro - dmesg logs.rar   54.09KB   1 downloads

[jootje]

Hi guys,

Absolute great image for my 920!

I just found out that when I push my Teletekst button, the receiver reboots.

If this could be solved, than its the perfect image for me!

[Persian Prince]

Maybe IPv6 is the problem and we need to revert https://github.com/P...ce646c6a2c3152f

[oldgraf]

Collected errors:
 * opkg_prepare_url_for_install: Couldn't find anything to satisfy 'enigma2-plugin-systemplugins-tempfancontrol'.
 * rm_r: Failed to open dir /other/src/openplidev/build/tmp/work/optimussos2plus-oe-linux/openpli-enigma2-image/1.0-r0/temp/ipktemp//opkg-UYdUXX: No such file or directory.

ERROR: openpli-enigma2-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /other/src/openplidev/build/tmp/work/optimussos2plus-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_rootfs.1685
ERROR: Task (/other/src/openplidev/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_rootfs) failed with exit code '1'
 

 

 Why is this error ?

Edited by oldgraf, 27 July 2018 - 14:07.

[moham96]

Maybe IPv6 is the problem and we need to revert https://github.com/P...ce646c6a2c3152f

Hard to believe that something like ipv6 would prevent the kernel from booting , anyway there are only five revisions left untested, if it turns out the ipv6 is the problem I will build it as a module to be loaded after a successful boot and if that failed I will disable ipv6 completely.

 

@engineerkhan15, You up for five more images to test?

[Beeker]

Do you have a crash log?

[engineerkhan15]

Yes, please upload. I will test those too.

[moham96]

Yes, please upload. I will test those too.

Ok, I've queued three images to be uploaded to this directory in gdrive https://drive.google...ME8xCsIKL8ac7r4

Download images as they appear on that link and test and report back, they should give us a pretty good idea if the problem is with the ipv6 module, if they all worked I'd have to upload a fourth image, my interntet connection is bad so be patient   

[moham96]

Also You said in a your previous reply

 

Display: Blank and message on LED screen "Mode not supported"

 

What LED screen do you mean ?

[engineerkhan15]

I mean LED Display (Samsung 32" 5 Series).

[engineerkhan15]

I have tested all three files and same results for all three images:

Boot: Yes
Display: "Please wait: booting ..." message, then spinner and then Language Selection Screen
WebIF: Working
Telnet: Working
FTP: Working
Skin: Full HD working
Remote: Not working
DVB Driver: Detected
DVB-S Scan: Enigma2 crashes at DVB-S tuner setup while changing configuration mode from simple to advanced (it does not crash if we first setup DVB-T or disable it and then go to DVB-S setup) but second time setup is completed, scan started, scanned all frequencies but completed without finding any channel.

Attached Files

•  enigma2_crash.log   9.07KB   1 downloads

Edited by engineerkhan15, 27 July 2018 - 17:48.

[moham96]

I have tested all three files and same results for all three images:

Boot: Yes
Display: "Please wait: booting ..." message, then spinner and then Language Selection Screen
WebIF: Working
Telnet: Working
FTP: Working
Skin: Full HD working
Remote: Not working
DVB Driver: Detected
DVB-S Scan: Enigma2 crashes at DVB-S tuner setup while changing configuration mode from simple to advanced (it does not crash if we first setup DVB-T or disable it and then go to DVB-S setup) but second time setup is completed, scan started, scanned all frequencies but completed without finding any channel.

well there is only one commit left that might caused the images to stop booting I've uploaded a new image with the name 0ca1593642bf017f57f77d0051f3af751b876686.zip

please test

[sauna]

moham96

can I download for testing on k1plus? I tried to compile myself, but there are errors.

[engineerkhan15]

File: 0ca1593642bf017f57f77d0051f3af751b876686
Boot: No
Display: Blank and message on LED screen "Mode not supported"
Telnet: No connectivity

[moham96]

File: 0ca1593642bf017f57f77d0051f3af751b876686
Boot: No
Display: Blank and message on LED screen "Mode not supported"
Telnet: No connectivity

The only change in that commit was using the meson-remote driver instead of meson-i, So maybe the k1pro has problem with that driver ?

one user (ftp21_) is running openpli with the latest commits on k1pro so could it be that your device is faulty ?

[moham96]

I think I found the problem and will upload a test image again(hit: it was a stupid mistake by me )

[moham96]

I pushed the k1pro fix to the pli-extras repo, do an update and build images, can someone provide k1pro and k1plus test images here for users, I can't upload files now.

Thanks