Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: AR5007 major problems

  1. #1
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    7

    Default AR5007 major problems

    I have tried a number of suggestions on this forum to get my Atheros AR5007 wifi card to work yet I am still hitting a brick wall. Below are the things I have done and the output, I have it running perfectly in Ubuntu using madwifi drivers yet can seem to achieve the same results with BT4.

    First I tried ifconfig ath0 up

    ath0: ERROR while getting interface flags: No such device
    Next I tried ifconfig wifi0 up

    wifi0: ERROR while getting interface flags: No such device
    iwconfig reads as

    lo no wireless extensions.

    eth0 no wireless extensions.

    wmaster0 no wireless extensions.

    wlan0 IEEE 802.11bg ESSID:""
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Tx-Power=0 dBm
    Retry min limit:7 RTS thrff Fragment thr=2352 B
    Power Managementff
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    So i try to install the madwifi drivers that worked in ubuntu

    /madwifi-ng-r3366+ar5007$ make
    Checking requirements... ok.
    Checking kernel configuration... ok.
    make -C /lib/modules/2.6.29.4/build SUBDIRS=/home/tom/madwifi-ng-r3366+ar5007 modules
    make[1]: Entering directory `/usr/src/linux-source-2.6.29.4'

    WARNING: Symbol version dump /usr/src/linux-source-2.6.29.4/Module.symvers
    is missing; modules will have no dependencies and modversions.

    CC [M] /home/tom/madwifi-ng-r3366+ar5007/ath/if_ath.o
    /home/tom/madwifi-ng-r3366+ar5007/ath/if_ath.c: In function 'ath_attach':
    /home/tom/madwifi-ng-r3366+ar5007/ath/if_ath.c:515: error: 'struct net_device' has no member named 'priv'
    There is a lot more output than this but all say the same thing at the end 'struct net_device' has no member named 'priv'

    /home/tom/madwifi-ng-r3366+ar5007/ath/if_ath.c: At top level:
    /home/tom/madwifi-ng-r3366+ar5007/ath/if_ath.c:12879: fatal error: opening dependency file /home/tom/madwifi-ng-r3366+ar5007/ath/.if_ath.o.d: Permission denied
    compilation terminated.
    make[3]: *** [/home/tom/madwifi-ng-r3366+ar5007/ath/if_ath.o] Error 1
    make[2]: *** [/home/tom/madwifi-ng-r3366+ar5007/ath] Error 2
    make[1]: *** [_module_/home/tom/madwifi-ng-r3366+ar5007] Error 2
    make[1]: Leaving directory `/usr/src/linux-source-2.6.29.4'
    make: *** [modules] Error 2
    still no luck, next was to start networking

    /etc/init.d/networking start
    Configuring network interfaces...Internet Systems Consortium DHCP Client V3.1.1


    wmaster0: unknown hardware address type 801
    wmaster0: unknown hardware address type 801
    Listening on LPF/eth0/00:1e:68:98:dd:c5
    Sending on LPF/eth0/00:1e:68:98:dd:c5
    Sending on Socket/fallback
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface eth2 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface ath0 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS mounts
    eth1: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    ]

    wmaster0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    eth1: ERROR while getting interface flags: No such device
    eth1: ERROR while getting interface flags: No such device
    wmaster0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up eth1.
    eth2: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.


    wmaster0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    eth2: ERROR while getting interface flags: No such device
    eth2: ERROR while getting interface flags: No such device
    wmaster0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up eth2.
    ath0: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    ]

    wmaster0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    ath0: ERROR while getting interface flags: No such device
    ath0: ERROR while getting interface flags: No such device
    wmaster0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up ath0.
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.


    wmaster0: unknown hardware address type 801
    wmaster0: unknown hardware address type 801
    Listening on LPF/wlan0/00:22:69:06:38:6a
    Sending on LPF/wlan0/00:22:69:06:38:6a
    Sending on Socket/fallback
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    if-up.d/mountnfs[wlan0]: waiting for interface eth1 before doing NFS mounts
    if-up.d/mountnfs[wlan0]: waiting for interface eth2 before doing NFS mounts
    if-up.d/mountnfs[wlan0]: waiting for interface ath0 before doing NFS mounts
    Again nothing and finally tried to start NetworkManager

    /etc/init.d/NetworkManager start
    bash: /etc/init.d/NetworkManager: No such file or directory
    Very stuck at this stage done many searches on this issue but seem to come across one of the above fixes, any help or pointers in the right direction as to how to fix this would be much appreciated, thanks

  2. #2
    Very good friend of the forum Gitsnik's Avatar
    Join Date
    Jan 2010
    Location
    The Crystal Wind
    Posts
    851

    Default

    Quote Originally Posted by toaksie View Post
    First I tried ifconfig ath0 up
    Next I tried ifconfig wifi0 up
    Without even reading further, take a look at your iwconfig. You have neither ath0 nor wifi0 there (but you do have what...).

    If you can't figure it out from there, try looking at ifconfig and spot the similarities.

    Pardon lack of spoonfeeding, answer seems strikingly obvious to me.
    Still not underestimating the power...

    There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

  3. #3
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    7

    Default

    I tried ifconfig eth0 up too with the same result if thats what you were pointing at?

  4. #4
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    19

    Default

    I have the exact same prob, all the same output as urs, i guess its something simple, but i cant for the life of me figure out what, let me no if you figure it out thanks

  5. #5
    Super Moderator Archangel-Amael's Avatar
    Join Date
    Jan 2010
    Location
    Somewhere
    Posts
    8,012

    Default

    I see you are trying to work as a user and I did not see sudo anywhere.
    Might give that a try first.
    #man sudo
    To be successful here you should read all of the following.
    ForumRules
    ForumFAQ
    If you are new to Back|Track
    Back|Track Wiki
    Failure to do so will probably get your threads deleted or worse.

  6. #6
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    7

    Default

    All commands were executed as root or ´sudo´ just haven´t shown it here, its not that but thanks for the suggestion.

  7. #7
    Very good friend of the forum Gitsnik's Avatar
    Join Date
    Jan 2010
    Location
    The Crystal Wind
    Posts
    851

    Default

    Ok so here is another hint:

    What is the name of your wireless adaptor if it is not wifi0 and it is not ath0? It would be the only adaptor with wireless extensions.
    Still not underestimating the power...

    There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

  8. #8
    Super Moderator Archangel-Amael's Avatar
    Join Date
    Jan 2010
    Location
    Somewhere
    Posts
    8,012

    Default

    /etc/init.d/NetworkManager start
    bash: /etc/init.d/NetworkManager: No such file or directory
    That came from your first post.
    Lets again look at the basics
    Capital letters in linux are treated different then in windows.
    As such NetworkManager and networkmanager are two different beasts.
    # /etc/init.d/ networking start should be all you need.
    Slow down mate take your time and you will get there.

    Also why are you trying to install a a system wide driver out of a users home directory if you are working as root? If you configure to run this out of a users directory and you deleted the directory (or corrupt it) then you will no longer have the driver. Put it in the right place to begin with.
    To be successful here you should read all of the following.
    ForumRules
    ForumFAQ
    If you are new to Back|Track
    Back|Track Wiki
    Failure to do so will probably get your threads deleted or worse.

  9. #9
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    19

    Default

    @Gitsnick

    ive also got the same problem, and I up wlan0, which is what i guess you were talking about, but if i put wlan0 into monitor mode it works, but then airodump wont detect any networks at all as if im too far away, but i have like 10 networks around me and on my other laptop it works fine, any ideas?

  10. #10
    Very good friend of the forum Gitsnik's Avatar
    Join Date
    Jan 2010
    Location
    The Crystal Wind
    Posts
    851

    Default

    Quote Originally Posted by cjloz View Post
    @Gitsnick

    ive also got the same problem, and I up wlan0, which is what i guess you were talking about, but if i put wlan0 into monitor mode it works, but then airodump wont detect any networks at all as if im too far away, but i have like 10 networks around me and on my other laptop it works fine, any ideas?
    You might try taking it out of monitor mode and using iwlist or something similar from the command line. That way you can at least see if the card is reporting anything (that and you tend to get better diagnostics from a command line). If something shows up there, you might get enough of an output to follow through with the issue. If you can pick stuff up outside of monitor mode you're at least part way to success. Let us know how you go.
    Still not underestimating the power...

    There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

Page 1 of 3 123 LastLast

Posting Permissions

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