creating menus

[errorsmith]

(2011-12-21 08:20)robinsmidsrod Wrote:  To my knowledge, any .lkrn compile target will never use UNDI, even if support for it is compiled in. It will always use a native driver.

mcb30: Is this a bug or a limitation?

As to your asrock problem, you might make it work with typical chainloading. What is the PCI id of the network card on that card, and what does it identify as in Linux?

I didn't compile it my self. I took the .lkrn from the .iso wich is provided on ipxe.org. I don't have any computers with Linux installed and ipxe doesn't compile on FreeBSD. I'm able to boot via a livecd, but this isn't quite the environment to compile anything. Currently I don't have a computer available to install Linux, as I'm in the process of transforming my machines into diskless clients.

I tried the asrock as follows:

• ipxe: boots, can load any .ipxe script and execute ist as long as I don't try to chain into (g)pxelinux.0 or gpxe.
• (g)pxelinux.0 et al: loads the pxe module but stalls / hangs when loading its configfile (i.e. /pxelinux.xfg/default).
• gpxe: doesn't even comes this far: hangs when trying to get a dhcp address, aparently isn't able to access the NIC correctly
  

According to lspci -v -nn -Q it identifies as follows:

Code:

00:11.0 Ethernet controller [0200]: ALi Corporation ULi 1689,1573 integrated ethernet. [10b9:5263] (rev 40)
        Subsystem: ASRock Incorporation Device [1849:5263]
        Flags: bus master, medium devsel, latency 128, IRQ 17
        I/O ports at e400 [size=256]
        Memory at febfec00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
        Kernel driver in use: uli526x
        Kernel modules: uli526x

With kind regards,
errorsmith