used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXC ONN. brand card, makes no attempt to boot plugged into a bananapi-m5. bring card back to reader, can't mount it, wrong filesystem for both partitions. Give up, write Armbian-jammie-full-desktop iso to card, mounts ok, boots bananapi-m5 normally.
What did I do wrong?
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXC
ONN. brand card, makes no attempt to boot plugged into a bananapi-m5.
bring card back to reader, can't mount it, wrong filesystem for both partitions. Give up, write Armbian-jammie-full-desktop iso to card,
mounts ok, boots bananapi-m5 normally.
What did I do wrong?
On 15/08/2023 17:44, gene heskett wrote:
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXC
ONN. brand card, makes no attempt to boot plugged into a bananapi-m5.
bring card back to reader, can't mount it, wrong filesystem for both
partitions. Give up, write Armbian-jammie-full-desktop iso to card, mounts >> ok, boots bananapi-m5 normally.
What did I do wrong?
The unfortunate reality is that boot on arm is *still* a mess. The server guys and the windows laptop guys
have settled on uefi (though the implementations are often far from
perfect), but the hobbyist board segment
is still all over the place, with each board (or family of closely related boards) still needing it's own build
of u-boot that knows how to initialise the board, load a kernel and initrd and pass them the relavent device
tree.
For some boards, Debian offers "concatenatable images", where a board-specific boot section can be concatenated
with a board-independent d-i section to produce a boot image suitable for a specific board, yours doesn't seem
to be one of them though.
.
On 15/08/2023 17:44, gene heskett wrote:It is not "U-Boot versus UEFI" problem.
What did I do wrong?
The unfortunate reality is that boot on arm is *still* a mess. The
server guys and the windows laptop guys have settled on uefi (though
the implementations are often far from perfect), but the hobbyist
board segment is still all over the place, with each board (or family
of closely related boards) still needing it's own build of u-boot
On 15/08/2023 17:44, gene heskett wrote:
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G
SDXC ONN. brand card, makes no attempt to boot plugged into a
bananapi-m5. bring card back to reader, can't mount it, wrong
filesystem for both partitions. Give up, write
Armbian-jammie-full-desktop iso to card, mounts ok, boots bananapi-m5
normally.
What did I do wrong?
The unfortunate reality is that boot on arm is *still* a mess. The
server guys and the windows laptop guys
have settled on uefi (though the implementations are often far from
perfect), but the hobbyist board segment
is still all over the place, with each board (or family of closely
related boards) still needing it's own build
of u-boot that knows how to initialise the board, load a kernel and
initrd and pass them the relavent device
tree.
For some boards, Debian offers "concatenatable images", where a board-specific boot section can be concatenated
with a board-independent d-i section to produce a boot image suitable
for a specific board, yours doesn't seem
to be one of them though.
.
.
On 2023-08-15, gene heskett wrote:
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXC
ONN. brand card, makes no attempt to boot plugged into a bananapi-m5.
bring card back to reader, can't mount it, wrong filesystem for both
partitions. Give up, write Armbian-jammie-full-desktop iso to card,
mounts ok, boots bananapi-m5 normally.
What did I do wrong?
Hard to say based on so little information...
My wild guess is the Armbian-jammie-full-desktop iso includes boot
firmware.
Do you have a URL to the exact image you used?The most recent build, 12-1 of the arm64 menu on debians quite confusing
Do you have any output from the serial console when trying to boot thedebian-12.1.0-arm64-netinst.iso Armbian_23.5.1_Bananapim5_jammy_current_6.1.30.img
Debian image? Armbian?
The only way what you did might work is if you have boot firmware
present on some other media (e.g. SPI, eMMC, etc.) that implements EFI,
such as edk2/tianocore or u-boot.
live well,
vagrant
W dniu 15.08.2023 o 20:57, peter green pisze:
On 15/08/2023 17:44, gene heskett wrote:
It is not "U-Boot versus UEFI" problem.What did I do wrong?
The unfortunate reality is that boot on arm is *still* a mess. The
server guys and the windows laptop guys have settled on uefi (though
the implementations are often far from perfect), but the hobbyist
board segment is still all over the place, with each board (or family
of closely related boards) still needing it's own build of u-boot
The problem is SBC vendors who go with "Shitty Bargain Crap" explanation
of acronym instead of "Small Board Computer" one.
When you have SBC without any on-board storage for boot firmware
(nevermind is it U-Boot, UEFI, Barebox or whatever) then you need to
provide (usually) microsd with firmware stored at some magical places.
One of solutions then is to make microsd card with firmware, put it into
a slot and forget that microsd slot exists. Then you can plug USB stick
with Debian installer (just "dd if=debian.iso of=/dev/usbstick") and boot.
This is how raspberry/pi 1/2/3 and several other SBC work.
.
On 8/15/23 14:57, peter green wrote:
On 15/08/2023 17:44, gene heskett wrote:
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G
SDXC ONN. brand card, makes no attempt to boot plugged into a bananapi-m5. bring card back to reader, can't mount it, wrong
filesystem for both partitions. Give up, write Armbian-jammie-full-desktop iso to card, mounts ok, boots
bananapi-m5 normally.
What did I do wrong?
The unfortunate reality is that boot on arm is *still* a mess. The
server guys and the windows laptop guys
have settled on uefi (though the implementations are often far from perfect), but the hobbyist board segment
is still all over the place, with each board (or family of closely
related boards) still needing it's own build
of u-boot that knows how to initialise the board, load a kernel and
initrd and pass them the relavent device
tree.
For some boards, Debian offers "concatenatable images", where a board-specific boot section can be concatenated
with a board-independent d-i section to produce a boot image suitable
for a specific board, yours doesn't seem
to be one of them though.
All no doubt true. But once this board is booted, its 20% faster than any
pi, but doesn't have, and I don't need, a wifi radio. And every usb port is usb3.
\
Thank you Peter Green.
.
.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXCAs explained, this board is not supported by the Debian Installer and it
ONN. brand card, makes no attempt to boot plugged into a bananapi-m5.
bring card back to reader, can't mount it, wrong filesystem for both >partitions. Give up, write Armbian-jammie-full-desktop iso to card,
mounts ok, boots bananapi-m5 normally.
What did I do wrong?
gheskett@shentel.net wrote:
used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXCAs explained, this board is not supported by the Debian Installer and it
ONN. brand card, makes no attempt to boot plugged into a bananapi-m5.
bring card back to reader, can't mount it, wrong filesystem for both
partitions. Give up, write Armbian-jammie-full-desktop iso to card,
mounts ok, boots bananapi-m5 normally.
What did I do wrong?
will probably never be since it requires a custom u-boot with
binary-only parts.
But if you recover the u-boot from an Armbian image then you can still install plain Debian:
https://blog.bofh.it/debian/id_466
(As long as you do not care about the SD card reader, at this point.)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 69:33:44 |
Calls: | 6,915 |
Files: | 12,380 |
Messages: | 5,431,960 |