Date: Sun, 5 Aug 2001 16:26:23 -0400 From: Peter Radcliffe <pir@pir.net> To: freebsd-mobile@freebsd.org Subject: Re: Boot hangs on mounting root with wireless card inserted. Message-ID: <20010805162623.G22031@pir.net> In-Reply-To: <a05001905b7934ea4f69f@[192.168.1.1]>; from michelle@primelogic.com on Sun, Aug 05, 2001 at 01:10:51PM -0700 References: <NDBBIHADDPAMAJLBPGCHGENADKAA.welch@igillc.com> <a05001905b7934ea4f69f@[192.168.1.1]>
next in thread | previous in thread | raw e-mail | index | archive | help
Michelle Brownsworth <michelle@primelogic.com> probably said:
> Not with WEP, unfortunately. It's my understanding (perhaps flawed)
> that WEP is currently fully functional only with the WaveLAN
> (Lucent/Orinoco) cards,
Incorrect. Certainly works with the Cisco Aironet cards and a few
others.
> card "SMC" "SMC2632W"
> config 0x1 "wi" 3 0x10000
> insert /etc/pccard_ether $device
> insert /etc/start_wi0
> remove /sbin/ifconfig $device delete
>
> /etc/start_wi0:
>
> #!/bin/sh
> wicontrol -i wi0 -p 1
Port type 1 (infrastructure) is the default, these days. Do you need
this is all ?
> The first question is, is it correct to place the second insert for
> the start_wi0 shell script in pccard.conf? If not, where should the
> script be executed? If so, should it precede the insert for
> pccard_ether? I've seen folks stick multiple inserts in pccard.conf,
> so I'm assuming it's okay to have more than one. I've even seen
> wicontrol statements placed directly in pccard.conf instead of in a
> separate script, the way I'm doing it. I guess what I'm getting at
> is, what is the standard, kosher, USDA-approved method of adding
> wicontrol commands?
There is no real, approved, way to do this. Personally I stay away
from adding extra insert lines since it makes pccard.conf files
unmaintainable.
/etc/start_if.${ifn} will get run at boot time and by pccard_ether so
you could lose the insert line and replace start_wi0 with
start_if.wi0. ifconfig in -STABLE and 4.4-R when it is released has
support for configuring cards, so with that you should be able to do
most of it from ifconfig.
I still hack pccard_ether for some additional support, but that's a
bit messy and I'm stil in search of a better way.
> I changed 10 to 3, since that was the interrupt that the card seemed
> to be set at by default. However, I did not change the 0x10000
> address, even though dmesg reports the SMC's address range as
> 0x0240-0x024f. I've seen some entries in pccard.conf with
>
> config 0x1 "wi" ?
>
> I have also seen this:
>
> config auto "wi" ?
>
> But the SMC works nonetheless with 0x1 and 0x10000, so I guess I'm a
> little confused about this address issue in the config statement, and
> I can't seem to dig up an explanation in the docs.
I'd strongly advise not hardcoding anything if at all possible.
The entry I used with an SMC card was;
card "SMC" "SMC2632W"
config auto "wi" ?
insert /etc/pccard_ether $device start
remove /etc/pccard_ether $device stop
P.
--
pir pir@pir.net pir@net.tufts.edu
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?20010805162623.G22031>