01-25-2020, 04:47 PM
I fail booting a selfcompiled kernel:
I built and installed Manajaro's latest kernel from source
For apt-install, a lot of messages passed by, initrd was receated and even extlinux.conf got automatically updated
I had a quick look into the new initrd and it looks reasonable.
A reboot booted straight into the previous kernel
How is that possible?
I built and installed Manajaro's latest kernel from source
Code:
make -j2 bindeb-pkg && apt-get install ../linux-image-5.5.0-rc7-1-pinebookpro-arm64+_5.5.0-rc7-1-pinebookpro-arm64+-5_arm64.debFor apt-install, a lot of messages passed by, initrd was receated and even extlinux.conf got automatically updated
Code:
$ cat /boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label Debian GNU/Linux kernel 5.5.0-rc7-1-pinebookpro-arm64+
linux /vmlinuz-5.5.0-rc7-1-pinebookpro-arm64+
initrd /initrd.img-5.5.0-rc7-1-pinebookpro-arm64+
fdt /rk3399-pinebook-pro.dtb
append root=LABEL=mmcblk1-RootFS console=ttyS2,1500000n8 console=tty0 ro maxcpus=4 coherent_pool=1M
label l0r
menu label Debian GNU/Linux kernel 5.5.0-rc7-1-pinebookpro-arm64+ (rescue target)
linux /vmlinuz-5.5.0-rc7-1-pinebookpro-arm64+
initrd /initrd.img-5.5.0-rc7-1-pinebookpro-arm64+
fdt /rk3399-pinebook-pro.dtb
append root=LABEL=mmcblk1-RootFS console=ttyS2,1500000n8 console=tty0 ro maxcpus=4 coherent_pool=1M single
label l1
menu label Debian GNU/Linux kernel 5.4.2-2-pinebookpro-arm64
linux /vmlinuz-5.4.2-2-pinebookpro-arm64
initrd /initrd.img-5.4.2-2-pinebookpro-arm64
fdt /rk3399-pinebook-pro.dtb
append root=LABEL=mmcblk1-RootFS console=ttyS2,1500000n8 console=tty0 ro maxcpus=4 coherent_pool=1M
label l1r
menu label Debian GNU/Linux kernel 5.4.2-2-pinebookpro-arm64 (rescue target)
linux /vmlinuz-5.4.2-2-pinebookpro-arm64
initrd /initrd.img-5.4.2-2-pinebookpro-arm64
fdt /rk3399-pinebook-pro.dtb
append root=LABEL=mmcblk1-RootFS console=ttyS2,1500000n8 console=tty0 ro maxcpus=4 coherent_pool=1M singleCode:
$ dir /boot/
total 50697
drwxr-xr-x 5 root root 1024 Jan 25 14:06 .
drwxr-xr-x 21 root root 4096 Jan 23 00:16 ..
-rw-r--r-- 1 root root 204751 Dec 13 04:21 config-5.4.2-2-pinebookpro-arm64
-rw-r--r-- 1 root root 204401 Jan 24 21:44 config-5.5.0-rc7-1-pinebookpro-arm64+
drwxr-xr-x 2 root root 512 Dec 31 1969 efi
drwxr-xr-x 2 root root 1024 Jan 25 14:06 extlinux
-rw-r--r-- 1 root root 6295863 Jan 24 21:19 initrd.img-5.4.2-2-pinebookpro-arm64
-rw-r--r-- 1 root root 6422051 Jan 25 14:06 initrd.img-5.5.0-rc7-1-pinebookpro-arm64+
drwx------ 2 root root 12288 Jan 22 23:30 lost+found
-rw-r--r-- 1 root root 62112 Jan 25 14:06 rk3399-pinebook-pro.dtb
-rw-r--r-- 1 root root 60795 Jan 25 14:06 rk3399-pinebook-pro.dtb.bak
-rw-r--r-- 1 root root 4416507 Dec 13 04:21 System.map-5.4.2-2-pinebookpro-arm64
-rw-r--r-- 1 root root 4807055 Jan 24 21:44 System.map-5.5.0-rc7-1-pinebookpro-arm64+
-rwxr-xr-x 1 root root 20220416 Dec 13 04:21 vmlinuz-5.4.2-2-pinebookpro-arm64
-rw-r--r-- 1 root root 9196524 Jan 24 21:44 vmlinuz-5.5.0-rc7-1-pinebookpro-arm64+Code:
$ dir /lib/modules/
total 16
drwxr-xr-x 4 root root 4096 Jan 25 14:05 .
drwxr-xr-x 17 root root 4096 Jan 25 10:27 ..
drwxr-xr-x 3 root root 4096 Jan 23 00:23 5.4.2-2-pinebookpro-arm64
drwxr-xr-x 3 root root 4096 Jan 25 14:05 5.5.0-rc7-1-pinebookpro-arm64+I had a quick look into the new initrd and it looks reasonable.
A reboot booted straight into the previous kernel
Code:
$ uname -a
Linux pinebook-pro 5.4.2-2-pinebookpro-arm64 #1 SMP PREEMPT Sun Jan 19 22:43:25 UTC 2020 aarch64 GNU/LinuxHow is that possible?