Rainer Dorsch
2021-12-28 08:20:02 UTC
Hi,
just for curiosity, on a new bullseye installation of a cubox-i, there is a
W95 FAT32 (LBA) partition created as first partition. It contains a boot setup:
***@bc-text:~# mount /dev/mmcblk1p1 /mnt/
***@bc-text:~# ls -l /mnt/
total 27026
-rwxr-xr-x 1 root root 1575 Dec 13 16:23 boot.scr
drwxr-xr-x 2 root root 75264 Dec 13 16:23 dtbs
-rwxr-xr-x 1 root root 22636034 Dec 13 16:23 initrd.gz
-rwxr-xr-x 1 root root 4960768 Dec 13 16:23 vmlinuz
***@bc-text:~#
I am just wondering, why that is there. Is it an installation process leftover
or a kind or a rescue kernel? If rescue kernel is there a bootcmd available?
Here is the printenv of u-boot for reference:
https://paste.debian.net/1225017/
Thanks
Rainer
just for curiosity, on a new bullseye installation of a cubox-i, there is a
W95 FAT32 (LBA) partition created as first partition. It contains a boot setup:
***@bc-text:~# mount /dev/mmcblk1p1 /mnt/
***@bc-text:~# ls -l /mnt/
total 27026
-rwxr-xr-x 1 root root 1575 Dec 13 16:23 boot.scr
drwxr-xr-x 2 root root 75264 Dec 13 16:23 dtbs
-rwxr-xr-x 1 root root 22636034 Dec 13 16:23 initrd.gz
-rwxr-xr-x 1 root root 4960768 Dec 13 16:23 vmlinuz
***@bc-text:~#
I am just wondering, why that is there. Is it an installation process leftover
or a kind or a rescue kernel? If rescue kernel is there a bootcmd available?
Here is the printenv of u-boot for reference:
https://paste.debian.net/1225017/
Thanks
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Rainer Dorsch
http://bokomoko.de/