Re: Exec format error from armv7 snapshot on RPi2

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On May 31, 2025, at 13:43, bob prohaska <[email protected]> wrote:

> Just downloaded 
> FreeBSD-15.0-CURRENT-arm-armv7-GENERICSD-20250522-30fd79b0c0a3-277396.img,
> wrote it to a microSD card and tried to boot an older (so armv7) Raspberry
> Pi 2.
> 
> It boots hands off, but complains about "exec format error" on some but
> not all commands. The first occurrence was during boot -s:
> ...
> ...
> umass0 on uhub2
> umass0: <JMicron SABRENT, class 0/0, rev 2.10/12.14, addr 6> on usbus0
> umass0:  SCSI over Bulk-Only; quirks = 0x0
> umass0:0:0: Attached to scbus0
> 
> -sh: /usr/bin/resizewin: Exec format error
> root@:/ # da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
> da0: <SABRENT  1214> Fixed Direct Access SPC-4 SCSI device
> da0: Serial Number 000000000000A
> ...
> ...
> 
> Many more appear during boot to multi-user. Nonetheless,
> it puts a login prompt on the serial console. 
> 
> Attempt to log in look like:
> 
> login: root
> pid 664 (login), jid 0, uid 0: exited on signal 11 (core dumped)
> 
> FreeBSD/arm (generic) (ttyu0)
> 
> login: 
> 
> Any insights appreciated. I understand armv7 is on its last legs,
> but was hoping not yet.

If you can get to the point of doing such, what does:

# file /usr/bin/resizewin

report?

Example that is not from that .img file:

# file /usr/bin/resizewin
/usr/bin/resizewin: ELF 32-bit LSB executable, ARM, EABI5 version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 15.0 (1500043), stripped
# /mnt/usr/bin/resizewin

A less direct possibility here is to boot an aarch64 system (that also
supports armv7 in user space) and to mount media on that system, say
to /mnt/ , then try:

# file /mnt/usr/bin/resizewin
# /mnt/usr/bin/resizewin

Also of interest might be:

# chroot /mnt/
# file /usr/bin/resizewin
# /mnt/usr/bin/resizewin
# exit

My use of mdconfig with the .img file did not show any problems
with the analogous /mnt/ use. (Windows Dev Kit 2023 used.)

If the aarch64 based context works in your context, it suggests
a kernel problem for the armv7 kernel, not a world problem.

===
Mark Millard
marklmi at yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.