I've asked this question, but unfortunatelly got no answer,
may be this time I will be more lucky ...
I have 486DX2/66 based ISA only machine, equipped with
WaveLAN/AT-2.4 board (ISA of cource). Currently it works
under Linux (WaveLAN-related stuff is OK). I have a tension
to move towards the FreeBSD for this machine... While trying
to determine the WaveLAN usability under FreeBSD (I've tryed
2.2.5-RELESE and 2.2.6-RELESE - the same results), I got the
at the time the kernel is booting, wavelan driver
successfully locates the board (it reports correct
port, irq, nwid, frequensy...),
BUT when I try to configure the wl0 interface, i.e.
ifconfig wl0 inet 220.127.116.11 netmask 255.255.255.252
the kernel exclames the following:
wl0: entered wlioctl() <- OK let it be so <g>, WLDEBUG is on
wl0: entered wlinit()
wl0: enterd wlhwrst() <- the trouble begins here
wl0: DCE_STATUS: 0x0, Correct NWID's: 0, Wrong NWID's: 0
THR_PRESET: 0xc0, SIGNAL_LVL: 64, SILENCE_LVL: 64
SIGNQUAL: 0x75, NETW_ID: fe:0, DES: 254 <- it's not mine
NETWID, nor mine
counterpart's, more -
there are no DES
wl0: doing wlack()
wl0: entered wldiag()
wl0: wldiag() failed: status=0; inw=0; outw=e0a0
wl0: init(): trouble resetting board <- THE FINAL BOOH !
wl0: wlintr() called
And the interface becomes "UP", but not "RUNNING"...
This is diagnostics from 2.2.5 kernel, 2.2.6 "blows"
with approximatelly the same stuff...
Please, lety me know if it is possible to insist the wl0
to become the "RUNNING" interface....
With best regards,
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message