[gPXE] Wireless boot attempt fail: command not found

Joshua Oreman oremanj at rwcr.net
Sat Jan 16 15:12:09 EST 2010


On Sat, Jan 16, 2010 at 2:31 PM, Juan Belmonte <jbmbhs at gmail.com> wrote:
> THANKS!!!
> There is this new try:
> Waiting for link-up on net0... failed: Not supported (0x3c1f6303)
> And using command prompt:
> gPXE> iwstat
> net0: 00:c0:02:00:02:41 on PCI04:00.0 (open)
>       [Link:down, TX:0 TXE:0 RX:0 RXE:1]
>       [Link status: Not supported (0x3c1f6303)]
>       [RXE: 1 x "Input/output error (0x1d504039)"]
>       [802.11 not associated, Ch:12 Sig:14/40 dB, Qual:0% Rate:1Mbps]
>       [associating...]
> gPXE> iwlist
> Scanning for networks on net0: Invalid argument (0x1c19e002)
>
> Under Freenas(FreeBSD) this machine has good wifi signal in the same
> location.
> Any idea?

First of all, you should grab the command prompt *before* gPXE tries
to do DHCP, waits for link-up, etc. If you come to it afterwards an
"ifclose net0" will restore it to the before-state. "iwlist" doesn't
work when the interface is trying to associate.

Your problem seems to be a lack of WPA support in the gPXE you
downloaded. You might not be trying to connect to a WPA-enabled
network, but if there's one near you with good signal strength, gPXE
may be choosing it automatically. You'll need to "set net0/ssid" the
SSID you want for it to work.

If you *are* trying to connect to a WPA-enabled network, you need a
gPXE image with WPA support. This will probably require another
rom-o-matic patch to make CRYPT_80211_WEP, CRYPTO_80211_WPA,
CRYPTO_80211_WPA2 configurable.

-- Josh


More information about the gPXE mailing list