-pureg doesn't stick - ReadList.com

4 msg	New world - about 2 days old - SSH broken?
1 msg	changes in src/lib/libc/arm/SYS.h broke arm
2 msg	sh: environment corrupt; missing value for LANG
1 msg	Can't profile automatically on x86/amd64 (after...

-pureg doesn't stick
\ Nathan Lay (5 Jul 2007)
. \ Sam Leffler (7 Jul 2007)

1 msg	HEADS UP: late change regarding syscalls in 7.0
5 msg	Everything (but /boot) on ZFS - trouble
54 msg	Environment handling broken in /bin/sh with cha...
1 msg	ptrace, freebsd and vmware dont get along?
7 msg	Panic with areca and dd
7 msg	glib compile problem
1 msg	USB mouse not working
1 msg	HEADS UP: i4b partly disconnect from build
13 msg	HEADS UP: getenv() and family API change
22 msg	ZFS vs Samba Debugging Results ... Need Help.
11 msg	HEADS UP: destroy_dev_sched() KPI in the tree
3 msg	bge/BCM5704 crashes current
4 msg	Dell PE2850 freeze on boot with PXE and FreeBSD...
11 msg	FAST_IPSEC is now IPSEC, please be advised...
3 msg	panic when printing

Subject:	-pureg doesn't stick
Group:	Freebsd-current
From:	Nathan Lay
Date:	5 Jul 2007

Hi list,
I have a recent build (July 1st) and running it as a wireless AP (with
hostapd WPA-PSK TKIP) using an atheros card (Netgear WG311T). I've been
trying to get an 802.11b client on and I noticed the -pureg option
doesn't seem to stick at bootup.
e.g. this rc.conf line
ifconfig_ath0="ssid Lamp channel 9 mediaopt hostap -pureg up"

Maybe -pureg should be specified somewhere else in that line (I also
tried "-pureg ssid Lamp channel 9 mediaopt hostap up")? Anyways, I have
to login and manually set ath0 to -pureg in order for the 802.11b client
to associate.

On the side, this same 802.11b client, which runs Windows XP SP2 on a
Thinkpad T41 with an Intel Pro Wireless 2100 card will crash both
6.2-RELEASE and 7.0-CURRENT with medium traffic (e.g. streaming radio).
On the 6.2 system, the backtrace indicated that the crash occurred in
the atheros driver itself ... though I don't have that core handy. I
have no way to get the debugging information off of the 7.0 machine
until I get a serial cable, but the crash is fairly simple to reproduce
(The 6.2 system would crash 2-3 times a day due to this one client).

Best Regards,
Nathan Lay

_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"