GDPR-2, I did clean installation of 8.90.4 , after this updated to new devel + new dtb. With crazycat scannng muxes does not work on tvh with hauppauge driver everything is ok
so with Hauppauge everything works as expected?
Did it work with crazycat before?
It's very hard for both myself and afl1 to fully work this out as we don't have access to the hardware however I appreciate you taking the time to test the changes. New codesnake changes are causing a headache.
make sure you DO NOT have crazycat installed when updating from 8.90.3 otherwise it will cause a conflict
Ok great. good to know.
The download link in the OP is from 27 OCT 2017. which is 4 months old. Where does one find the most recent build then going by what you're saying there should be atleast 4-8 updates since then?
I don't know where you are seeing 27th October? but the last release was on 2018-02-13 and there has been that many releases if not more since that October date.
Maybe you do not pass this time my posting
Did the update from 8.90.4 (installed on sdcard) to this devel build and... everything runs stable on my side and works the same way it did with 8.90.4. Could be a placebo but ui feels snappier.
This image is the first with that kernel.
The LE kernel uses a newer nougat source than the kszaq 8.2 one so I would not be surprised if this is true.
This is probably a stupid question so apologies in advance. I have a KI Pro and its website says it has "eMMC" does that mean it doesn't have NAND and will work with the new build installed to internal?
Try it and see
Devices with OS installed to internal will not be officially supported as this feature will not make it into official LE, it's a community feature done at your own risk.
DTBs need to be refreshed again which I will do later on today, the Tanix dtb was renamed recently, that's why yours didn't update. All other boxes should update fine from 8.90.4 (I hope).
hillz 8.2 has reached the end of it's life, all developers have moved on to focusing on 9.0, the differences between 8.2 and 9.0 have grown a considerable amount now that it would be impractical and very time consuming to backport changes.
belaid38 zbigzbig20 new devel version for you to try here.
Some important notes before flashing for you guys and some others.
The kernel in this dev image has been changed from kszaq/8.2 to official LE/9.0 pre-alpha, this is a big change and something I have held off from changing to for a couple of reasons which are listed below.
If you have LE installed to internal this image will not boot as the partition layout in the DTB is different. You can still install to internal but you will have to boot from SD and then re-run the scripts and if you go back to another image then you will have to do the same again.
Devices with NAND will not be able to run LE from internal memory due to the LE kernel having no NAND driver.
There may be frame drops/skips with certain content however I can't say with 100% certainty that this will be the case because it has been some time since I last tested it.
DTB will require updating or your box will not boot however this should be done automatically as part of the upgrade process.
If flashing this image, I very HIGHLY recommend making a back up.
If your device boots following the upgrade then I expect this to run just as well as any other release, I make these notes just so you are forewarned. DO NOT complain, if your box goes bang!!
Is a new version alpha or stable version in the works?
Or are there nightlies of this project or something?
No version should be considered stable.
I have refrained from nightlies as there is not enough changes in LE on a daily basis to make this worthwhile.
The current schedule is a new build every 2-4 weeks.
Noise reduction:
Codeecho 0 > /sys/module/di/parameters/nr2_enCPU:
Codeecho performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo performance > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governorThe speed of the GPU only affects the speed of the interface, but it is not however very important. Neither the overclocking of the CPU nor the overclocking of the GPU will not help either for the interface (most likely not if it already slows down), nor for the video.
Those latter commands do not overclock the cpu or gpu.
Display MoreHello everybody)
Pls. tell me why different NEC remotes uses a different lenght of codes in it's rc_keymaps files: 3 or 4?..
Maybe, there is a secret?)
I cannot up my remote with S905X box.
When i tryed to catch codes from my IR-remote (using procedure from 1st post), i've get codes like this:
CodeLibreELEC:~ # ir-keytable -c -p nec -t Old keytable cleared Protocols changed to nec Testing events. Please, press CTRL-C to abort. 341.971777: event type EV_MSC(0x04): scancode = 0xcc1d07 341.971777: event type EV_SYN(0x00). 343.989304: event type EV_MSC(0x04): scancode = 0xcc1d44 343.989304: event type EV_SYN(0x00). 351.999391: event type EV_MSC(0x04): scancode = 0xcc1d12 351.999391: event type EV_SYN(0x00). 353.025236: event type EV_MSC(0x04): scancode = 0xcc1d10 353.025236: event type EV_SYN(0x00).But, when i tryed then to insert those codes into files taken from other similar boxes (i'm use as tamplate m8s from this topic), trying to replace original codes with mine, nothing works. No any reaction on keypressing.
indeed, i'm carefully follow instructions from 1st post, stsrting\stoping services and using command "ir-keytable.....". noway
What's wrong?
Thank you for any ideas.
Hard to see what your problem is... everything looks normal, the box is picking up the remote codes so it is a configuration issue your end.
Every remote gives different scan codes, the length of the codes are also irrelevant as long as you copy them correctly.
I have a Sidiwen X11 box (S905X, 2GB RAM, 16GB ROM).The device tree gxl_p212_2g.dtb fails to show the internal memory of the box (apparently NAND) and if I replace it on the SD card with the gxl_p212_2g_nand.dtb (renaming, of course), the box does not boot. Which device tree should I try in addition to these two, or is it just that there is not a suitable one for the box?
One other strange thing: if I SSH to the box, the command xrandr is not recognized. Is this also due to the device tree?
Just use the dtb that works, not all NAND devices are supported, you will have to run LE off sdcard or usb flash drive.
belaid38 zbigzbig20 I have had chance to look at the problem with the wetek devices, the new module codesnake has built is incompatible with the kernel I am using in these releases by kszaq
I have messaged codesnake asking if he can fix it along with the error and a possible solution, for now you will have to wait a little longer I'm afraid.
Display MoreDear all,
I've just installed 8.90.4 on clear SD for gxl_p212_1g device. All perifery working fine, but there is issue with addons.
Some of it, ven installed form LibreELEC repositiry, cannot find dependency os.lireelec.tv - Unavalible.
When i open "Defendencies" list and click to this item, nothing happens.
For a simple, "System Tools" 9.0.1.107 by Team LibreELEC.
What a reason, how to fix?
Thank you for any help.
Just ignore and press OK, install will proceed as normal. This is a kodi bug as the dependency is there.
Hi,
I have a X92 and running LE from SD card. Most functions works well, but wondering if someone can help with a HDMI/output issue.
When I turn on the box after power is pulled, it will start up nicely, and the TV input will sense the signal (HDMI) from the box and show the LE interaface. But when i power the box down, and then power it back up, the box goes on, but the TV is not sensing the HDMI output as the TV is blank looking for input. I know the box is on, as i can hit remote and hear the movement. Only way to get signal back is to pull the power, or pull the HDMI cable and put it back in.
I have a S905 box with same Krypton 17.6 version, and that does sense each time it powers back on (and goes to that input).
Any ideas? Thank you.
You misunderstand how HDMI works, your TV does not sense HDMI output, it listens for the CEC wake up command, it is the box that doesn't send this after waking from standby.
I think the issue is with the bootloader because it works fine on LePotato, put it down to one of the pitfalls of buying a cheap chinese device.
hi GDPR-2 i tested this
wifi not work after rebout and wetekdvb not work after enable crazycat dvb
see me rabort
I didn't build this using my usual machine so that may have caused an issue, I will look into it more tonight.
In case someone else has this problem, here is the solution: Some keyboards are being detected as joystick in linux.
My keyboard A4Tech G800V is one of them.
As GDPR-2 said (then removed?) in his post, I had to make a udev rule to prevent my keyboard being detected as a joystick.1. Downloaded 51-these-are-not-joysticks.rules file from GitHub - denilsonsa/udev-joystick-blacklist: Fix for keyboard/mouse/tablet being detected as joystick in Linux
2. Copy to /etc/udev/rules.d/51-these-are-not-joysticks.rules
3. Reboot
keywords: A4 Tech G800V Multimedia Gaming Keyboard is not working in Linux
I wasn't sure if it would work that's why I removed my comment but I'm glad it did.
afl1 , there will be maybe devel build available with it and latest changes or new build will be released soon?
Please try this and report back LibreELEC-S905.arm-9.0-devel-20180224131444-r28220-ga32a2d5ce.tar
