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

Bug#526805: marked as done (firmware-iwlwifi: wlan0 needs extra poke to come up)

Your message dated Mon, 04 May 2009 01:12:53 +0100
with message-id <1241395973.11921.40.camel@deadeye>
and subject line Re: Bug#526805: firmware-iwlwifi: wlan0 needs extra poke to come up
has caused the Debian Bug report #526805,
regarding firmware-iwlwifi: wlan0 needs extra poke to come up
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.)


-- 
526805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526805
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-iwlwifi
Version: 0.16
Severity: normal

My /etc/network/interfaces has,

iface wlan0 inet dhcp
wireless_mode Managed
wireless_essid "mtbc at home"

I'm doing these tests without encryption, to make it simpler.

If I do an ifup wlan0 then it says,

ADDRCONF(NETDEV_UP): wlan0: link is not ready

and the DHCP goes ahead and doesn't get any response.

If I wait a moment after the ifup (three seconds is normally enough) and then
in another shell set an iwconfig option, e.g., iwconfig wlan0 essid "mtbc at
home", then I get a,

ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

and then the next DHCP request gets an answer.

This has been true for me ever since I first switched to iwl3945 from ipw3945
a few versions and many months ago.

(Also, I tried installing Debian 5.0 from a netinst CD on an identical machine
and after I fed it the firmware the installer couldn't get a DHCP address over
wifi so I had to do the first parts by using wired ethernet to a wireless
access point working as a transparent bridge instead - that worked fine.)

I have no idea if it's relevant, but I mention just in case: during boot the
kernel log mentions,

pci 0000:0a:08.0: Firmware left e100 interrupts enabled; disabling

and,

ACPI: EC: missing confirmations, switch off interrupt mode.

(I wondered if some sort of interrupt is generated when the card associates
with an AP.)

Mark

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (600, 'stable'), (50, 'unstable'), (40, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
pn  initramfs-tools               <none>     (no description available)
pn  linux-image                   <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sun, 2009-05-03 at 19:37 -0400, Mark T.B. Carroll wrote:
> Ben Hutchings <ben@decadent.org.uk> writes:
> 
> >> wireless_essid "mtbc at home"
> 
> > What does "iwconfig wlan0" say in this case?
> 
> Argh. I'm an idiot.
[...]

I wouldn't say that - I'd certainly have expected quotes to be needed.
This is documented though you have to look around a bit.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: