Posts by GDPR-7

    under linux the lm_sensors package handles stuff like that.

    commands are

    * sensors-detect

    (seems unavailable under LE, though) what let detect hardware monitor chips and on some distro's (?) create a initial config file under /etc

    * sensor

    displays the values

    the LE addon "System-tools" has the lm_sensors packages

    I guess under linux all (?) tools regarding sensor stuff depend on lm_sensors ...

    ===

    - a bios update available for your box ?

    I've seen boxes with outdated bios what left the fan on top speed

    - or some settings in bios to influence power control . e.g. CPU, what subseq. changes the fan speeds ?

    inspired by a thread in this forum and the wiki article "4K/HDR" I try to find the optimal setting for my monitor.

    first of all I realized a sort of mismatch between what the monitor spec's suggest and what LE finds (kodi.log)

    kodi.log (shortend for the relvant SAT-TV resolutions I see here)

    resolution 1920x1080 with 1920x1080 or 1920x1080i @ 60.000000 Hz / 59.940063 Hz / 50.000000 Hz

    resolution 1280x720 with 1280x720 @ 60.000000 Hz / 59.940063 Hz / 50.000000 Hz

    resolution 720x576 with 720x576 @ 50.000000 Hz

    attached is the suggested resolution for my monitor.

    Questions

    I wonder why there are some differences regarding resolution, frequencies, esp. 1280x720 and also 720x576 aren't in the attached monitor suggestion. - well I know *who* is forced to write the user manuals in company's ...  :rolleyes: -

    maybe I take "Empfohlene Auflösung" to serious, shouldn't I ?

    1. is it wise to have 1280x720 and 720x576 in my whitelist, even they aren't in the monitor spec's, but LE reported them as valid ?

    2. would it harm the monitor ?

    special question:

    3. how can LE report the above resolutions even when the monitor is powered OFF, cable is connected though ?

    ===

    my currently LE setting is (mostly following the wiki article):

    * Player:

    - adjust display refresh rate: on start/stop

    * System:

    - Resolution: 1920x1080p

    - Refresh Rate: 60:00

    - Set GUI resolution limit: 1080

    - whitelist: 1920x1080

    - Allow 3:2 pulldown refresh rates: ON

    - Allow double refresh rates: ON

    for the last three I'm unsure what to do here

    4. so what to do , esp. according the wiki article -IIRC- to prevent putting some "higher load on the CPU" ?

    5. what combination of whitelist and the both "Allow" are the correct one ?

    Hints:

    Monitor is an Philips 247E3LHSU

    in germany

    HD-TV is 1280x720 50 FPS,

    ServusTV is 1920x1088i 50 FPS

    Vox, n-tv is 720x576i 50 FPS

    it would be nice to handle them correct without running my monitor out of the spec's

    ... and please read the first page of this thread:

    GDPR-7
    July 19, 2022 at 6:50 PM

    esp.: => requirements

    and of course get the last script before

    thinking about to enhance my get_nightly script for other platform then Generic*, RPi* I came across that it isn't easy to identify the running box via reading the /etc/os-release only.

    wouldn't it be better to enhance /etc/os-release with one entry what matches the subdirectory (seems to be the machine model ?) on the download server ?

    example for Allwinner/tanix-tx6/

    LibreELEC-H6.arm-11.0-nightly-20220617-07254d4-tanix-tx6.img.gz (sha256)

    new entry in /etc/os-release

    let say in this case:

    MachineModel="tanix-tx6"

    or

    LIBREELEC_MachineModel="tanix-tx6"


    generell questions:

    - does it make sense to extend my script at all (is there a need to do so/ user need ) ?

    - are this boxes in general all accessable via ssh too (of course: if switched on) ?

    - I guess yes, but I don't own such a box -

    So now focusing on testing 5.19

    I've tried to run 5.19-rc7 here on my desktop (Intel i5-11400) and I was dissatisfied using the same config I was using for 5.18.x

    somethings seems broken regarding CPU freq./power saving or with my config is wrong

    reported it here:

    'Re: Linux 5.19-rc7' - MARC

    -rwxr-xr-x 1 root root 31944 Jul 16 22:50 sun50i-h6-tanix-tx6.dtb

    do all those boxes have such a *.dtb file under /flash ?

    and are all these boxes reachable via ssh too ?

    to extend my download script for other platforms (apart Generic*, RPi*) I'm searching for /etc/os-release.

    heitbaum from stable kernel testing I know/it seems you own a lot of devices (A64, H*, RK*, etc) which aren't supported by my script.

    care to provide the /etc/relases of that devices or a pointer to them ?

    ===

    btw.:

    you could leave out testing kernel 5.18.13-rc1, at least for x86_64

    it throws a lot of warnings, see:

    '[PATCH 5.18 000/231] 5.18.13-rc1 review' - MARC

    Excluding the change in the download server structure, may I ask if there are other changes between the old 0.10 and the new one?

    yes, there are changes esp. a fix for a bug I found.

    always use the newest script what is currently from 19.07.2020 !

    +++ EDIT +++

    ... from 24.07.2022 !


    ping CvH

    if you close/remove the elder thread could you remove the extension "(new version") from this thread ?

    or drop me a note I could do it ?

    as a command line user I wrote a shell script to download nightlies for updates/downgrades

    script supports the newer directory structure on the nightly download server and LE 11 nightlies.

    What is does

    - reads out /etc/os-release to get the nightly variant from your currently running LE box

    - checks the download server for last (for updates) and previous (for downgrades) nightlies

    where "updates" means: to the newest on the download server (in one step ! I don't know if that always work out)

    where "downgrades" means: one nightly down related to the currently running

    - checks need disk space (min. ~549 MB) what the update installer needs

    and only when okay it does the next 2 steps:

    - downloads the choosen nightly Image from the download server and places it under ~/.update

    - offers to reboot

    What it doesn't do

    - does (currently) NOT support boxes which are NOT Generic, Generic-legacy, RPi2, RPi4

    - does NOT support switching between Generic and Generic-legacy nightlies


    Requirements

    - always run the lastest script version.

    - you need at least a nightly on your LE box what is also currently available on the download server (URL: please see script line 44: "SERVER"), otherwise the script aborts !

    Background: if the script can't find your running nightly on the download server it can't decide what is the update/downgrade related to your box.

    HowTo

    1. download via webbrowser from here:

    2. https://gist.github.com/eldersixpack13

    - don't be confuse: eldersixpack13 and JoeAverage are the same (idiot)"

    3. unzip the downloaded file

    4. place the get_nightly.sh on your LE box somewhere, but NOT in ~/.update or /tmp

    5. to make the script executable run on linux (only once) :

    chmod u+x get_nightly.sh

    starting the script

    - ssh into the LE box

    - move to the folder where the script is stored

    - run the script via command:

    ./get_nightly.sh

    (for inexperienced linux users: it reads "./..."; (point slash ...)

    Be aware:

    - native tested is only Generic here (Generic-legacy and RPi* with dummy files only !)

    - script might contain "plain ol' men's thinkO's" and therefore Bugs

    - NO WARRANTY by me and use at you own risk.


    comments, bug reports, etc. are welcome.

    Coding-Hints

    - shell check analyse tool reports some minor (?) problems, I'm aware of...

    - piping the script through the tool "shfmt" and compare the original with the tool "meld" shows nearly the same, apart from the semicolon I use.

    - IIRC, I've learned it that way on Unix System V 30 years ago or might mix it with C programming.

    Anyway, to me it looks saner ending command lines with ";" -

    To remove the semicolons, you might use the following command line "cat <script-name> | shfmt > <output-name>"

    Changelog

    Version 0.10

    - today (24.07.2020) adjusted the server URL at line 44

    - initial release for the new (but tentatively) download server structure

    Now that v0.10 is missing in action ...

    My plan is to release the new script soonish, maybe in some hours.

    I just need to test what I can test here: Generic-legacy and dry run tests for RPI*.

    I'll open a new thread then.

    If you're able to come up with a better solution, I could wait ...

    your date problem was discussed here:

    GDPR-7
    July 4, 2022 at 12:33 AM

    comment #6