[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#485034: marked as done (linux-image-2.6.25-2-686: ath5k associates but no network with WEP and AR5211)

Your message dated Sun, 29 Mar 2009 19:43:14 +0200
with message-id <20090329174313.GF3901@baikonur.stro.at>
and subject line Re: Bug#485034: linux-image-2.6.25-2-686: ath5k associates but no network
has caused the Debian Bug report #485034,
regarding linux-image-2.6.25-2-686: ath5k associates but no network with WEP and AR5211
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
485034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485034
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.25-2-686
Version: 2.6.25-4
Severity: normal

I just installed linux-image-2.6.25-2-686 to try and take advantage of
the new ath5k driver. My /etc/network/interfaces file says:

    auto ath0
    iface ath0 inet static
	    wireless_essid <ESSID>
	    wireless_key <KEY>
	    address <ADDRESS>
	    netmask <MASK>
	    gateway <GW>

When I say "ifup ath0", iwconfig reveals that ath0 is associated to my
AP, ifconfig looks right (as it should with a static config). dmesg
looks great too:

    ath5k_pci 0000:02:02.0: registered as 'phy0'
    phy0: Selected rate control algorithm 'pid'
    ath5k phy0: Atheros AR5211 chip found (MAC: 0x42, PHY: 0x30)
    ath5k phy0: RF5111 5GHz radio found (0x17)
    ath5k phy0: RF2111 2GHz radio found (0x23)
    udev: renamed network interface wlan0 to ath0
    ADDRCONF(NETDEV_UP): ath0: link is not ready
    ath0: Initial auth_alg=0
    ath0: authenticate with AP 02:1e:58:07:5d:f2
    ath0: RX authentication from 02:1e:58:07:5d:f2 (alg=0 transaction=2 status=0)
    ath0: authenticated
    ath0: associate with AP 02:1e:58:07:5d:f2
    ath0: RX AssocResp from 02:1e:58:07:5d:f2 (capab=0x11 status=0 aid=2)
    ath0: associated
    ath0: switched to short barker preamble (BSSID=02:1e:58:07:5d:f2)
    ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
    ath0: CTS protection enabled (BSSID=02:1e:58:07:5d:f2)
    ath0: switched to long barker preamble (BSSID=02:1e:58:07:5d:f2)
    ath0: no IPv6 routers present

However, I can't ping my access point.

At this point I'm not sure if the source of this problem is a bug, an
immature driver, or a lack of magic dust in my /etc/network/interfaces
file. Please advise.

$ lspci -nn |grep Ath
02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5211 802.11ab NIC [168c:0012] (rev 01)

$ sudo lspci -v|less
02:02.0 Ethernet controller: Atheros Communications Inc. AR5211 802.11ab NIC (rev 01)
        Subsystem: Phillips Components Device 8310
        Flags: bus master, medium devsel, latency 168, IRQ 11
        Memory at c0210000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
        Kernel driver in use: ath_pci
        Kernel modules: ath5k, ath_pci


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (600, 'testing'), (80, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-686 depends on:
ii  debconf [debconf-2.0]         1.5.22     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92a      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

Versions of packages linux-image-2.6.25-2-686 recommends:
ii  libc6-i686                    2.7-10     GNU C Library: Shared libraries [i

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686:
  linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true
  linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686:
  linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false
  linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686:
  linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686:
  linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686:
  linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686:
  linux-image-2.6.25-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD

--- End Message ---
--- Begin Message --- 
Version: 2.6.29-1

On Sun, Mar 29, 2009 at 10:38:19AM -0700, Bill Wohler wrote:
> maximilian attems <max@stro.at> wrote:
> 
> > > I did, however, try WEP with 2.6.26. My box still did not associate.
> > 
> > could you please try a more recent kernel like 2.6.29.
> > ath5k saw a lot of work since.
> 
> Thanks. There are a couple of issues which will get in my way:
> 
> 1. The new kernels have really, really large /lib/modules directories
>    and are too big for my / partition. I therefore do not anticipate
>    upgrading the kernel on this particular machine any time soon. Know
>    of any HOWTOs for resizing an encrypted LVM root partition? :-)
> 
> 2. I'm using WPA now.
> 
> Sorry about that!

well 1. got fixed with 2.6.29, there were blog post about luks resize
on planet quick search there this popped up
http://www.enricozini.org/2008/tips/resize-luks.html

i'll close that bug report as ath5k improved a lot since and this
is thus assumed fixed.

thanks for report.

--- End Message ---
Reply to: