Posts by ochentay4

Quote from ilmich

Hi ochentay4,

please retry with this test build

https://ilmich.libreelec.tv/test/

cheers

Michele

Exact same issue with same message.

Hey guys! I just wanted to try latest version, as the latest I used "LibreELEC-RK322x.arm-9.2-devel-20200427220805-b7186bc-rk3229-v884k" boots fine but its old as hell, unstable and lots of bugs, and when I try to boot with "LibreELEC-RK322x.arm-10.0-nightly-20230206-b1e877a-rk322x" I get the following error:

I read something about a mutitool to flash the img to the device but cant find it, can anyone tell me why I cant boot and how to resolve this?

Thanks!

EDIT: found the multitool, it doesnt seem to boot at all because get a blackscreen. Yet I still get to boot fine with "LibreELEC-RK322x.arm-9.2-devel-20200427220805-b7186bc-rk3229-v884k.img" without issue.

I use balena etcher for all my Android boxes and Win MiniPCs without any issue.

Tried all these with the same error:

LibreELEC-RK322x.arm-10.0-nightly-20220707-e38bfe3-rk322x.img

LibreELEC-RK322x.arm-10.0-nightly-20221122-32b2e05-rk322x.img

LibreELEC-RK322x.arm-10.0-nightly-20230206-b1e877a-rk322x.img

Quote from Caassapaba

I have compiled a v88 4k image of ilmich 's latest release, and the libreelec addons repository absolutely refuses to connect, I've done every ntp and network troubleshooting that I could find, but no dice, does anyone have any idea on why is this happening?

if you want me to test the image, im here.

Quote from dtech

ochentay4

Code

[    1.813044@0] ethernet base addr is fe0c0000
[    1.847191@0] stmmac - user ID: 0x10, Synopsys ID: 0x33
[    1.852354@0]  Normal descriptors
[    1.855655@0]  Ring mode enabled
[    1.858857@0]  No HW DMA feature register supported
[    1.863541@0]  Wake-Up On Lan supported
[    1.887259@0] libphy: stmmac: probed
[    1.887291@0] eth%d: PHY ID 02430c54 at 0 IRQ POLL (stmmac-0:00) active
[   44.808738@1] eth0: device MAC address 00:01:23:cd:ee:af

This is seemingly good, which unfortunately does not mean good. (Well, that sounds like a pretty paradox.)

I have to ask if the device had the factory Android ROM on it, or is it possible that you crossflashed with the ROM of a similar device, such as the original (non-Tronsmart) MXIII or the ROM of another MXIII clone.

Unfortunately, this is an important question because I can't find any errors based on the kernel log, but this symptom you report usually occurs when it doesn't have the factory uboot bootloader on the device.

Another thing: based on the log, it seems that either the SD card or the slot is problematic because there are a lot of I/O errors:

Code

[    4.791202@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.791224@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.791235@2] Buffer I/O error on device mmcblk0, logical block 485887
[    4.792048@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.792065@2] mmc_blk_reset 939 reset error md->reset_done:1 and type:1
[    4.792074@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.792083@2] Buffer I/O error on device mmcblk0, logical block 485887
[    4.898018@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.898043@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.898056@2] Buffer I/O error on device mmcblk0p2, logical block 353791
[    4.898883@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.898900@2] mmc_blk_reset 939 reset error md->reset_done:1 and type:1
[    4.898910@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.898920@2] Buffer I/O error on device mmcblk0p2, logical block 353791
[    5.389003@0] mmcblk0: r/w command failed, status = 0x80000b00
[    5.389027@0] end_request: I/O error, dev mmcblk0, sector 3887096
[    5.389039@0] Buffer I/O error on device mmcblk0, logical block 485887
[    5.389856@0] mmcblk0: r/w command failed, status = 0x80000b00
[    5.389873@0] mmc_blk_reset 939 reset error md->reset_done:1 and type:1
[    5.389883@0] end_request: I/O error, dev mmcblk0, sector 3887096
[    5.389892@0] Buffer I/O error on device mmcblk0, logical block 485887
...

Display More

If the system is already running from internal memory, it is irrelevant, but this log is apparently still made from the SD card.

Display More

Regarding ROM, yes, I flashed, crossflashed, reflashed the device MANY times looking for a usable ROM, be a modded ROM, a ROM from other device (newer), Lakka, LibreElec, etc. Didnt know this could damage in any way ethernet.

Regarding SD card, it was just a reflashed 2GB crappy SD card, as internal installation of LibreElec got me wifi broken and couldnt access the device anymore, so decided to start fresh.

Will do the following if ok, will reflash original Tronsmart ROM, and use a new 32GB SD Card so I can send you dmesg again. Is this good?

Quote from dtech

H1601NL -> It's just a transformer, your Ethernet chip is actually an IC+ IP101GR.

It is located under the quartz behind your lower USB port.

I need a dmesg.

Here it is. Tronsmart MXIII / S802 / 2G RAM / 8GB ROM / AP 6330

Quote from dtech

No, I would like to thank you and wish you enjoyable and trouble-free use.

Experience shows that the n200 image is also perfect for k200 devices. Do you know what kind of wifi chip is in your box?

Ok, image seems to work nicely on Netxeon M82_V4.0_20141106 device (Tronsmart MXIII 2G/8GB Wifi 6330). Wifi worked correctly, funny enough, ethernet did not, cant get ip from DHCP (triple checked connections). Ethernet chip is H1601NL (1502-XG). Any fix you can think of?

I also managed to installtointernal, I like it. If I could get ethernet working Im golden.

Quote from dtech

No, I would like to thank you and wish you enjoyable and trouble-free use.

Experience shows that the n200 image is also perfect for k200 devices. Do you know what kind of wifi chip is in your box?

It probably has AP6330 WiFi. Will try the image and let you know so you can add to 1st post. Thanks!
EDIT: Indeed it has AP6330.

Quote from dtech

LibreELEC v9.2.8.2 (2021-09-12) has been released for S8X2 devices only.

---

Changes since v9.2.8.1 (2021-08-14):

• restore whitelist patch to fix cadence-correct playback problems (eg. 23.976 and 29.97 fps),
• disable all Realtek SDIO and USB wifi/bluetooth adapter drivers in kernel configuration,
• M8S-Plus: enable some external Realtek USB wifi adapter drivers.
• 3rdParty images: enable some updated external Realtek SDIO and USB wifi/bluetooth adapter drivers in options,
• 3rdParty images: merge MXIII-S8X2 devices to main S8X2 project,
• Minix-S8X2 images: sync boot scripts and kernel with datrh's repo (based on 9.0.2 with custom Kodi version),
• 3rdParty images: platform_init script replaced to prevent freeze problems after stop or seek.
• 3rdParty images: zram service is disabled on devices that have more than 1 GB of RAM.

---

Images can only be published after testing and positive confirmation!

So far, this has happened to these devices:

• OTT M8S+ (tested by me),
• Universal n200 devices (tested by loki7777 on an MXIII-G clone, gjstroom and Jerry on M8S clones).

Not-affected S8X2 devices: WeTek Core.

Affected but not yet confirmed (waiting for feedback):

• Minix X8/X8-H,
• Minix X8-H Plus,
• MXIII-1G,
• MXIII-G/-Plus.

If you would like to help with testing, please indicate what device you have and what you experienced during the test.

Only these images can be used for testing: Index of /snapshots/20210912/

(The image of the Minix devices has been updated since then, but for ease, I also put it in this directory.)

After positive confirmation, the images will be transferred to their own download directory.

---

IMPORTANT!

If you installed it as an update and you have a problem installing addons, you will need to manually update the LE repository addon:

repository.libreelec.tv-9.2.1.zip

Display More

Hi, love this project. Is Tronsmart MXIII 2GB/8GB (K200) going to be supported anytime soon?

Quote from ilmich

I'm trying to do a Libreelec 10 build with the legacy kernel and @knaersche patches.

Now I understand why the developers chose to switch to mainline code and remove proprietary software support :).

It took me a while to get kodi up and running (mali blobs works only with some glibc and kernel builds only with gcc 8).

But at this moment, it's the only way to get my box working 100%, so I decided to give it a try and eventually share my results :).

Hi! Im a little confused, I've been using this and it worked somewhat fine: LibreELEC-RK322x.arm-9.2-devel-20200427220805-b7186bc-rk3229-v884k
Was going to download on of yours that were updated but cant find them or dont know which is compatible. Any help?

Quote from Demetris

Some more exciting news coming up for this old champ:

I have ported Batocera Linux RetroGaming Firmware on this soc thanks to Martin Blumenstingl excellent work!

You can try and test it here

batocera-s812-30-20210214.img.gz | by Demetris. for MXQ TV Box

It should be able to boot straight on a MXIII-G/PLUS S812 board for the others you now the drill of renaming the dtb.

Is S802 a feasible release for the future? (MXIII 2GB/8GB)

Quote from jock2

ochentay4 Thanks for the image, I checked the device tree fabiobassa extracted and the dram timings are the very same as those for the v88 4k board. You may try that one to get much better performance.

I also checked out the configuration of the wifi and it appears to be the same as the other device with the esp8089 chip, so this is a step forward to add support to libreelec.

I hope knaerzche comes here around soon to merge the necessary patches, which should be quite easy.

Great! looking forward to a new build with this changes integrated (and kodi updated!). I have even played remuxed blu ray isos over network with almost no caching/stuttering. Hope something comes out soon! Thank you!

Quote from jock2

You may also share the original firmware image if you have one. Sharing just the first 20 megabytes of the firmware would be much better. Don't forget to make a zip/rar/gzip of it.

Remote should already work, you probably need to configure the key bindings: there are some useful posts about configuring rk3228 remotes in the rockchip forum section, but you can also use the procedure for amlogic or any other device.

About the esp8089 wifi, I added support for that in armbian and it works, but I had no chance to test it personally and it is based upon one user experience, so the device tree could be terribly useful for this also.

I dont know how to resize the image. Here is a working link of the original IMG: MXQ-4K_ota_20160308.zip

I would love to try a build with esp8089 wifi enabled. Let me know how can I help. I know that MANY has this same box so this could be useful.

Quote from knaerzche

The easiest way is probaly with adb: so connect your device via usb or network to your working machine and do:

Code

adb pull /sys/firmware/devicetree/. backup

this should copy all the files an directories in there to your PC.

after that you can decompile to a readable devicetree with:

Code

dtc -I fs -O dts backup/base

Note: I wrote this from my memories ... might be that syntax is slightly different.

unfortunately: yes.

jock2 did some experiemts with undervolting ... not sure how far he came

Maybe yes - honestly in my little spare time I'm trying to port more and more needed stuff to mainline kernel which I'm far more interessted in ... but I can do some builds ... in the meantime everbody else can build his on images which is really, really easy: You need just a linux computer (preferably with ubuntu 18.04 for LE 9.2), follow instrucations on Compile [LibreELEC.wiki], clone my repo and execute any command from LibreELEC.tv/README.md at libreelec-9.2 · knaerzche/LibreELEC.tv · GitHub which suits your device.

Display More

Thanks. Sadly I cant/wont do it myself as I dont know anything about linux and dont have another pc to try it. Will wait till someone builds it.
About my device, what do I have to do so I can have wifi and correct device settings like ram timings so you can put it on the project? Right now, thanks to your project, device has a purpose, but I find it incomplete without the remote, wifi, and probably wrong ram speeds.

Quote from knaerzche

sirmagus your device probably needs a different dram-configuration ... as a save start you could also try the tx2 image where the default settings are in. if it doesn't work either: Try to extract current device tree from android or link to a working android firmware image.

Any instructions how to extract device tree from Android? I'm struggling with this and Im trying to colaborate a little on this project.

Hey guys, I have an OTT MXQ 4K (not Pro) device with these specs (real and verified by me with my camera):

• RK3229 CBBKM43012 1552 CPU
• SanDisk P553072141 SDTNRGAMA-008G CP0813618 NAND
• NANYA NT5CC256M16DP-DI RAM (DDR3)
• Pulse H1102NL 1549-M ETH
• Espressif ESP8089 05215 P27X03 WiFi
• Board name T066-V1
• Firmware MXQ-4K_ota_20160308

-Do I have to get *any* file from Android to get remote working?

-Is a new release on the horizon? Latest is from April 2020 and I saw many commits on github, including Kodi 18.8.

-What could be the correct image to test? Thanks!

Fantastic project by the way!!!

EDIT1: Ok, I tested "LibreELEC-RK322x.arm-9.2-devel-20200427221002-b7186bc-rk3229-v88mars.img.gz" It worked, booted fine, had ethernet but no WIFI, 1080p was somewhat good. Now which one to test? This box is DDR3 and the firmware I tried DDR2.

EDIT2: I tried to play a movie 1080p remux bluray (30gb) from smb network (wired at 100mbps) and I encountered stutters and constant buffering. Main PC is a monster and work fine on Rpi3. Any ideas?

EDIT3: Tested "LibreELEC-RK322x.arm-9.2-devel-20200427220805-b7186bc-rk3229-v884k.img.gz" now no stuttering or buffering at 1080p, speed is fast! Even tried a 4K HEVC Remux file (60GB!!) and it worked somewhat fine, incredible!! But when I fast forwarded the video box resetted itself. Also still no WIFI. Im starting to think that Espressif ESP8089 is not supported at all on any release. Is there something I can do to help to get it working?

EDIT4: Temp is 208ºF (98ºC) when playing videos, is that reading correct? Holy crap!

Quote from zixelmike

I resoled problem by:

systemctl stop kodi

pactl load-module module-udev-detect

systemctl start kodi

Sound working perfect, but i see "pulseaudio default bluetooth" as default sound

BUT

sount via alsa in other apps not working.....need reboot =(

How can i combine this drivers& =(

Display More

Hey, I have a tablet with the same problem, I dont understand how did you fix it. Also, I have the same problem with Lakka (latest nightlies are LE based), so I dont have sound.

Quote from Demetris

Update: Since no reported bugs for some time now am moving the release on OP

Quote from Demetris

Hello and goodbye as this release should be my final one since these amlogic boxes cant be supported anymore due to lack of upstream support.

Here is LE9 with Kodi Leia 18.6 for S82 and MXIII-PLUS

StackPath

Enjoy

Hey! Thanks for the release! Will test it later! Was looking for an updated release! Thank you!!

Quote from Demetris

OP is updated with LE9.0.2 download links

Enjoy.

Thank you! Will try it later on my Tronsmart MXIII device.