Page 1 of 5 123 ... LastLast
Results 1 to 10 of 48

Thread: *-network UNCLAIMED - so how do I 'claim' it?

  1. #1
    Join Date
    Nov 2008
    Location
    West Sussex, UK
    Beans
    32
    Distro
    Ubuntu 16.04 Xenial Xerus

    *-network UNCLAIMED - so how do I 'claim' it?

    Hi,

    I've just put Jaunty on a Toshiba NB200 netbook. Got all 9.04 updates using a 3G dongle (so that works!).

    I am trying to install a Netgear 3G Broadband Wireless Router. I'm pretty sure that I've set it up correctly as I can access the web (wirelessly) from my Windows laptop, as I'm using it now.

    I can connect to the web using my 3G mobile broadband dongle directly connected. My problem - I just can't figure out how to configure things for wireless in Jaunty!

    I know the wifi wasn't disabled in Windows (apparently, that would mean it could never be enabled in Linux) and I have downloaded the 'backports' for Jaunty (which is supposed to help) - but I still cannot find any wireless networks available.

    Code:
    lspci
    told me that the network controller is an Atheros AR9285.

    Code:
    lshw -C network
    returned

    *-network UNCLAIMED
    description: Network controller
    product: AR9285 Wireless Network Adapter (PCI-Express)
    vendor: Atheros Communications Inc.
    physical id: 0
    bus info: pci@0000.03.00.0
    version: 01
    width: 64 bits
    clock: 33MHz
    capabilities: bus_master cap_list
    configuration: latency=0


    Now, I'm afraid that I have no idea what that means, but I'm guessing that 'unclaimed' may mean something - how do I 'claim' it?. I'm fully aware that this is due to my short-comings and not Ubunto. What is that 'stupid something' that I either have or haven't done? Please, point me on my way to a suitable tutorial.

    Tim

  2. #2
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,241
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    'Unclaimed' typically means no driver has attached to it. If you have an internet connection by ethernet, I suggest you open a terminal and do:
    Code:
    sudo apt-get install linux-backports-modules-jaunty
    Reboot and you should be good to go.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  3. #3
    Join Date
    Mar 2009
    Location
    Helsinki, Finland
    Beans
    650
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    What it means that there's no driver claiming it and thus it's not going to work until one does. For your card, you'll need the ath9k driver. And if you installed the backports, then you should indeed have the latest version available.

    Try opening up a terminal and running lsmod | grep ath, if the output is empty, it means there are no modules with "ath" in them loaded. If it does show some, then run sudo modprobe -r <module_name> for each possibility (ath_pci, ath5k & ath9k - the rest depend on these and get unloaded as the driver module is unloaded). Afterwards run sudo modprobe ath9k to load the ath9k and then try lshw again to see if it gets associated this time.

  4. #4
    Join Date
    Nov 2008
    Location
    West Sussex, UK
    Beans
    32
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    Guys, thank you.

    I'd downloaded the backports, but I hadn't rebooted! What an old fool!

    Many thanks,

    Tim

  5. #5
    Join Date
    Jul 2011
    Beans
    3
    Distro
    Lubuntu

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    Quote Originally Posted by t0mppa View Post
    What it means that there's no driver claiming it and thus it's not going to work until one does. For your card, you'll need the ath9k driver. And if you installed the backports, then you should indeed have the latest version available.

    Try opening up a terminal and running lsmod | grep ath, if the output is empty, it means there are no modules with "ath" in them loaded. If it does show some, then run sudo modprobe -r <module_name> for each possibility (ath_pci, ath5k & ath9k - the rest depend on these and get unloaded as the driver module is unloaded). Afterwards run sudo modprobe ath9k to load the ath9k and then try lshw again to see if it gets associated this time.
    Man... lol...

    I got this error after I tried to use a Ndiswrapper driver... then the network goes unclaimed...

    When I loaded the modprobe, the network became "claimed".

    Thank You!

  6. #6
    Join Date
    Jul 2011
    Beans
    3
    Distro
    Lubuntu

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    Quote Originally Posted by fernando_pinhal View Post
    Man... lol...

    I got this error after I tried to use a Ndiswrapper driver... then the network goes unclaimed...

    When I loaded the modprobe, the network became "claimed".

    Thank You!
    Oh my god... guys... now I found something that made me mad...

    On a new boot, I used a lsmod and didn't find any ath9k modules... so, I used a sudo modprobe ath9k, then the modules was found on the next lsmod... how can I set the ath9k module to load with the computer boot??

  7. #7
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,241
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    Open a terminal and do:
    Code:
    sudo su
    echo ath9k >> /etc/modules
    exit
    You should be all set.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  8. #8
    Join Date
    Jul 2011
    Beans
    3
    Distro
    Lubuntu

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    Quote Originally Posted by chili555 View Post
    Open a terminal and do:
    Code:
    sudo su
    echo ath9k >> /etc/modules
    exit
    You should be all set.
    Man.. thank you so much... unfortunately... I formated my HD last night when I discovered that the wireless conected and didn't surf on the network...

    The windows, worked fine... so the problem should be any mess the I made with the Lubuntu...

    I'll kept this information you gave me safe.

    Thanks.

  9. #9
    Join Date
    Jan 2013
    Beans
    1

    Question Re: *-network UNCLAIMED - so how do I 'claim' it?

    I have an Intel DQ67EP motherboard with the 82579LM NIC onboard. It is showing up as unclaimed when i run lshw -C network.

    I installed the e1000e 2.1.4 driver directly from intel
    I follewed the make install process then
    I then rmmod e1000e
    then modprobe e1000e
    I have also rebooted

    when i did both of these activities the add in nic which is detected lost connectivity and came back but the onboard one is still unclaimed.
    Any help would be appreciated.


    Code:
    sudo lshw -C network
      *-network               
           description: Ethernet interface
           product: 82574L Gigabit Network Connection
           vendor: Intel Corporation
           physical id: 0
           bus info: pci@0000:01:00.0
           logical name: eth0
           version: 00
           serial: 68:05:ca:0d:4b:2a
           size: 1Gbit/s
           capacity: 1Gbit/s
           width: 32 bits
           clock: 33MHz
           capabilities: pm msi pciexpress msix bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.1.4-NAPI duplex=full firmware=1.8-0 ip=10.1.1.125 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
           resources: irq:16 memory:fe5c0000-fe5dffff memory:fe500000-fe57ffff ioport:e000(size=32) memory:fe5e0000-fe5e3fff memory:fe580000-fe5bffff
      *-network UNCLAIMED
           description: Ethernet controller
           product: 82579LM Gigabit Network Connection
           vendor: Intel Corporation
           physical id: 19
           bus info: pci@0000:00:19.0
           version: 04
           width: 32 bits
           clock: 33MHz
           capabilities: pm msi cap_list
           configuration: latency=0
           resources: memory:fe600000-fe61ffff memory:fe628000-fe628fff ioport:f080(size=32)
    Code:
    uname -a
    Linux Polymethia 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
    Code:
    lsmod
    Module                  Size  Used by
    e1000e                195811  0 
    w83627ehf              38805  0 
    hwmon_vid              12827  1 w83627ehf
    coretemp               13525  0 
    snd_hda_codec_hdmi     32474  1 
    snd_hda_codec_realtek   224066  1 
    parport_pc             32866  0 
    ppdev                  17113  0 
    rfcomm                 47604  0 
    bnep                   18281  2 
    bluetooth             180104  10 rfcomm,bnep
    dm_multipath           23230  0 
    psmouse                87692  0 
    snd_hda_intel          33773  3 
    snd_hda_codec         127706  3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
    snd_hwdep              13668  1 snd_hda_codec
    snd_pcm                97188  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
    serio_raw              13211  0 
    tpm_tis                18804  0 
    snd_seq_midi           13324  0 
    snd_rawmidi            30748  1 snd_seq_midi
    snd_seq_midi_event     14899  1 snd_seq_midi
    snd_seq                61896  2 snd_seq_midi,snd_seq_midi_event
    snd_timer              29990  2 snd_pcm,snd_seq
    snd_seq_device         14540  3 snd_seq_midi,snd_rawmidi,snd_seq
    snd                    78855  16 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
    i915                  472941  4 
    joydev                 17693  0 
    mac_hid                13253  0 
    drm_kms_helper         46978  1 i915
    drm                   242038  5 i915,drm_kms_helper
    soundcore              15091  1 snd
    snd_page_alloc         18529  2 snd_hda_intel,snd_pcm
    i2c_algo_bit           13423  1 i915
    mei                    41616  0 
    video                  19596  1 i915
    lp                     17799  0 
    parport                46562  3 parport_pc,ppdev,lp
    usbhid                 47199  0 
    hid                    99559  1 usbhid
    dm_raid45              78155  1 
    xor                    12894  1 dm_raid45
    dm_mirror              22203  0 
    dm_region_hash         20918  1 dm_mirror
    dm_log                 18564  4 dm_raid45,dm_mirror,dm_region_hash
    Last edited by zack0273; January 5th, 2013 at 06:12 AM. Reason: adding specs

  10. #10
    Join Date
    Jan 2013
    Beans
    1

    Re: *-network UNCLAIMED - so how do I 'claim' it?

    So I have managed to do even worse, and this is the situation for both my Ethernet and Wireless connections! Is there a way of finding out which particular drivers I need, and installing them from a USB stick or something?

    I have a Realtek RTL8111/8168B ethernet controller, and a Intel Centrino Wireless-N Network controller.

    Any ideas?

Page 1 of 5 123 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •