Hi Beeker, please tell me what’s wrong with my box? Why can’t I install it in a normal way?
Thanks & Best Regards
Posted 10 July 2018 - 21:53
Hi Beeker, please tell me what’s wrong with my box? Why can’t I install it in a normal way?
Thanks & Best Regards
?
You mean, you can't install plugins
Dreambox dm920, Uclan Ustym4Kpro, Gigablue UHD TRIO 4K and Dreambox dm8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.
Posted 11 July 2018 - 06:20
To be able to install this image, I have to follow your instruction as follows,
telnet
init 4
enigma2
If not it could not be install, it keep on rebooting non-stop. Is there a permanent solution to this?
Besides the above, I also wish to have the following plugins please,
Thanks & Best Regards
Posted 11 July 2018 - 12:08
To be able to install this image, I have to follow your instruction as follows,
telnet
init 4
enigma2
If not it could not be install, it keep on rebooting non-stop. Is there a permanent solution to this?
Besides the above, I also wish to have the following plugins please,
- full backup image plugin
- Terrestrial scan
- Dream explorer
Thanks & Best Regards
Wait for new image with feed for plugins.
Then you can install backupsuite for full backup.
This image was build with a trick, it was build as dm7020hd with machine config of dm7020hdv2.
Why enigma2 crahs, i have no idea yet.
Dream explorer is 3-rd party plugins, and Terrestrial scan also, but i'm not sure about that.
You have 3th party feed opkg files for dm7020hd and 3-rd party feed for all boxes.
So perhaps you can install 3-rd party plugins at this moment (if feed for dm7020hd exist).
With telnet run:
opkg update
And see if 3-rd party feed fails or not.
Edited by Beeker, 11 July 2018 - 12:10.
Dreambox dm920, Uclan Ustym4Kpro, Gigablue UHD TRIO 4K and Dreambox dm8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.
Posted 11 July 2018 - 12:15
meta-blackbox added:
meta-ixuss added:
Edited by Persian Prince, 11 July 2018 - 12:15.
Open Vision sources: https://github.com/OpenVisionE2
Posted 11 July 2018 - 12:39
ixussone test image: http://www.mediafire...ne_usb.zip/file
Open Vision sources: https://github.com/OpenVisionE2
Posted 11 July 2018 - 13:12
sogno8800hd test image: http://www.mediafire...hd_usb.zip/file
Open Vision sources: https://github.com/OpenVisionE2
Posted 11 July 2018 - 14:02
develop-dm7020hd-11.07.2018
https://www.online.e...0d-bcb283a599dd
develop-dm7020hdv2-11.07.2018
https://www.online.e...9d-67d4ea436225
Live feed inside.
bumperbee, for you take the second link (with v2 image)
Edited by zeros, 11 July 2018 - 14:02.
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 11 July 2018 - 17:00
Just for info, everything OK with my dm7020hd V1
Feed is OK, all asked plugins inside, oscam is by default installed
and ..... everything works great
Waiting for conformation about v2 box.
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 11 July 2018 - 21:41
I've ported the e2procfs for the k2pro on the 3.14.29 kernel now I have some of the proc/stb nodes(some of them are just set to null)
I've loaded the avl6862 drivers and I have /dev/dvb/adapter0/frontend0
for /proc/bus/nim_sockets most of the tools I've tried fails to detect that the avl6862 support muliple standards(dvb-s,dvb-s2 and dvb-t) and instead they identify it as dvb-t frontend, I've tried linkdroid-cnim and create_nimsockets
and they both result in the following:
NIM Socket 0:
Type: DVB-T2
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0
Unfortunately I can't test dvb-T2, I can only test dvb-s and dvb-s2 so I wrote the following to the /proc/bus/nim_scokets
NIM Socket 0:
Type: DVB-S
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0
now enigma2 sees the tuner as dvb-s and I can use the setup and set the satellite, but the scan doesn't find any channels, when running a scan I get this error in the console
FE_SET_PROPERTY failed: Bad address
the error is repeated with every frequency it scans.
So what is the cause of this error ? a particular /proc/stb node missing ? How can I collect more info about this error(enable debuggig ?)
note that the avl6862 driver uses dvb api version 3 (I think) and when running enigma I get this in the console:
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
So maybe enigma2 is compiled for dvb api version 5 and this causes it to not being able to communicate correctly with the avl6862 ?
Would appreciate if any of enigma2 experts can help me debug this
Thanks
Posted 11 July 2018 - 22:01
I've ported the e2procfs for the k2pro on the 3.14.29 kernel now I have some of the proc/stb nodes(some of them are just set to null)
I've loaded the avl6862 drivers and I have /dev/dvb/adapter0/frontend0
for /proc/bus/nim_sockets most of the tools I've tried fails to detect that the avl6862 support muliple standards(dvb-s,dvb-s2 and dvb-t) and instead they identify it as dvb-t frontend, I've tried linkdroid-cnim and create_nimsockets
and they both result in the following:
NIM Socket 0:
Type: DVB-T2
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0Unfortunately I can't test dvb-T2, I can only test dvb-s and dvb-s2 so I wrote the following to the /proc/bus/nim_scokets
NIM Socket 0:
Type: DVB-S
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0now enigma2 sees the tuner as dvb-s and I can use the setup and set the satellite, but the scan doesn't find any channels, when running a scan I get this error in the console
FE_SET_PROPERTY failed: Bad address
the error is repeated with every frequency it scans.
So what is the cause of this error ? a particular /proc/stb node missing ? How can I collect more info about this error(enable debuggig ?)
note that the avl6862 driver uses dvb api version 3 (I think) and when running enigma I get this in the console:
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
So maybe enigma2 is compiled for dvb api version 5 and this causes it to not being able to communicate correctly with the avl6862 ?
Would appreciate if any of enigma2 experts can help me debug this
Thanks
Very Very good work
If you need i can scan DVB-T
Posted 11 July 2018 - 22:36
I've ported the e2procfs for the k2pro on the 3.14.29 kernel now I have some of the proc/stb nodes(some of them are just set to null)
I've loaded the avl6862 drivers and I have /dev/dvb/adapter0/frontend0
for /proc/bus/nim_sockets most of the tools I've tried fails to detect that the avl6862 support muliple standards(dvb-s,dvb-s2 and dvb-t) and instead they identify it as dvb-t frontend, I've tried linkdroid-cnim and create_nimsockets
and they both result in the following:
NIM Socket 0:
Type: DVB-T2
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0Unfortunately I can't test dvb-T2, I can only test dvb-s and dvb-s2 so I wrote the following to the /proc/bus/nim_scokets
NIM Socket 0:
Type: DVB-S
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0now enigma2 sees the tuner as dvb-s and I can use the setup and set the satellite, but the scan doesn't find any channels, when running a scan I get this error in the console
FE_SET_PROPERTY failed: Bad address
the error is repeated with every frequency it scans.
So what is the cause of this error ? a particular /proc/stb node missing ? How can I collect more info about this error(enable debuggig ?)
note that the avl6862 driver uses dvb api version 3 (I think) and when running enigma I get this in the console:
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
So maybe enigma2 is compiled for dvb api version 5 and this causes it to not being able to communicate correctly with the avl6862 ?
Would appreciate if any of enigma2 experts can help me debug this
Thanks
Very Very good work
If you need i can scan DVB-T
Well I just tested dvb-t (without antenna) and it give the same error (FE_SET_PROPERTY failed: Bad address) So it probably doesn't work either.
Posted 12 July 2018 - 04:31
Is there a test build available for download for the Octagon SF4008?
Open Vision sources: https://github.com/OpenVisionE2
Posted 12 July 2018 - 04:33
Open Vision sources: https://github.com/OpenVisionE2
Posted 12 July 2018 - 07:42
I've ported the e2procfs for the k2pro on the 3.14.29 kernel now I have some of the proc/stb nodes(some of them are just set to null)
I've loaded the avl6862 drivers and I have /dev/dvb/adapter0/frontend0
for /proc/bus/nim_sockets most of the tools I've tried fails to detect that the avl6862 support muliple standards(dvb-s,dvb-s2 and dvb-t) and instead they identify it as dvb-t frontend, I've tried linkdroid-cnim and create_nimsockets
and they both result in the following:
NIM Socket 0:
Type: DVB-T2
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0Unfortunately I can't test dvb-T2, I can only test dvb-s and dvb-s2 so I wrote the following to the /proc/bus/nim_scokets
NIM Socket 0:
Type: DVB-S
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0now enigma2 sees the tuner as dvb-s and I can use the setup and set the satellite, but the scan doesn't find any channels, when running a scan I get this error in the console
FE_SET_PROPERTY failed: Bad address
the error is repeated with every frequency it scans.
So what is the cause of this error ? a particular /proc/stb node missing ? How can I collect more info about this error(enable debuggig ?)
note that the avl6862 driver uses dvb api version 3 (I think) and when running enigma I get this in the console:
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
So maybe enigma2 is compiled for dvb api version 5 and this causes it to not being able to communicate correctly with the avl6862 ?
Would appreciate if any of enigma2 experts can help me debug this
Thanks
Mhhhh how many frontends you have into /dev/dvb?
Patches are applied to Openpli kernel or to Coreelec?
Posted 12 July 2018 - 08:44
Mhhhh how many frontends you have into /dev/dvb?
just one AVL6862(which support DVB-S and DVB-T)
/ # find /dev/dvb/ /dev/dvb/ /dev/dvb/adapter0 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/net2 /dev/dvb/adapter0/dvr2 /dev/dvb/adapter0/demux2 /dev/dvb/adapter0/net1 /dev/dvb/adapter0/dvr1 /dev/dvb/adapter0/demux1 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/demux0
Patches are applied to Openpli kernel or to Coreelec?
coreelec kernel
Posted 12 July 2018 - 10:07
I try to copy the dvb-avl into dvb_tv but i receive:
| make[5]: *** No rule to make target 'drivers/media/dvb-core/dvb-core.c', needed by 'drivers/media/dvb-core/dvb-core.o'. Stop. | /home/openatvbuilder/openpli-oe-core/build/tmp/work-shared/k1pro/kernel-source/scripts/Makefile.build:455: recipe for target 'drivers/media/dvb-core' failed | make[4]: *** [drivers/media/dvb-core] Error 2
How i can fix?
Posted 12 July 2018 - 16:48
Fe set property patchI've ported the e2procfs for the k2pro on the 3.14.29 kernel now I have some of the proc/stb nodes(some of them are just set to null)
I've loaded the avl6862 drivers and I have /dev/dvb/adapter0/frontend0
for /proc/bus/nim_sockets most of the tools I've tried fails to detect that the avl6862 support muliple standards(dvb-s,dvb-s2 and dvb-t) and instead they identify it as dvb-t frontend, I've tried linkdroid-cnim and create_nimsockets
and they both result in the following:Unfortunately I can't test dvb-T2, I can only test dvb-s and dvb-s2 so I wrote the following to the /proc/bus/nim_scokets
NIM Socket 0:
Type: DVB-T2
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0now enigma2 sees the tuner as dvb-s and I can use the setup and set the satellite, but the scan doesn't find any channels, when running a scan I get this error in the consoleNIM Socket 0:
Type: DVB-S
Name: Availink avl6862
Has_Outputs: no
Frontend_Device: 0the error is repeated with every frequency it scans.FE_SET_PROPERTY failed: Bad address
So what is the cause of this error ? a particular /proc/stb node missing ? How can I collect more info about this error(enable debuggig ?)
note that the avl6862 driver uses dvb api version 3 (I think) and when running enigma I get this in the console:So maybe enigma2 is compiled for dvb api version 5 and this causes it to not being able to communicate correctly with the avl6862 ?DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
Would appreciate if any of enigma2 experts can help me debug this
Thanks
0 members, 3 guests, 0 anonymous users