On Fri, 2006-01-06 at 09:53 -0800, Jesse Barnes wrote:
> > No, that's needed because it doesn't reassociate if going down and
> > up again.
>
> Will that be fixed at some point, or should I modify my scripts to do
> it automatically?
It'll get fixed in the end, yes. At all times while the device
On Fri, 2006-01-06 at 09:53 -0800, Jesse Barnes wrote:
> Will that be fixed at some point, or should I modify my scripts to do it
> automatically?
It will be fixed at some point. But I don't know when :)
johannes
signature.asc
Description: This is a digitally signed message part
On Friday, January 6, 2006 1:35 am, Johannes Berg wrote:
> On Thu, 2006-01-05 at 19:17 -0800, Jesse Barnes wrote:
> > It may just be that getting an address takes a long time, but it
> > seems like running the 'iwconfig bcm43xx essid virtuousgeek' during
> > the 'ifup' operation gets things going.
On Thu, 2006-01-05 at 19:17 -0800, Jesse Barnes wrote:
> It may just be that getting an address takes a long time, but it seems like
> running the 'iwconfig bcm43xx essid virtuousgeek' during the 'ifup' operation
> gets things going.
No, that's needed because it doesn't reassociate if going dow
Using the driver that comes with the fedora rawhide kernel-2.6.15-1.1819_FC5
for ppc, I've managed to get the bcm43xx device in my PowerBook5,4 up and
running!
[EMAIL PROTECTED] ~]$ cat /etc/sysconfig/networking/devices/ifcfg-bcm43xx
DEVICE=bcm43xx
ONBOOT=no
BOOTPROTO=dhcp
NETMASK=
DHCP_HOSTNAME
