Have you tried the + and - keys on the laptop keyboard?
This would be the most trivial thing, but not all laptops have a numeric keypad, so that's why I didn't ask. 
Posts by dtech
-
-
-
Though unfortunately I no longer have a built-in tuner.
Then there is no question, in this case I clearly recommend the LE11.
-
The working LE10 shows that I have 1528MB total RAM; I cannot use the toothpick method to boot into the device, whichever way I try doing the toothpick method, it never seems to get into the necessary state; I could try ssh while in the flashed LE on the box, with the sd card plugged in, and then reboot update or reboot recovery to see if that would make a difference.
I suspect that if by some miracle the toothpick method still succeeds, then the n200 image (without any modification) would be able to boot on your box.
I will also try reflashing without replacing dtb.img and see if that will make a difference.
It's useless to try. Unfortunately, that's exactly what I wanted to point out, because it doesn't matter whether you replace this dtb.img file or not. You can even delete it, because the 3.10 kernel doesn't use that file at all.
-
Thanks! Have changed the steps value from 10 to 90 but LE is still only working in 6db increments, the steps has absolutly no effect on the ability to fine tune the volume
Okay, that's very strange. Could you elaborate a bit on what device you are using the LE on (PC and/or box or board type) and how you are trying to adjust the volume level (remote control, game controller, keyboard +/- button, or a pysical volume button/encoder, etc.).
-
Hello, thank you for the suggestion, I just reflashed the same build ( LibreELEC-n200-AP6330_2G.arm-9.2.8.8.img.gz ) replacing the .dtb file you linked as: dtb.img and also kernel.img file; still no boot from sd card or usb.
The v3.10-based legacy kernel does not care about dtb.img, it only cares about the one integrated in the kernel.img file. So, it is unnecessary to exchange dtbs under the old kernel, because it will have no effect. In addition, the Meson8* devices cannot boot the OS from an USB drive, so it is worth trying only from an SD card.
The aml_autoscript under each version also differs, so if you do not use the toothpick method, it is not certain that it will boot. LE10 test versions are not compatible with the old 9.x. So you may have 2GB of RAM, but if you did the toothpick with the LE10, you have to do it again for the 9.x version. (And vice-versa...)
How much memory does the working LE10 show? (Due to the root squashfs filesystem unpacked into the memory, it will be less, so if there is around 1.5 GB, you actually have 2 GB RAM in your box.)
-
Thank you for pointing me towards the LE 9.2.8 release. It would be nice to have something a little more current to play with. Perhaps even LE11+.
I would also recommend the LE11, but if you want to use the built-in tuner in your WP2, it will unfortunately not work at the moment.
As a reassurance, I have the same TvHeadend (v4.2.8-36 and v4.3-6091) and Oscam version (2022-10-22) in my LE9.2 repo as in the current LE11.
Leia might be out of date, but I'm updating some packages for it: https://github.com/dtechsrv/Libre…master/packages
-
Wait dont you mean decreasing?
Oh, come on... When will there be more steps within the same interval? If you reduce the number of steps, there will definitely be a larger distance between two values.
This number simply determines how many equal units it divides the entire volume range into.
-
Settings -> System -> Audio -> Volume control steps
The default value is 20, but increasing this value allows finer tuning.
-
I am trying to go from 9.2.8 CoreELEC since they dont support -ng for S912 to LibreELEC 11.0.1 but upon burning the microSD, setting the correct DTB for the box and inserting it into the box and then do a 'reboot update' and the screen goes black after the initial splash screen for Beeliknk. I dont know if I am doing something wrong with the new ways to boot from SD or do I need to flash it back to stock firmware first then try again?
For versions based on the mainline kernel (LE10+), the dtb setting is different compared to legacy versions.
Please check if you have done the settings correctly as described in the description:
-
- booting other roms : LibreELEC-n200-AP6330_2G.arm-9.2.8.8.img.gz and LibreELEC-MXIII-Plus.arm-9.2.8.8.img.gz respectively to no avail
I have a hunch that you only have 1GB of RAM in your box, and then these images won't even start.
Please try this method:
-
command doesnt do mutch also after it trying to boot whitout sd same result not booting
Nothing is displayed because the output is sent to /dev/null. Okay, new round...
Codeecho $(cat /proc/device-tree/le-dt-id) dd if=/dev/zero of=/dev/dtb bs=256k count=1 dd if="/usr/share/bootloader/device_trees/gxl_p212_2g_nand.dtb" of=/dev/dtb bs=256kIf it has already run, please send me the output as well.
-
tryed to update the internal again and seen in the writing its updating the device tree to gxl_p212_2g.dtb can i force it that it ll use gxl_p212_2g_nand.dtb when updating from tar
It's quite interesting to me how that can happen, because the update script looks for the le-dt-id value in the dtb, and it is clearly "gxl_p212_2g_nand".
Please boot from the SD card containing the v9.2.8.8 LE image and apply the following command:
Codedd if=/dev/zero of=/dev/dtb bs=256k count=1 2> /dev/null dd if="/flash/device_trees/gxl_p212_2g_nand.dtb" of=/dev/dtb bs=256k 2> /dev/nullThen turn off the box, remove the SD card and try to boot from the internal eMMC.
-
ive a Tanix TX5 Pro S905X 2GB and its installed on internal eMMC i reinstalled again till LibreELEC-MXQ-4K-Pro_2G.arm-9.2.8.6
Okay, we are now one step closer to the fact that you are using the factory dtb of MXQ Pro 4K+, which is already named gxl_p212_2g_nand.dtb in the Generic_S905 version since 9.2.8.7.
I still recommend testing an SD card with the latest version (v9.2.8.8) and the dtb mentioned above.
-
Runing LibreELEC-MXQ-4K-Pro_2G.arm-9.2.8.6 when trying to update to LibreELEC-Generic_S905.arm-9.2.8.8.tar i get:
###Starting debugging shell for boot step: mount _storage…type exit to quit ###
*** Error in mount_storage: mount_commin: Could not mount LABEL=STORAGE ***
i updated before whit the tar files and didnt had this kind of error.You did not write exactly what kind of device you have, nor whether the LE runs from an SD card or an eMMC. If you boot from an SD card, you should try a clean installation first (with the correct dtb) on another SD card to see if it boots at all.
-
ok, thanks, but how come that my XBOX One does not support 23.976 with kodi in the same TV(lg oled b1) as my other pc and rpi3 does?
This is OS and/or driver specific, so Microsoft may be the only one who can answer your question.
-
now i have 9.0.2. Should I update as you described?
If you want to update your existing LE9.x system, do this:
Install an update package:
To install the update, you need to download, and then copy the update file (tar) to the Update folder via SMB, and then restart the device. The update process will start automatically after the restart. -
After last update an week before, I have a problem - Faled load Kernel modules during start. Video and audio are playing with very long lag, impossible to watch. Device is M8mini with s905 1gb ram
Please send a link from dmesg | paste. Unfortunately, I can't help without a log.
Also important information is which version you updated from and which dtb you are using.
