Viald Posted December 1, 2019 Posted December 1, 2019 Hello. I have an error when trying to upgrade the kernel root@jdm:/boot# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-image-aml-g12 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/27.2 MB of archives. After this operation, 31.3 MB of additional disk space will be used. Do you want to continue? [Y/n] Reading changelogs... Done (Reading database ... 53286 files and directories currently installed.) Preparing to unpack .../linux-image-aml-g12_5.99_arm64.deb ... Unpacking linux-image-aml-g12 (5.99) over (5.98) .............................................................................................................................................................................................] dpkg: error processing archive /var/cache/apt/archives/linux-image-aml-g12_5.99_arm64.deb (--unpack): unable to make backup link of './boot/System.map-5.3.0-aml-g12' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) mv: cannot stat '/boot/vmlinuz-5.3.0-aml-g12': No such file or directory......................................................................................................................................................................] Errors were encountered while processing: /var/cache/apt/archives/linux-image-aml-g12_5.99_arm64. The content of /boot root@jdm:/boot# ll total 40802 drwxr-xr-x 2 root root 2048 Oct 4 12:21 'System Volume Information' -rwxr-xr-x 1 root root 4381366 Oct 8 11:22 System.map-5.3.0-aml-g12 -rwxr-xr-x 1 root root 660 Oct 2 09:01 aml_autoscript -rwxr-xr-x 1 root root 588 Oct 2 09:01 aml_autoscript.cmd -rwxr-xr-x 1 root root 651 Oct 2 09:01 aml_autoscript.zip -rwxr-xr-x 1 root root 1536 Oct 2 09:01 armbian_first_run.txt.template -rwxr-xr-x 1 root root 4882 Oct 2 09:01 boot-desktop.png -rwxr-xr-x 1 root root 38518 Oct 2 09:01 boot.bmp -rwxr-xr-x 1 root root 709 Oct 2 09:09 boot.ini -rwxr-xr-x 1 root root 177990 Oct 8 11:22 config-5.3.0-aml-g12 drwxr-xr-x 3 root root 6144 Oct 16 12:49 dtb drwxr-xr-x 2 root root 6144 Oct 2 09:00 dtb-5.3.0-aml-g12 -rwxr-xr-x 1 root root 679 Oct 2 09:01 emmc_autoscript -rwxr-xr-x 1 root root 607 Oct 2 09:01 emmc_autoscript.cmd drwxr-xr-x 2 root root 2048 Oct 2 09:01 extlinux -rwxr-xr-x 1 root root 7934926 Nov 17 13:42 initrd.img-5.3.0-aml-g12 drwxr-xr-x 2 root root 2048 Oct 12 12:02 old -rwxr-xr-x 1 root root 1112 Oct 2 09:01 s905_autoscript -rwxr-xr-x 1 root root 1040 Oct 2 09:01 s905_autoscript.cmd -rwxr-xr-x 1 root root 209 Oct 2 09:01 uEnv.ini -rwxr-xr-x 1 root root 7934990 Nov 17 13:42 uInitrd -rwxr-xr-x 1 root root 21262344 Oct 8 11:22 zImage root@jdm:/boot# And the kernel release: root@jdm:/boot# uname -a Linux jdm 5.3.0-aml-g12 #5.98 SMP PREEMPT Tue Oct 8 12:22:08 MSK 2019 aarch64 GNU/Linux Thank you
guidol Posted December 1, 2019 Posted December 1, 2019 I also the "update-problem" on my Sunvell T95K Pro (S912) - so I did leave the actual version intact and will update in future with a complete new installation, because @balbes150 is now using the new naming convention from armbian like 19.11.3 Welcome to Ubuntu Bionic with Armbian Linux 5.4.0-rc3-aml-g12 package bsp-kernel[5.98] u-boot[5.98] dtb[Khadas VIM2] firmware[5.98] config[5.98] branch[dev]
Viald Posted December 2, 2019 Author Posted December 2, 2019 Ok, but I didn't plan to do a complete new installation and I want my system to be up to date. So how can I do ?
Igor Posted December 2, 2019 Posted December 2, 2019 45 minutes ago, Viald said: Ok, but I didn't plan to do a complete new installation and I want my system to be up to date. So how can I do ? You are using unofficial builds. Upgrade is not supported on them, not possible to cover ... It can work or not. Your problem.
Viald Posted December 2, 2019 Author Posted December 2, 2019 May I wrong, the kernel update comes from @balbes150 and it's not an official update. If I want a official Debian release, where can I find it ?
Igor Posted December 2, 2019 Posted December 2, 2019 7 minutes ago, Viald said: May I wrong, the kernel update comes from @balbes150 and it's not an official update. Ahaa, I see. He was indeed trying to provide updates via apt.armbian.com but perhaps something went wrong ... well, I added those files to our repository but I have no options nor will to test if update really works. 7 minutes ago, Viald said: If I want a official Debian release, where can I find it ? There is no official Debian release & Debian is a community project. IMO you already receive the best and the only possible support there is for this hardware.
Viald Posted December 2, 2019 Author Posted December 2, 2019 I just tried, still the same issue trying to "Unpacking linux-image-aml-g12 (5.99) over (5.98)"
Igor Posted December 2, 2019 Posted December 2, 2019 Is this first boot partition FAT? Are you perhaps running out of space? Perhaps scripts are just broken ... we will need to wait for Oleg to explain what is wrong.
balbes150 Posted December 3, 2019 Posted December 3, 2019 No need to try to update "over the top", this does not always work yet (problem with names, parsing in current versions does not allow this to be done correctly). Before installing a new package, you must remove the old kernel package. I recommend that you make a copy of the entire partition /boot and the module directory (for example, in the user /root directory) before deleting , if something goes wrong, you can restore the files to their original form (run from external media and copy them back). It is convenient to use Synaptic to remove kernel packages and then install new ones.
Viald Posted December 4, 2019 Author Posted December 4, 2019 Thank you all for your help. I'm running the server release so I can't use Synaptic. I will try with apt command.
Viald Posted December 4, 2019 Author Posted December 4, 2019 root@jdm:~# tar cvf ~/boot.051219.tar /boot root@jdm:~# dpkg -l | grep linux-image ii linux-image-aml-g12 5.98 arm64 Linux kernel, version 5.3.0-aml-g12 root@jdm:~# sudo apt-get purge linux-image-aml-g12 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-aml-g12* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 110 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 53311 files and directories currently installed.) Removing linux-image-aml-g12 (5.98) ... update-initramfs: Deleting /boot/initrd.img-5.3.0-aml-g12 (Reading database ... 51042 files and directories currently installed.) Purging configuration files for linux-image-aml-g12 (5.98) ... dpkg: warning: while removing linux-image-aml-g12, directory '/boot/dtb' not empty so not removed root@jdm:~# apt update Hit:1 https://deb.nodesource.com/node_12.x buster InRelease Hit:2 http://mirrors.dotsrc.org/armbian-apt buster InRelease Hit:3 http://security.debian.org buster/updates InRelease Hit:4 http://cdn-fastly.deb.debian.org/debian buster InRelease Hit:5 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease Hit:6 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@jdm:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@jdm:~# apt install linux-image-aml-g12 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: linux-image-aml-g12 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/27.2 MB of archives. After this operation, 141 MB of additional disk space will be used. Selecting previously unselected package linux-image-aml-g12. (Reading database ... 51041 files and directories currently installed.) Preparing to unpack .../linux-image-aml-g12_5.99_arm64.deb ... Unpacking linux-image-aml-g12 (5.99) ...######################................................................................................................................................................................................] Setting up linux-image-aml-g12 (5.99) ...#################################################################....................................................................................................................................] update-initramfs: Generating /boot/initrd.img-5.3.0-aml-g12###########################################################################################........................................................................................] update-initramfs: Converting to u-boot format root@jdm:~# apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://mirrors.dotsrc.org/armbian-apt buster InRelease Hit:3 https://deb.nodesource.com/node_12.x buster InRelease Hit:4 http://cdn-fastly.deb.debian.org/debian buster InRelease Hit:5 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease Hit:6 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@jdm:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@jdm:~# dpkg -l | grep linux-image ii linux-image-aml-g12 5.99 arm64 Linux kernel, version 5.3.0-aml-g12 5.99 And voila root@jdm:/boot# uname -a Linux jdm 5.3.0-aml-g12 #5.98 SMP PREEMPT Tue Oct 8 12:22:08 MSK 2019 aarch64 GNU/Linux Need to reboot
Viald Posted December 5, 2019 Author Posted December 5, 2019 @balbes150 it seems that you enabled UAS driver in 5.99. It hangs my system at boot time
Viald Posted December 5, 2019 Author Posted December 5, 2019 I have added this option in boot.ini file to blacklist the UAS driver usb-storage.quirks=2109:0715:u
balbes150 Posted December 6, 2019 Posted December 6, 2019 Kernel 5.98 uses two packages (image and dtb). 5.99 the kernel uses a single shared package. You need to delete both packages (image and dtb).
Viald Posted December 7, 2019 Author Posted December 7, 2019 root@jdm:~# dpkg -l | grep dtb ii linux-dtb-aml-g12 5.98 arm64 Linux DTB, version 5.3.0-aml-g12 Indeed ! Should I have to reinstall 5.99 after removing linux-dtb-aml-g12 ? And should it solves my UAS issue ?
Viald Posted December 7, 2019 Author Posted December 7, 2019 ii linux-buster-root-aml-g12 5.98 arm64 Armbian tweaks for buster on aml-g12 (default branch) ii linux-u-boot-aml-g12-default 5.98 arm64 Uboot loader 2019.07-rc3 @balbes150 What about those one ?
balbes150 Posted December 7, 2019 Posted December 7, 2019 12 minutes ago, Viald said: Indeed ! Should I have to reinstall 5.99 after removing linux-dtb-aml-g12 ? And should it solves my UAS issue ? No need to reinstall. USB operation depends on the equipment and DTB settings (all individually).
Viald Posted December 7, 2019 Author Posted December 7, 2019 It seems that the 5.99 kernel package doesn't install meson-g12b-odroid-n2.dtb file in dtb directory. It only installs amlogic and rockchip directories. Update: My bad the file is in amlogic directory. I have to modify my boot.ini file.
balbes150 Posted December 9, 2019 Posted December 9, 2019 On 12/7/2019 at 9:34 PM, Viald said: It seems that the 5.99 kernel package doesn't install meson-g12b-odroid-n2.dtb file in dtb directory. It only installs amlogic and rockchip directories. Update: My bad the file is in amlogic directory. I have to modify my boot.ini file. Did I understand correctly that you have N2 ? Try the latest generic images (RK+AML), there's a 5.4 kernel. I pay attention, these images setup DTB is executed in other files (the description is in a subject about these images). By the way, which startup option (u-boot placement) do you use ?
Viald Posted December 14, 2019 Author Posted December 14, 2019 On 12/9/2019 at 10:52 AM, balbes150 said: Did I understand correctly that you have N2 ? Yes I have a N2. On 12/9/2019 at 10:52 AM, balbes150 said: Try the latest generic images (RK+AML), there's a 5.4 kernel Could you please point me the link ? On 12/9/2019 at 10:52 AM, balbes150 said: By the way, which startup option (u-boot placement) do you use ? I'm using your odroid-n2 SPI u-boot image https://yadi.sk/d/pHxaRAs-tZiei/UPDATE_U-BOOT_odroid_n2
balbes150 Posted December 14, 2019 Posted December 14, 2019 5 minutes ago, Viald said: Could you please point me the link ? 5 minutes ago, Viald said: I'm using your odroid-n2 SPI u-boot image With this u-boot, everything should work properly on N2 with the new universal image. I pay attention if the switch is included in the mode of start of u-boot from SPI. DTB settings are performed in the file " uEnv.ini", the file "boot.ini" is not used to specify DTB. If you need to pass additional parameters to the kernel, this should be done in the "bootargs" section of the file "uEnv.ini". If the boot switch is enabled on the SD, u-boot-2019 from the SD card is used and the settings are made only in "extlinux.conf" (the file "boot.ini " "uEnv.ini" boot loader not used).
Recommended Posts