2740 replies to this topic

[moham96]

 

Regards

Can you give the output of

blkid

The booting issue might be related to the faulty amlogic emmc drivers, If you have Uart cable that would be useful also

 

Regards

 

Sorry but I don'T have Uart cable.

 

This is the output of

blkid

grab

 

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="1dc052af-fc5c-4690-9ce3-00ae3920916b" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="D18D-D209" TYPE="vfat"
root@k1plus:~# grab
Framebuffer failed
Grabbing Video ...
Resizing Video to 127 x -1627645944 ...
Segmentation fault

 

yes your device has the emmc problem, maybe it's causing the device not to boot, I have no Idea how to solve it without the device by my side, if you know how  compile kernel you can try some kernel configs and see if they change anything

[thmls]

ftp21 image
after reboot no boot

[bumperbee]

That’s great, thanks very much Master Zeros

[frankviana]

K1pro: http://www.mediafire...pro_sdcard.zip 

K1 pro

Boot ok, only 31 channels found 58w c band. Good to see my k1 tunning channels.

[frankviana]

I have the signal (lock) for all transponders using signal finder option, but when scan manually, don't store anymore, only the first.

 

When reboot the device and choosing tuner configuration (dvt-t/atsc) and after dvbs2, we have the option again to scan manually another transponder and find a lot of channels again. The tuner block the firsts transponders until reboot receiver. The first manually search I found 31 channels, the second transponder after reboot, I found 21 channels.

 

 IMG_20180809_232308.jpg   99.72KB   12 downloads

 

 IMG_20180809_231432.jpg   89.51KB   10 downloads

[frankviana]

The problem is only to store after first channels... I have the lock/signal tuner for all transponders all time: before or after finish search (manually or automatic scan). Very good sensibility

[zeros]

guard77, please give some more info. On DM900 UHD, what you use, if the thing was okay a while ago? If so, may need to review the latest changes.
However, I guess I can't help but the ones that read the information about your answers may help.
Thank you for your explanations.

[algdu83]

k1_pro

For me Is boot

I have test with my favoris i have signal with all channels but not workin why

thnks

[moham96]

I have the signal (lock) for all transponders using signal finder option, but when scan manually, don't store anymore, only the first.

 

When reboot the device and choosing tuner configuration (dvt-t/atsc) and after dvbs2, we have the option again to scan manually another transponder and find a lot of channels again. The tuner block the firsts transponders until reboot receiver. The first manually search I found 31 channels, the second transponder after reboot, I found 21 channels.

 

IMG_20180809_232308.jpg

 

IMG_20180809_231432.jpg

Yes this is a known issue, the tuner is kept locked after the scan, needs resetting

[engineerkhan15]

 

Why persian prince's images don't work !! @persian any Idea ?

 

you should see four types, if you see only two then probably the dvb drivers are not loaded and enigma is reading the hardcoded nim_sockets

try to ssh into the device and run

lsmod

also boot into the working image(ftp21_)  and run this

echo "dmx0" > /sys/class/stb/source

and then tune into a channel and see if this changes anything

 

Persian Prince:

root@k1pro:~# lsmod
Module                  Size  Used by
mali                  241508  0
e2_procfs              23151  0
r848a                  34309  1
avl6862               253365  1
aml_fe                  5178  0
aml                    91002  1 aml_fe

ftp21_:

No change in behavior after the telnet command: echo "dmx0" > /sys/class/stb/source

[moham96]

 

Regards

Can you give the output of

blkid

The booting issue might be related to the faulty amlogic emmc drivers, If you have Uart cable that would be useful also

 

Regards

 

Sorry but I don'T have Uart cable.

 

This is the output of

blkid

grab

 

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="1dc052af-fc5c-4690-9ce3-00ae3920916b" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="D18D-D209" TYPE="vfat"
root@k1plus:~# grab
Framebuffer failed
Grabbing Video ...
Resizing Video to 127 x -1627645944 ...
Segmentation fault

 

Can you try this:

push this module to the device

https://drive.google...pFVja5jjiIhTwqy

 

then change directory to the same path and exectue:

insmod aml_nftl_dev.ko 

and see the output of blkid if it changes

[belaid38]

hi

 

you can add patch fix audio ac3 for amiko alien 5  to wetek play 2 

 

 

They use the same sound chip AUDIO MESON8 DEVICES  AML-M8AUDIO

[moham96]

hi

 

you can add patch fix audio ac3 for amiko alien 5  to wetek play 2 

 

 

They use the same sound chip AUDIO MESON8 DEVICES  AML-M8AUDIO

linkdroid doesn't provides sources, everything they changed in the kernel or libamcodec or gstreamer plugins are provided as a binary blobs.

their latest gst-plugins update

https://github.com/o...8ffa8ec78953837

caused the plugins to be blackisted by gstreamer, probably they did something finiky in the plugins.

[thmls]

[/quote]
Can you try this:
push this module to the device
https://drive.google...pFVja5jjiIhTwqy[/quote]




on which route should I move the module?

Edited by thmls, 10 August 2018 - 18:29.

[belaid38]

 

hi

 

you can add patch fix audio ac3 for amiko alien 5  to wetek play 2 

 

 

They use the same sound chip AUDIO MESON8 DEVICES  AML-M8AUDIO

linkdroid doesn't provides sources, everything they changed in the kernel or libamcodec or gstreamer plugins are provided as a binary blobs.

their latest gst-plugins update

https://github.com/o...8ffa8ec78953837

caused the plugins to be blackisted by gstreamer, probably they did something finiky in the plugins.

 

 

i think amlogic s905  will support gstreamer 1.0 with development baylibre in mainline kernel  future

 

From here we will see a puzzle in full definitions

 

wetek play 2 is supported

 

https://github.com/s.../topic/v4l2-m2m

[moham96]

[/quote]
Can you try this:
push this module to the device
https://drive.google...pFVja5jjiIhTwqy[/quote]




on which route should I move the module?

any path will be okay, you can just move it to the home directory

/home/root/

[moham96]

 

 

hi

 

you can add patch fix audio ac3 for amiko alien 5  to wetek play 2 

 

 

They use the same sound chip AUDIO MESON8 DEVICES  AML-M8AUDIO

linkdroid doesn't provides sources, everything they changed in the kernel or libamcodec or gstreamer plugins are provided as a binary blobs.

their latest gst-plugins update

https://github.com/o...8ffa8ec78953837

caused the plugins to be blackisted by gstreamer, probably they did something finiky in the plugins.

 

 

i think amlogic s905  will support gstreamer 1.0 with development baylibre in mainline kernel  future

 

From here we will see a puzzle in full definitions

 

wetek play 2 is supported

 

https://github.com/s.../topic/v4l2-m2m

 

Baylibre work is great but it's far from being done.

The DVB part is still not worked on

see here: http://linux-meson.com/doku.php

Also switching to mainline kernel means we need a new e2procfs module, since all amlogic headers are probably gone in the mainline kernel.

[starz]

 

 

Regards

Can you give the output of

blkid

The booting issue might be related to the faulty amlogic emmc drivers, If you have Uart cable that would be useful also

 

Regards

 

Sorry but I don'T have Uart cable.

 

This is the output of

blkid

grab

 

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="1dc052af-fc5c-4690-9ce3-00ae3920916b" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="D18D-D209" TYPE="vfat"
root@k1plus:~# grab
Framebuffer failed
Grabbing Video ...
Resizing Video to 127 x -1627645944 ...
Segmentation fault

 

Can you try this:

push this module to the device

https://drive.google...pFVja5jjiIhTwqy

 

then change directory to the same path and exectue:

insmod aml_nftl_dev.ko 

and see the output of blkid if it changes

Ok,I did it.

after insmod this is the output:

root@k1plus:/lib/modules/3.14.29/kernel/drivers/amlogic/extra# insmod aml_nftl_d
ev.ko
root@k1plus:/lib/modules/3.14.29/kernel/drivers/amlogic/extra# cd
root@k1plus:~# blkid
/dev/data: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/system: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/cache: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="0b3c53d6-8ad8-4af0-a20c-599a98120cae" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="6945-F30C" TYPE="vfat"
root@k1plus:~# 

then restarted and again "no signal" on tv screen.but when I changed hdmi inputs, box booted very well and without any blank screen:)

tried a few times and results are same every time.

-restart the box,

-goes to the "no signal".

-change hdmi inputs on tv remote and it boots well,no any blank screen and waitings. thanks moham96

 

and after restart blkid output;

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="0b3c53d6-8ad8-4af0-a20c-599a98120cae" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="6945-F30C" TYPE="vfat"
root@k1plus:~# 

[starz]

Regards

Can you give the output of

blkid

The booting issue might be related to the faulty amlogic emmc drivers, If you have Uart cable that would be useful also

Regards

Sorry but I don'T have Uart cable.

This is the output of
blkid
grab

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="1dc052af-fc5c-4690-9ce3-00ae3920916b" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="D18D-D209" TYPE="vfat"
root@k1plus:~# grab
Framebuffer failed
Grabbing Video ...
Resizing Video to 127 x -1627645944 ...
Segmentation fault

Can you try this:
push this module to the device
https://drive.google...pFVja5jjiIhTwqy

then change directory to the same path and exectue:

insmod aml_nftl_dev.ko

and see the output of blkid if it changes

Ok,I did it.
after insmod this is the output:

root@k1plus:/lib/modules/3.14.29/kernel/drivers/amlogic/extra# insmod aml_nftl_d
ev.ko
root@k1plus:/lib/modules/3.14.29/kernel/drivers/amlogic/extra# cd
root@k1plus:~# blkid
/dev/data: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/system: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/cache: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="0b3c53d6-8ad8-4af0-a20c-599a98120cae" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="6945-F30C" TYPE="vfat"
root@k1plus:~# 

then restarted and again "no signal" on tv screen.but when I changed hdmi inputs, box booted very well and without any blank screen:)
tried a few times and results are same every time.
-restart the box,
-goes to the "no signal".
-change hdmi inputs on tv remote and it boots well,no any blank screen and waitings. thanks moham96

and after restart blkid output;

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="0b3c53d6-8ad8-4af0-a20c-599a98120cae" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="6945-F30C" TYPE="vfat"
root@k1plus:~# 

After some more tests and power on-off the device.it started to stay on blank screen.
Can it be a result of using malaysk's custom rom on my box? Or an updated multiboot recovery?

[engineerkhan15]

Here is another test image for K1 Pro which I compiled last night:

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

 

Tested and found 4 tuners in tuner setup as in ftp21_'s image.

Channels tuned but only on few transponders, then tuner is locked and does not find any channel further until box is rebooted.

Signal level shows on all saved channels as well as on all transponders in satfinder in "Service Searching" menu.

No video or audio on any saved channel (not even on saved radio channels).