Date: Thu, 09 Jul 1998 20:02:44 -0700 From: Mike Smith <mike@smith.net.au> To: "Jim Flowers" <jflowers@ezo.net> Cc: mobile@FreeBSD.ORG Subject: Re: WaveLAN Driver for FreeBSD Message-ID: <199807100302.UAA05047@antipodes.cdrom.com> In-Reply-To: Your message of "Thu, 09 Jul 1998 20:41:45 EDT." <01bdab9b$84139b80$8a8266ce@violet.eznets.canton.oh.us>
next in thread | previous in thread | raw e-mail | index | archive | help
> I see you were one of the last to overhaul the wl driver in 1997. I just > moved an old style (pre 802.11) wavelan isa card and the hard drive with > FreeBSD 2.2.6 on it from a 486 machine to a Pentium 133 and it stopped > initializing with the following log entries: The ISA Wavelans are *extremely* touchy about timing. You might want to start by checking the ISA config on your new board, and perhaps crank out some of the I/O delays, etc. > wl0: bldcu() not ready after reset > wl0: diag() failed; status=0,inw=0,outw=e0a0 > scb_status 0 > scb_command 100 > scb_cbl adaa > cu_cmd 8007 > wl0: init(): trouble resetting board You could also try upping STATUS_TRIES in sys/i386/isa/if_wl.c. There are quite a few hardcoded spin loops in this driver; the diag() failure may be symptomatic of this too. What motherboard chipset(s) are you using? > Pings to the ifconfigged address work; beyond that, no response. Not > surprising as it's marked up but not running. Same problem on a Pentium > 200MMX. Um, actually if it's responding to pings, then it's more or less working. > Any suggestions on where to start looking? I know the driver is well > documented so that's where I'll be but I'm hoping this is something obvious > as I would like to use a lot of these boxes for a wireless network. Try increasing the STATUS_TRIES value to start with, and see if that makes the 'not ready after reset' message go away. If that works, then increase the value in the poll loop above the 'failed; status' message. It may be that when the first is fixed, the card will be happy enough that the rest work. Apart from that, it actually appears to be running well enough - the interrupt handler is being called, and it's sending stuff in response OK, it's just not passing the startup tests. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807100302.UAA05047>