• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

gilarelli's Achievements

  1. Hey @CarlosGomes , great blog! I found some times ago your post on your 3D printed nanopi case and it's really good and interesting! I didn't look further to try to solve my apt-get problem inside the chroot, as being able to download the packages was good enough for me - and my priority was to be able to boot as quickly as possible as all my documents are on this machine. Be careful with those 2.5 disks as I had the same RAID configuration and 3 out of 4 disks (WD black too) died at the same time... Luckily, I could get nearly 90% of my data back. My advice would be to use NAS designed disks (such as WD RED Pro) and not desktop ones as they are NOT designed to handle the kind of stress. And be careful with some WD disks: Anyway, I'm honored to have been able to help you! Cheers!
  2. You should try the mmc app to check your eMMC disk if you haven't already: # mmc extcsd read /dev/mmcblk1 |grep EXT_CSD eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01 eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x01 eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01 More info here on the values returned:
  3. Hey, just solved the same issue yesterday evening (bricked nanopi v1 after kernel update last sunday). Here is what I did to solve it: create a SDCard boot disk plug the SDCard and boot with it (it will bypass the eMMC card) set the root password and you should be able to ssh into it mount the eMMC filesystem rw chroot in the mount (lol) - with the right folder binded before (proc & sys) wget some files - for me it was those 3: linux-dtb-legacy-rk3399_21.08.2_arm64.deb linux-headers-legacy-rk3399_21.08.2_arm64.deb linux-image-legacy-rk3399_21.08.2_arm64.deb from here: (the new ones were still in /var/cache/apt/archives so I knew which ones were upgraded - and for some reason, I was unable to use apt-get in the chroot, that's why I had to download them directly - and I choose those versions because I thought that going back to the previous versions was enough) dpkg -i those files halt the nanopi and remove the SDCard restart and voilà I installed manually the linux-libc-dev package once booted with as I couldn't find it for downloading: # sudo apt-get install linux-libc-dev=21.08.2 -V To be sure that those packages will not be upgraded with future upgrades, I put a hold on them with "apt-mark hold": # apt-mark hold linux-libc-dev linux-dtb-legacy-rk3399 linux-headers-legacy-rk3399 linux-image-legacy-rk3399 # dpkg -l | grep "^hi" hi linux-dtb-legacy-rk3399 21.08.2 arm64 Linux DTB, version 4.4.213-rk3399 hi linux-headers-legacy-rk3399 21.08.2 arm64 Linux kernel headers for 4.4.213-rk3399 on arm64 hi linux-image-legacy-rk3399 21.08.2 arm64 Linux kernel, version 4.4.213-rk3399 hi linux-libc-dev:arm64 21.08.2 arm64 Armbian Linux support headers for userspace development Feel free to ask if you want any more information!
  4. Hi and sorry for the late answer - I had troubles with faulty drives in my RAID setup and thought that I lost everything and only solved this 2 weeks ago. Your system is on a sdcard? Because mine is on an eMMC, so I could boot on a sdcard. Maybe you can boot on your system with an USB pen drive (with a base OS installed on it) and access your OS on the sdcard will pluged in your board? If you can boot with another device while your sdcard is plugged in, then you've got good chances to get it back IMHO. Edit: PM me if you wish, as I'm not always on this forum and will probably miss your reply
  5. Hi, I noticed that on my board I didn't have notification with MOTD when updates were available and I think that I've found the culprit: In the file /usr/lib/armbian/armbian-apt-updates of the package linux-buster-root-legacy-nanopim4_20.08.17_arm64.deb, this line stop the script to go further : # give up if packages are broken [[ ! $(dpkg -l | grep ^..r) ]] && exit 0 If I remove the ! then it works (because the script, in fact, gives up if packages are not broken )
  6. It's solved ! So: after modifying the /boot/armbianEnv.txt file and booting in maintenance mode, I installed the same packages as the ones on the SDCard (*rk3399 instead of *rockchip64) and now it's working fine. I'll just check if everything is really fine, but this topic can be closed. Thanks for your help !
  7. I have a different kernel on the eMMC after running the armbian-config tool that the one on the SDCard: SDCard /boot emmc /boot config-4.4.213-rk3399 dtb-4.4.213-rk3399 initrd.img-4.4.213-rk3399 uInitrd-4.4.213-rk3399 vmlinux-4.4.213-rk3399 config-4.4.213-rockchip64 dtb-4.4.213-rockchip64 initrd.img-4.4.213-rockchip64 uInitrd-4.4.213-rockchip64 vmlinux-4.4.213-rockchip64 Here are some other differences SDCard /etc/armbian-release eMMC /etc/armbian-release BOARD=nanopim4 BOARD_NAME="NanoPi M4" BOARDFAMILY=rk3399 DISTRIBUTION_CODENAME=buster DISTRIBUTION_STATUS=supported VERSION=20.08.1 LINUXFAMILY=rk3399 BRANCH=legacy ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image BOARD=nanopim4 BOARD_NAME="NanoPi M4" BOARDFAMILY=rk3399 DISTRIBUTION_CODENAME=buster DISTRIBUTION_STATUS=supported VERSION=20.08.3 LINUXFAMILY=rk3399 BRANCH=legacy ARCH=arm64 IMAGE_TYPE=user-built BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image SDCard /etc/armbian-image-release eMMC /etc/armbian-image-release BOARD=nanopim4 BOARD_NAME="NanoPi M4" BOARDFAMILY=rk3399 BUILD_REPOSITORY_URL= DISTRIBUTION_CODENAME=buster DISTRIBUTION_STATUS=supported VERSION=20.08.1 LINUXFAMILY=rk3399 BRANCH=legacy ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image BOARD=nanopim4 BOARD_NAME="NanoPi M4" BOARDFAMILY=rk3399 BUILD_REPOSITORY_URL= DISTRIBUTION_CODENAME=buster DISTRIBUTION_STATUS=supported VERSION=20.02.1 LINUXFAMILY=rockchip64 BRANCH=current ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image Edit: I can boot on the eMMC system by changing the armbianEnv.txt ; go to maintenance mode, but that's already a start.
  8. Well, that didn't went as planned... The bad news is that it doesn't boot anymore: The "good" news is that I can boot with a legacy SDCard (yay !). I've tried the menu "Install/Update the bootloader on SD/eMMC" in the armbian-config tool, but I've got the same error... The legacy boot files seems to be all there on my /boot folder : -rw-r--r-- 1 root root 151 Sep 23 08:02 armbianEnv.txt -rw-r--r-- 1 root root 0 Sep 23 10:10 armbianEnv.txt.out -rw-r--r-- 1 root root 1536 Mar 9 2020 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Mar 9 2020 boot.bmp -rw-r--r-- 1 root root 2868 Mar 9 2020 boot.cmd -rw-r--r-- 1 root root 4882 Mar 9 2020 boot-desktop.png -rw-r--r-- 1 root root 2940 Mar 9 2020 boot.scr -rw-r--r-- 1 root root 160119 Sep 18 11:19 config-4.4.213-rockchip64 lrwxrwxrwx 1 root root 22 Sep 25 06:40 dtb -> dtb-4.4.213-rockchip64 drwxr-xr-x 3 root root 4096 Sep 25 06:40 dtb-4.4.213-rockchip64 lrwxrwxrwx 1 root root 26 Sep 25 06:40 Image -> vmlinux-4.4.213-rockchip64 -rw-r--r-- 1 root root 12165147 Sep 25 06:40 initrd.img-4.4.213-rockchip64 -rw-r--r-- 1 root root 0 Sep 25 06:40 .next -rw-r--r-- 1 root root 4553000 Sep 18 11:19 lrwxrwxrwx 1 root root 26 Sep 25 06:40 uInitrd -> uInitrd-4.4.213-rockchip64 -rw-r--r-- 1 root root 12165211 Sep 25 06:40 uInitrd-4.4.213-rockchip64 -rwxr-xr-x 1 root root 22114312 Sep 18 11:19 vmlinux-4.4.213-rockchip64 Any idea on what I can try to boot from the emmc again ?
  9. Hi, I would like to know if it is possible to switch from the current branch to the legacy one as I've read that the board will be much more stable with the older kernel ? I've installed my NanopiM4 last march, and I've experienced some random freezes of my board after some time (can take weeks). It seems that one of my solutions would be to use the legacy kernel as it is much more stable - information I got by reading the forums (something I haven't done before because I'm stupid and was in a hurry...). Is it possible to downgrade only the kernel at all ? Here are the packages that (I think) I have to replace : linux-buster-root-current-nanopim4/buster,now 20.08.3 arm64 [installed] linux-dtb-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-headers-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-image-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-u-boot-nanopim4-current/buster,now 20.08.1 arm64 [installed] With those packages, then : linux-buster-root-legacy-nanopim4 - armbian tweaks for buster on nanopim4 (legacy branch) linux-dtb-legacy-rockchip64 - linux dtb, version 4.4.213-rockchip64 linux-headers-legacy-rockchip64 - linux kernel headers for 4.4.213-rockchip64 on arm64 linux-image-legacy-rockchip64 - linux kernel, version 4.4.213-rockchip64 linux-u-boot-nanopim4-legacy - uboot loader 2020.07 Will that be enough or are more packages needed without screwing my install ? Should I use apt-get or do I have to use the armbian-config tool instead ? Is there an order to respect ?