Nightly builds (NEW)

Tictid TX6 Plus (S905X3):

CoreELEC:~ # dd if=/dev/zero of=/storage/test.tmp bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 5.515423 seconds, 185.7MB/s
CoreELEC:~ # dd if=/storage/test.tmp of=/dev/null bs=1M
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 0.785345 seconds, 1.3GB/s
CoreELEC:~ #

Erario: You don’t read old posts? Because your results are not valid either.

1 Like

Capture

V30, A1 micro-SD card.

I’m no Linux expert but isn’t filling a file up with /dev/zero going to be pretty well optimized. Wouldn’t a better real world test be actually copying a file? I get wildly different results on my N2 using both /dev/zero and an actual 1GB file.

/dev/zero

CoreELEC:~ # echo 3 > /proc/sys/vm/drop_caches
CoreELEC:~ # dd if=/dev/zero of=/storage/test.tmp bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 9.751487 seconds, 105.0MB/s

a real world file that isn’t just a stream of zeros

CoreELEC:~ # echo 3 > /proc/sys/vm/drop_caches
CoreELEC:~ # dd if=/storage/test.mkv of=/storage/test.tmp bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 25.546974 seconds, 40.1MB/s

or better yet, /dev/urandom so as not to incur the speed penalty of also reading from the disk

CoreELEC:~ # echo 3 > /proc/sys/vm/drop_caches
CoreELEC:~ # dd if=/dev/urandom of=/storage/test.tmp bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 12.921527 seconds, 79.2MB/s

Here a write result using a file from a nfs share

CoreELEC:~ # mkdir /storage/test
CoreELEC:~ # mount -t nfs 192.168.0.4:/volume1/Media /storage/test
CoreELEC:~ # echo 3 > /proc/sys/vm/drop_caches
CoreELEC:~ # dd if=/storage/test/test.mkv of=/storage/test.tmp bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 12.998821 seconds, 78.8MB/s

For example: hdparm -Tt /dev/data (/dev/system, /dev/data, /dev/mmcblk0)
hdparm -tT /dev/mmcblk0

CoreELEC:~ # hdparm -tT /dev/mmcblk0

/dev/mmcblk0:
Timing cached reads: 1742 MB in 2.00 seconds = 871.07 MB/sec
HDIO_DRIVE_CMD(identify) failed: Invalid argument
Timing buffered disk reads: 408 MB in 3.01 seconds = 135.35 MB/sec

My box it’s 24/7 on, and from a week more or less, sometimes I found it without network connection (wifi), and need to reboot because it doesn’t reconnect from menu, even turning off/on the wireless network.

It’s a X96 Max S905X2 4/64, and it happens since a week aprox, nothing changed in config and router conf…

How can I identify the problem? I am not able to see anything in kodi log, only errors in addons teying to get network…

Not sure if you meant ONCE a week or for past week.

If regularly - once per - then maybe the router is being cycled and dropping the wireless connection?

Since a week, it happens every day.

And about the router… Don’t think it’s the problem, with other devices it doesn’t happen, and nothing changed in router conf.

I guess you should try to recall if any changes were made at the time … such as a new addon installed or such.

Nothing, same config and addons since months

Wifi is easily interfered with by other devices in the vicinity.
Maybe try channel change to see if it improves things?

Does nobody else has this problem - really?

There is a newer nightly you can try.
What\s the purpose of rebooting btw? Not saying it’s fine it doesn’t reboot for you, just wonder why you need to reboot it.

change settings or hardware sometimes need reboot. or wakeup via remote also does not work.

Hi,

Just started to use an S905X3 box with the latest nightly build. 4K@60p video playback seems to be broken. The picture is ok, but the audio (TrueHD stream) gets out of sync after a few minutes and occasionally there’s no audio at all, then it comes back again.
Is this a known issue?
(The same video was ok with my old S912 (Gemini Man 4K/HDR@60p version))

with newest nightly: its the same

@andy5macht please provide a copy of dmesg… dmesg|paste

The only reason this would happen is if there has been a kernel oops and it’s preventing a graceful shutdown.

http://ix.io/27Uh

Edit: i found it myself in Logfile:
[ 0.530434@2] clk_set_rate failed: -5, new cluster: 0
[ 0.530447@2] failed to set clock 1992Mhz rate: -5
[ 0.530458@2] cpufreq: __target_index: Failed to change cpu frequency: -5

if i comment out a53 overclock in config.ini - reboot and wakeup works fine: # max_freq_a53=‘1992’

Same issue here.