Posts by jim_p

The following story/issue is part of the "How technology helped me lose my mind completely" book I may write one day

So, the all black mxq connects wirelessly to the isp's router, which is one of the worst routers the isps here in Greece provide. It gets a static ip (192.168.2.2) via dhcp binding since ~1 year ago, because mom wants to check what the kids are watching and she does that via kore on her phone.
When something happens on the tvbox and needs my intervention, I connect via anydesk to the family's pc and then via ssh (the built in command of powershell) to the tvbox. Annoying procedure I know.

One of the things I wanted to change for 2024 was to ssh straight to the tvbox, without all the above. So, I created a new (and the ONLY) port forward on the router which forwared a random public port (over 20000) to the tvboxs port 22. Without even trying to see if whole thing works remotely, I tried to connect locally with the forementioned procedure. Not only poweshell popped this error and the tvbox did not allow me to connect

kex_exchange_identification: write: Connection reset

but in order to fix it I had to remove the port forward completely!

As for the gamepad... it still does not work despite the udev rule

Let me explain what I meant on the other thread, just to let you know that your build does not have an issue.

As I have mentioned in the past, I have an s905 tvbox which only works with chewitt's le 12 build, on which it boots from an sd card. Before that, and before your builds for s905, I had ce 9.2.6 on its emmc and a fully configured kodi in it, e.g. with youtube and twitch, access to my dlna server for media, iptv with a list I maintain, weather info, and even a couple of games.

After that, let's say that "curiosity killed the cat", because with le 11 returning to amlogic and most addons becoming python3 only, I decided to install it at all costs. You know the rest of the story, I have mentioned it here before.
The thing I first installed on it was the iptv part, which I use as a backup when my aerial reception has issues, and frankly it is the only thing I don't want to break right now. I have been through a lot since late October/early November and I have lost any motivation to do more than what is absolutely necessary for stuff to work. E.g. my dlna server died in early September, I was planning to replace it by December, but I won't replace it at all.
For that reason, installing your build on the s905 tvbox (or even at an s912 tvstick that I found a couple of months ago), is just a "wish" I will probably never fulfil.

That's all I had to say. Thank you for listening. Have a nice day

I thought so
Stupid manufacturers!

Thanks a lot! I will create a file and test it tomorrow. I assume that my gamepad's name is "USB Gamepad" without the extra spaces of dmesg, right?

Any idea on how to make this gamepad work on the all black mxq? It works fine on the pc (tested only on windows' built in app for checking the controllers) and it does show up inside kodi as you can see on the image below, but nothing happens when pressing the arrows/keys/joysticks. I have tried connecting it on all 4 usbs and changing its driver from linux to udev.

I have also tried an older, and better, gamepad from spartangear, which worked first try.

[  305.188133@0] Indeed it is in host mode hprt0 = 00041901
[  305.390771@0] usb 2-1: New USB device found, idVendor=0810, idProduct=0001
[  305.390787@0] usb 2-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[  305.390794@0] usb 2-1: Product:  USB Gamepad
[  305.421210@0] input:  USB Gamepad           as /devices/lm0/usb2/2-1/2-1:1.0/input/input2
[  305.433236@0] pantherlord 0003:0810:0001.0001: input,hidraw0: USB HID v1.10 Joystick [ USB Gamepad          ] on usb-lm0-1/input0
[  305.433304@0] pantherlord 0003:0810:0001.0001: Force feedback for PantherLord/GreenAsia devices by Anssi Hannula <[email protected]>

We have reached 6.7, which is now stable and is there since the previous build (the one before Jan 9th), yet the wifi issue remains

https://paste.libreelec.tv/flexible-ghoul.log

Honest question. Can I install this on a usb stick and free my sd card for something more important like openwrt? Will it still boot from the stick now that its boot method has changed and it no longer looks inside its emmc for an os?
Ideally, I would rather install dtech's 9.2.x build on its emmc, since there is no real benefit of using the latest version of kodi or le just for iptv.

Quote from chewitt

The images in my test share exist solely to support me testing things with random users. I deliberately use a fixed version and rarely clean build and almost never document the changes inside. I have no plans to change that, so use them at your own peril

If you want something that more directly tracks the upstream LE repo and with known content, it's time to learn how to build your own images. It's not rocket science: https://wiki.libreelec.tv/development/build-basics

It may not be rocket science for you, because you know how everything works. Sadly, and leaving my old hw aside, it is for me. I won't say again why I use your images and not the ones from the repo. And no, wifi is not the only reason, wired connection does not work as well with the stock image.

On the other hand, if the image creation is something that can be scripted, I would offer you some help on a 58000x system (+64gb of ram +m2 ssd). I damaged it ~2 months ago (psu failed) and I do not have the money and the time to fix it

Quote from chewitt

I'm attempting to guess/fix the GXLX audio problem in the posts above. Nothing that needs you to update all the time.

Ok. The problem is that the new releases do not have a build number on their names (unlike the regular nightlies) nor it can be found in any other way other than updating. I do not mind downloading the image, so if there is a way to learn the build number before updating to it, please tell me.

Hello and happy new year!

Is there any significant difference between the s905 images of the last couple of days? Yesterday, I updated to the one from Jan 1st. A fresh image showed up later on the day, so I updated to that one too (jan 2nd). And today (Jan 3rd) a third image showed up and I updated to that one too. But the build number, under /etc/os-release, remained the same.

Quote from chewitt

And people wonder why we loathe Realtek vendor drivers so much

I agree on that. However, I have to point out 2 things

- 90%+ of the usb adapters out there are using realtek chips. When they do not work on linux, it is a pita to make them work. But on windows, they are almost plug n play, and even on old windows like w7.
- When I first tried the original s905 image for le 11, I also tried my precious wn722n v1 that has an atheros chipset. It did not work back then, although its atheros driver is included in the kernel for 10+ years now. I keep it in my drawer for such occasions that I desperately need a linux compatible wifi adapter.

Moving on to more important and ontopic stuff. Yesterday I noticed the fresh image from Dec 24th, so I wanted to upgrade to it. This time, it did not connect even via ethernet! I gave up after a couple of tries and tried it again today. It connected with no issues via ethernet, so I did the update. After the update, wifi connected like it used to, so I assume that the issue with the previous image was fixed. The same messages appear on dmesg though.

One thing that does not work, and I do not know if it is because of le 12 or something else is its remote control. It was the first time I connected it to a tv that is not hdmi cec capable, so I could not use the tv's remote to control the tvbox. I can not recall if it was working with le 11, but it was definitely working with ce 9.

I know that the driver is only at your image, that is why I use it.

Today's update to "b5823b71dbb8163bf73b03a9873674e292be23df" broke wifi a bit more. It simply does connect or at least not get an ip at launch. I connect to it via ethernet, remove the relevant folder under ~/.cache/connman and then, though connman (instructions at the arch wiki) I connect to it again. The problem is when it is supposed to ask for a password, it simply does not. However it does connect, but it stays like so until the reboot.

Thanks. Are there any changelogs for it? The nightlies' log at test.libreelec.tv says it is still on 6.6.y.

First post in this thread, so excuse any mistakes. I have the annoying mxq pro 4k box with s905 and use/update it with chewitt's image from the testing page. I try not to miss any upgrades, so all I can remember is that I went from the one from Dec 11th to the one from Dec 13th and to the one from Dec 19th (yesterday).

Before making today's upgrade, I noticed that it was too slow to connect to the wifi and some errors in dmesg. After making it, the issue remains, so here is what dmesg outputs.

https://paste.libreelec.tv/assuring-possum.log

I have no big plans for it anymore, I just want to use it as an iptv device for the rainy days that the tv signal is bad.

Since the conversation is now focusing on my hw and not on dtech's images, can we please continue at my thread here? I do not know how to quote between threads, so if you do know, please do it and I will reply there. Thank you in advance.

Thread

Installing on old S905 TV box

How can I boot a s905 tvbox that already runs coreelec 9.2.x from its internal storage? I downloaded the image of le 11 b1, flashed it on the sd card, edited the uEnv.ini file, but all I get is a blue-tinted image of the amlogic boot picture, then complete darkness, followed by a non-tinted image, followed by the regular boot to coreelec. All that happens in like 5 seconds.

Normally, the amlogic boot picture is not tinted, shows up only once and right after that it boots to coreelec.

Its device…

jim_p

February 3, 2023 at 1:18 PM

Here is the short story of how I got it with le 11, i.e. omitting the failed parts and the obvious ones like "I copied the dtb file".

Prepare sd card with ce 9.2.x because your images did not support s905 at that time > boot to android (4.4 I think) > sideload terminal app > launch terminal app > su to get root > reboot update > insert sd > boot to ce from the sd > ssh to it > installtointernal > android gone > (fast forward to 2023) > prepare sd with le 11 > ssh to ce > reboot update > insert sd > boot to le 11 on the sd > bootloader altered so as to boot only from the sd > lose any access to internal mmc since then

Tldr version: there is nothing related to android in it since 2021 and the only workaround to boot from the sd without the reset button was to run reboot update in a terminal.

Statements like this make me regret trying le 11 even more

There are 3 holes under the reset button. 2 of them connect to each other via that copper "line", so I soldered the button between the remaining one and one of those 2. I don't know anything else. And the reset button was supposed to solve all that compatibility mess.

How can I install your s905 image on an mxq pro 4k that already has the latest development version of le 12 and boots ONLY from its sd slot and with a specific sd card?

Preface: ~9 months ago I installed le 11 on an sd card, completely unaware that after that the tvbox will boot ONLY from it and never from its internal storage. If you want more info, there is a thread I started for that.

And since chewitt no longer creates images for le 11, I updated it to the development ones of le 12, which are available from the same testing folder of his.

Last but not least, the tvbox now has a reset button, but it does not seem to do much.

So, I downloaded the s905 image for it, flashed it to a 16gb sd card with rufus, deleted dtb.img and replaced it with the proper one from the device trees folder (there is actually a file named mxq_pro_4k), inserted the sd card, pressed the reset button, powered it on and... nothing showed up except the amlogic logo with the tiger. What else can I do?

Thank you

May I now ask were is the mesa-demos package?