Hi, Gene Heskett wrote: > /dev/sdl2 7783552 7798783 15232 7.4M ef EFI (FAT-12/16/32) > Now, that looks like something that might boot an intel system,
Or on one of the other systems with EFI firmware. EFI boot program names are defined for 32-bit and for 64-bit ARM CPUs. But - as you meanwhile pointed out - there are ARM systems without EFI. > Now power it down, pull the card and put it back in the reader, and write > the armbian server .img file to it. > /dev/sdl1 8192 4161535 4153344 2G 83 Linux Are there any files matching "start*.elf" to see in that filesystem ? find ...where.it.is.mounted... -name 'start*.elf' If so, then you may hope that the Debian Raspberry .img.xz and armbian are following a similar boot path. > So the $64,000 question is: where do I get a genuine debian-arm64 .img that > will boot a pi clone using the arm bootp protocol. The Debian wiki https://wiki.debian.org/RaspberryPi does not talk of "bootp" but points to the promising download page https://raspi.debian.net/tested-images/ and to descriptions of particular versions like https://wiki.debian.org/RaspberryPi4 which talks of "Current status (2024-07)" So it is actively maintained. ... and it has lots of detail and links to interesting tangents. George at Clug wrote: > > If the aim is to make a bootable USB then I like to use: > > # cp debian-12.6.0-arm64-DVD-1.iso /dev/sdl > Dammit, people, I am NOT making a bootable /usb device/, Seen from Linux userland, a USB stick and a SD card behave the same, namely like conventional hard disks. After all you see yours as /dev/sdl, a disk device operated by SCSI commands. Insofar the advise is correct for your case. Any differences between usual USB sticks and your storage device have for now to be considered red herrings. The obvious problem is that your system has no EFI but the Debian arm64 ISO aims at EFI as boot firmware. Have a nice day :) Thomas
