I'm using ipxe.lkrn/ipxe.exe. Since my mail I found out that
the problem is that when building ipxe.lkrn from the new(er)
snapshot the resulting binary does not fall back to undipci
when no drivers are found, whereas the march snapshot does.
I have had no time to check the latest version in which, as
it seems to me from the commit logs, the build process was
fixed.
What do you think
-will undipci work in ipxe.exe?
-is 8086:1502 (there is an 8086:1503, too) would be a difficult
task?
Levente
On 12/6/2011 2:34 PM, Michael Brown wrote:
On Saturday 26 Nov 2011 19:09:48 Levente LEVAI wrote:
I have diffed the e1000e driver code in the two versions and found no
relevant
differences (found only some icr related changes, in fact). In
particular 0x1502 is
not explicitly listed in either driver, but the March snapshot still
grabs the device.
Does anyone has a clue what's happening? How should I set about
resolving this
issue?
Are you sure that the March snapshot is using the e1000e driver? Is it
possible that you were using something like undionly.kpxe (which uses the UNDI
driver rather than a native driver)?
Michael
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo/ipxe-devel
