undionly no packets received
|
2017-07-11, 19:35
Post: #4
|
|||
|
|||
RE: ipxe network stack not functioning
(2017-07-11 19:23)eray Wrote: I used the ipxe.pxe image and it works great. I tried to build the DEBUG image for undionly and used the steps from http://ipxe.org/download#debug_builds as well, but I am not seeing any more output than without the DEBUG mode. I am using a serial console connection to view the host, but I believe it should be echoing there..Good that native drivers work that way we know that it is only the UNDI stack or firmware that is causing your issue with undionly.kpxe On that page you linked there is this explanation: The numeric debug level (3 in this example) is a bitmask: Value Meaning 1 Enable basic debug messages 2 Enable verbose debug messages (e.g. one message per event) 4 Enable extra-verbose debug messages (e.g. one message per byte) 8 Enable I/O tracing (e.g. one message per readl()/writel() call) With DEBUG=undionly:8 you have only enabled the I/O tracing and not the other (more important) ones. If you really want to enable all (you don't, see below) then you should have 8+4+2+1 = 15 so DEBUG=undionly:15 However as I said it is unlikely that you want all since it will give just to much information, just build with my suggested Code: make bin/undionly.kpxe DEBUG=undionly Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
undionly no packets received - eray - 2017-07-10, 20:59
RE: ipxe network stack not functioning - NiKiZe - 2017-07-11, 07:21
RE: ipxe network stack not functioning - eray - 2017-07-11, 19:23
RE: ipxe network stack not functioning - NiKiZe - 2017-07-11 19:35
|
User(s) browsing this thread: 1 Guest(s)