TDCroPower
-
Posts
99 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by TDCroPower
-
-
@going I am not quite sure if I can use my instructions from back then for the problem.
Is this variant correct to change the kernel?
If so which one is best to use?edit:
unfortunately the switch to the following previous kernel probably didn't work, after installing the debs the image still boots from 6.1.50 ?
https://mirror.yandex.ru/mirrors/armbian/apt/pool/main/l/linux-6.1.11-rockchip64/
In the root filesystem you can also see symlinks to it...root@helios64:/# ll total 64448 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin/ drwxr-xr-x 2 root root 4096 Mar 30 2022 boot/ drwxr-xr-x 2 root root 4096 Oct 3 01:11 dev/ drwxr-xr-x 114 root root 12288 Sep 29 02:15 etc/ drwxr-xr-x 3 root root 4096 Apr 4 2022 export/ drwxr-xr-x 5 root root 4096 Jun 10 2021 home/ lrwxrwxrwx 1 root root 41 Sep 27 01:11 initrd.img -> boot/initrd.img-6.1.50-current-rockchip64 lrwxrwxrwx 1 root root 41 Sep 27 01:11 initrd.img.old -> boot/initrd.img-6.1.50-current-rockchip64 -rwxr-xr-x 1 root root 0 Mar 21 2022 inxi* lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib/ -rw-r--r-- 1 root root 304640 Feb 25 2023 linux-dtb-edge-rockchip64_23.02.2_arm64.deb -rw-r--r-- 1 root root 12522640 Feb 25 2023 linux-headers-edge-rockchip64_23.02.2_arm64.deb -rw-r--r-- 1 root root 53078604 Feb 25 2023 linux-image-edge-rockchip64_23.02.2_arm64.deb drwx------ 5 root root 4096 Oct 5 2020 lost+found/ drwxr-xr-x 5 root root 4096 Apr 2 2022 media/ drwxr-xr-x 2 root root 4096 Apr 2 2022 mnt/ drwxr-xr-x 4 root root 4096 Dec 2 2020 opt/ dr-xr-xr-x 2 root root 4096 Mar 30 2022 proc/ drwx------ 9 root root 4096 Sep 29 01:44 root/ drwxr-xr-x 2 root root 4096 Apr 2 2022 run/ lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin/ drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux/ drwxr-xr-x 6 root root 4096 Apr 3 2022 srv/ dr-xr-xr-x 2 root root 4096 Mar 30 2022 sys/ lrwxrwxrwx 1 root root 42 Sep 29 02:15 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Apr 2 2022 tmp/ drwxr-xr-x 12 root root 4096 Nov 27 2020 usr/ drwxr-xr-x 14 root root 4096 Oct 6 2020 var/ lrwxrwxrwx 1 root root 38 Sep 27 01:11 vmlinuz -> boot/vmlinuz-6.1.50-current-rockchip64 lrwxrwxrwx 1 root root 38 Sep 27 01:11 vmlinuz.old -> boot/vmlinuz-6.1.50-current-rockchip64here the install log...
root@helios64:/# dpkg -i *.deb Selecting previously unselected package linux-dtb-edge-rockchip64. (Reading database ... 92306 files and directories currently installed.) Preparing to unpack linux-dtb-edge-rockchip64_23.02.2_arm64.deb ... Unpacking linux-dtb-edge-rockchip64 (23.02.2) ... Selecting previously unselected package linux-headers-edge-rockchip64. Preparing to unpack linux-headers-edge-rockchip64_23.02.2_arm64.deb ... Unpacking linux-headers-edge-rockchip64 (23.02.2) ... Selecting previously unselected package linux-image-edge-rockchip64. Preparing to unpack linux-image-edge-rockchip64_23.02.2_arm64.deb ... stat: cannot statx '/proc/1/root/.': No such file or directory Unpacking linux-image-edge-rockchip64 (23.02.2) ... Setting up linux-dtb-edge-rockchip64 (23.02.2) ... Setting up linux-headers-edge-rockchip64 (23.02.2) ... Compiling headers - please wait ... grep: /proc/cpuinfo: No such file or directory Setting up linux-image-edge-rockchip64 (23.02.2) ... update-initramfs: Generating /boot/initrd.img-6.1.11-rockchip64 W: Couldn't identify type of root file system for fsck hook W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays. W: mdadm: failed to auto-generate temporary mdadm.conf file. update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.11-rockchip64 Image Name: uInitrd Created: Tue Oct 3 01:14:25 2023 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15116959 Bytes = 14762.66 KiB = 14.42 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.11-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.1.11-rockchip64' update-initramfs: Armbian: done.edit2:
i have just try another kernel from here...
https://mirror.yandex.ru/mirrors/armbian/apt/pool/main/l/linux-5.10.63-rockchip64/root@helios64:/# dpkg -i *.deb dpkg: warning: downgrading linux-dtb-current-rockchip64 from 23.8.1 to 21.08.2 (Reading database ... 121330 files and directories currently installed.) Preparing to unpack linux-dtb-current-rockchip64_21.08.2_arm64.deb ... Unpacking linux-dtb-current-rockchip64 (21.08.2) over (23.8.1) ... dpkg: warning: downgrading linux-headers-current-rockchip64 from 23.8.1 to 21.08.2 Preparing to unpack linux-headers-current-rockchip64_21.08.2_arm64.deb ... Armbian 'linux-headers-current-rockchip64' for '6.1.50-current-rockchip64': 'prerm' starting. Cleaning directory /usr/src/linux-headers-6.1.50-current-rockchip64 ... Armbian 'linux-headers-current-rockchip64' for '6.1.50-current-rockchip64': 'prerm' finishing. Unpacking linux-headers-current-rockchip64 (21.08.2) over (23.8.1) ... dpkg: warning: downgrading linux-image-current-rockchip64 from 23.8.1 to 21.08.2 Preparing to unpack linux-image-current-rockchip64_21.08.2_arm64.deb ... Armbian 'linux-image-current-rockchip64' for '6.1.50-current-rockchip64': 'prerm' starting. Armbian 'linux-image-current-rockchip64' for '6.1.50-current-rockchip64': 'prerm' finishing. stat: cannot statx '/proc/1/root/.': No such file or directory Unpacking linux-image-current-rockchip64 (21.08.2) over (23.8.1) ... Armbian 'linux-image-current-rockchip64' for '6.1.50-current-rockchip64': 'postrm' starting. Armbian 'linux-image-current-rockchip64' for '6.1.50-current-rockchip64': 'postrm' finishing. Setting up linux-dtb-current-rockchip64 (21.08.2) ... Setting up linux-headers-current-rockchip64 (21.08.2) ... Compiling headers - please wait ... grep: /proc/cpuinfo: No such file or directory grep: /proc/cpuinfo: No such file or directory Setting up linux-image-current-rockchip64 (21.08.2) ... update-initramfs: Generating /boot/initrd.img-5.10.63-rockchip64 W: Couldn't identify type of root file system for fsck hook W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays. W: mdadm: failed to auto-generate temporary mdadm.conf file. update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-5.10.63-rockchip64 Image Name: uInitrd Created: Tue Oct 3 01:42:41 2023 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16200156 Bytes = 15820.46 KiB = 15.45 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-5.10.63-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-5.10.63-rockchip64' update-initramfs: Armbian: done.i am still a little confused about the symlinks of initrd.img, initrd.img.old, vmlinuz and vmlinuz.old which still point to 6.1.50.
Should these be changed as well?
Because when I look in the mounted boot directory, I see both installed kernels...root@helios64:/# ll boot/ total 128664 -rw-r--r-- 1 root root 221500 Sep 8 2021 config-5.10.63-rockchip64 -rw-r--r-- 1 root root 239553 Feb 18 2023 config-6.1.11-rockchip64 lrwxrwxrwx 1 root root 22 Oct 3 01:41 dtb -> dtb-5.10.63-rockchip64/ drwxr-xr-x 6 root root 4096 Oct 3 01:41 dtb-5.10.63-rockchip64/ drwxr-xr-x 3 root root 4096 Oct 3 01:13 dtb-6.1.11-rockchip64/ lrwxrwxrwx 1 root root 26 Oct 3 01:42 Image -> vmlinuz-5.10.63-rockchip64 -rw-r--r-- 1 root root 16200156 Oct 3 01:42 initrd.img-5.10.63-rockchip64 -rw-r--r-- 1 root root 15116959 Oct 3 01:14 initrd.img-6.1.11-rockchip64 -rw-r--r-- 1 root root 5840624 Sep 8 2021 System.map-5.10.63-rockchip64 -rw-r--r-- 1 root root 4907435 Feb 18 2023 System.map-6.1.11-rockchip64 lrwxrwxrwx 1 root root 26 Oct 3 01:42 uInitrd -> uInitrd-5.10.63-rockchip64 -rw-r--r-- 1 root root 16200220 Oct 3 01:42 uInitrd-5.10.63-rockchip64 -rw-r--r-- 1 root root 15117023 Oct 3 01:14 uInitrd-6.1.11-rockchip64 -rw-r--r-- 1 root root 28580352 Sep 8 2021 vmlinuz-5.10.63-rockchip64 -rw-r--r-- 1 root root 29295104 Feb 18 2023 vmlinuz-6.1.11-rockchip64edit3:
i seem to have managed to switch to the old kernel....
root@helios64:/# uname -a Linux helios64 6.1.50-current-rockchip64 #3 SMP PREEMPT Wed Aug 30 14:11:13 UTC 2023 aarch64 GNU/Linuxi booted from the ssd for this and did the installation directly in the running system....
root@helios64:/# dpkg -i *.deb (Reading database ... 93629 files and directories currently installed.) Preparing to unpack linux-dtb-current-rockchip64_21.08.2_arm64.deb ... Unpacking linux-dtb-current-rockchip64 (21.08.2) over (21.08.2) ... Preparing to unpack linux-headers-current-rockchip64_21.08.2_arm64.deb ... Unpacking linux-headers-current-rockchip64 (21.08.2) over (21.08.2) ... Preparing to unpack linux-image-current-rockchip64_21.08.2_arm64.deb ... Unpacking linux-image-current-rockchip64 (21.08.2) over (21.08.2) ... Setting up linux-dtb-current-rockchip64 (21.08.2) ... Setting up linux-headers-current-rockchip64 (21.08.2) ... Compiling headers - please wait ... Setting up linux-image-current-rockchip64 (21.08.2) ... update-initramfs: Generating /boot/initrd.img-5.10.63-rockchip64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-5.10.63-rockchip64 Image Name: uInitrd Created: Tue Oct 3 02:21:00 2023 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16595743 Bytes = 16206.78 KiB = 15.83 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-5.10.63-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-5.10.63-rockchip64' update-initramfs: Armbian: done. Free space after deleting the package linux-image-current-rockchip64 in /boot: 3.5G root@helios64:/# root@helios64:/# ll /boot/ total 100344 lrwxrwxrwx 1 root root 26 Oct 3 02:21 Image -> vmlinuz-5.10.63-rockchip64 -rw-r--r-- 1 root root 5840624 Sep 8 2021 System.map-5.10.63-rockchip64 -rw-r--r-- 1 root root 4805119 Aug 30 18:33 System.map-6.1.50-current-rockchip64 -rw-r--r-- 1 root root 166 Oct 3 01:52 armbianEnv.txt -rw-r--r-- 1 root root 1536 Oct 15 2020 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Oct 15 2020 boot.bmp -rw-r--r-- 1 root root 3113 Apr 2 2022 boot.cmd -rw-r--r-- 1 root root 3185 Apr 2 2022 boot.scr -rw-r--r-- 1 root root 221500 Sep 8 2021 config-5.10.63-rockchip64 -rw-r--r-- 1 root root 238929 Aug 30 18:33 config-6.1.50-current-rockchip64 lrwxrwxrwx 1 root root 22 Oct 3 02:19 dtb -> dtb-5.10.63-rockchip64/ drwxr-xr-x 6 root root 4096 Oct 3 02:18 dtb-5.10.63-rockchip64/ drwxr-xr-x 3 root root 4096 Sep 27 01:09 dtb-6.1.50-current-rockchip64/ -rw-r--r-- 1 root root 16595743 Oct 3 02:21 initrd.img-5.10.63-rockchip64 lrwxrwxrwx 1 root root 26 Oct 3 02:21 uInitrd -> uInitrd-5.10.63-rockchip64 -rw-r--r-- 1 root root 16595807 Oct 3 02:21 uInitrd-5.10.63-rockchip64 -rw-r--r-- 1 root root 28580352 Sep 8 2021 vmlinuz-5.10.63-rockchip64 -rw-r--r-- 1 root root 29792768 Aug 30 18:33 vmlinuz-6.1.50-current-rockchip64in the time as I write this, the helios unfortunately just restarts by itself
-
-
-
@phidauex ah, that's right, I totally forgot, I used it to track and log the startup problems back then.
I will record it and post it here....edit:
the first failed start...
edit2:
another failed start, but with verbository = 7...
and after rebooting a good start...
and after a few minutes a crash and reboot...
edit3:
maybe we should open ticket?
https://armbian.atlassian.net/jira/software/c/projects/AR/issues/?filter=allissues
-
-
Because I can get into the system from time to time, I can fortunately clean up or copy data away to start from scratch in the worst case.
Unfortunately, I can't find any information on what the problem could be.I hope someone still gets lost here and can give us tips
-
I updated my Helios64 last night and now it keeps rebooting.
Every now and then it runs for a few minutes so I can log in via ssh and then it reboots all at once.
Installed on the system is only OMV 6.9.1-1 (Shaitan) and Docker with the image of Emby.the system runs on an installed M.2 SSD on slot 1.
4TB WD Reds are installed in slots 2, 3 and 5.Welcome to Armbian 23.8.1 Bullseye with Linux 6.1.50-current-rockchip64 No end-user support: community creations System load: 9% Up time: 4 min Memory usage: 17% of 3.77G IP: 172.18.0.1 172.17.0.1 192.168.180.5 CPU temp: 42°C Usage of /: 7% of 117Ghelios@helios64:~# uname -a Linux helios64 6.1.50-current-rockchip64 #3 SMP PREEMPT Wed Aug 30 14:11:13 UTC 2023 aarch64 GNU/Linux helios@helios64:~# helios@helios64:~# cat /etc/os-release PRETTY_NAME="Armbian 23.8.1 bullseye" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 23.8.1 bullseye"the limits set for the CPU...
helios@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_max_freq 1416000 1800000 helios@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_min_freq 408000 408000 helios@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq 1008000 408000does anyone have an idea where I can start looking for the error?
-
if who has installed OMV 5, this should be updated before update to Bullseye!
OMV 5 still uses pam_tally2.so which is no longer present with the lib package in Bullseye.
With OMV 6 this is only corrected ! -
On the actual topic.
Has anyone been able to upgrade an OMV 5 installation from Buster to Bullseye?
OMV 5 seems to use pam_tally2 and this is no longer supported in the current version of libpam-modules 1.4.0-9.
You are supposed to change this, but I read at OMV that the change was/will be implemented in OMV 6.Is it possible to work around this without upgrading to OMV6 or do I have to get in with an OMV 5 -> OMV 6 upgrade first and then bullseye?
Unfortunately OMV 6 is only in release candidate 1 status.
edit:
the attempt to edit the files used by OMV 5 with pam_tally2 with pam_faillock.so unfortunately did not work, because OMV 5 still searches for the pam_tally2 and thus a login in the WebInterface is not possible afterwards.
-
-
@RockBian I had already added a partition to the SSD, nevertheless I see only the OMV RAID5 partition...
root@helios64:~# parted -l Model: ATA NT-128 (scsi) Disk /dev/sda: 128GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End Size File system Flags 1 0.00B 128GB 128GB ext4 -
Hi to all,
after the 16GB of the eMMC is slowly reaching my limits, I installed a 128GB M.2 SSD and wanted to use the kobol tutorial to transfer the system data on it...
https://wiki.kobol.io/helios64/install/transfer/#transfer-rootfs-from-emmc-to-sata-or-usb... unfortunately I see at position 4 only /dev/md0 instead of the M.2 Sata on /dev/sda
root@helios64:/dev# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 119.2G 0 disk sdb 8:16 0 3.7T 0 disk └─md0 9:0 0 7.3T 0 raid5 /srv/dev-disk-by-label-nas sdc 8:32 0 3.7T 0 disk └─md0 9:0 0 7.3T 0 raid5 /srv/dev-disk-by-label-nas sdd 8:48 0 3.7T 0 disk └─md0 9:0 0 7.3T 0 raid5 /srv/dev-disk-by-label-nas mmcblk2 179:0 0 14.6G 0 disk └─mmcblk2p1 179:1 0 14.4G 0 part / mmcblk2boot0 179:32 0 4M 1 disk mmcblk2boot1 179:64 0 4M 1 disk root@helios64:/dev#does anyone know what my error is here?
I use OMV and have 3 hard disk running in RAID 5.
Previously the hard drives were connected to SATA 1, SATA 3 and SATA 5.
I had to change the hard drive on SATA 1 to 2, because the M.2 needs the SATA 1.
Is it perhaps because of this? -
Use instead of jumper 11 the jumper 10, so you should be able to see and write your emmc in running mode.
See also here how... -
-
It worked, I have my eMMC system back!
Here are all the steps in case someone else has the problem and wants to repair his eMMC image...
1. download a previous Helios64 image from here...
https://wiki.kobol.io/download/
2. install the image on a microSD e.g. for Windows and macOS there is Etcher...
https://www.balena.io/etcher/
3a. boot your Helios64 with the microSD and Jumper 10, see here...
https://wiki.kobol.io/helios64/troubleshoot/#how-to-force-boot-from-microsd
3b. Alternative: from the serial console press a key on the keyboard while u-boot start. You will get the u-boot prompt.From this prompt write and press enter. Helios64 will boot from SD... (thx @prahal)
run bootcmd_mmc14. if you are logged in as root user (normal users must put a sudo in front of the commands) execute the following commands...
root@helios64:~# mkdir -p /mnt/system root@helios64:~# mount /dev/mmcblk2p1 /mnt/system root@helios64:~# cd /mnt/system/
5. The contents of the /mnt/system directory should now be filled with the contents of your eMMC....root@helios64:/mnt/system# ll total 80 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 03:01 boot drwxr-xr-x 2 root root 4096 Oct 15 2020 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var
6. now download the 3 old packages...
root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-dtb-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-headers-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-image-current-rockchip64_21.05.4_arm64.deb
7. now changes the root directory...
root@helios64:/mnt/system# chroot /mnt/system root@helios64:/# pwd / root@helios64:/# ll total 50996 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 14:56 boot drwxr-xr-x 2 root root 4096 Sep 1 16:15 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib -rw-r--r-- 1 root root 314304 Jul 8 19:32 linux-dtb-current-rockchip64_21.05.4_arm64.deb -rw-r--r-- 1 root root 11527696 Jul 8 19:32 linux-headers-current-rockchip64_21.05.4_arm64.deb -rw-r--r-- 1 root root 40290884 Jul 8 19:33 linux-image-current-rockchip64_21.05.4_arm64.deb drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var
8. now installs the downloaded packages...
root@helios64:/# dpkg -i *.deb dpkg: warning: downgrading linux-dtb-current-rockchip64 from 21.08.1 to 21.05.4 (Reading database ... 62558 files and directories currently installed.) Preparing to unpack linux-dtb-current-rockchip64_21.05.4_arm64.deb ... Unpacking linux-dtb-current-rockchip64 (21.05.4) over (21.08.1) ... Selecting previously unselected package linux-headers-current-rockchip64. Preparing to unpack linux-headers-current-rockchip64_21.05.4_arm64.deb ... Unpacking linux-headers-current-rockchip64 (21.05.4) ... dpkg: warning: downgrading linux-image-current-rockchip64 from 21.08.1 to 21.05.4 Preparing to unpack linux-image-current-rockchip64_21.05.4_arm64.deb ... update-initramfs: Deleting /boot/initrd.img-5.10.60-rockchip64 Removing obsolete file uInitrd-5.10.60-rockchip64 stat: cannot stat '/proc/1/root/.': No such file or directory Unpacking linux-image-current-rockchip64 (21.05.4) over (21.08.1) ... Setting up linux-dtb-current-rockchip64 (21.05.4) ... Setting up linux-headers-current-rockchip64 (21.05.4) ... Compiling headers - please wait ... grep: /proc/cpuinfo: No such file or directory grep: /proc/cpuinfo: No such file or directory Setting up linux-image-current-rockchip64 (21.05.4) ... update-initramfs: Generating /boot/initrd.img-5.10.43-rockchip64 W: Couldn't identify type of root file system for fsck hook update-initramfs: Converting to u-boot format
9. reset the root change with exit and restart your helios64 with reboot...
root@helios64:/# exit exit root@helios64:/mnt/system# reboot
10. after a reboot you should now boot from the eMMC again...
root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 21.08.1 Buster with Linux 5.10.43-rockchip64 No end-user support: built from trunk System load: 74% Up time: 3 min Memory usage: 34% of 3.77G IP: 172.18.0.1 172.19.0.1 172.20.0.1 172.17.0.1 192.168.180.5 CPU temp: 66°C Usage of /: 87% of 15G [ 0 security updates available, 3 updates total: apt upgrade ] Last check: 2021-09-01 16:38 [ General system configuration (beta): armbian-config ] Last login: Wed Sep 1 16:26:23 2021 root@helios64:~# root@helios64:~# uname -a Linux helios64 5.10.43-rockchip64 #21.05.4 SMP PREEMPT Wed Jun 16 08:02:12 UTC 2021 aarch64 GNU/Linux root@helios64:~#
11. if the eMMC was used you can see with mount...
root@helios64:~# mount | grep /dev/mmc /dev/mmcblk2p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/log type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/tmp type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/lib/openmediavault/rrd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/spool type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/lib/rrdcached type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/lib/monit type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/cache/samba type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600)
-
ok i got a little further.
I wrote the armbian image 21.02.3 with 5.10.21-rockchip64 on a SD and triggered the boot from microSD via jumper 10...https://wiki.kobol.io/helios64/troubleshoot/#how-to-force-boot-from-microsd
i am back on the box and was able to mount the emmc under /dev/mmcblk2p1...
root@helios64:~# ll /mnt/ total 0 root@helios64:~# mkdir -p /mnt/system root@helios64:~# mount /dev/mmcblk2p1 /mnt/system root@helios64:~# cd /mnt/system/ root@helios64:/mnt/system# ll total 80 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 03:01 boot drwxr-xr-x 2 root root 4096 Oct 15 2020 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var root@helios64:/mnt/system#
remains only the question how/where I install the packages that were described here...
https://forum.armbian.com/topic/18855-upgrading-to-bullseye/?tab=comments#comment-128189maybe it has something to do with the boot/ directory....
root@helios64:/mnt/system# ll boot/ total 64696 -rw-r--r-- 1 root root 166 Sep 1 03:01 armbianEnv.txt -rw-r--r-- 1 root root 1536 Oct 15 2020 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Oct 15 2020 boot.bmp -rw-r--r-- 1 root root 3113 Oct 15 2020 boot.cmd -rw-r--r-- 1 root root 3185 Oct 15 2020 boot.scr -rw-r--r-- 1 root root 221489 Aug 25 20:56 config-5.10.60-rockchip64 lrwxrwxrwx 1 root root 22 Sep 1 02:31 dtb -> dtb-5.10.60-rockchip64 drwxr-xr-x 6 root root 4096 Sep 1 02:30 dtb-5.10.60-rockchip64 lrwxrwxrwx 1 root root 26 Sep 1 02:31 Image -> vmlinuz-5.10.60-rockchip64 -rw-r--r-- 1 root root 15767106 Sep 1 02:32 initrd.img-5.10.60-rockchip64 -rw-r--r-- 1 root root 5839373 Aug 25 20:56 System.map-5.10.60-rockchip64 lrwxrwxrwx 1 root root 26 Sep 1 02:32 uInitrd -> uInitrd-5.10.60-rockchip64 -rw-r--r-- 1 root root 15767170 Sep 1 02:32 uInitrd-5.10.60-rockchip64 -rw-r--r-- 1 root root 28580352 Aug 25 20:56 vmlinuz-5.10.60-rockchip64 root@helios64:/mnt/system#
-
vor 17 Minuten schrieb ebin-dev:
emmc is accessible with linux 5.10.43. The emmc partition is not write protected in any way - it is simply not writable with linux 5.10.60.
In order to recover you will need to boot a system from SD with linux 5.10.43. If you have a valid backup of your emmc on SD - just boot from that one and use armbian-config to copy it to emmc (System&security -> Install to -> system on emmc, boot from emmc).
I don't have a clean backup of the eMMC unfortunately, will probably have to introduce in the future to have a backup for such a step.
I found the following tutorial to clone the system from the emmc to a connected media....
https://averagelinuxuser.com/backup-and-restore-your-linux-system-with-rsync/After that I would have to somehow downgrade my emmc backup on the media?
Does anyone have a tip which files have to be replaced?After that I should clone from the fixed medium to a new SD and boot from it, now I should see my system again or?
And then in the armbian-config with...
System&security -> Install to -> system on emmc, boot from emmc
... to clone the image again on the emmc... -
vor 16 Stunden schrieb ebin-dev:
@bunducafeYou could try to update the bootloader on emmc first. @IcerJo claims that this would make it writable again. Then you could downgrade linux on emmc to 21.05.4. There is no need to format emmc - alternatively you could also repair errors in the filesystem with 'fsck -f /dev/mmcblk2p1'. You will see that something needs to be corrected. If you trust that everything is fine after that you are done.
The intention of this thread was to show that Buster can be upgraded to Bullseye and that it is stable with Armbian 21.05.4 with linux-5.10.43.
Issues arise if Buster or Bullseye installations are updated from 21.05.4 to Armbian 21.08.1 with linux-5.10.60 against the recommendations earlier in this thread, because emmc will not be accessible anymore without i/o errors.
Edit: You also could boot a fresh Armbian 21.05.4 off SD and rsync with it the content from emmc to another bootable SD. Then you continue to downgrade linux on that second SD (booted) ... and rsync the result back to emmc.
Maybe somebody else could explain how to downgrade the kernel on emmc using a chrooted environment.
I unfortunately ran fsck last night as mentioned by you, which probably does not boot cleanly or I no longer have ssh access.
Maybe I have to connect it to the monitor and check what I see in the bootlog.If someone could offer a step by step guide on how to recover I would be very grateful!
-
vor 13 Stunden schrieb IcerJo:
Ahh, so it's essentially a ticking time bomb? I pushed the bootloader from an SD card and got my system back up yesterday.
Can you explain how you got your system back?
Unfortunately, I also updated to 21.08.01 tonight and urgently need a downgrade to get the system back.
Would be very grateful to you! -
My upgrade is done.
Before...
root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.08.21 Buster with Linux 5.8.17-rockchip64 No end-user support: work in progress System load: 8% Up time: 16 days 6:46 Memory usage: 77% of 3.71G IP: 172.18.0.1 192.168.180.5 CPU temp: 47°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-config ] Last login: Fri Nov 27 02:53:45 2020 from 192.168.180.83 root@helios64:~#After...
root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.11 Buster with Linux 5.9.10-rockchip64 No end-user support: work in progress System load: 53% Up time: 0 min Memory usage: 8% of 3.71G IP: 192.168.180.5 CPU temp: 43°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-config ] Last login: Fri Nov 27 03:42:24 2020 from 192.168.180.83 root@helios64:~# -
After the official release of Armbian 20.11 today I would like to collect feedback if and how the firmware runs on the Helios64.
Is it possible to upgrade already or should we Helios64 owners wait?
apt-get lists these already...
armbian-config/buster,buster 20.11 all [upgradable from: 20.08.22] armbian-firmware/buster,buster 20.11 all [upgradable from: 20.08.22] libgssapi-krb5-2/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libk5crypto3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5-3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5support0/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libldap-2.4-2/stable,stable 2.4.47+dfsg-3+deb10u4 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u3] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u4 all [upgradable from: 2.4.47+dfsg-3+deb10u3] linux-buster-root-current-helios64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-dtb-current-rockchip64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-image-current-rockchip64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-u-boot-helios64-current/buster 20.11 arm64 [upgradable from: 20.08.21] openmediavault/usul,usul,usul,usul 5.5.17-3 all [upgradable from: 5.5.16-1]The changelog is here...
-
vor einer Stunde schrieb Jaques-Ludwig:
I have installed Debian OS on eMMC. Now I want to install Debian on a SD-Card to boot from there. I thought I do Backup of eMMC with fsarchiver and restore it on a SD-Card. Then to put the SD-Card on the back of the Helios-NAS. Is Helios64 booting now from SD-Card or eMMC? How can I see it? Both memories are shown in the drive-section of OMV.
What do I have to do, if I don't want to start from eMMC anymore? Do I have to delete it and if yes, how does it work? Is it possible to switch through both boot-modes?
Thanks a lot,
Jaques-Ludwig
you can use the boot mode jumper to switch between eMMC (P10) and microSD (P11) boot, see the Helios wiki...
https://wiki.kobol.io/helios64/jumper/
@Helios Team...
what is the current image status?
Is it now possible to upgrade from 20.08.10 to the current version?
By now we are already at 20.08.22...armbian-config/buster,buster 20.08.22 all [upgradable from: 20.08.10] armbian-firmware/buster,buster 20.08.22 all [upgradable from: 20.08.10] libfreetype6/stable,stable 2.9.1-3+deb10u2 arm64 [upgradable from: 2.9.1-3+deb10u1] libldap-2.4-2/stable,stable 2.4.47+dfsg-3+deb10u3 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u2] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u3 all [upgradable from: 2.4.47+dfsg-3+deb10u2] linux-buster-root-current-helios64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-dtb-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-image-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-libc-dev/stable,stable 4.19.152-1 arm64 [upgradable from: 4.19.146-1] linux-u-boot-helios64-current/buster 20.08.21 arm64 [upgradable from: 20.08.10] openmediavault-omvextrasorg/buster,buster 5.4.2 all [upgradable from: 5.4.1] openmediavault/usul,usul,usul,usul 5.5.16-1 all [upgradable from: 5.5.12-1] salt-common/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] salt-minion/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] tzdata/stable-updates,stable-updates 2020d-0+deb10u1 all [upgradable from: 2020a-0+deb10u1] -
vor 2 Stunden schrieb axeleroy:
Welp, I removed the SD card and it did not boot to eMMC.
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 environmentIn: 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) foundDevice 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 20191016use 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 -
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.
Helios64 unstable with 23.8.1 Bullseye and 6.1.50-current-rockchip64
in Rockchip
Posted · Edited by TDCroPower
@going thanks for the tutorial, i used /dev/sda1 in step 4 as it is my m.2 ssd partition.
Was that not correct?
Is not /dev/mmcblk2p1 the partition of the emmc ?
root@helios64:~# fdisk -l Disk /dev/mmcblk2: 14.56 GiB, 15634268160 bytes, 30535680 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x728863aa Device Boot Start End Sectors Size Id Type /dev/mmcblk2p1 32768 30230303 30197536 14.4G 83 Linux Disk /dev/mmcblk1: 59.69 GiB, 64088965120 bytes, 125173760 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x8b029f90 Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 32768 123895807 123863040 59.1G 83 Linux Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NT-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0182fc84 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 250069679 250067632 119.2G 83 Linux Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EFRX-68W Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EFRX-68W Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdd: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EFRX-68N Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/md127: 7.28 TiB, 8001302822912 bytes, 15627544576 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 1048576 bytes Disk /dev/zram0: 1.89 GiB, 2025508864 bytes, 494509 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram2: 1.89 GiB, 2025508864 bytes, 494509 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytesTo your important question:
I now have Armbian 21.08.2 Bullseye with Linux 5.10.63-rockchip64 running stably via the microSD for over 60 minutes without reboots.
I haven't had time to open the case today to look for the battery but as I understand it on the Kobol wiki there is no battery installed as the UPS takes over this task...
https://wiki.kobol.io/helios64/rtc/
Since also other kernel leads to the similar problem, I suspect that it is perhaps the update of the OMV to 6.9.1?
The first time it crashed was after the update when I wanted to apply the settings in the OMV web frontend.
@phidauex Did you also install OMV and update it to version 6.9.1?
edit:
I installed the latest image Armbian 23.8.1 Bookworm with Linux 6.1.50-current-rockchip64 on the microSD for further testing and again the system remains stable, currently over 90 minutes.
edit2:
i didn't have to remove the motherboard from the case to look for the battery, you can remove the front cover and see the battery connector from there.
The battery is not installed as described in the kobol wiki.