> I think most people would not place that on a tftp server. You seem oriented by what most peole do, without actually having evidence of what they really do and why they do it.
> The fetch is attempted because of how the boot loader works but I'd expect > you should be able to ignore the missing file, doss that work? You are confusing what I may want to do, which you do not know, with what the pxeboot actually does, which you know if you enable tftpd verbose log and read the log. My question stands as to why it fails. > The official binary for OpenBSD is available via fw_update. The OpenBSD official binaries are a copy of the official Linux binaries. I just downloaded both, and they are identical. -------- Original Message -------- On 2/19/25 21:00, Rupert Gallagher <r...@protonmail.com> wrote: > > > What hardware are you using? From your description, I can see it's > amd64. But what specifically is it? > > pcengines apu2 > > > Why use 6.7 and not the latest release 7.6? > > Typing error. > > > What official binary from "linux git" are you referring to? > > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/amd-ucode/ > > > > > -------- Original Message -------- > On 2/19/25 13:53, Rupert Gallagher <r...@protonmail.com> wrote: > > > openbsd 6.7 pxeboot calls /etc/firmware/amd/microcode_amd_fam16h.bin via > tftp right after /openbsd/bsd.rd. I retrieved the official binary file from > linux git and put it where it belongs with correct permissions. The tftpd log > registers 'retry: operation timeout'. Is this the file you need? Is the file > rejected for some reason?
