rodinux Posted August 24, 2019 Posted August 24, 2019 Hello, I am still having some troubles with my server Yunohost configured with an Orange Pi 2+ I have Frreze the kernel since few months. But I try to Defreeze the kernel, I have updated the kernel using armbian-config then 'Other Switch to others kernels' to update the last linux-image-next-sunxi=5.90 4.19.57.sunxi but every time I reboot, I'm still booting with the kernel 4.14.18-sunxi I don't understand how to make the boot loading the new kernel... This is my u-boot environment: verbosity=1 console=both overlay_prefix=sun8i-h3 rootdev=UUID=173bb8f3-f2d3-4fce-9f51-e55dfd9605e5 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u It is strange because I don't recognize the UUID with this: $ sudo blkid /dev/mmcblk0p1: UUID="cca8b465-859f-44b3-a832-e1de3f6766d2" TYPE="ext4" PARTUUID="d252feef-01" /dev/mmcblk1p1: UUID="0bd18549-75f4-48a5-a29e-41d9c10701c4" TYPE="ext4" PARTUUID="c168bf4c-01" /dev/sda1: UUID="53745c47-3b92-45ee-9f98-3e6297e40b97" TYPE="ext4" PARTUUID="000011cd-01" /dev/sda2: UUID="b8261aeb-c028-4368-9def-a1296ff74a50" TYPE="swap" PARTUUID="000011cd-02" /dev/mmcblk0: PTUUID="d252feef" PTTYPE="dos" /dev/mmcblk1: PTUUID="c168bf4c" PTTYPE="dos"
rodinux Posted August 24, 2019 Author Posted August 24, 2019 I have this also compromised: $ ls /boot/ armbianEnv.txt boot.scr overlay-user armbianEnv.txte config-4.19.62-sunxi script.bin armbianEnv.txt.out dtb System.map-4.19.62-sunxi armbian_first_run.txt.template dtb-4.17.4-sunxi uInitrd boot.bmp dtb-4.19.62-sunxi uInitrd-4.19.62-sunxi boot.cmd dtb.old vmlinuz-4.19.62-sunxi boot-desktop.png initrd.img-4.19.62-sunxi zImage and $ dpkg --list | grep linux-image rc linux-image-dev-sunxi 5.92 armhf Linux kernel, version 5.2.5-sunxi ii linux-image-next-sunxi 5.92 armhf Linux kernel, version 4.19.62-sunxi I imagine I have to remove a kernel ? the 5.2.5-sunxi ? Ok, I have purge an old configuration waiting for the the linux-image-dev-sunxi and now I only see the linux-image-next-kernel, but I still booting on a kernel 4.14.18-sunxi...
rodinux Posted August 24, 2019 Author Posted August 24, 2019 I think the matter is my u-boot environment I have to edit I have try to edit like this: verbosity=1 console=both overlay_prefix=sun8i-h3 root=UUID=0bd18549-75f4-48a5-a29e-41d9c10701c4 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I also try root=/dev/sda1 This is my fstab $ cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> # tmpfs /tmp tmpfs defaults,nosuid 00 UUID=cca8b465-859f-44b3-a832-e1de3f6766d2 # partition boot sur SD UUID=0bd18549-75f4-48a5-a29e-41d9c10701c4 /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 /media/mmcboot/boot /boot none bind 0 0 # partition / sur sda1 UUID=53745c47-3b92-45ee-9f98-3e6297e40b97 / ext4 defaults,errors=remount-ro 0 1 # Partition swap UUID=b8261aeb-c028-4368-9def-a1296ff74a50 swap swap sw 0 0 What's the matter ? how can I edit correctly u-boot and get to boot on the kernel 4.19.62-sunxi ?? help !!
Werner Posted August 24, 2019 Posted August 24, 2019 Usually you should have one kernel image only installed on your SBC. armbian-config should handle this for you. Some things looking strange indeed. Any chance to start over with a fresh Armbian?
rodinux Posted August 26, 2019 Author Posted August 26, 2019 Hello, I am trying few things to debug. I am afraid to install all my server without trying just to resolve what's happening. Now I have edit this file /boot/armbianEnv.txt: $ cat /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=sun8i-h3 root_dev=/dev/sda1 root=/dev/sda1 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I have try to change the /etc/fstab also as the files of the directory /boot was inside /media/mmcboot/boot so I saw the files were in /media/mcboot/boot/boot But now it is fine, I resolved it changing first the line: /media/mmcboot/boot /boot none bind 0 0 with /media/mmcboot/boot/boot /boot none bind 0 0 and now I write back again /media/mmcboot/boot /boot none bind 0 0 I also try to make the command sudo mkimage -C none -A arm -T script -d /boot/boot/boot.cmd /boot/boot/boot.scr and now the goods new is this $ ls /media/mmcboot/boot/ armbianEnv.txt boot boot.scr dtb-4.19.62-sunxi script.bin vmlinuz-4.19.62-sunxi armbianEnv.txte boot.bmp config-4.19.62-sunxi dtb.old System.map-4.19.62-sunxi zImage armbianEnv.txt.out boot.cmd dtb initrd.img-4.19.62-sunxi uInitrd armbian_first_run.txt.template boot-desktop.png dtb-4.17.4-sunxi overlay-user uInitrd-4.19.62-sunxi ls /boot/ armbianEnv.txt boot boot.scr dtb-4.19.62-sunxi script.bin vmlinuz-4.19.62-sunxi armbianEnv.txte boot.bmp config-4.19.62-sunxi dtb.old System.map-4.19.62-sunxi zImage armbianEnv.txt.out boot.cmd dtb initrd.img-4.19.62-sunxi uInitrd armbian_first_run.txt.template boot-desktop.png dtb-4.17.4-sunxi overlay-user uInitrd-4.19.62-sunxi But I am still booting on 4.14.18-sunxi kernel.
rodinux Posted August 26, 2019 Author Posted August 26, 2019 I try armbianmonitor -u logs, this is the link with the results: http://ix.io/1Txf
rodinux Posted August 26, 2019 Author Posted August 26, 2019 I come back to use the kernel 4.14.18-sunxi and Freeze the updates of armbian. Now I boot from the external HDD, I have commented before the mount of the sdcard on my fstab $ cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> # tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=cca8b465-859f-44b3-a832-e1de3f6766d2 # partition boot sur SD UUID=0bd18549-75f4-48a5-a29e-41d9c10701c4 /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 #/media/mmcboot/boot /boot none bind 0 0 # partition / sur sda1 UUID=53745c47-3b92-45ee-9f98-3e6297e40b97 / ext4 defaults,errors=remount-ro 0 1 # Partition swap UUID=b8261aeb-c028-4368-9def-a1296ff74a50 swap swap sw But I am not sure it is a good idea, because there is no more the files armbianEnv.txt on the directory boot $ ls /boot/ config-4.14.18-sunxi dtb-4.14.18-sunxi System.map-4.14.18-sunxi uInitrd-4.14.18-sunxi zImage dtb initrd.img-4.14.18-sunxi uInitrd vmlinuz-4.14.18-sunxi Can I stay like this or it is not recommended ??
martinayotte Posted August 27, 2019 Posted August 27, 2019 You can probably copy the /boot from other media into this /boot, you will recover the armbianEnv.txt as well as the newest kernel.
Recommended Posts