Page 6 of 19 FirstFirst ... 4567816 ... LastLast
Results 51 to 60 of 190

Thread: ath9k

  1. #51
    Join Date
    Aug 2008
    Location
    Northfield, IL
    Beans
    88
    Distro
    Ubuntu Intrepid Ibex (testing)

    Re: ath9k

    Quote Originally Posted by volanin View Post
    Good News!

    Answering requests, I have created a shell script that will compile the ath9k wireless driver for your kernel. You might be using any ubuntu kernel, or even a custom kernel, and the script will generate a custom deb package for you.

    To use it, just extract the script from the tar.gz attached.
    Then run:

    Code:
    $ bash compat-wireless-ath9k-20080806.sh
    If you have a custom kernel, you must edit the script before running it, to remove the ubuntu-specific kernel dependencies. Just open the extracted script in any text editor and change both lines:

    Code:
    PACKAGE_DEPENDENCIES="linux-image-`uname -r`"
    
    BUILD_DEPENDENCIES=(build-essential module-init-tools linux-headers-`uname -r`)
    To:

    Code:
    PACKAGE_DEPENDENCIES=""
    
    BUILD_DEPENDENCIES=(build-essential module-init-tools)
    And run it!
    The script will generate a shiny new deb package for you!
    Please, try it and report any bugs to me here!


    compat-wireless-ath9k-20080806.tar.gz (Hosted at Rapidshare)

    It finally works!! Thanks for making an awesome script!
    Ubuntu: IntrepidIbex x32 v8.10-RC (v2.6.27-7 Kernel) / Gnome / C.Fusion / Emerald / Guake / wicd / etc...
    UbuntuUser#: 24216

  2. #52
    Join Date
    May 2007
    Beans
    126

    Re: ath9k

    great, thx!

  3. #53
    Join Date
    Aug 2008
    Location
    Northfield, IL
    Beans
    88
    Distro
    Ubuntu Intrepid Ibex (testing)

    Exclamation Problems again! :(

    volanin (or anyone else), I was experiencing some random crashes with my Ubuntu installation. Figured that it may have been caused with removing Beryl & installing compiz-fusion. So, I decided to wipe the OS and reinstall. After updating everything, I only installed wicd & the ath9k driver w/ the script you posted. However, the problem still persists.

    Basically, what happens is the OS will crash randomly when I am on wireless and attempting to access a website or download something through the terminal (or anywhere else). However, when I am on wired (ethernet), the problem goes away. Any ideas? I have tried a multitude of setting configurations and can't get rid of it (static vs dhcp, manual config vs wicd, etc).
    Ubuntu: IntrepidIbex x32 v8.10-RC (v2.6.27-7 Kernel) / Gnome / C.Fusion / Emerald / Guake / wicd / etc...
    UbuntuUser#: 24216

  4. #54
    Join Date
    Aug 2008
    Beans
    32

    Re: ath9k

    I don't know what's wrong, but with all the variants of installing ath9k on my computer I've tried, the associated devices never show up in /dev or ifconfig. What am I missing here?

    - Tim

  5. #55
    Join Date
    Aug 2005
    Location
    Huntsville, AL, USA
    Beans
    7,526
    Distro
    Ubuntu

    Re: ath9k

    Quote Originally Posted by tbessie View Post
    I don't know what's wrong, but with all the variants of installing ath9k on my computer I've tried, the associated devices never show up in /dev or ifconfig. What am I missing here?

    - Tim
    are you sure that you have a card that is supported by ath9k? Is the module loaded? Is there any output about it in dmesg?

  6. #56
    Join Date
    Aug 2008
    Beans
    32

    Re: ath9k

    Quote Originally Posted by cyberdork33 View Post
    are you sure that you have a card that is supported by ath9k? Is the module loaded? Is there any output about it in dmesg?
    Sorry, I had to change the wireless interface in wicd to wlan0 (from ath0).

    So now it thinks it's connecting, but it still doesn't work for me. Logs show it got an IP address, but I cannot ping any ip. I'm using a MacBook Pro v3, and it's supposed to be supported ("0b:00.0 Network controller: Atheros Communications Inc. AR5418 802.11abgn Wireless PCI Express Adapter (rev 01)". I am getting the following errors in syslog. Also, sometimes the machine hangs at the end of this, and sometimes not, but either way, I get no connection:

    Aug 21 14:28:51 pixelpipe-tbessie dhclient: There is already a pid file /var/run/dhclient.pid with pid 9418
    Aug 21 14:28:51 pixelpipe-tbessie dhclient: removed stale PID file
    Aug 21 14:28:51 pixelpipe-tbessie dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Aug 21 14:28:51 pixelpipe-tbessie dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Aug 21 14:28:51 pixelpipe-tbessie dhclient: All rights reserved.
    Aug 21 14:28:51 pixelpipe-tbessie dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Aug 21 14:28:51 pixelpipe-tbessie dhclient:
    Aug 21 14:28:51 pixelpipe-tbessie dhclient: wmaster0: unknown hardware address type 801
    Aug 21 14:28:52 pixelpipe-tbessie dhclient: wmaster0: unknown hardware address type 801
    Aug 21 14:28:52 pixelpipe-tbessie dhclient: Listening on LPF/wlan0/00:1e:52:74:0c:cf
    Aug 21 14:28:52 pixelpipe-tbessie dhclient: Sending on LPF/wlan0/00:1e:52:74:0c:cf
    Aug 21 14:28:52 pixelpipe-tbessie dhclient: Sending on Socket/fallback
    Aug 21 14:28:55 pixelpipe-tbessie dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
    Aug 21 14:28:59 pixelpipe-tbessie kernel: [ 485.727991] wlan0: authenticate with AP 00:1f:f3:07:d7:d7
    Aug 21 14:28:59 pixelpipe-tbessie kernel: [ 485.821060] wlan0: authenticate with AP 00:1f:f3:07:d7:d7
    Aug 21 14:28:59 pixelpipe-tbessie kernel: [ 485.909314] wlan0: authenticate with AP 00:1f:f3:07:d7:d7
    Aug 21 14:28:59 pixelpipe-tbessie kernel: [ 485.962026] wlan0: authentication with AP 00:1f:f3:07:d7:d7 timed out
    Aug 21 14:29:00 pixelpipe-tbessie dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Aug 21 14:29:11 pixelpipe-tbessie dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.913560] wlan0: authenticate with AP 00:1f:f3:07:d7:d7
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.913662] wlan0: authenticate with AP 00:1f:f3:07:d7:d7
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.913977] wlan0: authenticated
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.913980] wlan0: associate with AP 00:1f:f3:07:d7:d7
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.915157] wlan0: RX AssocResp from 00:1f:f3:07:d7:d7 (capab=0x511 status=0 aid=3)
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.915162] wlan0: associated
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 489.923835] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Aug 21 14:29:11 pixelpipe-tbessie kernel: [ 490.025574] padlock: VIA PadLock not detected.
    Aug 21 14:29:11 pixelpipe-tbessie modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.24-21-generic/kernel/drivers/crypto/padlock-aes.ko): No such device
    Aug 21 14:29:12 pixelpipe-tbessie avahi-daemon[5248]: Registering new address record for fe80::21e:52ff:fe74:ccf on wlan0.*.
    Aug 21 14:29:21 pixelpipe-tbessie kernel: [ 493.107670] applesmc: wait status failed: 5 != 4
    Aug 21 14:29:21 pixelpipe-tbessie kernel: [ 493.223940] applesmc: wait status failed: c != 8
    Aug 21 14:29:21 pixelpipe-tbessie kernel: [ 493.302110] wlan0: no IPv6 routers present
    Aug 21 14:29:26 pixelpipe-tbessie dhclient: No DHCPOFFERS received.
    Aug 21 14:29:26 pixelpipe-tbessie dhclient: No working leases in persistent database - sleeping.
    Aug 21 14:29:26 pixelpipe-tbessie avahi-autoipd(wlan0)[13343]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
    Aug 21 14:29:26 pixelpipe-tbessie avahi-autoipd(wlan0)[13343]: Successfully called chroot().
    Aug 21 14:29:26 pixelpipe-tbessie avahi-autoipd(wlan0)[13343]: Successfully dropped root privileges.
    Aug 21 14:29:26 pixelpipe-tbessie avahi-autoipd(wlan0)[13343]: Starting with address 169.254.6.90
    Aug 21 14:29:31 pixelpipe-tbessie avahi-autoipd(wlan0)[13343]: Callout BIND, address 169.254.6.90 on interface wlan0
    Aug 21 14:29:31 pixelpipe-tbessie avahi-daemon[5248]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.6.90.
    Aug 21 14:29:31 pixelpipe-tbessie avahi-daemon[5248]: New relevant interface wlan0.IPv4 for mDNS.
    Aug 21 14:29:31 pixelpipe-tbessie avahi-daemon[5248]: Registering new address record for 169.254.6.90 on wlan0.IPv4.
    Aug 21 14:29:35 pixelpipe-tbessie avahi-autoipd(wlan0)[13343]: Successfully claimed IP address 169.254.6.90
    Last edited by tbessie; August 22nd, 2008 at 12:41 AM.

  7. #57
    Join Date
    Aug 2005
    Location
    Huntsville, AL, USA
    Beans
    7,526
    Distro
    Ubuntu

    Re: ath9k

    Actually, you are not getting an IP:
    Quote Originally Posted by tbessie View Post
    Aug 21 14:29:26 pixelpipe-tbessie dhclient: No DHCPOFFERS received.
    It looks like it is associating, but it is not getting an IP. (The 169 address at the bottom of your log is a self-assigned IP that the card will set when it is not offered an IP via DHCP.)

  8. #58
    Join Date
    Feb 2008
    Beans
    1

    Smile Re: ath9k

    Hello Volanin,

    Thanks a lot for your work with compat-wireless-ath9k-20080806.sh
    You did a really great job.

    On my eeepc 1000, I replaced my wifi adapter for an ath9k one.
    I tried to use your script with Ubuntu Kernel 2.6.24-21-eeepc (from array.org) and I encountered problems compiling wme.c which is in mac80211 directory.
    It comes from the ifdef CONFIG_MAC80211_QOS which is not evaluated correctly with my kernel. I did not find exactly why but may there is a confusion with CONFIG_NET_SCHED which is used as comment behind the #endif at the end of wme.h
    I have compiled with no problem using kernel 2.6.24-22 but I needed 2.6.24-21-eeepc for other problems encountered in 2.6.24-22 on my eeepc

    I hope these informations will be usefull in order to correct the problem.

    If it is not clear enough don't hesitate to ask questions

    Thanks a lot for your help

    Regards

    Charles

  9. #59
    Join Date
    Aug 2008
    Beans
    32

    Re: ath9k

    Quote Originally Posted by cyberdork33 View Post
    Actually, you are not getting an IP:


    It looks like it is associating, but it is not getting an IP. (The 169 address at the bottom of your log is a self-assigned IP that the card will set when it is not offered an IP via DHCP.)
    Ah yes, I was wondering about that - looked suspicious.

    Right now, I'm depending on ndiswrapper and a driver from Lenovo, and it's working (tho' for B/G only). Any idea, from what you see, what might be causing the problem when using ath9k (not the symptom, but a possible cause)?

    - Tim

  10. #60
    Join Date
    Aug 2005
    Location
    Huntsville, AL, USA
    Beans
    7,526
    Distro
    Ubuntu

    Re: ath9k

    Quote Originally Posted by tbessie View Post
    Right now, I'm depending on ndiswrapper and a driver from Lenovo, and it's working (tho' for B/G only). Any idea, from what you see, what might be causing the problem when using ath9k (not the symptom, but a possible cause)?
    no, but it is even stranger that changing the driver got dhcp working correctly.

Page 6 of 19 FirstFirst ... 4567816 ... LastLast

Tags for this Thread

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
  •