Posts by GDPR-7

and I guess power consumption too...

me is confused, that your disk doesn't support hdparm.

from a newer WD disk (WD-Black-P10) made years later as yours.

I haven't tried to set power feature, though.

anyway my mom owns a 1 TB of your disk type and I'll check hdparm support next time I get my fingers on the disk (700 km away)

sudo hdparm -I /dev/sdX:

ATA device, with non-removable media

Model Number: WDC WD50NMZW-59A8NS1

Serial Number: WD-WX92E317FZUN

Firmware Revision: 01.01A01

Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0

Standards:

Used: unknown (minor revision code 0x006d)

Supported: 10 9 8 7 6 5

Likely used: 10

Configuration:

Logical max current

cylinders 16383 0

heads 16 0

sectors/track 63 0

--

LBA user addressable sectors: 268435455

LBA48 user addressable sectors: 9767475632

Logical Sector size: 512 bytes

Physical Sector size: 4096 bytes

Logical Sector-0 offset: 0 bytes

device size with M = 1024*1024: 4769275 MBytes

device size with M = 1000*1000: 5000947 MBytes (5000 GB)

cache/buffer size = unknown

Form Factor: 2.5 inch

Nominal Media Rotation Rate: 5400

Capabilities:

LBA, IORDY(can be disabled)

Queue depth: 32

Standby timer values: spec'd by Standard, with device specific minimum

R/W multiple sector transfer: Max = 16 Current = 0

Advanced power management level: 128

DMA: *mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6

Cycle time: min=120ns recommended=120ns

PIO: pio0 pio1 pio2 pio3 pio4

Cycle time: no flow control=120ns IORDY flow control=120ns

Commands/features:

Enabled Supported:

* SMART feature set

Security Mode feature set

* Power Management feature set

* Write cache

* Look-ahead

* WRITE_BUFFER command

* READ_BUFFER command

* NOP cmd

* DOWNLOAD_MICROCODE

* Advanced Power Management feature set

Power-Up In Standby feature set

* SET_FEATURES required to spinup after power up

* 48-bit Address feature set

* Mandatory FLUSH_CACHE

* FLUSH_CACHE_EXT

* SMART error logging

* SMART self-test

* General Purpose Logging feature set

* 64-bit World wide name

* IDLE_IMMEDIATE with UNLOAD

* {READ,WRITE}_DMA_EXT_GPL commands

* Segmented DOWNLOAD_MICROCODE

* Gen1 signaling speed (1.5Gb/s)

* Gen2 signaling speed (3.0Gb/s)

* Gen3 signaling speed (6.0Gb/s)

* Native Command Queueing (NCQ)

* Phy event counters

* Idle-Unload when NCQ is active

* NCQ priority information

* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT

DMA Setup Auto-Activate optimization

Software settings preservation

* SMART Command Transport (SCT) feature set

* SCT Write Same (AC2)

* SCT Features Control (AC4)

* SCT Data Tables (AC5)

unknown 206[7]

unknown 206[12] (vendor specific)

unknown 206[13] (vendor specific)

* DOWNLOAD MICROCODE DMA command

* WRITE BUFFER DMA command

* READ BUFFER DMA command

* Data Set Management TRIM supported (limit 255 blocks)

* Deterministic read data after TRIM

Security:

Master password revision code = 65534

supported

not enabled

not locked

not frozen

not expired: security count

supported: enhanced erase

886min for SECURITY ERASE UNIT. 886min for ENHANCED SECURITY ERASE UNIT.

Logical Unit WWN Device Identifier: 50014ee2697f04ff

NAA : 5

IEEE OUI : 0014ee

Unique ID : 2697f04ff

Checksum: correct

Quote from cobalt2035

old Radeon HD 3000 work on the latest LibreELEC version as well as they do.

Incidentally, I just tested an HEVC file 3840x1600 24 FPS and it works fine! Unfortunately, bigger ones (e.g. 3840x2064 or 3840x1920) stutter noticeably.

according to this:

https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM3+/M5A78L-M_USB3/E8017_M5A78L-M-USB3.pdf

page ix:

see "Graphics"

Supports HDMI with max. resolution up to 1920 x 1200 (1080P) (@60Hz)

Supports DVI-D compliant with HDCP with max. resolution up to 2560 x 1600 (@60Hz)

Supports RGB with max. resolution of 2560 x 1440 (@75Hz)

I'm overask why you can watch with 3840x1600 24 FPS !

maybe you'll find a answer here:

https://wiki.libreelec.tv/hardware/intel-x86-64-generic

could filesystem "btrfs" in combination with mount option "autodefrag" an option ?

btw.: does the disk support TRIM ?

on linux:

sudo hdparm -I /dev/sdX|grep -i trim

adjust "X"

on windoof: driveInfo

DH DriveInfo

Quote from blueribb

I guess you have to remove that partition before formatting the drive and installing Libreelec.

me is unsure, but does the LE installer allow to leave partitions (in this case a hidden one) on a drive ?

I could image a boot key/a bios setting/something in the boot sector is tied with the recovery partition, which (my guess) doesn't exist anymore.

I would read the manual, maybe there is a hint to remove the recovery stuff cleanly.

maybe there is a setting in the bios what searches/checks the recovery at box startup

maybe it's sufficing to overwrite the bootsector (if the installer doesn't handle this already - does he ?) via system-rescue USB stick.

SystemRescue - System Rescue Homepage

I slightly remember I had the similar issue with an samsung NC10 or an NF310 [1] years ago ...

Francesco Cianci did you ask the internet/sony forum regarding this issue ?

care to post a photo about what you see at startup ?

Quote from greycat

but I don't know how much of that is a function of the sd card's write speeds.

cd to a folder of the sdcard and for

write speed run:

dd if=/dev/zero of=tempfile bs=1MB count=10240

read speed run:

dd if=tempfile of=/dev/zero bs=1MB count=10240

if the values you get are under the sdcard spec's format the card with

SD Memory Card Formatter | SD Association

www.sdcard.org

note:

sdcards (and most usb sticks) do not have a TRIM function/command, so a from time-to-time long format (not quick !) or better a format with the above tool should improve the sdcards write values

Quote from Danarchy

Not sure if that link above works...

could be tested by just clicking the link, but with one eye only ...

from the log:6.229416] F2FS-fs (sdb2): Magic Mismatch, valid(0xf2f52010) - read(0x8e0e89 66) [ 6.229422] F2FS-fs (sdb2): Can't find valid F2FS filesystem in 1th superbloc k

[ 6.229636] F2FS-fs (sdb1): Magic Mismatch, valid(0xf2f52010) - read(0x8e0e89 66)

[ 6.229639] F2FS-fs (sdb1): Can't find valid F2FS filesystem in 1th superbloc k

[ 6.229689] F2FS-fs (sdb2): Magic Mismatch, valid(0xf2f52010) - read(0x0)

[ 6.229691] F2FS-fs (sdb2): Can't find valid F2FS filesystem in 2th superbloc k

[ 6.229800] F2FS-fs (sdb1): Magic Mismatch, valid(0xf2f52010) - read(0x0)

[ 6.229802] F2FS-fs (sdb1): Can't find valid F2FS filesystem in 2th superbloc

to *me* that doesn't look right.

*I* would backup the files from the disk and would format it

1. I ssh into my LE, ( I had a typo in comment #9, wrongly wrote ssd'ed - me old idiot -)

2. cd to the folder where the script is

3. and run the script from there with

./get_nightly.sh

note the point in front of the slash ("/") !

the script just downloads the last nightly into ~/.update (script line 32+34) and additional copies it to ~/backup (line 36) and then offers you to run the commands "sync && sync && systemctl reboot" (line 38).

it offers only !

if you don't run the offered commands nothing will happen until you reboot the box.

only during reboot the last nightly in ./update will get installed and the folder ./update will emptied from the update-installer

the scripts doesn't stop any service, e.g. smb.

hint:

on linux you could just mark/highlight the command "sync && ..." with your mouse and now do a middle-click to copy it for subseq. execution with the Enter-Key

in an terminal on one box for the iperf3-server run:

iperf3 -s -p 5002

in an terminal on the other box for the iperf3-client run:

iperf3 -c <put the iperf3-server-IP-Address-here> -p 5002

Normally, the test data is sent from the client to the server, and measures the UPLOAD speed of the client.

Measuring the DOWNLOAD speed from the server can be done by specifying the -R flag on the client.

iperf3 -c <put the iperf3-server-IP-Address-here> -p 5202 -R

This causes data to be sent from the server to the client.

note:

you maybe need to install the iperf3 packages on your linux box and the "Network Tools"-Addon under LE

AFAIK, scan files are maintained here:

LinuxTV.org - Television with Linux

or

dtv-scan-tables.git - Digital TV scan tables

and TVH fetches them from there.

I would be wise and a benefit for others in your country to contact linuxtv direct (ML ?) so that outdated/wrong scan files could be updated

w_scan2

- used it with my Hauppauge WinTV-NOVA-HD-S2 moons ago -

seems to be outdated and replaced with w_scan_cpp (cit.: can output dtv scan tables für dvbv5-scan)

see:

w_scan_cpp

and

Frequency scan - LinuxTVWiki

care to provide the exact disk/brand type ?

Quote from slubberman

Don't know what else to say

usually what the "specific add-on" is (in case I'm not the only one who couldn't figure it out reading the log)

I guess switching debug mode on too (and a subseq. reboot) wouldn't harm too

more to read:

https://wiki.libreelec.tv/support/log-files

Quote from pchristy

I can't edit the file directly on the sd card, as it all appears to be contained in a squashfs file system!

AFAIK, the scan files are under:

/storage/.kodi/addons/service.tvheadend43/dvb-scan

and editable

Quote from heitbaum

as long as you keep a copy of the img.gz file around.

AGLyons I use a small script to manage that.

the script fetches a new nightly (the *.tar) and keeps a copy in ~/backup.

cleaning of ~/backup is up to your own ...

#!/bin/bash

NIGHTLY="LibreELEC-Generic.x86_64-11.0-nightly-";
SERVER_URL="https://test.libreelec.tv";

# clean in any case ~/.update/
cd ~/.update/ && rm -rf *;

# operate in /tmp and clean up before
cd /tmp/ && rm -rf releases.json*;

wget ${SERVER_URL}/releases.json;

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

if [ ! -z "${NEW_NIGHTLY}" ]; then

# get currently running nightly version
CURRENT_NIGHTLY=$(cat /etc/issue |grep nightly|cut -d: -f2|cut -d "(" -f1|sed -e 's/ //g');

# and compare with the one on the server
RC=$(echo ${NEW_NIGHTLY} | grep ${CURRENT_NIGHTLY});

[ ! -z "${RC}" ] && echo -e "\n lastest nightly already running \n" && exit 13;


rm -rf ${NEW_NIGHTLY};   # clean maybe old downloaded stuff before downloading the new nightly

echo -e "\n fetching ${NEW_NIGHTLY} \n\t wait ...\n";

# download new nightly to ~/.update/ and save a copy to ~/backup/
cd ~/.update/ && rm -rf *;

wget -nc ${SERVER_URL}/${NEW_NIGHTLY};

cp *.tar ~/backup/;

echo -e "\n\n reboot to install the new nightly, e.g. \n\n\t sync && sync && systemctl reboot \n";

else
echo -e "\n No new nightly \n";
fi;

exit 0;

copy the content of the "code box" into a file, and name it, let's say "get_nightly.sh".

chmod u+x get_nightly.sh to make it executable

and run it - after ssh'ed into the box with:

./get_nightly.sh

shortcomming's:

- script doesn't distinguish between new nightlies with same git tag and different date. what leads to a 2^cd download...

- my thinko's I did in the script

- warranty does not exit !

seems to be fixed with nightly-20220504-b75264b

thanks

Quote from tekno

I was also looking at these as they are plenty cheap but not sure if there are drivers in Libreelec or not for either of them.

a good page what's support by linux/LE is this:

Hardware device information - LinuxTVWiki

the page is partly NOT up to date, so check the INet too *before* buying.

and also check *before* buying if and how to send the device back/get your money back in case it doesn't play

Quote from mglae

It is at least filled when accessed via samba.

thanks mglae, samba is off here...

Quote from smp

Not sure. I don't see anyone mentioning it on Kodi's github or elsewhere. The issue is pretty obvious though and easy to reproduce.

bug filled:

nightly LE crashes hitting "I" for info" and afterwards another key apart "I" while running a tv channel · Issue #21333 · xbmc/xbmc

Bug report Describe the bug Here is a clear and concise description of what the problem is: I&#39;m running last LE nightly (nightly-20220429-2e7f384) LE…

github.com