HC1 kernel update gone wrong?

[MichaIng]

Just linking the GitHub issue here, which explains the reason and ships another functional alternative: https://github.com/armbian/build/issues/3085

[belegdol]

I did as you suggested, but after doing the changes and installing 21.08.8.3 aka 5.4.181 kernel I have 5.4.177 leftovers in /boot:

Quote

$ sudo apt install ./linux-{dtb,image}-current-odroidxu4_21.08.8.3_armhf.deb 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'linux-dtb-current-odroidxu4' instead of './linux-dtb-current-odroidxu4_21.08.8.3_armhf.deb'
Note, selecting 'linux-image-current-odroidxu4' instead of './linux-image-current-odroidxu4_21.08.8.3_armhf.deb'
The following packages will be upgraded:
  linux-dtb-current-odroidxu4 linux-image-current-odroidxu4
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/30.4 MB of archives.
After this operation, 7,168 B of additional disk space will be used.
Get:1 /home/julas/linux-dtb-current-odroidxu4_21.08.8.3_armhf.deb linux-dtb-current-odroidxu4 armhf 21.08.8.3 [120 kB]
Get:2 /home/julas/linux-image-current-odroidxu4_21.08.8.3_armhf.deb linux-image-current-odroidxu4 armhf 21.08.8.3 [30.3 MB]
(Reading database ... 48784 files and directories currently installed.)
Preparing to unpack .../linux-dtb-current-odroidxu4_21.08.8.3_armhf.deb ...
Unpacking linux-dtb-current-odroidxu4 (21.08.8.3) over (21.08.8.2) ...
Preparing to unpack .../linux-image-current-odroidxu4_21.08.8.3_armhf.deb ...
Unpacking linux-image-current-odroidxu4 (21.08.8.3) over (21.08.8.2) ...
Free space after deleting the package linux-image-current-odroidxu4 in /boot: 10196
Setting up linux-image-current-odroidxu4 (21.08.8.3) ...
update-initramfs: Generating /boot/initrd.img-5.4.181-odroidxu4
W: Possible missing firmware /lib/firmware/xc3028L-v36.fw for built-in driver tuner_xc2028
W: Possible missing firmware /lib/firmware/xc3028-v27.fw for built-in driver tuner_xc2028
W: Possible missing firmware /lib/firmware/dvb-fe-xc5000c-4.1.30.7.fw for built-in driver xc5000
W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.fw for built-in driver xc4000
W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.1.fw for built-in driver xc4000
update-initramfs: Converting to u-boot format
Setting up linux-dtb-current-odroidxu4 (21.08.8.3) ...

$ sudo ls -l /boot/
total 54364
-rw-r--r-- 1 root root       64 Feb  5 15:56 armbianEnv.txt
-rw-r--r-- 1 root root        0 Sep  6  2019 armbianEnv.txt.out
-rw-r--r-- 1 root root     1536 May 29  2018 armbian_first_run.txt.template
-rw-r--r-- 1 root root    38518 May 29  2018 boot.bmp
-rw-r--r-- 1 root root     4882 May 29  2018 boot-desktop.png
-rw-r--r-- 1 root root    12489 Jan 16  2021 boot.ini
-rw-r--r-- 1 root root        0 Jun 25  2019 boot.ini.out
-rw-r--r-- 1 root root   169688 Feb 24 18:59 config-5.4.181-odroidxu4
lrwxrwxrwx 1 root root       21 Feb 24 19:03 dtb -> dtb-5.4.181-odroidxu4
drwxr-xr-x 3 root root     3072 Feb 24 19:02 dtb-5.4.181-odroidxu4
-rw-r--r-- 1 root root 11217935 Feb  5 15:42 initrd.img-5.4.177-odroidxu4
-rw-r--r-- 1 root root 11218103 Feb 24 19:03 initrd.img-5.4.181-odroidxu4
drwx------ 2 root root    12288 May 29  2018 lost+found
-rw-r--r-- 1 root root  3194931 Feb 24 18:59 System.map-5.4.181-odroidxu4
lrwxrwxrwx 1 root root       25 Feb 24 19:03 uInitrd -> uInitrd-5.4.181-odroidxu4
-rw-r--r-- 1 root root 11217999 Feb  5 15:42 uInitrd-5.4.177-odroidxu4
-rw-r--r-- 1 root root 11218167 Feb 24 19:03 uInitrd-5.4.181-odroidxu4
-rwxr-xr-x 1 root root  7346112 Feb 24 18:59 vmlinuz-5.4.181-odroidxu4
lrwxrwxrwx 1 root root       25 Feb 24 19:03 zImage -> vmlinuz-5.4.181-odroidxu4

Should I have rebooted before installing the new kernel? I can give it a try once 5.4.182 is available.

[going]

Yes, I have the same picture. Most likely, you need to change the order of the scripts in postrm.d. I'll check again tomorrow.

[going]

Checked it out!
I'm setting up a multi-boot and just installing and removing the kernel package.

But when the name of the package that is installed and that I am installing match, that is, a replacement occurs,

then the order of execution of the scripts changes and the cleanup script is triggered earlier than necessary.

Move it:

sudo mv /etc/kernel/postrm.d/initramfs-cleanup /etc/kernel/postinst.d/xx-initramfs-cleanup

That is, the script should be run as postinst.d and after the initramfs-tools script completes.

[going]

The final version is here:

https://github.com/armbian/build/pull/3511

[belegdol]

This still seems not to be working as intended with the versions from git:

Quote

$ sudo ls -l /boot/
total 54363
-rw-r--r-- 1 root root       64 Feb 24 19:09 armbianEnv.txt
-rw-r--r-- 1 root root        0 Sep  6  2019 armbianEnv.txt.out
-rw-r--r-- 1 root root     1536 May 29  2018 armbian_first_run.txt.template
-rw-r--r-- 1 root root    38518 May 29  2018 boot.bmp
-rw-r--r-- 1 root root     4882 May 29  2018 boot-desktop.png
-rw-r--r-- 1 root root    12489 Jan 16  2021 boot.ini
-rw-r--r-- 1 root root        0 Jun 25  2019 boot.ini.out
-rw-r--r-- 1 root root   169688 Mar  2 20:28 config-5.4.182-odroidxu4
lrwxrwxrwx 1 root root       21 Mar  2 20:32 dtb -> dtb-5.4.182-odroidxu4
drwxr-xr-x 3 root root     3072 Mar  2 20:31 dtb-5.4.182-odroidxu4
-rw-r--r-- 1 root root 11218103 Feb 24 19:03 initrd.img-5.4.181-odroidxu4
-rw-r--r-- 1 root root 11218319 Mar  2 20:32 initrd.img-5.4.182-odroidxu4
drwx------ 2 root root    12288 May 29  2018 lost+found
-rw-r--r-- 1 root root  3195000 Mar  2 20:28 System.map-5.4.182-odroidxu4
lrwxrwxrwx 1 root root       25 Mar  2 20:32 uInitrd -> uInitrd-5.4.182-odroidxu4
-rw-r--r-- 1 root root 11218167 Feb 24 19:03 uInitrd-5.4.181-odroidxu4
-rw-r--r-- 1 root root 11218383 Mar  2 20:32 uInitrd-5.4.182-odroidxu4
-rwxr-xr-x 1 root root  7343728 Mar  2 20:28 vmlinuz-5.4.182-odroidxu4
lrwxrwxrwx 1 root root       25 Mar  2 20:32 zImage -> vmlinuz-5.4.182-odroidxu4

 

$ ls -l  --recursive /etc/kernel/
/etc/kernel/:
total 0
drwxr-xr-x 1 root root   0 Dec  3  2017 install.d
drwxr-xr-x 1 root root 156 Mar  2 20:27 postinst.d
drwxr-xr-x 1 root root  70 Mar  2 20:28 postrm.d
drwxr-xr-x 1 root root   0 Feb 24 18:56 preinst.d
drwxr-xr-x 1 root root   0 Oct 13  2020 prerm.d

/etc/kernel/install.d:
total 0

/etc/kernel/postinst.d:
total 20
-rwxr-xr-x 1 root root 410 Jun 10  2021 apt-auto-removal
-rwxr-xr-x 1 root root 863 Jan 14  2021 initramfs-tools
-rwxr-xr-x 1 root root 196 Jan 22  2017 pm-utils
-rwxr-xr-x 1 root root 364 Jun  8  2019 unattended-upgrades
-rwxr-xr-x 1 root root 978 Mar  2 20:27 xx-initramfs-cleanup

/etc/kernel/postrm.d:
total 8
-rwxr-xr-x 1 root root 816 Jan 14  2021 initramfs-tools
-rwxr-xr-x 1 root root 978 Mar  2 20:27 xx-initramfs-cleanup

/etc/kernel/preinst.d:
total 0

/etc/kernel/prerm.d:
total 0
 

 

[belegdol]

After the reboot it is still the same. I have tested the logic comparing the contents of /lib/modules to /boot and it seems to work. Can the issue be that I am installing the packages with apt install? Is there another way?

 

Quote

$ sudo apt install ./linux-{dtb,image}-current-odroidxu4_22.02.1.1_armhf.deb
[sudo] password for julas:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'linux-dtb-current-odroidxu4' instead of './linux-dtb-current-odroidxu4_22.02.1.1_armhf.deb'
Note, selecting 'linux-image-current-odroidxu4' instead of './linux-image-current-odroidxu4_22.02.1.1_armhf.deb'
The following packages will be upgraded:
  linux-dtb-current-odroidxu4 linux-image-current-odroidxu4
2 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/30.4 MB of archives.
After this operation, 6,144 B of additional disk space will be used.
Get:1 /home/julas/linux-dtb-current-odroidxu4_22.02.1.1_armhf.deb linux-dtb-current-odroidxu4 armhf 22.02.1.1 [120 kB]
Get:2 /home/julas/linux-image-current-odroidxu4_22.02.1.1_armhf.deb linux-image-current-odroidxu4 armhf 22.02.1.1 [30.3 MB]
(Reading database ... 48796 files and directories currently installed.)
Preparing to unpack .../linux-dtb-current-odroidxu4_22.02.1.1_armhf.deb ...
Unpacking linux-dtb-current-odroidxu4 (22.02.1.1) over (21.08.8.4) ...
Preparing to unpack .../linux-image-current-odroidxu4_22.02.1.1_armhf.deb ...
Unpacking linux-image-current-odroidxu4 (22.02.1.1) over (21.08.8.4) ...
Setting up linux-image-current-odroidxu4 (22.02.1.1) ...
update-initramfs: Generating /boot/initrd.img-5.4.184-odroidxu4
W: Possible missing firmware /lib/firmware/xc3028L-v36.fw for built-in driver tuner_xc2028
W: Possible missing firmware /lib/firmware/xc3028-v27.fw for built-in driver tuner_xc2028
W: Possible missing firmware /lib/firmware/dvb-fe-xc5000c-4.1.30.7.fw for built-in driver xc5000
W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.fw for built-in driver xc4000
W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.1.fw for built-in driver xc4000
update-initramfs: Converting to u-boot format
Setting up linux-dtb-current-odroidxu4 (22.02.1.1) ...

 

[going]

14.03.2022 в 23:48, belegdol сказал:

Can the issue be that I am installing the packages with apt install? Is there another way?

apt install

or

apt-get install

or

aptitude

All these commands are wrappers to make a call  dpkg -i pkgname.deb.

 

Most likely the problem is in the scripts.
I can't reach your target installed system on the board. You'll have to do it yourself.

[belegdol]

OK, with update from 5.4.184 to 5.4.185 the hooks finally worked:

Quote

$ sudo apt install ./linux-{dtb,image}-current-odroidxu4_22.02.1.2_armhf.deb 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'linux-dtb-current-odroidxu4' instead of './linux-dtb-current-odroidxu4_22.02.1.2_armhf.deb'
Note, selecting 'linux-image-current-odroidxu4' instead of './linux-image-current-odroidxu4_22.02.1.2_armhf.deb'
The following packages will be upgraded:
  linux-dtb-current-odroidxu4 linux-image-current-odroidxu4
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/30.4 MB of archives.
After this operation, 1,024 B disk space will be freed.
Get:1 /home/julas/linux-dtb-current-odroidxu4_22.02.1.2_armhf.deb linux-dtb-current-odroidxu4 armhf 22.02.1.2 [120 kB]
Get:2 /home/julas/linux-image-current-odroidxu4_22.02.1.2_armhf.deb linux-image-current-odroidxu4 armhf 22.02.1.2 [30.3 MB]
(Reading database ... 48801 files and directories currently installed.)
Preparing to unpack .../linux-dtb-current-odroidxu4_22.02.1.2_armhf.deb ...
Unpacking linux-dtb-current-odroidxu4 (22.02.1.2) over (22.02.1.1) ...
Preparing to unpack .../linux-image-current-odroidxu4_22.02.1.2_armhf.deb ...
Unpacking linux-image-current-odroidxu4 (22.02.1.2) over (22.02.1.1) ...
Setting up linux-image-current-odroidxu4 (22.02.1.2) ...
update-initramfs: Generating /boot/initrd.img-5.4.185-odroidxu4
W: Possible missing firmware /lib/firmware/xc3028L-v36.fw for built-in driver tuner_xc2028
W: Possible missing firmware /lib/firmware/xc3028-v27.fw for built-in driver tuner_xc2028
W: Possible missing firmware /lib/firmware/dvb-fe-xc5000c-4.1.30.7.fw for built-in driver xc5000
W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.fw for built-in driver xc4000
W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.1.fw for built-in driver xc4000
update-initramfs: Converting to u-boot format
Remove unused generated file: /boot/initrd.img-5.4.184-odroidxu4
Remove unused generated file: /boot/uInitrd-5.4.184-odroidxu4
Free space after deleting the package linux-image-current-odroidxu4 in /boot: 21M
Setting up linux-dtb-current-odroidxu4 (22.02.1.2) ...
$

 

[belegdol]

I hit another problem today. I tried updating to my local 5.4.199 build, but the free space ran out during the uInitrd conversion. I was able to rescue the system by putting the SD card in my Fedora machine and doing the conversion there, but the 58 MB boot is slowly becoming an issue. Is this still the default? If not, what is the current default? Can I just increase the partition size with gparted and be done with it?