Friday, April 26, 2024
 Popular · Latest · Hot · Upcoming
0
rated 0 times [  0] [ 0]  / answers: 1 / hits: 10891  / 2 Years ago, thu, april 21, 2022, 8:55:11

There seems to be a problem with my network drivers. Neither eth0 nor wlan0 are recognized, and I'm running 13.04 over the 3.8.0-27-generic kernel.



Here's some diagnostic information:




  1. ifconfig yields an entry for lo and some virtual ethernet bridges, but no eth0 nor wlan0.


  2. nm-tool yields:



    NetworkManager Tool

    State: disconnected

  3. cat /etc/network/interfaces yields:



    auto lo
    iface lo inet loopback

  4. lshw -sanitize -C network yields:



    PCI (sysfs)

    *-network UNCLAIMED
    description: Network controller
    product: Centrino Wireless-N 1030 [Rainbow Peak]
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:02:00.0
    version: 34
    width: 64 bits
    clock: 33 MHz
    capabilities: pm msi pciexpress bus_master cap_list
    configuration: latency=0
    resources: memory:f7d00000-f7d01fff
    *-network UNCLAIMED
    description: Ethernet controller
    product: RTL8111/8168 PCI Express Gigabit Ethernet controller
    vendor: Realtek Semiconductor Co., Ltd.
    physical id: 0.2
    bus info: pci@0000:03:00.2
    version: 0a
    width: 64 bits
    clock: 33 MHz
    capabilities: pm msi pciexpress msix vpd bus_master cap_list
    configuration: latency=0
    resources: ioport:e000(size=256) memory:f0004000-f0004fff memory:f0000000-f0003fff



What I've tried:



I tried to connect the NetworkManager Tool. From other sites, I've seen that it sometimes helps to change the file /etc/NetworkManager/NetworkManager.conf from:



[main]
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=false


To:



[main]
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=true


And then doing a sudo service network-manager restart and/or rebooting the machine, but that has not worked either.



Any other ideas? Many thanks.


More From » 13.04

 Answers
0

Some years later ...



I recently hit the same issue in Ubuntu Mate 16.04 (kernel 4.4) with Broadcom 802.11 module and after some digging and questioning I found solved answer in stackoverflow - https://stackoverflow.com/questions/45691434/nmcli-device-unavailable



Basically you have to delete the connection and start over with new connection after network-manager restart.



sudo nmcli c delete connection_name
sudo service network-manager restart


Time to time, it helps and sometimes you have to reboot whole machine. I am suspecting you have to also leave the wifi device resting for some longer time in order to get it working again (but that's purely subjective).



What helped me a lot - to run another terminal with monitor command:



mncli m


Anyway I consider this as a serious bug which is preventing me to use Ubuntu system smoothly and in production state, and it is really pity.


[#29233] Saturday, April 23, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
gavgenerati

Total Points: 120
Total Questions: 126
Total Answers: 119

Location: Marshall Islands
Member since Wed, Feb 9, 2022
2 Years ago
gavgenerati questions
Wed, Jun 22, 22, 17:24, 2 Years ago
Fri, Jul 30, 21, 04:32, 3 Years ago
Fri, Jan 14, 22, 14:20, 2 Years ago
Tue, Jul 27, 21, 19:05, 3 Years ago
;