On Mon, 2010-12-13 at 12:56 -0600, Dan Williams wrote: > On Thu, 2010-12-09 at 14:41 -0800, Inaky Perez-Gonzalez wrote: > > On Wed, 2010-12-08 at 16:53 +0000, Kerry Hartnett wrote: > > > hi > > > > > > ... > > > > > > 1-5:1.0: firmware interface version 9.3.2 > > > Dec 8 16:35:53 kerry-laptop NetworkManager[841]: <info> (wmx0): > > > preparing device. > > > Dec 8 16:35:53 kerry-laptop NetworkManager[841]: <info> (wmx0): > > > deactivating device (reason: 2). > > > Dec 8 16:35:53 kerry-laptop kernel: [ 2652.255323] > > > ADDRCONF(NETDEV_UP): wmx0: link is not ready > > > > NetworkManager is 'deactivating' it's view of the interface (Dan might > > want to correct my phrasing here) because the network interface has no > > carrier (it is not connected). > > I forget what we wanted to do here; either unmanage wimax interfaces > until we have actual support, or exclude them entirely via a driver > check... Though it can be useful to bring them up manually via wimaxcu > and then have NM control the IP side. That's how it is working so far -- at least on my FC12 machine. wimaxcu plugs it in and then NM brings it up to IP with DHCP.
