TDCroPower Posted November 1, 2020 Share Posted November 1, 2020 Am 27.10.2020 um 07:45 schrieb flower: Yes, all docker container and system together is around 1gb ram usage. It uses zram after a while but that seems unrelated to that sync error. I never saw my ram completely filled. I dont use armbian nextcloud. I tweaked the mysql, redis, alpine variant which now runs stable on my old pc. Emby takes much ram there, but that container wasnt enabled on helios64. how did you display this ingenious output? I currently have a consumption of 88-90% on my Helios64 and suspect that a container is at fault. edit: ok with docker stats I got a similar output, but yours is even more "neat". CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 7b42ac796d6f pihole 0.13% 18.92MiB / 3.711GiB 0.50% 0B / 0B 2.87GB / 621MB 21 3d3d14ccf50d unifi-controller 3.85% 938.7MiB / 3.711GiB 24.70% 0B / 0B 6.22GB / 8.44GB 124 711e02b8f517 iobroker 15.94% 977.9MiB / 3.711GiB 25.73% 0B / 0B 4.79GB / 59.5GB 144 ae4aba42dce4 embyserver 2.94% 928MiB / 3.711GiB 24.42% 0B / 0B 13.2GB / 423MB 39 0150a9f8edfb portainer-ce 0.66% 14.87MiB / 3.711GiB 0.39% 5.95MB / 9.88MB 741MB / 136MB 15 Link to comment Share on other sites More sharing options...
flower Posted November 1, 2020 Share Posted November 1, 2020 1 hour ago, TDCroPower said: how did you display this ingenious output? apt install glances it also has a web interface - but it is resource intensive 1 Link to comment Share on other sites More sharing options...
aegiap Posted November 1, 2020 Share Posted November 1, 2020 Hello, I am trying to setup LACP aggregation on my helios64 between the two ethernet ports on the helios64 and I noticed I can set the MTU of the 2.5G port up to 9000 but the 1G ethernet port top at 1500. I use the 2.5G port as 1G as my network switch is gigabit only. Can you confirm that the 'first' port (aka the 1G port) is not jumbo frame compliant ? This error shows up when I try to change the size: rk_gmac-dwmac fe300000.ethernet eth0: must be stopped to change its MTU when the command is used: # ip link set mtu 3000 eth0 RTNETLINK answers: Device or resource busy Even when the link eth0 is down, the MTU cannot be changed. Kernel version: 5.8.16-rockchip64 #20.08.14 Packages versions: armbian-config : 20.08.20 armbian-firmware : 20.08.17 linux-dtb-current-rockchip64 : 20.08.14 linux-headers-current-rockchip64 : 20.08.14 linux-image-current-rockchip64 : 20.08.14 Link to comment Share on other sites More sharing options...
aprayoga Posted November 2, 2020 Share Posted November 2, 2020 22 hours ago, AurelianRQ said: Apparently Kobol team recommended to stay off the new kernels and to use their recommended ones. The problem is that every few days I get the Red System error led flashing and the box is not reachable so I have to force restart it so I can have access to it again and many many others. I don't see network activity as well on the front panel, is that pending as well ? It would be nice to have something functional that does not crash . Is this a hardware issue or just software issue ? Running your image 5.8.14-rockchip64 #20.08.10 SMP PREEMPT Tue Oct 13 16:58:01 CEST 2020 aarch64 GNU/Linux It seem you get a kernel crash. You should connect to serial console to get the kernel crash log. The network activity led is still not implemented yet. 20 hours ago, bverhagen said: Hi all, Last week I rendered my device unbootable by upgrading to 20.08.13 (it is stuck in U-boot rather than in starting the kernel though). This is 'known territory' though. So starting again from a vanilla install, 20.08.10 gets stuck in U-boot too, with the following error: Reveal hidden contents In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 253 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14792MB FwPartOffset=2000 , 0 StorageInit ok = 66004 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xded88 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Sep 23 2020 - 17:44:09 +0200) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... unable to select a mode *** Warning - No block device, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 5 ms (32.2 KiB/s) 14089265 bytes read in 599 ms (22.4 MiB/s) 27275776 bytes read in 1156 ms (22.5 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 2698 bytes read in 8 ms (329.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14089201 Bytes = 13.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Loading Ramdisk to f5174000, end f5ee3bf1 ... OK FDT and ATAGS support not compiled in - hanging ### ERROR ### Please RESET the board ### Installing to either SD or the eMMC rendered the same issue. I had to revert to 20.08.4 for my device to properly boot again (from SD, as eMMC does not work yet for this release). Since the 5.8.14 kernel is considered stable, I followed https://blog.kobol.io/2020/10/27/helios64-software-issue/ to upgrade to that kernel from 20.08.4 (using armbian-config). Fearing I would draw in the bad 5.8.16 kernel, I did not update anything else from 20.08.4. Unfortunately, this once again rendered my device unbootable, with the same error message as above. So for me, 20.08.10 seems to be not stable too. The Helios64 wiki claims it is though and many users of this forum seem to have no issues with 20.08.10 either. After another fresh install of 20.08.4 - and no further upgrades - the Helios 64 is running stable for over a week now (it had been running on this version stable for a month previously too). So this finally gets me to my question: Does anyone have any idea what goes wrong here? Does anyone have any suggestions on how to debug this? Why is my device unable to boot a fresh image for the 'stable' 20.08.10 release? At no point in the lifetime of the NAS did I tinker with U-boot. You are using old U-Boot. It couldn't get the required device tree file. There was file renaming applied to Armbian 20.08.8 (released on 13 Oct 2020). You can do 1. Get serial console 2. When U-Boot appear, spam Enter key until you get U-Boot prompt (=> ) 3. enter this command setenv fdtfile "rockchip/rk3399-kobol-helios64.dtb" bootd 4. After boot to Linux and login create symlink to new dtb sudo ln -sf rk3399-kobol-helios64.dtb /boot/dtb/rockchip/rk3399-helios64.dtb 5. Upgrade the bootloader using armbian-config, System > Install > 5 Install/Update the bootloader on SD/eMMC On next boot you should see U-Boot with more recent build date. On 11/1/2020 at 11:28 AM, djurny said: Have not checked if the buttons can be disabled in software yet (https://wiki.kobol.io/helios64/button/), perhaps the PMIC can be programmed in user space? Unfortunately the Reset and Power button wired directly to PMIC and no configuration on the PMIC to disable it. However, short press Power button (graceful shutdown) can be disabled by editing /etc/systemd/logind.conf and set HandlePowerKey=ignore Link to comment Share on other sites More sharing options...
gprovost Posted November 2, 2020 Author Share Posted November 2, 2020 @wurmfood and @357up it could be an issue with the wire harness. Can you do more try by swapping the cable between the bay slots and sata ports in order to narrow down the problem to the wire harness. If it's the case then you can contact us to support@kobol.io and we will help you from there. @AurelianRQ Regarding the issue for 2.5GbE port that doesn't perform properly when used in 1000Mb mode, unfortunately there is no fix that can be done by software. But it's actually pretty easy to fix on the board itself, it only requires to solder one wire between 2 points. Our mistake is that we didn't connect center tap of the 2.5Gb MAGJACK to 2.5V power rail (connected to ground instead) in order to provide common mode for MDI signals which is required for 1000Mb mode somehow. We will post a PCN bulletin to explain better this limitation and how to fix it for people who are up for a bit of soldering. @aegiap Unfortunately your link aggregation is going to be impacted to the issue mentioned above. The 2.5GbE doesn't perform properly in 1000Mb mode. 1 Link to comment Share on other sites More sharing options...
aegiap Posted November 2, 2020 Share Posted November 2, 2020 19 minutes ago, gprovost said: @AurelianRQRegarding the issue for 2.5GbE port that doesn't perform properly when used in 1000Mb mode, unfortunately there is no fix that can be done by software. But it's actually pretty easy to fix on the board itself, it only requires to solder one wire between 2 points. Our mistake is that we didn't connect center tap of the 2.5Gb MAGJACK to 2.5V power rail (connected to ground instead) in order to provide common mode for MDI signals which is required for 1000Mb mode somehow. We will post a PCN bulletin to explain better this limitation and how to fix it for people who are up for a bit of soldering. That's sad. 19 minutes ago, gprovost said: @aegiap Unfortunately your link aggregation is going to be impacted to the issue mentioned above. The 2.5GbE doesn't perform properly in 1000Mb mode. Any information about the jumbo frame support on the working ethernet port ? Link to comment Share on other sites More sharing options...
jessie Posted November 2, 2020 Share Posted November 2, 2020 Hello, after setting up my Helios64 kit, flashing an SD card, and setting up the serial, i connect to picocom and nobody's home. there are no HDD installed yet because I am testing the board itself, but it will not boot. I have tried multiple known-good sandisk microsds, both the armbian and ubuntu version (whatever was current as of 1 Nov) with no success. would maskrom mode be my first logical step to recovery? Link to comment Share on other sites More sharing options...
Z06Frank Posted November 2, 2020 Share Posted November 2, 2020 Has anyone tried moving Armbian OS over from the emmc to a sata drive? Any advantages to doing this? I found this in a banana pi forum:https://wiki.daniel-keil.de/projekte/banana-pro/install-armbian-to-a-sata-drive Had no problem with general install of armbian to the emmc and updating firmware thru armbian-config (worked like a charm). Link to comment Share on other sites More sharing options...
TDCroPower Posted November 2, 2020 Share Posted November 2, 2020 vor 12 Stunden schrieb gprovost: @AurelianRQ Regarding the issue for 2.5GbE port that doesn't perform properly when used in 1000Mb mode, unfortunately there is no fix that can be done by software. But it's actually pretty easy to fix on the board itself, it only requires to solder one wire between 2 points. Our mistake is that we didn't connect center tap of the 2.5Gb MAGJACK to 2.5V power rail (connected to ground instead) in order to provide common mode for MDI signals which is required for 1000Mb mode somehow. We will post a PCN bulletin to explain better this limitation and how to fix it for people who are up for a bit of soldering. Soldering? No problem here ! I can help users from Germany to fix their helios board once the solution is released. 4 Link to comment Share on other sites More sharing options...
gprovost Posted November 3, 2020 Author Share Posted November 3, 2020 @jessie You mean even the system led doesn't blink after 20-30 sec you powered up the system ? Yes the maskrom mode would be the next step : https://wiki.kobol.io/helios64/maskrom/ Link to comment Share on other sites More sharing options...
gprovost Posted November 3, 2020 Author Share Posted November 3, 2020 @TDCroPower Here the small hardware tweak ;-) WARNING Please understand we are not responsible for any damage you might do to the board ! 5 Link to comment Share on other sites More sharing options...
RockBian Posted November 3, 2020 Share Posted November 3, 2020 On 11/1/2020 at 7:29 PM, TonyMac32 said: power delivery through USB-C. Oh and mode switching. So if it set to the mode you want by default it should be ok, but the better question is why was it eating clock cycles So far I have found that the I2C bus generates ~20k interrupts sec: root@helios64:/proc# cat interrupts && sleep 10 && cat interrupts <snip> 43: 4107025 0 0 0 0 0 GICv3 88 Level ff3d0000.i2c <snip> 43: 4311805 0 0 0 0 0 GICv3 88 Level ff3d0000.i2c but I don't know what exactly that means. A simple i2cdetect on that bus generates 351 interrupts. So it's not bits. 17 hours ago, Z06Frank said: Has anyone tried moving Armbian OS over from the emmc to a sata drive? Any advantages to doing this? I found this in a banana pi forum:https://wiki.daniel-keil.de/projekte/banana-pro/install-armbian-to-a-sata-drive Had no problem with general install of armbian to the emmc and up: dating firmware thru armbian-config (worked like a charm). Yes I did. I wrote about it in the comments section of sata in the wiki: https://wiki.kobol.io/helios64/sata/ Link to comment Share on other sites More sharing options...
SIGSEGV Posted November 4, 2020 Share Posted November 4, 2020 Is the U-Boot image installed on the SPI Flash? If not is it possible to install it there? The instructions on the Wiki page say to write it to the microSD card and have the board boot from the microSD. Link to comment Share on other sites More sharing options...
gprovost Posted November 4, 2020 Author Share Posted November 4, 2020 15 hours ago, RockBian said: So far I have found that the I2C bus generates ~20k interrupts sec: Yes we are aware of that, something wrong with fusb302 driver, @aprayoga is looking into it. Link to comment Share on other sites More sharing options...
axeleroy Posted November 4, 2020 Share Posted November 4, 2020 Hello, I just tried to copy my Armbian install from the SD Card to the eMMC, but I'm not sure it has been successful, how can I be sure? For information, I also encrypted my HDDs using LUKS and I use MergerFS to pool their data. Boot sequence from serial console Spoiler DDR Version 1.24 20191016 In soft reset SRX channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x82 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 323 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=61056MB FwPartOffset=2000 , 0 StorageInit ok = 66065 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xdcfd8 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Oct 13 2020 - 16:49:59 +0200) SoC: Rockchip rk3399 Reset cause: RST DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 5 ms (32.2 KiB/s) 16452750 bytes read in 700 ms (22.4 MiB/s) 27275776 bytes read in 1156 ms (22.5 MiB/s) 79946 bytes read in 10 ms (7.6 MiB/s) 2698 bytes read in 8 ms (329.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16452686 Bytes = 15.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f4f35000, end f5ee5c4e ... OK Loading Device Tree to 00000000f4eb9000, end 00000000f4f34fff ... OK Starting kernel ... openmediavault 5.5.14-1 (Usul) helios64 ttyS2 Output from df Spoiler axel@helios64:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 1869984 0 1869984 0% /dev tmpfs 389128 10396 378732 3% /run /dev/mmcblk0p1 60910176 5312260 54945884 9% / tmpfs 1945632 0 1945632 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 1945632 0 1945632 0% /sys/fs/cgroup tmpfs 1945632 12 1945620 1% /tmp folder2ram 1945632 14632 1931000 1% /var/log folder2ram 1945632 0 1945632 0% /var/tmp folder2ram 1945632 484 1945148 1% /var/lib/openmediavault/rrd folder2ram 1945632 724 1944908 1% /var/spool folder2ram 1945632 13988 1931644 1% /var/lib/rrdcached folder2ram 1945632 4 1945628 1% /var/lib/monit folder2ram 1945632 1288 1944344 1% /var/cache/samba /dev/mapper/sda-crypt 2883204744 1150794608 1732393752 40% /srv/dev-disk-by-label-parity1 /dev/mapper/sdb-crypt 2883204744 1127952968 1755235392 40% /srv/dev-disk-by-label-data1 /dev/mapper/sdc-crypt 2883204744 1127947312 1755241048 40% /srv/dev-disk-by-label-data2 tmpfs 389124 0 389124 0% /run/user/1000 pool0:65b1923f-43cc-499b-b4c3-265b982c7f8a 5766409488 2255900280 3510476440 40% /srv/65b1923f-43cc-499b-b4c3-265b982c7f8a /etc/fstab Spoiler axel@helios64:~$ cat /etc/fstab UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 # >>> [openmediavault] [...] Link to comment Share on other sites More sharing options...
RockBian Posted November 4, 2020 Share Posted November 4, 2020 1 hour ago, axeleroy said: /dev/mmcblk0p1 60910176 5312260 54945884 9% / As far as I can see it booted from sd, or at least the root file system is an 64GB sd card. To boot from emmc you have to remove the sd card. 15 hours ago, gprovost said: Yes we are aware of that, something wrong with fusb302 driver, @aprayoga is looking into it. OK, thanks. Link to comment Share on other sites More sharing options...
axeleroy Posted November 4, 2020 Share Posted November 4, 2020 Welp, I removed the SD card and it did not boot to eMMC. Spoiler picocom v2.2 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 1500000 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, Type [C-a] [C-h] to see available commands Terminal ready [ 5681.802401] reboot: Power down [ 5�DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 254 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67773 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xdcfd8 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Oct 13 2020 - 16:49:59 +0200) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr ## Executing script at 00500000 Wrong image format for "source" command SCRIPT FAILED: continuing... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device scanning bus for devices... Device 0: unknown device Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.110 (2 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-64-62-66-d0-03-7c Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8006E Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8006 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A800 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399-helios64 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default Speed: 1000, full duplex *** ERROR: `serverip' not set Config file not found Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.110 (3 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.110 (1 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET => DDR Version 1.24 20191016 Link to comment Share on other sites More sharing options...
TDCroPower Posted November 4, 2020 Share Posted November 4, 2020 vor 2 Stunden schrieb axeleroy: Welp, I removed the SD card and it did not boot to eMMC. Versteckten Inhalt anzeigen picocom v2.2 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 1500000 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, Type [C-a] [C-h] to see available commands Terminal ready [ 5681.802401] reboot: Power down [ 5�DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 254 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67773 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xdcfd8 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Oct 13 2020 - 16:49:59 +0200) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr ## Executing script at 00500000 Wrong image format for "source" command SCRIPT FAILED: continuing... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device scanning bus for devices... Device 0: unknown device Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.110 (2 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-64-62-66-d0-03-7c Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8006E Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8006 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A800 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399-helios64 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399 Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm Speed: 1000, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default Speed: 1000, full duplex *** ERROR: `serverip' not set Config file not found Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.110 (3 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.110 (1 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET => DDR Version 1.24 20191016 use the command df -h to show from which storage the system was loaded. If it says /dev/mmcblk1p1 it is the eMMC and if it says /dev/mmcblk0p1 it is still your microSD. You can also tell from the memory size whether it is the eMMC (has 15GB) or your microSD. root@helios64:~# df -h Filesystem Size Used Avail Use% Mounted on udev 1.8G 0 1.8G 0% /dev tmpfs 381M 37M 344M 10% /run /dev/mmcblk1p1 15G 7.8G 5.7G 59% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup tmpfs 1.9G 4.0K 1.9G 1% /tmp Link to comment Share on other sites More sharing options...
djurny Posted November 5, 2020 Share Posted November 5, 2020 (edited) Spoiler Hi all, A few days ago, I started my backup scripting on the Helios64 box. This is an rsync that will grab files from the Helios4 box and stores it on local disk. To my surprise, the backup took over 20 hours. At the time I did not think much of it, as it was a new month, and every new month means a new non-incremental backup will take place. Yesterday I decided to have a closer look at what had happened. To my surprise, I found that eth0 was running at 100Mbps? Spoiler Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: ug Wake-on: d Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes Now I know for a fact that the switch connected to it, is capable of 1Gbps. After changing the cabling, I managed to rule out at least all the cables I have lying around - as all reported 100Mbps, short cables, long cables, cables that were working fine in the Helios4 box. Next up, was to try an intermediate 1Gbps switch: This worked; Helios64 showed 1000Mbps speed - but - it did not show any network activity, the box was unreachable from the outside and the box was not able to reach anything on the outside. After connecting the original cable back, it flipped to 100Mbps again, but at least connectivity was there. Anyone have any idea on what to check next? Thanks, Groetjes, Edited November 6, 2020 by djurny Issue was cabling after all. Link to comment Share on other sites More sharing options...
RockBian Posted November 5, 2020 Share Posted November 5, 2020 23 hours ago, axeleroy said: Scanning mmc 0:1... Found U-Boot script /boot/boot.scr ## Executing script at 00500000 Wrong image format for "source" command SCRIPT FAILED: continuing... The boot.scr script is damaged. You can try to recreate it. Boot from sd once again, mount the emmc filesystem and recreate mkdir /tmp/mmc mount /dev/mmc/mmcblk1p1 /tmp/mmc chroot /tmp/mmc mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr 1 Link to comment Share on other sites More sharing options...
gprovost Posted November 6, 2020 Author Share Posted November 6, 2020 13 hours ago, djurny said: Anyone have any idea on what to check next? Well according to your ethtool ouput. Your switch only advertise 10 and 100baseT/Full. What switch model it is ? Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full I think you need to try again with the other switch you mentioned about. What switch model it is ? Link to comment Share on other sites More sharing options...
djurny Posted November 6, 2020 Share Posted November 6, 2020 Hi, 17 hours ago, gprovost said: Well according to your ethtool ouput. Your switch only advertise 10 and 100baseT/Full. What switch model it is ? I think you need to try again with the other switch you mentioned about. What switch model it is ? Both are Zyxel switches, one is 16 ports GS1100 -16 and the other is 8 ports GS-108Bv3. Both are Gbps capable, as shown by other devices connected to the same switch: Helios4: Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Just now, I tried yet another set of cables to connect to the Helios64 box, and it seems I have bought several batches of cat "5e" cables, with stress on "5e". Looks like a cabling issue still. I never noticed this, as most are connected to either Raspberry Pi2b or OrangePi zero devices (see ethtool output from one of the Pis below, connected to the same 16ports Gbps capable switch). I already ordered another batch of [apparently] shielded cat 6 cables, hopefully they are indeed shielded, cat 6 and not cat "6". Raspberry Pi2b: Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Please disregard my previous post. Thanks, Groetjes, Link to comment Share on other sites More sharing options...
RockBian Posted November 7, 2020 Share Posted November 7, 2020 What is a normal CPU temperature on idle? Mine is never lower than 40°C, at an ambient temperature of 19°C, which makes me wonder how much electricity it draws. Is it possible that the GPU is actively doing nothing, or something like that? If so, can it be switched off? The NAS has been placed vertically, with the CPU on bottom. The disk in slot 5 is 22°C. Link to comment Share on other sites More sharing options...
Rmleonard Posted November 7, 2020 Share Posted November 7, 2020 On 10/7/2020 at 7:45 PM, gprovost said: Could you please send us an email to support@kobol.io with some pictures in order to check what's wrong with your enclosure unit. When I received my Helios64 - the case was out of whack -- the alignment was off by about 1/4 inch (3-5mm or so).... since it was out of whack -- I gave it one - with a rubber mallet - worked perfectly - a gentle but sharp tap - once on both sides (I'll go through my phone later today to see if I took pictures) Rich 1 Link to comment Share on other sites More sharing options...
SIGSEGV Posted November 7, 2020 Share Posted November 7, 2020 7 hours ago, RockBian said: What is a normal CPU temperature on idle? Mine is never lower than 40°C, at an ambient temperature of 19°C, which makes me wonder how much electricity it draws. Is it possible that the GPU is actively doing nothing, or something like that? If so, can it be switched off? The NAS has been placed vertically, with the CPU on bottom. The disk in slot 5 is 22°C. Mine is running somewhere around 44 - 52°C - at an ambient temperature of 23°C. CPU frequency for both Big and Little cores are around 408 MHz according to 'htop' Link to comment Share on other sites More sharing options...
barnumbirr Posted November 7, 2020 Share Posted November 7, 2020 14 minutes ago, SIGSEGV said: Mine is running somewhere around 44 - 52°C - at an ambient temperature of 23°C. CPU frequency for both Big and Little cores are around 408 MHz according to 'htop' Weird, htop on my Helios doesn't seem to be the armbian version anymore: no temperature, no frequency. Could you please share your APT sources.list so I can check I didn't accidentally overwrite mine. Link to comment Share on other sites More sharing options...
AurelianRQ Posted November 7, 2020 Share Posted November 7, 2020 On 11/2/2020 at 11:58 AM, gprovost said: @wurmfood and @357up it could be an issue with the wire harness. Can you do more try by swapping the cable between the bay slots and sata ports in order to narrow down the problem to the wire harness. If it's the case then you can contact us to support@kobol.io and we will help you from there. @AurelianRQ Regarding the issue for 2.5GbE port that doesn't perform properly when used in 1000Mb mode, unfortunately there is no fix that can be done by software. But it's actually pretty easy to fix on the board itself, it only requires to solder one wire between 2 points. Our mistake is that we didn't connect center tap of the 2.5Gb MAGJACK to 2.5V power rail (connected to ground instead) in order to provide common mode for MDI signals which is required for 1000Mb mode somehow. We will post a PCN bulletin to explain better this limitation and how to fix it for people who are up for a bit of soldering. @aegiap Unfortunately your link aggregation is going to be impacted to the issue mentioned above. The 2.5GbE doesn't perform properly in 1000Mb mode. T On 11/2/2020 at 11:58 AM, gprovost said: Cool, well I can do that I guess if that does not void the warranty in this case, Honestly to get a 300 E switch to manage 2.5 or 100 E adapters that I don't even know they work, I prefer to fix it the easy way if possible. Thanks and I guess waiting for your details. Link to comment Share on other sites More sharing options...
gprovost Posted November 8, 2020 Author Share Posted November 8, 2020 @AurelianRQ You post is a bit messed up (can you edit/fix it ?). You can find multi-gigabit switch at 150euros check Zyxel XGS1010-12 or even QNAP QSW-1105-5T. As for the instruction to fix the 1000Mb mode on the 2.5Gbe port, it was posted above. Link to comment Share on other sites More sharing options...
JeffDwork Posted November 8, 2020 Share Posted November 8, 2020 Assembled my first (of two) helios64s. I needed to insulate the chassis around the leds, but the USB-C connector fit perfectly into the back panel opening. I noticed a problem with the sata cable for slot 1 where it passes under the chassis to reach the board socket. The chassis has a sharp edge that presses onto the cable, so I padded it with some electrical tape. In the box containing the system board there was a plastic bag with two jumper plugs and two screws and a threaded spacer. What is the purpose of the spacer and screws? I had stability problems using Windows to install OS to eMMC. Windows recognized the eMMC as a storage device for a few seconds after helios64 started but then it disappeared. It finally worked after about 10 tries. I was using a USB3 extension cable to reach my pc - perhaps that was the cause. Thanks, Jeff Link to comment Share on other sites More sharing options...
gprovost Posted November 8, 2020 Author Share Posted November 8, 2020 @JeffDwork Well noted on your feedback, yes we will improve cable routing in next revision. As for the screws and spacer on the picture those are to be used when installing a device in the M.2 SATA slot. https://wiki.kobol.io/helios64/m2/#installation Link to comment Share on other sites More sharing options...
Recommended Posts