0

I'm providing some of the terminal tests I done for a Dell latitude D520 with Ubuntu 12.04. Please any help will be appreciated.

PCI:

lspci

02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 
0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

Network Devices:

ifconfig -a 
eth1      Link encap:Ethernet  HWaddr 00:19:b9:71:8b:fb  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B) 
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0 
          inet6 addr: ::1/128 Scope:Host 
          UP LOOPBACK RUNNING  MTU:16436  Metric:1 
          RX packets:1165 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:1165 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:0 
          RX bytes:120890 (120.8 KB)  TX bytes:120890 (120.8 KB) 

wlan0     Link encap:Ethernet  HWaddr 00:1b:fc:53:d9:c6  
          inet addr:192.168.1.105  Bcast:192.168.1.255  Mask:255.255.255.0 
          inet6 addr: fe80::21b:fcff:fe53:d9c6/64 Scope:Link 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
          RX packets:23937 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:20346 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:20576514 (20.5 MB)  TX bytes:2424136 (2.4 MB)

Local Networks:

nm-tool 

NetworkManager Tool 

State: connected (global) 

- Device: eth1 ----------------------------------------------------------------- 
  Type:              Wired 
  Driver:            b44 
  State:             unavailable 
  Default:           no 
  HW Address:        00:19:B9:71:8B:FB 

  Capabilities: 
    Carrier Detect:  yes 

  Wired Properties 
    Carrier:         off 


- Device: wlan0  [kouts103] ---------------------------------------------------- 
  Type:              802.11 WiFi 
  Driver:            b43 
  State:             connected 
  Default:           yes 
  HW Address:        00:1B:FC:53:D9:C6 

  Capabilities: 
    Speed:           54 Mb/s 

  Wireless Properties 
    WEP Encryption:  yes 
    WPA Encryption:  yes 
    WPA2 Encryption: yes
mchid
  • 43,546
  • 8
  • 97
  • 150
GEORGE
  • 13
  • 6
  • 1
    I know it sounds silly but what happens when you plug the ethernet cable in and then click on auto eth0 from the dropdown network menu? – mchid Mar 29 '15 at 03:05
  • Hi mchid, nothing happens. with my limited knowledge I think the problem is in the driver b44 is unavailable or Kernel can't see the driver. – GEORGE Mar 30 '15 at 04:14
  • Hey, can you please post the output of lspci -knn | grep -A 3 Ethernet to show that the device is using the driver; it will show "driver in use:" and other usefull info that can help. Although it looks like the driver is enabled, you can run sudo modprobe b44 to enable the kernel module and lsmod | grep b44 to verify that it is indeed loaded by the kernel. – mchid Mar 30 '15 at 05:43
  • see if this helps http://askubuntu.com/questions/71159/network-manager-says-device-not-managed – mchid Apr 21 '15 at 18:13
  • Hi mchid, I have tried the /71159/ suggestion and couldn't get wired connection. sudo nano /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile no-auto-default=00:19:B9:71:8B:FB, managed=true From the weeks of reading about BCM4401 driver connecting to SSB bus, it looks that when update manager added lib/modules/3.2.0-58-generic-pae, the wireless BCM43 took over SSB Bus, thou it shows b44 connected. I also installed Synaptic File Manager, and when i search for B44 it cannot find it. I appreciate any help. Thanks – GEORGE Apr 23 '15 at 00:46
  • The problem is the NetworkManager.conf file and I have updated the answer for you. – mchid Apr 23 '15 at 06:53
  • Hi mchid, I have tried the suggestion but still wireless takes control. Why in Synaptic b44 not showing? Is it possible the the software updater doing 3.2.0-80-generic-pae changed priority of ssb, I also noticed: lsmod has b43 in 4 places 1) mac80211 436493 1 b43 2) cfg80211 178877 2 b43,mac80211 3) bcma 25651 1 b43 4) ssb 50691 2 b43,b44 Sorry mchid but i don't understand much these things, I' m just questioning and maybe give you a hind. Thanks George – GEORGE Apr 24 '15 at 18:25
  • 1
    Possible duplicate of Ethernet Network card BCM4401-B0 no longer recognised? – Pilot6 Feb 02 '16 at 19:31

2 Answers2

1

Edit:

Okay, from what you have listed, the problem appears to be your file /etc/NetworkManager/NetworkManager.conf. Open a terminal and execute the following commands:

sudo nano /etc/NetworkManager/NetworkManager.conf

Make sure the file says the following, nothing more and nothing less:

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

Then, press CTRL + o to save the file and press CTRL + x to exit the file.

Also, edit /etc/network/interfaces:

sudo nano /etc/network/interfaces

and make sure that file has only these contents:

auto lo
iface lo inet loopback

Again, press CTRL + o to save the file and press CTRL + x to exit the file.

Finally, execute the following commands and then connect the ethernet cable and it should automatically detect and switch to the wired connection:

sudo service network-manager restart

To explain: You do not want the network as "managed" because you want to use "auto" instead. Also, you had the default device set to wireless for some reason. Both of those together along with the "no-auto-..." flag basically disabled your auto ethernet.

Normally, however, when the system has a wired and a wireless connection, the wired connection will always be favored and used even when they are both connected because eth0 should be the default device by default.

First:

Unplug in your ethernet cable and run the following commands from an open terminal:

sudo mkdir /etc/NetworkManager/connections-backup
sudo mv /etc/NetworkManager/system-connections/* /etc/NetworkManager/connections-backup

sudo service network-manager restart

Plug the ethernet cable in. Click on the network-manager icon on your desktop panel to open the dropdown menu. Then, click on "Auto eth0"

enter image description here

If you see some message similar to "device is not managed" or "device is managed" please let me know and I'll post instructions on how to get around that.

If the network doesn't come up like it's supposed to after plugging in the ethernet cable, run the following command to refresh network-manager:

sudo service network-manager restart

Or, run these commands to unload and reload the driver:

sudo modprobe -r b44
sudo modprobe b44

If it says that b44 is in use, run 

lsmod | grep b44

and it should show what module is using b44. Use 

sudo modprobe -r

followed by the module name you wish to disable before pressing enter.

Then, use 

sudo modprobe b44

to load the driver again.

Make sure your firewall is not blocking ports 67, 68, or 53 (dhcp, dhcp, and dns respectively). If you have not done anything to explicitly block these ports they are most likely not blocked as you would've had to have set a rule yourself to block them.

mchid
  • 43,546
  • 8
  • 97
  • 150
  • Hi mchid, sorry for the delay. I have tried what you suggested: sudo mkdir /etc/NetworkManager/connections-backup sudo mv /etc/NetworkManager/system-connections/* /etc/NetworkManager/connections-backup command not found sudo service network-manager restart network-manager stop/waiting network-manager start/running, process 2424 and I connected the ethernet cable and voilà!! worked like a charm!! thank you very much mchid!!! – GEORGE Apr 01 '15 at 13:33
  • Hi mchid, when i shutdown the laptop and restarted, the ethernet was lost.when I run the command: lsmod | grep b44 b44 31364 0 ssb 50691 2 b44,b43 b44 showns in red color. please help – GEORGE Apr 01 '15 at 20:03
  • @GEORGE those are in red because you used grep to search for them so the results show in red. Try restarting network-manager again and see if it worked like last time. If a network exists for eth0 you may need to erase it so the network can set it self up again. – mchid Apr 04 '15 at 17:11
  • @GEORGE oh yeah, that also means those drivers are currently loaded and in use – mchid Apr 04 '15 at 20:44
  • Hi mchid, I tried network-manager, no luck. I have followed your suggestion: sudo modprome -r b44 to reveme b44 from: ssb module ssb 50691 2 b43 and removeded. Then, use sudo modprobe b44 to load the driver again. put it pouts it back with b33 at module ssb. Sorry for the delay, this week we having the grand kinds. an help will be appreciated. – GEORGE Apr 08 '15 at 01:47
  • Hi mchid, I have been reading many posts concerning BCM4401 driver connected to SSB bus and it gives me the impression that bcm44 after updating, the Network manager, could not communicate with SSB busand allowing BCM43 to take over. I wonder if you want me to open Software Center in History, and remove the last network. Also network-manager icon dropdown menu doesn't have Auto Ethernet, if that means something. Thanks – GEORGE Apr 15 '15 at 02:03
0

Finally suspected the Ethernet port not working,and at, system setting / network showed wired unplugged. I ordered from ebay "USB to Ethernet connector" and soonest i connected, Ethernet became live.

GEORGE
  • 13
  • 6