Posts by GDPR-7

    very likely its not the driver

    +1

    running e1000e over years with different kernels without errors, esp. connection problems.

    same goes for my NUC (see signature)

    surfing the kernel bugzilla (e1000e): bugs are all elder and more PCI-e (?) power save related AND should be fixed since, otherwise there should be newer reports.

    couldn't figure what's the last version of the e1000e driver in an kernel tree is.

    any hints ?

    if it related to the date in the copyright string in the driver files: the newest date is "2018" (Kernel 5.16)

    I guess a LE log file could show some more what's up with connection problem the OP is seeing

    I didn't give me some choice

    what happens if you tap/click/select and hit enter the two white points in the backup tool window ? [1]

    hint: two points in linux means the upper directory

    Questions:

    as you said you're running LE from an usb stick, where is the need to move the backup file (at this point) ?

    isn't the backup directory not already on the same usb stick too ?

    or better:

    the backup directory is one entry of the directory structure of a running LE and in this case: on the usb stick

    so, aren't you already done with creating the backup in it's default backup directory (which *is* already on the usb stick) and pulling the stick after you powered the box down ?

    [1]

    there seems to be a bug regarding the cancel-button in that window: a backup is in any case created

    at least here on (yesterdays) nightly

    I guess it should go like this:

    - create a backup [1] with LE config tool/addon on the stick

    - pull off the stick

    - install the ssd and on it LE

    - plug in the stick

    and now either

    - point in the LE config tool/addon the "backup restore" to the stick (should be /var/media/<something need to filled in>/....)

    or

    - copy the backup from the stick to the backup folder on the ssd (~/backup) and restore with LE config tool

    - reboot (to activate the restored settings/services)

    - check your setting

    - create a new backup (now on the ssd)

    The "I'm unsure -"part :

    - are there special folders for pics/movies/... ?

    I guess they should backup by hand (addon "system tools" => MC maybe via ssh'ed in OR with internal filebrowser)

    if you're running with special kernel boot parameter, e.g. i915 FW: needs adjustment by hand, caused ironed by the installer

    [1]

    backup contains:

    - ~/.cache with all it's content/settings

    - ~/.config with all it's content/settings

    - ~/.kodi with all it's content/settings (and I guess the setting for pic/movie libraries too, but not the pics/movies files itself)

    Specials:

    - if it's a used ssd you should think about secure erase the ssd *before* installing LE (usually with vendor tools)

    - if the usb stick is free now you should think about "long format" it under windows

    both to get them back to (nearly) initial speed

    - run "fstrim -va" via ssh for your ssd from time to time (weekly/monthly)

    I use my script using ssh and wget:

    GDPR-7
    December 26, 2021 at 2:15 AM

    comment #5

    planning to run a Samsung Evo Plus NVMe in an Intel NUC.

    I wonder how hot it would be. :/

    sensors from addon system tools should tell something like this:

    nvme-pci-0100

    Adapter: PCI adapter

    Composite: +31.9°C (low = -273.1°C, high = +81.8°C)

    (crit = +84.8°C)

    Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C)

    Sensor 2: +35.9°C (low = -273.1°C, high = +65261.8°C)

    from my Desktop running kernel 5.16.0-rc8

    I slightly remember there is a heat pad in the NUC cover integrated ?!

    yup, quiet clear, did it the same, but the main background of my question was "how to do it *without* a second box.

    anyway the above script works for me.

    if you want, you could use the script after adjustments, as you're anyhow ssh intoyour LE.

    if you got questions, just ask !

    to prepare the script for your rock54 box adjustments are needed:

    line 3 to:

    NIGHTLY="rock64";

    and

    line 14 to:

    [ -e releases.json ] && NEW_NIGHTLY=$(grep -i ${NIGHTLY} releases.json | grep .gz | cut -d: -f2| sed -e 's/"//g' -e 's/ //g' -e 's/,//g');

    alas I'm able to test it here only partly, means: a download starts

    but I can't test line 22, where the last rock64 nightly is already installed and I therefore want to prevent the unnecessary download.

    I would need a rock64 box (or at least the out of "cat /etc/issue"), but I don't own one !

    ====

    questions to the developer/maintainer:

    compared to generic, why do only *.gz exists for of "LibreELEC-RK3399.arm-11.0-nightly"

    here, on nightly it also doesn't work:

    mount|grep loop0

    => /dev/loop0 on / type squashfs (ro,relatime,errors=continue)

    mount -o remount,rw /

    mount|grep loop0

    /dev/loop0 on / type squashfs (ro,relatime,errors=continue)

    Klojum do you mixed it with:

    mount -o remount,rw /dev/sda1 /flash


    doejohn

    a shoot in the dark:

    maybe ~/.config/bluetooth takes precedence over /etc/bluetooth ???

    so what happens if you copy the folder /etc/bluetooth to ~/.config/

    and

    adjust your settings

    and

    reboot

    and

    "soundcheck"