Z06Frank

  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Z06Frank's Achievements

  1. I updated kernel and firmware to this version of Armbian 21.02.3 Buster with Linux 5.10.21-rockchip64 (latest) and ran the u-boot update per "ebin-dev" and Kobol developers. Update went smooth as silk....thanks
  2. Thanks for the response and recommendation. I wasn't sure if it was necessary to keep this updated during the early development of firmware/software of this board.
  3. I have the same exact issue as with Gareth above where the boot OSs on the EMMc and OS on my M2 SATA and I can't upgrade the bootloader for the SAME reasons. FYI...I'm on 5.10.16-rockchip64 Armbian 21.02.2 My "lsblk" key info is: mmcblk2 179:0 0 14.6G 0 disk └─mmcblk2p1 179:1 0 14.4G 0 part /media/mmcboot mmcblk2boot0 179:32 0 4M 1 disk mmcblk2boot1 179:64 0 4M 1 disk Not sure what you needed with the cat /proc/mounts so here's the dump (minus some other drive and ram non necessary info): sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=1868980k,nr_inodes=467245,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=389020k,mode=755 0 0 /dev/sda1 / ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 configfs /sys/kernel/config configfs rw,relatime 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 tmpfs /tmp tmpfs rw,relatime 0 0 /dev/mmcblk2p1 /media/mmcboot ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 0 0 /dev/mmcblk2p1 /boot ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 0 0 tracefs /sys/kernel/debug/tracing tracefs rw,relatime 0 0 nsfs /run/docker/netns/6406a1ca38e9 nsfs rw 0 0 tmpfs /run/user/0 tmpfs rw,nosuid,nodev,relatime,size=389016k,mode=700 0 0 Can I assume the I change the lines from above to this below????? (i.e, to the correct Armbian version of 21.02.2 and my bootloader of mmcblk2). cd /usr/lib/linux-u-boot-current-helios64_21.02.2_arm64 dd if=idbloader.bin of=/dev/mmcblk2 seek=64 conv=notrunc dd if=uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc dd if=trust.bin of=/dev/mmcblk2 seek=24576 conv=notrunc I want to make sure I do this right to avoid a serious boot error Thanks Kobol team!!!
  4. I know this is an older topic but I have one question as I'm setting up some details to the HHD's on my OMV (5.5.20-1 Usul) based Helios64 NAS. I'm on the latest kernel 5.9.4 rockchip64. I have my primary OS on an M2 SATA drive and 3 8TB HHD's using Snapraid and UnionFS (2 in pool & 1 in parity). I have not set up HD-Idle yet....but plan to shortly. Question is why turn off write cache in the OMV "Disks" interface? PS...set APM=127 and spindown_time=240 on all three HHDs
  5. djurny......thanks for your help but I decided to restart from scratch knowing the issue. Back up and running now. I set CPU Governor to "Performance". I read and make some power management changes in Windows 10 (esp ACHI Power Management) to get max performance for SSD/HHDs file transfer and turned off any idling/power savings. I also wanted an option on this tweak to prevent data loss on power loss to hdparm.conf: http://ubuntuhandbook.org/index.php/2014/01/disable-disk-caching-prevent-data-loss/
  6. Here is the serial output...... 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, 253 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 = 67768 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=0xdd6b0 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 31 2020 - 08:21:38 +0100) 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 3185 bytes read in 18 ms (171.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 194 bytes read in 15 ms (11.7 KiB/s) 17971400 bytes read in 1723 ms (9.9 MiB/s) 27507200 bytes read in 2627 ms (10 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! 276 bytes read in 19 ms (13.7 KiB/s) Applying user provided DT overlay dwc3-0-device.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17971336 Bytes = 17.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Loading Ramdisk to f4dc3000, end f5ee6888 ... OK FDT and ATAGS support not compiled in - hanging ### ERROR ### Please RESET the board ###
  7. Note: I tried the basic reset button; the HHD's spin (and blue LED's flicker) for about 25 sec and it freezes with all blue LED's solid.
  8. I just froze my system late last night. I cannot SSH or get into the web interface. I tried to let the battery backup discharge and reboot to no avail. All lights on the the LEDs sit a solid blue. I had updated Armbian a few days ago to the latest stable build: "5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux" to get the eth1 working again. I have latest OMV and Armbian running on the M2 slot. What I was doing was doing a full data transfer of my media via Ethernet and samba shares from a Windows 10 PC server setup. I let this go overnight and forgot I had hibernation set on the Windows PC. Woke up today to find the Helios 64 in a frozen state....and can't determine what's going on without help here. Thoughts on what to do besides a wipe and restart of the OS/OMV. I'm guess with a larger high speed transfer (i.e. running about 150mb/sec) that I ran into a stability issue and I can't figure out how to read the kernal panic/or logs. Any ideas what I can try?
  9. I can confirm on "5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux" and checking the ethernet ports via CLI sudo ip link show that both eth0 and eth1 are showing in the output. Thanks......
  10. I' upgraded to OK.....I upgraded to "Armbian 20.11 Buster with Linux 5.9.10-rockchip64" and I want to add the USB-C DAS. One noob question.....do I create/add the dwc3-0-device.dts file to the folder: /boot/dtb/rockchip/ ? Thanks....
  11. 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).