Posts by kszaq
-
-
People here reported that it's present in some variety of "MXQ Pro" boxes.
-
Okay. K1 Pro is fully supported.
-
jachrima Have you read the first post?
-
I'm very happy to hear this. I hope that it works for S905 as well.
Thank you for the continuous coffee support.
I should really lower my caffeine intake!
-
advb I am not familiar with V3 partitioning scheme. It's quite possible that they used partition names different than system and data. You should be able to see user-accessible partitions by running blkid. The main issue would be that if they use different partition names, they are not supported by my platform_init script. Please also check cat /proc/cmdline to see if bootloader provides partition names for the system.
-
Be aware that 4.12 kernel has no support for hardware video decoding. You can see what is working/not working here: start [linux-meson]
-
Recently I have obtained SSV6051 driver source code. Here are S805 and S905 test builds with SSV6051 WiFi drivers:For S905 you need to use 8.2 device tree if you're updating from 7.0.x or 8.0.x: Index of /s905/8.2/device_trees/The build is 8.1.6 + the driver (+ some other little improvements)Calling people who requested the driver:sonofdibnah files32 Bruur wizard5458 willyfanPlease confirm if the internal WiFi is working for you.Driver is now integrated in 8.1.7 build and later.
-
Nofan Tasi I have one old box with fake RAM (claims to be 1GB, in reality 512MB) and free is also faking the result.
-
*COUGH* The Mecool device has 9082c WiFi chip... *COUGH*
-
Thank you very much. Can I ask what you changed to fix it?
Revert projects/S9*: use static buffer for Broadcom WiFi · kszaq/LibreELEC.tv@1a69b7e · GitHub
Is it a device specific issue with my Beelink Mini Mx?
It might be WiFi chip specific as all my devices using the same driver work fine.
-
Is it possible using mksquashfs rather than re compiling? Cant figure out where to find CMDLINE either
No, CMDLINE is not stored in squashfs, it is a kernel configuration option: LibreELEC.tv/linux.arm.conf at libreelec-8.2 · kszaq/LibreELEC.tv · GitHub
-
Thanks kszaq, I actually just made a new sd card install from scratch, ran it on the working box, then booted it on the faulty box, Installtointernal and presto.
The whole thing took about 9 mins. Should have just done that from the start. I did start trying to create/edit the remote.conf file... Yeah that is a long process... Worth doing if you have no other option, but I did, so I was glad to avoid that.
Thanks for the location of the remote.conf file on the working box.
FYI the /tmp/remote.conf is the place where a user-provided remote.conf is placed to be used by amremote. So no matter where you have put your configuration file, it is always placed in /tmp/remote.conf before being applied. Please note that you shouldn't copy your configuration file to /tmp folder as it is a ramdisk cleared on every reboot.
Hi kszaq,
I'm sorry I did not read the instruction for reporting logs.
Tonight I retried flashing you 8.1.6 libreelec build and I still have the same problem.
I created a zipfile with the needed logs. See the attached file.
To be clear. I have a Beelink Mini MX. (Beelink Mini MX Ver 1.0 TV Box Android 5.1 2G/16G Amlogic S905 Quad Core 2.4GHz/5.8GHz HDMI 2.0 Bluetooth 4.0 Support Gigabit LAN), bought on Geekbuying.
I allready tried to give the device a static IP (via router) but the wireless connection does not work. For some reason build 8.1.6. disables/kills the wireless connection on my Beelink Mini MX. All your previous firmware versions worked flawlessly!
Thank you for all your great work! I hope you can fix my problem
For now I have to go back to 8.1.5 to get my wireless connection to work...
Thank you for providing logs. I think the issue will be solved in 8.1.7.
-
So the limitation is common to all the Libreelec platform
I see that in Windows there are multiple, selectable, "exit mode", I think this is the approach to follow
This is not correct at all. I don't think you understand what I wrote in my earlier posts. I purposely disabled suspend in my builds. I think we need to end this discussion. Please wait for a solution.
-
But are you talking about the systemd default ACPI actions? So Kodi will actually issue an ACPI event and not just running a poweroff?
It's not ACPI but it doesn't matter in this case. Kodi issues power-related commands using systemd (in LibreELEC).
-
I SSHd in using winscp... Copied the libreelec.conf from one box working ok and tried to overwrite the libreelec.conf on the dodgy box... It is a read only file. Fml
Copy from /tmp/remote.conf (working box) to /storage/.config/remote.conf .
-
Suspend is enabled/disabled at systemd level for applications like Kodi. If I enable it, it becomes the default action for power button, CEC poweroff etc. I will not enable something that would force unaware users to power cycle their devices by unplugging power. The only solution I can accept is to make the systemd configuration file available to the user so that it can be manually enabled.
-
All changes are included in the changelog. The reasons for not including suspend have been explained many times. I have not yet developed a way to make it configurable. PRs welcome.