WanWizard

Files in trash are not deleted automatically I think, it is like in Windows you need to ask to empty the trash.

Press Menu when on the trash folder and choose empty.

I think it depends on where your Trash is.

A trash folder is created on every file system you have available, but I'm pretty sure (without looking at the code) Enigma doesn't scan them all, it only checks the trash folder on the filesystem that holds your recording location.

So if you navigate to an USB stick or a NAS mount, and you delete something there, it will not be deleted automatically if your recording location is your local harddisk...

You're not saying that you've invented yet another flavour of "branding"?

Flash procedure for an ET5000:

• Insert the USB stick into either any of the USB ports on the ET5000 on the front or rear panel, it doesn't matter which you use.
• Now Power Off and Power On the ET5000 through the powerswitch at the rear panel of the box
• After Power On, ET5000 will try and detect if there is ET5000 firmware available on the USB stick.
• When the yellow/orange LED shines then there is ET5000 firmware detected. To load the ET5000 firmware you'll need to press the up button on the frontpanel at this point. When the green and the yellow/orange LED shine together the ET5000 is loading the firmware.
• Please be patient because it will take a couple of minutes to finish upgrading.
• When the yellow/orange LED disappears then the ET5000 is finished upgrading the firmware. The ET5000 will startup automatically after the upgrade is finished.

Yup, redsea now builds, I've restarted a full develop build run. Thanks.

Thanks, merged.

Ja. En die tool heet ook nog eens smart.

root@vuduo4k:~# opkg install smartmontools
Installing smartmontools (5.42) on root
Downloading http://xxxxx/feeds/openpli-develop/armv7ahf-neon/smartmontools_5.42-r1.0.1_armv7ahf-neon.ipk.
Configuring smartmontools.

root@vuduo4k:~# smartctl -a /dev/sdb
smartctl 5.42 2011-10-20 r3458 [armv7l-linux-4.1.45-1.17] (local build)
Copyright (C) 2002-11 by Bruce Allen, [url=http://smartmontools.sourceforge.net]http://smartmontools.sourceforge.net[/url]
 
=== START OF INFORMATION SECTION ===
Device Model:     ST1500LM006 HN-M151RAD
Serial Number:    S35UJ9AFA04664
LU WWN Device Id: 5 0004cf 20e4d6a63
Firmware Version: 2BC10001
User Capacity:    1,500,301,910,016 bytes [1.50 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Wed Aug 28 13:00:51 2019 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
 
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
 
General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever 
been run.
Total time to complete Offline 
data collection: (17520) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine 
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities:        (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
 
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       2
  2 Throughput_Performance  0x0027   252   252   000    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   091   090   025    Pre-fail  Always       -       2872
  4 Start_Stop_Count        0x0032   093   093   000    Old_age   Always       -       7774
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   252   252   051    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   252   252   015    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       10627
 10 Spin_Retry_Count        0x0033   252   252   051    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       981
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       5727823
183 Runtime_Bad_Block       0x0032   252   252   010    Old_age   Always       -       0
184 End-to-End_Error        0x0033   252   252   097    Pre-fail  Always       -       0
186 Unknown_Attribute       0x0032   252   252   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   252   252   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   252   252   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0002   070   052   040    Old_age   Always       -       30 (Min/Max 13/48)
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       29
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       468
193 Load_Cycle_Count        0x0032   025   025   000    Old_age   Always       -       757828
194 Temperature_Celsius     0x0002   064   052   000    Old_age   Always       -       30 (Min/Max 13/48)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       136
 
SMART Error Log Version: 1
No Errors Logged
 
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      5026         -
# 2  Offline             Interrupted (host reset)      90%      4380         -
# 3  Extended captive    Self-test routine in progress 90%      4380         -
# 4  Extended offline    Aborted by host               90%      4380         -
# 5  Short offline       Completed without error       00%         6         -
 
Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
root@vuduo4k:~#

Ok, and this should solve all network problem?

How about a solution??

OR some kind of tips - quick and straight to the point.

How can we create a solution if we don't know the problem, and we can't find the problem because you're using something that does not exist, and has never existed.

There is a reason why we have retired the old entry level DMM boxes...

Problem in the ipk, the dependency isn't defined. Badly created.

You don't need it in your STB. You can use an ordinary hdd. Seagate have a 5TB 2½" and it works without problem in DUO 4K.

A 5TB 2,5" disk is with almost 100% certainty an SMR disk.

SMR disks requires tracks to be written in sequence because they overlap, which is why they have large (128MB+) caches. Once the cache fills up, it has to be written to disk, and the performance of the disk plummets.

This means that as long as the disk can keep up with your writing (aided by the cache), you're fine. As soon as it can't do it anymore, your recordings will have dropouts.

The fact you say it works fine means you haven't reached this point yet.

Een FBC tuner bestaat niet, en er is niks dual aan een FBC module. Een FBC module heeft 2 root tuners, elk gekoppeld aan een input, en 6 leaf tuners, die dynamisch intern worden doorgelust op een van de twee root tuners.

Elk van die root tuners kun je configureren als een legacy tuner, direct op een LNB of gekoppeld aan een DiseqC switch, en dan emuleert de root tuner een traditionele tuner. De leaf tuners gedragen zich dan als gewone tuners, die intern doorgelust zijn (en hebben dan dus de beperking van het kwadrant waarop de root tuner is afgestemd).

Dus ja, je kunt de A en B tuner van zo'n FBC module (of I en J als het de tweede module is) configureren alsof het ouderwetse tuners zijn, werkt prima. Van de andere moet je afblijven, laat die op "FBC automatic" staan.

as far as it's ok, but i thought if i flash a new image from date 12.08.2019 and now install the three plugins as above mentioned from feed

all these commits are in the new image, but that is not the case - why ?

Because a release image is a stable image, which means everything is pinned on commit hash, which needs manual updating after a component is updated and properly tested in develop.

Often, the component gets updated, if we're lucky it gets properly tested, but a PR to update the commit hash is hardly ever created.

Ok. Here you go: https://github.com/O...2a8fa9d3d0b826a

SDL2 2.0.5 is part of the OE version we ship with OpenPLi 7.1. 

2.0.10 has only been updated in OE 6 days ago (https://github.com/o...raphics/libsdl2), but the recipe is different.

I'd rather port this one, then use a custom recipe, which will always become a pain when we need to upgrade OpenPLi to a newer OE version...

Haha, huge, i presume that there are all packages builded and entire cache.

All images, all packages, complete sstate-cache, rm_work active for release images.
 

I wonder why 7.1 is bigger than RC or develop.

It's the other way around, the second value is "used". I suspect that for debug reasons the RC's where build without rm_work, and with buildhistory active (is used to generate the pinning in reporefs.conf).

Also, we've created a cleanup script that runs after every build, which hasn't run for rc, as that hasn't been build for a while.
 

Can you share infos regarding the hardware behind those buildservers?

Our buildervers are Intel Core i7 7700K machines, 32GB ram, with 2 SATA disks for storage and the OS (part in raid 1), and 2 Samsung EVO 970 1TB SSD disks for the images (hence two build directories per server).

Thanks, I believe I've merged all of them?