iPXE EFI - no network after the DHCP sequence
|
2016-09-13, 20:03
Post: #2
|
|||
|
|||
RE: iPXE EFI - no network after the DHCP sequence
If you must include ipxe into firmware then uou should build the efi that is specific for your NIC, and not use snp.
Let me try and explain like this: snponly.efi will have support for the SNP/NII driver framework and relies on the existing firmware driver to work, if you add this to your firmware you normally replace the existing NIC fw. if you add both that will be weird. Instead you will want to use the ipxe native driver for your nic (if there is one) to help further on this we would need more info about your hardware, pci device id to begin with 8086:xxxx you can get it in linux with lspci -nn My suggestion otherwise is to use the normal firmware pxe support and chain into snponly.efi or ipxe.efi Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
iPXE EFI - no network after the DHCP sequence - cbn38 - 2016-09-12, 17:21
RE: iPXE EFI - no network after the DHCP sequence - NiKiZe - 2016-09-13 20:03
RE: iPXE EFI - no network after the DHCP sequence - cbn38 - 2016-09-14, 16:34
RE: iPXE EFI - no network after the DHCP sequence - cbn38 - 2016-09-16, 17:31
RE: iPXE EFI - no network after the DHCP sequence - methodmath - 2016-12-16, 21:43
RE: iPXE EFI - no network after the DHCP sequence - NiKiZe - 2016-12-17, 11:04
|
User(s) browsing this thread: 3 Guest(s)