[S922X-H] Bee-link GS-King X

PatrickJB · 9 June 2020 19:55

Aren’t these NAS things able to wake-on-Lan? Unless of course some are running them 24/7 for certain, not to be mentioned, reasons!

Yes we’d all love a home server that’s robust but are they fully baked or still iffy? I would expect the lifetime standard to be 10 years excepting HD upgrades but I doubt the technology is there yet. Power usage and redundancy is also something that isn’t perhaps there yet for home servers.

The day will come when every home has a silicon brain which is a bit scary in some respects.

Me? Oh I run media files from an old MXQ, always on but drives sleep when not in use, but it’s slow and I’ve only got ADSL which is crap but no fibre in my area. Hey it works but it’s basic. Been on 24/7 for 3 years. Stop laughing!!

broleke · 10 June 2020 18:47

a few pictures:

I think that the box is well made, with extruded aluminium for the case.
There is a fan on top of the chip, I think it aimed at air flow for the whole device.
Also, the HDD seems to be connected using a SATA to USB device.

Here is a short video to get an idea about the fan/hdd noise (there is an old 4TB in the box)

The overall quality is much better than that of the GT-King, but I’m not a big fan of the added fan.

Compent · 11 June 2020 17:03

When populated with 2 HDD’s I think that a fan would be an inevitable requirement.

The aluminium casing should aid dissipation too.

If the hard drive connections are tied to the USB controller, this would mean that you would potentially have 6 devices running through 1 channel, which probably won’t matter in real world use but I can see reviewers criticising it for having to spread disk i/o load this way.

cdu13a · 11 June 2020 17:52

There are two options for adding SATA to a S922X device, USB to SATA (as done with this device) or PCIe to SATA.

However if you use the PCIe option, you loose all of your USB3 because the S922X can either do USB3 or PCIe, and not both at the same time. More people will get upset about no USB 3.0

The USB to SATA chipset being used in this device is a reasonably good quality chipset. Considering how most people will use this I don’t think anybody will likely have any issue with this configuration.

As for reviewers. It’s 2020 all reviewers should come with a clue now.

broleke · 12 June 2020 07:24

Booting fine with the GT-King revA dtb file.
The extra storage (there is a 4TB HDD in my box) is detected too.

vpeter · 12 June 2020 07:38

Can you extract dtb from android and post it? Run this command and post file dtb.img.gz.

dd if=/dev/dtb | gzip > /storage/downloads/dtb.img.gz

broleke · 12 June 2020 07:43

I use the revA dtb from the CoreELEC distribution.
Here is the file you asked dtb.img.gz (60.4 KB) .

broleke · 12 June 2020 07:55

Ray, can you let me know which iperf command you’d like me to run for testing RW over the Gb ethernet connection ?

I get this when using the GT-King as server:

CoreELEC:~ # iperf3 udp test - iperf3 -c 192.168.179.30 -u -b 1000m
Connecting to host 192.168.179.30, port 5201
[  5] local 192.168.179.77 port 37675 connected to 192.168.179.30 port 5201
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec  2.09 MBytes  17.6 Mbits/sec  1517
[  5]   1.00-2.00   sec  2.12 MBytes  17.7 Mbits/sec  1532
[  5]   2.00-3.00   sec  2.03 MBytes  17.0 Mbits/sec  1471
[  5]   3.00-4.00   sec  2.12 MBytes  17.8 Mbits/sec  1535
[  5]   4.00-5.00   sec  2.03 MBytes  17.0 Mbits/sec  1471
[  5]   5.00-6.00   sec  2.03 MBytes  17.0 Mbits/sec  1471
[  5]   6.00-7.00   sec  2.03 MBytes  17.0 Mbits/sec  1471
[  5]   7.00-8.00   sec  2.12 MBytes  17.8 Mbits/sec  1535
[  5]   8.00-9.00   sec  2.03 MBytes  17.0 Mbits/sec  1471
[  5]   9.00-10.00  sec  2.03 MBytes  17.0 Mbits/sec  1471
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec  20.6 MBytes  17.3 Mbits/sec  0.000 ms  0/14945 (0%)  sender
[  5]   0.00-10.05  sec  20.6 MBytes  17.2 Mbits/sec  0.042 ms  0/14943 (0%)  receiver

iperf Done.

Portisch · 12 June 2020 07:59

Can u give me the output of mount please?

broleke · 12 June 2020 08:01

devtmpfs on /dev type devtmpfs (rw,relatime,size=1917076k,nr_inodes=479269,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/mmcblk1p1 on /flash type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/loop0 on / type squashfs (ro,relatime)
/dev/mmcblk1p2 on /storage type ext4 (rw,noatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tmpfs on /var type tmpfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda1 on /var/media/android type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)

broleke · 12 June 2020 08:02

wouldn’t it make sense to reformat the HDD with proper ext4 (I’m running CoreELEC exclusively)?

Portisch · 12 June 2020 08:04

Yes, please try this speed test of the internal HDD:

Be sure test file is removed before and after speed test:
rm -rf /var/media/android/test.speed

Write speed test:
echo 3 > /proc/sys/vm/drop_caches
dd if=/dev/zero of=/var/media/android/test.speed bs=1M count=1024

Read test:
echo 3 > /proc/sys/vm/drop_caches
dd if=/var/media/android/test.speed of=/dev/null bs=1M

broleke · 12 June 2020 08:07

the HDD is a Hitachi HUS724040ALE641
the controller is an ASM1156-PM from ASMT

CoreELEC:~ # rm -rf /var/media/android/test.speed && echo 3 > /proc/sys/vm/drop_caches && dd if=/dev/zero of=/var/media/andro
id/test.speed bs=1M count=1024 && sync
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 3.777888 seconds, 271.1MB/s
CoreELEC:~ # echo 3 > /proc/sys/vm/drop_caches
CoreELEC:~ # dd if=/var/media/android/test.speed of=/dev/null bs=1M
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 6.375163 seconds, 160.6MB/s
CoreELEC:~ #

the 271MB/s seems pretty high for such a HDD, I increased the amount of data written to get a better picture:

CoreELEC:~ # rm -rf /var/media/android/test.speed && echo 3 > /proc/sys/vm/drop_caches && dd if=/dev/zero of=/var/media/android/test.speed bs=1M count=8192
8192+0 records in
8192+0 records out
8589934592 bytes (8.0GB) copied, 49.376390 seconds, 165.9MB/s
CoreELEC:~ # echo 3 > /proc/sys/vm/drop_caches && dd if=/var/media/android/test.speed of=/dev/null bs=1M
8192+0 records in
8192+0 records out
8589934592 bytes (8.0GB) copied, 68.781393 seconds, 119.1MB/s

broleke · 12 June 2020 09:50

I also try the Netflix Add-on to check for temps, but I cannot find a way to select a fullHD stream, it stays at 960p max.

As for spotifyd, it just works !

I’m using the port from @jant90 available here : Release: Spotifyd addon for CoreELEC

I’m not sure about the dac stuff. I used the headphones jack located on the dac board, but the sound seems saturated
On the other hand, the RCA outputs deliver a good sound

Ray · 12 June 2020 16:29

That’s slow. 17.3mbit/s?

If you can please create a samba share on the internal disk. Then try to transfer a big file from Windows using Gigabit Lan. I would like to know the speed.

broleke · 12 June 2020 16:31

I guess yes, but I would need another server for proper testing (I was using the GT-King for the iperf server).

Ray · 12 June 2020 16:35

If you have a laptop with Windows, linux or Mac then you don’t need another server. Iperf is not very reliable anyway

broleke · 12 June 2020 16:43

I’ve just tried the gs-king wlan and results are much better:

CoreELEC:~ # iperf3 udp test - iperf3 -c 192.168.179.30 -u -b 1000m
Connecting to host 192.168.179.30, port 5201
[  5] local 192.168.179.78 port 34220 connected to 192.168.179.30 port 5201
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec  22.5 MBytes   189 Mbits/sec  16287
[  5]   1.00-2.00   sec  22.7 MBytes   190 Mbits/sec  16430
[  5]   2.00-3.00   sec  22.6 MBytes   190 Mbits/sec  16383
[  5]   3.00-4.00   sec  22.7 MBytes   191 Mbits/sec  16461
[  5]   4.00-5.00   sec  22.3 MBytes   187 Mbits/sec  16168
[  5]   5.00-6.00   sec  22.8 MBytes   191 Mbits/sec  16483
[  5]   6.00-7.00   sec  21.3 MBytes   179 Mbits/sec  15421
[  5]   7.00-8.00   sec  17.7 MBytes   149 Mbits/sec  12839
[  5]   8.00-9.00   sec  22.7 MBytes   190 Mbits/sec  16405
[  5]   9.00-10.00  sec  22.7 MBytes   191 Mbits/sec  16472
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec   220 MBytes   185 Mbits/sec  0.000 ms  0/159349 (0%)  sender
[  5]   0.00-10.05  sec   220 MBytes   184 Mbits/sec  0.045 ms  0/159345 (0%)  receiver

iperf Done.
CoreELEC:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr C4:4E:AC:B3:AB:7B
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:14

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:206 errors:0 dropped:0 overruns:0 frame:0
          TX packets:206 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:209155 (204.2 KiB)  TX bytes:209155 (204.2 KiB)

wlan0     Link encap:Ethernet  HWaddr C0:84:7D:5A:31:8A
          inet addr:192.168.179.78  Bcast:192.168.179.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:70601 errors:0 dropped:2098 overruns:0 frame:0
          TX packets:343052 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:91432374 (87.1 MiB)  TX bytes:476986465 (454.8 MiB)

I also retried using the gb lan connection (with another server that the gt-king) and it worked better too.

CoreELEC:~ # iperf3 udp test - iperf3 -c 192.168.179.45 -u -b 1000m -p5349
Connecting to host 192.168.179.45, port 5349
[  5] local 192.168.179.78 port 42934 connected to 192.168.179.45 port 5349
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec  21.5 MBytes   180 Mbits/sec  15548
[  5]   1.00-2.00   sec  21.5 MBytes   180 Mbits/sec  15549
[  5]   2.00-3.00   sec  20.9 MBytes   175 Mbits/sec  15111
[  5]   3.00-4.00   sec  20.8 MBytes   175 Mbits/sec  15064
[  5]   4.00-5.00   sec  20.6 MBytes   173 Mbits/sec  14907
[  5]   5.00-6.00   sec  20.4 MBytes   171 Mbits/sec  14799
[  5]   6.00-7.00   sec  21.0 MBytes   176 Mbits/sec  15176
[  5]   7.00-8.00   sec  20.6 MBytes   173 Mbits/sec  14926
[  5]   8.00-9.00   sec  17.5 MBytes   146 Mbits/sec  12641
[  5]   9.00-10.00  sec  17.7 MBytes   148 Mbits/sec  12811
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec   202 MBytes   170 Mbits/sec  0.000 ms  0/146532 (0%)  sender
[  5]   0.00-10.00  sec   202 MBytes   170 Mbits/sec  0.188 ms  0/146517 (0%)  receiver

iperf Done.