Posts by GDPR-7

  • Looking to buy newest NUC version compatible with latest LE release

    some thoughts:

    - Intel is involved in active developing linux, esp. LAN, GPU (driver i915), chipset (?), wifi

    I would suggest to stay completely with Intel (GPU, LAN, WIFI,..., the NUC) and no derivations (Gigabyte, ...)

    you're on a save(r) side

    - newer NUC's => longer support

    - newer NUC's, esp. newer Intel GPU => maybe currently(!, WIP) only support with LE nightly: in-kernel GPU driver "i915": kernel 5.15.y versus 5.10.y)

    - newer NUC's, esp. Video Format "AV1" => maybe currently no or never support for that video format in LE

    - be aware: some NUC lacks audio output via cinch (?) if you need this; so audio only via HDMI /DP

    - be aware: NUC with non-intel GPU (nvidia) maybe no support by LE (in the future)

    - is the harmony website still online to configure the CIR/Harmony for that newer NUC ?

    - and double check the connection NUC <=> TV/Audio (=> user forum of that TV and/or the NUC Specs)

    - look out for bring back support and fee's (if something overlooked)

    Intel GPU and Features e.g. Video Format (=> chap.: "GPU video acceration"):

    https://en.wikipedia.org/wiki/Intel_Gra…s_(GPU_hardware)

  • Samba Server is sometimes not working

    Quote from sam-y

    can i start the journalctl by default every time i start the HTPC?

    "journalctl" or exactly "systemd journal (in short: journald)" *is* started by default.

    but on LE the log's go per default and without adjustment (see comment #9) to RAM only (thrown away at reboot/shutdown, because they could become very large and could fill up the disk)

    "journalctl" is the command to query the systemd journal

  • No signal (new install) Generic / 10.0

    Quote from Da Flex

    The log says, DP is in use, so the connected HDMI cable makes no sense without a DP adapter.

    are you sure ?

    running a NUC (see signature) with HDMI and "tail /sys/class/drm/*/status" shows me this:

    LibreELEC:~ # tail /sys/class/drm/*/status

    ==> /sys/class/drm/card0-DP-1/status <==

    connected

    ==> /sys/class/drm/card0-DP-2/status <==

    disconnected

    ==> /sys/class/drm/card0-HDMI-A-1/status <==

    disconnected

    AFAIK here is converter (LSPCON) DP => HDMI involved (picture attached)

    I guess this could be the case for the Gigabyte Brix 8250u too (don't know)

  • Installing nightly build...

    something up with your downloaded file ?

    maybe the following could help:

    1. ssh into LE

    2. cd ~/.update

    3. key in: wget <copy-paste the link from the image here> [1]

    4. reboot

    after 2cd reboot: ssh into LE again

    =>

    "...

    LibreELEC (community): nightly-20211205-03893cb (Generic.x86_64)

    ...

    "

    no ?

    [1]

    on

    Index of /

    - key in "gen" in the textbox to see only generic's

    - right click on the *.tar

    - in firefox: "copy link"

    ===

    in case you want install new /nightly from scratch:

    be aware: backup before and move the backup offline !

    - fetch LE Release and install it as usual

    - after 1st boot switch on ssh

    - ssh into LE

    - same as above see "2. cd ..."

    - run "systemctl stop kodi"

    - run "rm -fr /storage/.kodi"

    - reboot

  • Samba Server is sometimes not working

    I would run

    journalctl -u smbd

    directly after the smb server appears to be down (when it was running before)

    or run it with "-f" ("f" for ~follow up~) all the time

    journalctl -u smbd -f

    or

    journalctl -f

    to see all what's up with your box

    maybe with increased log level:

    [Chapter 4] 4.8 Logging Configuration Options

    ===

    btw.:

    the smb server box is connected via ethernet, too ?

    ===

    maybe something in your smb.conf is ~slightly~ wrong (full wrong => smb wouldn't start)

    run [1]

    testparm -v

    I'm unsure here: I guess it cry's when error are found, anyway I fetched the return status via "echo $?" where I guess "0" means no errors

    one of this has caused trouble for some users (I guess the first one)

    server max protocol ?

    server min protocol ?

    [1]

    I've attached the output of testparm -v

    be aware:

    - it's from nightly

    - it's the untouched default, cause smb is here NOT in use

    if you've a linux box available you could e.g. use "meld" to compare yours and mine

    Meld

    Quote from sam-y

    There is nothing in the log that helps solving the problem:

    journal log files are thrown away when you reboot the box ...

    and you just checked for smb only, so maybe it's not smb (my bet: it's network ...[if you don't find any weird config settings with testparm] or it's something with the kernel)

    last part could be checked with nightly (newer kernel: 5.15.y)

  • Virtualbox 6.1 with LibreELEC-Generic.x86_64-10.0.1.ova

    just checked

    Host: fedora 35 on an Intel i5-11400

    GPU:

    - Video Mem. :128 MB

    - Graphic controller: VMSVGA

    - Acceleration: enable 3D A.

    with I got the LE-VM up, but the installer doesn't not see a disk to install on.

    running it with "run" I got for storage (Size/Used)

    - /flash 511,7M / ~264M

    - /storage 26.5M / 7,7M !


    VGA seems to be a LLVM

    AFAIK it's a GPU in software

    anyway, I've read to get an usb stick bootable in Virtualbox.

    with that there is maybe a chance to get an LE release or nightly installed ...

    I need more time to play with it somewhat more, don't know when ...

    liberi are the VM bits on in your Bios ?

  • Something wrong here?

    Quote from Reddirt

    I would have tried the H2testw but my German is limited to Please and thank you.

    well, "german" "download" is the same as the english "download" ;)

    the file downloaded and unzipped provides an (english) readme !

    other way:

    *long* format the stick under windows and "chdsk /F ..." (see: chkdsk /?)

    dumb question:

    you tried the windows install usb stick on a windows box ?

    hint:

    with an the windows installer stick, even with elder GPU's, it needs some time until the setup/install window appears (seen with elder Intel GPU, HD4000, Ivy Bridge)

    time to shovel ~4GB (win10) from an slow (?) usb stick into RAM !

    Quote from Reddirt

    So....I fired up my Linux Mint machine but couldn't download the gz file

    md5 checksum to compare:

    da23178c4b1d9700842d7df9386e95e6 LibreELEC-RPi2.arm-11.0-nightly-20211127-b9d3fa5.img.gz

    it's the last but one file in the list from comment #5

    and for the LE usb creator:

    3e094fac708fa3008864260e820ba1c7 LibreELEC.USB-SD.Creator.Linux-64bit.bin

  • Something wrong here?

    Quote from Reddirt

    I decided it's time for a shiny new RPi4 so that's my next project and I understand. I'm still stuck on the sd-usb creator issue. I've prepared two different usb sticks of different brands and sizes and neither will boot up on my Windows PC. I have a few other usb sticks with LE9.2 on them which still boot up just fine. What would cause this?

    maybe a test with an window install image to exclude it's the usb stick itself:

    on windows:

    open a terminal with admin rights and key in the following commands (all after "#" are comments not commands !) :

    diskpart

    list disk

    select disk N # adjust "N"

    detail disk # to see you selected the correct disk

    clean # cause this will move your data to /dev/null 8)

    create partition primary

    format fs=ntfs quick

    assign

    active

    exit

    now unzip [1] or mount under linux a windows install dvd and copy the content to the stick

    does the stick boot (now) ?

    no: [2]


    [1]

    don't known if the windows buildin zipper is that smart.

    if not:

    Download

    [2]

    H2testw
    H2testw erkennt gefälschte USB-Sticks, indem es deren tatsächliche Speicherkapazität ermittelt. Auch andere Wechselmedien sowie Festplatten lassen sich testen.
    www.heise.de

    from the included readme (please read at first !) :

    "... H2testw was developed to test USB sticks for various kinds of errors. ..."