Posts by GDPR-7

Quote from aff14

I was wondering if there is a way to update or reflash the BIOS from within LibreELEC itself?

not direct, but you don't need to install Windows to flash the Bios !

just get the WY0054.bio on an USB Stick

BIOS Update [WYLPT10H]

Options for updating the BIOS of Intel® NUC Kit D54250WY and D34010WY, and Intel® NUC Board D54250WYB and D34010WYB.

www.intel.com

and boot with F7-Key

- if you managed to get the box reacting on any Keys during boot, see comment #2 -

BIOS Update and Recovery Instructions for Intel® NUC with Visual BIOS

Instructions for the BIOS update options available for Intel® NUC products.

www.intel.com

click on "F7 Update"

Quote from CvH

... so this is fixed after the change is done in a ~week or so

thanks for doing it in 2 days.

currently tvheadend 102 is scanning...

and GBM is now also in nightly... neat !

Quote from bg.lebowski

no, this one is valid ... at that time the sync folder didn't exists and the process would create the directory in the next step ...

but failing because of access conditions ...

okay, so both error messages have one cause I guess

Quote from bg.lebowski

LE 10.0 ...

2021/09/22 09:38:32 [1019] rsyncd version 8.95.002-6436-g4b15caf9

shouldn't that read ... rsyncd version 3.2.3 ?

and is this another bug/misconfiguration:

rsync: link_stat "/Synology3_1" (in Synology3_Backup) failed: No such file or directory (2)

Quote from JoeAverage

I couldn't find out what the differences between the rsync version exactly were.

+++ correction +++

I couldn't temporary find...

network-tools version number's and the containing rsync version

LibreELEC.tv/changelog.txt at fc7984acc19d36613e4e1a2065537bcc45897261 · LibreELEC/LibreELEC.tv · GitHub

=> all network-tool version > 104 contain rsync version 3.2.3

=> all network-tool version < 104 contain rsync version 3.1.3

change logs (=>News), man pages, etc for the specific rsync version are here:

rsync

Quote from bg.lebowski

Hmm ... I just imagine that I did a test upgrading from LE 9.2.6 to LE 9.95 but before disabling autoupdate for "network tools".

After LE upgrade to LE 9.95 "network tools" (rsync v .104) where marked as "incompatible" !!!

So there must be a change !!!

sure, that wasn't my argument.

I meant:

I couldn't find out what the differences between the rsync version exactly were.

I could find on github that the version number with a short comment had changed, but not what internal in the source has changed (a direct comparison of both version was impossible [to me])

I guess you should find a hint why 9.2.6 addons in 9.95 are "incompatible" here (somewhere):

LibreELEC

or maybe this one (after very short flying over it):

Upcoming Changes - LibreELEC

=> change from Python2 to Python3

In general:

to me it seems your problems are laying somewhere in

- user rights on the LE box (seen from the rsync server)

- network behaviour of the different rsync versions

I would also suggest to search the INet with keywords "rsync" and your exact "NAS type".

maybe there is a update for your NAS out that fixes that (too) ...??

are there no debug options on the NAS, to see what's going on.

on LE there is one: switch that on and start the rsync from the NAS again...

Quote from bg.lebowski

I'm more thinking in the smb (Samba) implementation on LE 10

I somewhat lately saw your comment #9 after I wrote the above and I'm somewhat confused:

What has SMB with rsync to do ?

and if needed: SMB/Samba has debug options too, switch them ON !

what is if you start with a lean rsyncd.conf and debug ON on both ends ?

means:

old cruft and defaults should be out e.g. "max connections = 0" is such an default

and double check all entries e.g. "host allow" correct ? , uid/gid, ..., even when the problem has something to do with rights

see:

rsyncd.conf(5) - Linux man page

config files working yesterday don't mean they will work today too...

maybe the newer version of rsync now looks somewhat "sharper" to some config options then the prev. version of rsync did ...

don't know

in a *nix world you also should mask blanks:

comment = Synology3 Video Backup

versus

comment = "Synology3 Video Backup"

Quote from bg.lebowski

But unfortunately after pressing the save button and error message appears ...

"Insufficient privileges to access this destination shared folder. Please contact the destination administrator for assistance"

This is due the fact that the rsync process will create the destination share and store its rsync notes (synobkpinfo.db) inside.

I've no idea from that tool running on your NAS.

and couldn't find out what's the differences between the rsync versions are.

sorry !

but some wild guesses:

where is that "destination" on LE 10 exactly ?

have you tried to create the directory and the file "synobkpinfo.db" in it (maybe an old synobkpinfo.db from LE 9.x copied) ?

the password in the first picture is "libreelec" and the IP adress matches ?

what would be if you unselect "Enable configuration backup (mandatory)" ?

it seems the second picture is uncomplete.

there seem to be more config. options further down (?!)

all I cant do is provide my rsync script :

#!/bin/bash

CLIENT="192.168.100.22";
# export CLIENT;

OPTs="-vauH --delete --progress --stats -h";

STD_EXCLUDE="Sync.log" && for i in ${STD_EXCLUDE}; do EXCLUDES="${EXCLUDES} --exclude=$i"; done;

SRC="/home/otto/Media";    # What to sync

DEST="/storage/Media";     # where to sync to on the LE box

LOG="./Sync_$(date +%F).log" && rm -rvf ./Sync_*.log;

    $(which rsync) ${OPTs} -e ssh ${SRC}/ root@${CLIENT}:${DEST} ${EXCLUDES} --log-file=${LOG};
    RSYNC_RC=$?;

    echo -e "\n\n Sync_RC=${RSYNC_RC} \n\n" >> ${LOG};

exit 0;

please adjust:

- CLIENT

- SRC (path !)

- DEST (path !)

- LOG (path !)

script asks for ssh login password on LE10 (if you keep it default it's "libreelec")

script removes on each run the old Log file.

it runs that way without errors

you could add " --dry-run" to "OPTs" line (within the brackets '"' !!!)

see man page rsync => "--dry-run"

and/or run the script with "sh -vx ./<scriptname>"

chmod u+x ./<scriptname> done once (if you're not from the *nix world)

assuming the NAS run a sort of *nix and "which rsync" expands to something useful

Quote from CvH

the generic builds are currently broken at our build slave, we need to redo the whole buildserver config anyway so this is fixed after the change is done in a ~week or so

thanks for clarification

Quote from elonesna

What you want is also in docker...

I only need a running TVHeadend addon for LE 11, nothing else

it seems there are no generic addon's builded or landed for some days:

Index of /addons/10.80.0

guessing "no commit's" leads to no new builds (saving electron's) ?

but, tvheadend 4.3-1979 is awaited for LE 11

assuming state "Approved" means building in the next round (within 24 h ?) ...

am I wrong or are my claims to high here ?

testing mediacenter software without TV or movies is somewhat senseless...

Quote from bg.lebowski

LE 10.0 didn't allow the Rsync Server (Synology NAS) to create the rsync folder configured in the "rsync module" in rsync.conf on Rsync Client (LibreELEC).

isn't there a ssh involved ?

are you able to ssh into LE from the the server ?

try it and run touch a (creates the file named "a" in the current folder).

Error ?

I'm rsyncing from a linux box to LE 10 via an bash script without errors here (running LE 10 generic)

both rsync version (rsync -V) are "protocol version 31"

are you sure you're try to rsync to an destination under ~/storage

- assuming generic and RPI disk layout are the same -

see the Usage section in the man page of rsync: a missing/wrong slash in the rsync command

- no Pi4 here -

on my generic box are two options to fill timeservers

in LE config tool:

- Network => NTP Servers

- Connections => click on your device => Edit => NTP Servers (was auto filled, maybe cause my router is configured as a time server)

while in that LE config tool:

- I'm currently don't know if the "addon update setting" are independent from "LE update setting" (Question is two independent "update setting" or both dependent ?) -

recheck if LE updates points to LE 10 see "Update Channel" !

unknown to me is if this is unset or misconfigured are addon's, the correct ones belonging the LE-Version, installable ?

but it won't hurt to set the correct Update Channel.

your time is wrong ?

see "LE System configuration" => Interface => "Regional"

are the settings there correct ???

Quote from bg.lebowski

With LE 9.2 i was able to setup rsync without any issue ... Also the the first "sync run" was successful.

and have you also tested a "first sync run" with LE 10 ?

Quote from bg.lebowski

... next i updated my box to LE 10.0 again ... means same configuration ...

and could also mean old addon's for LE 9.2 running on LE 10 (?!)

did you also upgrade the addon's for LE 10 ?

here is a man page for rsync:

rsync(1) - Linux man page

see there the "Exit Values".

if you run the rsync command manually you should get the exit value with "echo $?"

are both boxes in general pingable ? (LE 10 <=> second box)

addon "system-tools" gives a console

Quote from LybsterKodi

...

JoeAverage

"why that ?" - because it was suggested I start reading the source headers

...

I guess the advise was given to e.g. recheck the "ID on Interface" (see in LinuxTVWiki) usually also named USB-ID or PCI-ID (for non-usb-devices).

in short: if the specific ID is not in the kernel-driver-file (yet) : NO support for that specific device !

for example see:

TerraTec Cinergy S2 - LinuxTVWiki

=> under "Update" (written by me)

I tried to declare that stuff in my prev. comment

=> "vendor's change the device internals ..."

yup, LE11

thanks

Quote from LybsterKodi

... I would prefer not to have to learn yet another programming language just to find which bits of hardware are currently supported...

why that ?

throwing the correct Firmware on the device is mostly all you need to do and mainly reading before buying.

in your first post you mentioned LinuxTVWiki and there the device list

just check the column "Supported" and esp. "in kernel"

- feed google with the "Vendor Device / Model" and the add "+linux" to the search

- and feed google with the device components (column "Hardware") and add "+linux" to the search

be aware:

your are more on the safer side if you buy elder hardware, at least not the newest (keyword: kernel support, maybe is planed, but could last ...month...) and not from exotic vendor.

as said: hauppauge has a good name, but also a price. bought a sat device ~7 years ago, driver/software (windows though, but...) are still available from hauppauge.

vendor's change the device internals and let the name and description the same (only findable with device ID or in Wiki "ID on interface" (PCI, USB) when the device is in your box)

so all finding with google maybe outdated

double check and make sure you are able to give the device back to the seller and of course get the money back (not only a credit item)

it's not rocket sci*ence

Quote from DDuck007

Compiled ok and is running …

Thank you!

compiled for generic ?

[ ${answer} = "yes" ] && echo "care to make it downloadable for fans ?"

ping ${AllDeveloper}

what could one do to get commits on github out of state "Review required"

[ ] wait

[ ] wait more

[ ] review => how ?

[ ] review that a reviewer reviews => how and where to find the reviewer ?

[ ] init a "beer-induced" reviewer-brainstorming

heitbaum thanks for the fix

and many more thanks for pushing things on github (what I daily read), e.g. kernel 5.14, mesa and more

Quote from DDuck007

...

Does not start under LE10.0 ...

Why ?

anything in

/storage/.kodi/userdata/addon_data/service.tvheadend43/service.log

?