Geert Stappers

> Any idea? Make a nice table like ```text | works fine | gets stuck -----------------------+---------------------+------------ Link on onboard NIC | not applic Links on 4 port Card | 4...

> Next test: I will use intelx.efi on both. And how did that go? Also about five days ago: > also post pciid Those _PCI identities_ can be found with...

> Hope this is the correct id It is the _pci id_ that @Rampftl provided. I had a look at both screenshots. ( I don't understand why there are two.)...

@Rampftl do you meanwhile know why there is a working server?

This issue was never an _iPXE_ issue. In the initial message is _"boot with iPXE one server is working fine"_. The _"Any idea?"_ was responsed with _"provide PCI ids"_ and...

Let's assume that some day two lists of PCI device IDs are provided. With `sort` and `diff` we can find easily differences. With some luck is the only different indeed...

This update was written after reading _"I expect both machine to have same behaviors"_, which reminded me of this issue. And that did remind of [_How to ask smart questions_](http://www.catb.org/~esr/faqs/smart-questions.html),...

Idea: Install `/bin/echo` as build dependency. My websearch on `NixOS /bin/echo` yielded: * [known problem](https://github.com/hmemcpy/milewski-ctfp-pdf/issues/208) * [workaround](https://github.com/hmemcpy/milewski-ctfp-pdf/issues/209)

> Someone update the docs here to list DHE. Tq! https://ipxe.org/crypto Part of current source of that wiki page. ``` ===== Supported configurations ===== ^ Protocol versions | TLSv1.0 TLSv1.1...

Why is this merge request still open? I'm asking because dangling PRs do drain human energy. We, the iPXE project, pay a price each time when we see open merge...