Hi, Gene Heskett wrote: > I once wrote the "debian-10.0.0-arm64-netinst.iso" to an u-sd card, > which booted and did a net-install on an rpi-3b [...] > /dev/sde1 /media/sde1 iso9660 ro,relatime 0 0 > /dev/sde2 /media/sde2 vfat > rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortna > me=mixed,utf8,errors=remount-ro 0 0 > > first partition is iso9660 ? Don't recall seeing that before.
That's the normal partition table content of a bootable Debian ISO for i386, amd_64, armhf, arm64. (i386 and amd64 ISOs suffer from partition nesting, but that does not keep PC-BIOS or EFI from booting them.) The statement "iso9660" stems from inspection of the partition content, not from the partition table where type is 0x83 = "Linux" in the armhf and arm64 ISOs. The second partition is of type 0xEF and contains a FAT filesystem with EFI boot equipment. As stated already in another thread: The combination of Raspberry and EFI is exotic. I get the impression that uboot is a usual firmware and bootloader, but that there are also mechanisms which rather remind me of the ROM of my VIC-20. See e.g. https://www.beyondlogic.org/compiling-u-boot-with-device-tree-support-for-the-raspberry-pi/ So, unless your rpi-3b has an EFI-compatible first booting step in its firmware, i assume that debian-10.0.0-arm64-netinst.iso never booted on it. Have a nice day :) Thomas
