Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On 2022-Oct-2, at 14:43, Mark Millard <[email protected]> wrote: > On 2022-Oct-2, at 13:18, Klaus Küchemann <[email protected]> wrote: > >> . . . >> >>> Am 02.10.2022 um 21:48 schrieb Mark Millard <[email protected]>: >>> >>> (RaspiOS and Ubuntu do not use U-Boot last I knew. So >>> they do not make for good comparisons for the purpose >>> as far as I know.) >> >> RaspiOS doesn’t , Ubuntu(and others) use u-boot since years … >> while possible Ubuntu(or others) have own u-boot patches , >> from guessing it seems more probable that they also will sometimes hang after (re)boot. > > Sufficiently modern Ubuntu does not use U-Boot by > default, at least for server builds. > > ubuntu-22.04.1-preinstalled-server-arm64+raspi.img > has: > > # more /mnt/config.txt > [all] > kernel=vmlinuz > . . . > > where vmlinux is seen as: > > /mnt/vmlinuz I should have mentioned the naming convention that is in use: vmlinuz is a compressed variant of vmlinux as I remember the naming. > No use of U-Boot: direct booting of vmlinux via > the RPi* firmware's ability to do so. > > They do provide uboot_rpi_*.bin 's for folks that > want to change to use such: > > /mnt/uboot_rpi_3.bin > /mnt/uboot_rpi_4.bin > /mnt/uboot_rpi_arm64.bin > > But the supplied config.txt makes no mention of any > uboot*.bin and things have to be changed to cause > a uboot_rpi_*.bin to be involved. === Mark Millard marklmi at yahoo.com