Re: Problem with bcm43xx-80211 Revisited

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



John W. Linville wrote:
On Tue, Aug 28, 2007 at 01:44:28PM -0400, Andrew Robinson wrote:

[root@proteus ~]# lsmod | grep bcm43xx

bcm43xx_mac80211      397601  0
ssb                    35141  1 bcm43xx_mac80211
mac80211              145865  2 rc80211_simple,bcm43xx_mac80211

[root@proteus ~]# ifconfig

eth1      Link encap:Ethernet  HWaddr 00:90:96:79:86:70
          inet addr:192.168.1.25  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::290:96ff:fe79:8670/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:71 errors:0 dropped:0 overruns:0 frame:0
          TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4118 (4.0 KiB)  TX bytes:9175 (8.9 KiB)

[root@proteus ~]# ping -c 3 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.25 icmp_seq=2 Destination Host Unreachable
From 192.168.1.25 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2008ms
, pipe 2

[root@proteus ~]# modprobe bcm43xx-mac80211

[root@proteus ~]# ifup eth1

[root@proteus ~]# ping -c 3 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.87 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.31 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.95 ms

Did you leave something out?  The lsmod showed that you already had
bcm43xx-mac80211 loaded ('-' == '_' for lsmod), and you already had
eth1 marked up and with an IP address assigned.  I can't think of
any reason why those commands should make any difference.

Is this repeatable?  Did you move the laptop during this process?

It's repeatable. I found I did not need to do the 'modprobe bcm43xx-mac80211', just the 'ifup eth1' to get the network working. It seems like some kind of timing problem, like ifcfg-eth1 is getting run before the bcm43xx-mac80211 module has made eth1 the network interface. If eth1 were a wired network interface, it would be like I forgot to plug in the ethernet cable. Does that make any sense or help describe the problem?

Thanks!

Andrew


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux