Re: ifconfig create breaks between r238227 - r238290?
On Mon, Jul 9, 2012 at 8:19 AM, David Wolfskill da...@catwhisker.org wrote: Just finished updating from r238227 to r238290 on the head slice of my laptop, and was unable to make use of the wlan(4) NIC; I captured the following via cut/paste from ttyv0: ... Setting hostname: localhost. Starting dhclient. em0: no link .. giving up /etc/rc.d/dhclient: WARNING: failed to start dhclient Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting dhclient. dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT dhclient: Setting hostname from localhost to null string ifconfig: ioctl (SIOCAIFADDR): Invalid argument dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT dhclient: reason was PREINIT; no action taken dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 wlan0: not found exiting. /etc/rc.d/dhclient: WARNING: failed to start dhclient Starting Network: lo0 em0 iwn0 fwe0 fwip0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL _MAGIC,VLAN_HWTSO ether 00:24:e8:9c:11:0f nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect status: no carrier iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:21:6a:26:34:c0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8VLAN_MTU ether 4a:4f:c0:37:06:01 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL ch 1 dma -1 fwip0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 lladdr 4a.4f.c0.0.10.37.6.1.a.2.ff.fe.0.0.0.0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL Starting devd. ifconfig: create: bad value Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting dhclient. dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT dhclient: Leaving hostname set to ifconfig: ioctl (SIOCAIFADDR): Invalid argument dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT dhclient: reason was PREINIT; no action taken dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 wlan0: not found exiting. /etc/rc.d/dhclient: WARNING: failed to start dhclient Starting Network: iwn0. iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:21:6a:26:34:c0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ifconfig: create: bad value Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Yesterday, I had updated to: FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #614 238227M: Sun Jul 8 06:47:51 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and things seemed OK -- I was certainly able to use the NIC. :-} uname output from this morning: FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #615 238290M: Mon Jul 9 05:39:15 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 I glanced through the list of commits to head in that range, but didn't note anything glaringly obvious (yet). I hadn't tried a wired NIC on the laptop; I can, if there's anything likely to be of value in doing so. I've attached a copy of the associated dmesg.boot. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. Same thing here, and I tracked it down to r238279: http://svnweb.freebsd.org/base?view=revisionrevision=238279 Not yet sure why though, looking info it... -Brandon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 6:38 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: ... Same thing here, and I tracked it down to r238279: http://svnweb.freebsd.org/base?view=revisionrevision=238279 Not yet sure why though, looking info it... What does `ifconfig -l` say :)? -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
David Wolfskill da...@catwhisker.org wrote in 20120709131957.gi1...@albert.catwhisker.org: da Just finished updating from r238227 to r238290 on the head slice of my da laptop, and was unable to make use of the wlan(4) NIC; I captured the da following via cut/paste from ttyv0: (snip) da da I glanced through the list of commits to head in that range, but da didn't note anything glaringly obvious (yet). da da I hadn't tried a wired NIC on the laptop; I can, if there's anything da likely to be of value in doing so. Gr, it may be due to my change of r238279. I am investigating it. -- Hiroki pgp7OKgM7g6bN.pgp Description: PGP signature
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 06:50:57PM -0700, Garrett Cooper wrote: On Tue, Jul 10, 2012 at 6:38 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: ... Same thing here, and I tracked it down to r238279: http://svnweb.freebsd.org/base?view=revisionrevision=238279 Not yet sure why though, looking info it... What does `ifconfig -l` say :)? g1-228(10.0-C)[1] uname -a FreeBSD g1-228.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #615 238290M: Mon Jul 9 05:39:15 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 g1-228(10.0-C)[2] ifconfig -l em0 iwn0 fwe0 fwip0 lo0 wlan0 g1-228(10.0-C)[3] (I'm connected via the em0 NIC at the moment.) Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpXPc30CcGg0.pgp Description: PGP signature
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 7:06 PM, David Wolfskill da...@catwhisker.org wrote: On Tue, Jul 10, 2012 at 06:50:57PM -0700, Garrett Cooper wrote: On Tue, Jul 10, 2012 at 6:38 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: ... Same thing here, and I tracked it down to r238279: http://svnweb.freebsd.org/base?view=revisionrevision=238279 Not yet sure why though, looking info it... What does `ifconfig -l` say :)? g1-228(10.0-C)[1] uname -a FreeBSD g1-228.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #615 238290M: Mon Jul 9 05:39:15 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 g1-228(10.0-C)[2] ifconfig -l em0 iwn0 fwe0 fwip0 lo0 wlan0 g1-228(10.0-C)[3] (I'm connected via the em0 NIC at the moment.) Curious. I was wondering about this because there's some logic in network.subr that parses ifconfig -l output -- thinking that the fallout might have been there. I would be curious next to see what devd is trying to execute. As a fun next test, try adding the following line to devd.conf (look for dhclient) and restart devd: nomatch bus uhub[0-9]+; Cheers, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 07:15:21PM -0700, Garrett Cooper wrote:
...
Curious. I was wondering about this because there's some logic in
network.subr that parses ifconfig -l output -- thinking that the
fallout might have been there.
I would be curious next to see what devd is trying to execute.
As a fun next test, try adding the following line to devd.conf (look
for dhclient) and restart devd:
nomatch bus uhub[0-9]+;
Well, devd wasn't particularly happy about that:
g1-228(10.0-C)[7] sudo service devd restart
Stopping devd.
Waiting for PIDS: 1736.
Starting devd.
devd: Cannot parse /etc/devd.conf at line 55
/etc/rc.d/devd: WARNING: failed to start devd
g1-228(10.0-C)[8] cat -n devd.conf | grep -wC 3 55
52 notify 0 {
53 match system IFNET;
54 match typeLINK_UP;
55 nomatch bus uhub[0-9]+;
56 media-type ethernet;
57 action /etc/rc.d/dhclient quietstart $subsystem;
58 };
g1-228(10.0-C)[9]
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgpDRv0DBdtbA.pgp
Description: PGP signature
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 7:26 PM, David Wolfskill da...@catwhisker.org wrote:
On Tue, Jul 10, 2012 at 07:15:21PM -0700, Garrett Cooper wrote:
...
Curious. I was wondering about this because there's some logic in
network.subr that parses ifconfig -l output -- thinking that the
fallout might have been there.
I would be curious next to see what devd is trying to execute.
As a fun next test, try adding the following line to devd.conf (look
for dhclient) and restart devd:
nomatch bus uhub[0-9]+;
Well, devd wasn't particularly happy about that:
g1-228(10.0-C)[7] sudo service devd restart
Stopping devd.
Waiting for PIDS: 1736.
Starting devd.
devd: Cannot parse /etc/devd.conf at line 55
/etc/rc.d/devd: WARNING: failed to start devd
g1-228(10.0-C)[8] cat -n devd.conf | grep -wC 3 55
52 notify 0 {
53 match system IFNET;
54 match typeLINK_UP;
55 nomatch bus uhub[0-9]+;
56 media-type ethernet;
57 action /etc/rc.d/dhclient quietstart $subsystem;
58 };
g1-228(10.0-C)[9]
My bad -- I misread the manpage.
This will work better probably:
notify 0 {
match system IFNET;
match type LINK_UP;
media-type 802.11;
match devicewlan[0-9]+;
action /etc/rc.d/dhclient quietstart $subsystem;
};
Kind of funny why things are setup that way anyhow for wireless post-8.x...
All else fails, you sh -x the rc.d script at boot or add
rc_debug=YES to rc.conf and see what's getting passed along...
Cheers,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 07:36:09PM -0700, Garrett Cooper wrote:
..
Well, devd wasn't particularly happy about that:
...
My bad -- I misread the manpage.
This will work better probably:
notify 0 {
match system IFNET;
match type LINK_UP;
media-type 802.11;
match devicewlan[0-9]+;
action /etc/rc.d/dhclient quietstart $subsystem;
};
OK; didn't get a whine from that:
devd.conf: 327 lines, 9863 characters.
g1-228(10.0-C)[10] rcsdiff -u !$
rcsdiff -u devd.conf
=
RCS file: RCS/devd.conf,v
retrieving revision 1.1
diff -u -r1.1 devd.conf
--- devd.conf 2012/07/11 02:20:46 1.1
+++ devd.conf 2012/07/11 02:45:04
@@ -73,6 +73,7 @@
match system IFNET;
match typeLINK_UP;
media-type 802.11;
+ match device wlan[0-9]+;
action /etc/rc.d/dhclient quietstart $subsystem;
};
g1-228(10.0-C)[11] sudo service devd restart
devd not running?
Starting devd.
g1-228(10.0-C)[12]
Kind of funny why things are setup that way anyhow for wireless
post-=
8.x...
All else fails, you sh -x the rc.d script at boot or add
rc_debug=YES to rc.conf and see what's getting passed along...
Well, the wifi LED isn't lit on the machine (which it is -- at
least blinking -- if it's even trying to associate). So I suspect that
the devd.conf stuff is a bit moot at this point.
I've attached a typescript from sh -x /etc/rc.d/netif restart.
(And then I need to flip back to my stable/8 slice in order to maintain
domestic tranquility -- don't ask. :-})
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
netif.gz
Description: Binary data
pgp2lEATDG1hh.pgp
Description: PGP signature
Re: ifconfig create breaks between r238227 - r238290?
Hiroki Sato h...@freebsd.org wrote in 20120711.110203.744611964086256554@allbsd.org: hr David Wolfskill da...@catwhisker.org wrote hr in 20120709131957.gi1...@albert.catwhisker.org: hr hr da Just finished updating from r238227 to r238290 on the head slice of my hr da laptop, and was unable to make use of the wlan(4) NIC; I captured the hr da following via cut/paste from ttyv0: hr (snip) hr da hr da I glanced through the list of commits to head in that range, but hr da didn't note anything glaringly obvious (yet). hr da hr da I hadn't tried a wired NIC on the laptop; I can, if there's anything hr da likely to be of value in doing so. hr hr Gr, it may be due to my change of r238279. I am investigating it. Committed a fix as r238361. Please try it. -- Hiroki pgpTqXxJ7neAD.pgp Description: PGP signature
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 9:02 PM, Hiroki Sato h...@freebsd.org wrote: David Wolfskill da...@catwhisker.org wrote in 20120709131957.gi1...@albert.catwhisker.org: da Just finished updating from r238227 to r238290 on the head slice of my da laptop, and was unable to make use of the wlan(4) NIC; I captured the da following via cut/paste from ttyv0: (snip) da da I glanced through the list of commits to head in that range, but da didn't note anything glaringly obvious (yet). da da I hadn't tried a wired NIC on the laptop; I can, if there's anything da likely to be of value in doing so. Gr, it may be due to my change of r238279. I am investigating it. -- Hiroki The issue with wpa_supplicant failing is due to the wlan0 interface being cloned from one of the new usbus/usbpf devices instead of the actual wireless network device: brandon@m6500[/home/brandon] $ ifconfig -v wlan0 wlan0: flags=1UP metric 0 mtu 0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL groups: usbus How this might be happening is strange to me, how can the system be confused as to which interface to clone from? Off-by-one error somewhere? -Brandon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 8:11 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Tue, Jul 10, 2012 at 9:02 PM, Hiroki Sato h...@freebsd.org wrote: David Wolfskill da...@catwhisker.org wrote in 20120709131957.gi1...@albert.catwhisker.org: da Just finished updating from r238227 to r238290 on the head slice of my da laptop, and was unable to make use of the wlan(4) NIC; I captured the da following via cut/paste from ttyv0: (snip) da da I glanced through the list of commits to head in that range, but da didn't note anything glaringly obvious (yet). da da I hadn't tried a wired NIC on the laptop; I can, if there's anything da likely to be of value in doing so. Gr, it may be due to my change of r238279. I am investigating it. -- Hiroki The issue with wpa_supplicant failing is due to the wlan0 interface being cloned from one of the new usbus/usbpf devices instead of the actual wireless network device: brandon@m6500[/home/brandon] $ ifconfig -v wlan0 wlan0: flags=1UP metric 0 mtu 0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL groups: usbus How this might be happening is strange to me, how can the system be confused as to which interface to clone from? Off-by-one error somewhere? Hiroki just fixed it a little while ago. -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
On Tue, Jul 10, 2012 at 10:20 PM, Garrett Cooper yaneg...@gmail.com wrote: On Tue, Jul 10, 2012 at 8:11 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Tue, Jul 10, 2012 at 9:02 PM, Hiroki Sato h...@freebsd.org wrote: David Wolfskill da...@catwhisker.org wrote in 20120709131957.gi1...@albert.catwhisker.org: da Just finished updating from r238227 to r238290 on the head slice of my da laptop, and was unable to make use of the wlan(4) NIC; I captured the da following via cut/paste from ttyv0: (snip) da da I glanced through the list of commits to head in that range, but da didn't note anything glaringly obvious (yet). da da I hadn't tried a wired NIC on the laptop; I can, if there's anything da likely to be of value in doing so. Gr, it may be due to my change of r238279. I am investigating it. -- Hiroki The issue with wpa_supplicant failing is due to the wlan0 interface being cloned from one of the new usbus/usbpf devices instead of the actual wireless network device: brandon@m6500[/home/brandon] $ ifconfig -v wlan0 wlan0: flags=1UP metric 0 mtu 0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL groups: usbus How this might be happening is strange to me, how can the system be confused as to which interface to clone from? Off-by-one error somewhere? Hiroki just fixed it a little while ago. -Garrett Thanks for the heads up, I kept dropping offline to debug, then when I had something to report, I find that a fix had been committed -- now that's service! Thanks Hiroki! -Brandon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ifconfig create breaks between r238227 - r238290?
On Wed, Jul 11, 2012 at 12:01:01PM +0900, Hiroki Sato wrote: ... hr Gr, it may be due to my change of r238279. I am investigating it. Committed a fix as r238361. Please try it. And we have a winner! Thank you! :-) [Sorry for the delay; I had already updated my sources to r238345 early this morning. But that wouldn't build the kernel, so I needed to also apply r238349 r238350, But it did finally work.] Ref.: FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #616 238345M: Tue Jul 10 20:31:44 PDT 2012 r...@g1-228.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and g1-227(10.0-C)[1] ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:21:6a:26:34:c0 inet 172.17.1.227 netmask 0x broadcast 172.17.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid lmdhw-net channel 11 (2462 MHz 11g) bssid 08:10:75:08:8c:1c country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 15 bmiss 10 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL g1-227(10.0-C)[2] Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpjNQrQtm9nZ.pgp Description: PGP signature
ifconfig create breaks between r238227 - r238290?
Just finished updating from r238227 to r238290 on the head slice of my laptop, and was unable to make use of the wlan(4) NIC; I captured the following via cut/paste from ttyv0: ... Setting hostname: localhost. Starting dhclient. em0: no link .. giving up /etc/rc.d/dhclient: WARNING: failed to start dhclient Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting dhclient. dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT dhclient: Setting hostname from localhost to null string ifconfig: ioctl (SIOCAIFADDR): Invalid argument dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT dhclient: reason was PREINIT; no action taken dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 wlan0: not found exiting. /etc/rc.d/dhclient: WARNING: failed to start dhclient Starting Network: lo0 em0 iwn0 fwe0 fwip0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL _MAGIC,VLAN_HWTSO ether 00:24:e8:9c:11:0f nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect status: no carrier iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:21:6a:26:34:c0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8VLAN_MTU ether 4a:4f:c0:37:06:01 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL ch 1 dma -1 fwip0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 lladdr 4a.4f.c0.0.10.37.6.1.a.2.ff.fe.0.0.0.0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL Starting devd. ifconfig: create: bad value Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting dhclient. dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT dhclient: Leaving hostname set to ifconfig: ioctl (SIOCAIFADDR): Invalid argument dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT dhclient: reason was PREINIT; no action taken dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 wlan0: not found exiting. /etc/rc.d/dhclient: WARNING: failed to start dhclient Starting Network: iwn0. iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:21:6a:26:34:c0 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ifconfig: create: bad value Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Yesterday, I had updated to: FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #614 238227M: Sun Jul 8 06:47:51 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and things seemed OK -- I was certainly able to use the NIC. :-} uname output from this morning: FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #615 238290M: Mon Jul 9 05:39:15 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 I glanced through the list of commits to head in that range, but didn't note anything glaringly obvious (yet). I hadn't tried a wired NIC on the laptop; I can, if there's anything likely to be of value in doing so. I've attached a copy of the associated dmesg.boot. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #615 238290M: Mon Jul 9 05:39:15 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 WARNING: WITNESS option enabled, expect reduced performance. WARNING: DIAGNOSTIC option enabled, expect reduced performance. MEMGUARD DEBUGGING ALLOCATOR INITIALIZED: MEMGUARD map base: 0xc840 MEMGUARD map limit: 0xcad34000 MEMGUARD map size: 42192 KBytes CPU: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz (2793.07-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10676
