Awesome, thank you. And yeah, after you mention that I did know that. It's just silly formatting we have at our company (a sysadmin on the tools team actually made me change them all to .ikpxe because he found it confusing to use md5sum's to tell the difference when we moved from gpxe to ipxe...sad.)
On Fri, Aug 3, 2012 at 10:14 AM, Michael Brown <[email protected]>wrote: > On Friday 03 Aug 2012 17:55:28 Hoey, Matthew wrote: > > We use three different images for chain loading depending on the > hardware. > > We use undionly.kpxe, undionly.kkpxe, and r8169.kpxe. I successfully > built > > the first two but I'm getting an "undefined symbol" error when attempting > > to build r8169. The actual card says it is an rtl8167. I'm curious what > is > > the correct kpxe file to build and more importantly, how would I know > that > > without bothering you guys the next time? I noticed there are several > > possible builds I can do (rtl8139, rtl8180, rtl8185); do any of these > > supersede r8169? > > realtek.pxe (which handles 8139 as well as 8169-based cards) is what you > want. > (rtl8169.pxe will also work as a built target, and will give you the exact > same binary.) > > As a side point: only use ".kpxe" with the "undionly" driver; for loading > the > native iPXE driver you want realtek.pxe rather than realtek.kpxe. > > Michael >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
