Closed mrchrisster closed 9 months ago
MichaIng
commented
9 months ago Hmm, you are running a very old image, it seems. We migrated our images to Armbian-based kernel packages some years ago. The kernel you tried to install Debian cannot work without modifying the boot environment/script as well. But uff, where the hack is this 4.4 kernel image, actually, and the boot script 😄?
Can you check this please:
df
lsblk
mrchrisster
commented
9 months ago Thanks for getting back to me. I was thinking of just starting from scratch but this little guy has been such a trooper ever since I started using dietpi and I'd hate to start all over.
root@nanopc:/boot# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 14631928 11818968 2194828 85% /
devtmpfs 1974228 0 1974228 0% /dev
tmpfs 1975132 4 1975128 1% /dev/shm
tmpfs 790056 90256 699800 12% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 51200 20 51180 1% /var/log
tmpfs 1974272 12 1974260 1% /tmp
tmpfs 395024 24 395000 1% /run/user/0
/dev/nvme0n1p6 490846472 38186148 452643940 8% /mnt/nvme
root@nanopc:/boot#root@nanopc:/boot# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 7.8M 0 rom
mmcblk1 179:0 0 14.6G 0 disk
├─mmcblk1p1 179:1 0 4M 0 part
├─mmcblk1p2 179:2 0 4M 0 part
├─mmcblk1p3 179:3 0 12M 0 part
├─mmcblk1p4 179:4 0 32M 0 part
├─mmcblk1p5 179:5 0 32M 0 part
└─mmcblk1p6 179:6 0 14.2G 0 part /
mmcblk1boot0 179:32 0 4M 1 disk
mmcblk1boot1 179:64 0 4M 1 disk
mmcblk1rpmb 179:96 0 4M 0 disk
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 4M 0 part
├─nvme0n1p2 259:2 0 4M 0 part
├─nvme0n1p3 259:3 0 12M 0 part
├─nvme0n1p4 259:4 0 32M 0 part
├─nvme0n1p5 259:5 0 32M 0 part
└─nvme0n1p6 259:6 0 476.6G 0 part /mnt/nvme
root@nanopc:/boot#Hey Micha,
I bit the bullet and just started over from scretch with a fresh image. i compiled a new u-boot and flashed it to the location specified in the friendlyarm wiki docs but it crashed the system. in the end it's all good now with a fresh install
MichaIng
commented
9 months ago Ah, now I remember it was this multi-partition image, and the kernel was located on one of the other partition, but in raw format, hence no filesystem which could be mounted.
Coincidentally I was just about testing a migration of such system to Armbian-based kernel, but NanoPi R5S/R6S, which currently have the kernel similarly distributed. But a fresh image is definitely cleaner.
with a fresh image. i compiled a new u-boot and flashed it to the location specified in the friendlyarm
The Armbian bootloader packages ship with a script which flashes the bootloader correctly OOTB. But a kernel and boot script which tells the bootloader to load this kernel is required as well. And I guess the leading 5 partitions need to be removed, so that only the root partition is left, and the new bootloader does not overlap with one of the first partitions. As said, I'm just going to test this process now. But probably not relevant for you anymore, as you flashed a new image already.
I'm trying to update my kernel to use wireguard. I spend a good chunk of the day getting everything upgraded to bullseye but I'm not sure how to switch over to the new kernel.
dietpi-config -> update firmware didn't seem to do anything or produce an error. reboot did not help unfortunately.