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

Bug#606824: marked as done (firmware-iwlwifi: after disconnect unable to reconnect until reboot)



Your message dated Fri, 9 Aug 2013 16:31:46 +0200
with message-id <20130809143146.GC21262@inutil.org>
and subject line Re: iwlwifi: after disconnect unable to reconnect until reboot
has caused the Debian Bug report #606824,
regarding firmware-iwlwifi: after disconnect unable to reconnect until reboot
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.)


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

After losing the wireless connection for whatever reason, i'm unable to
reconnect to it and actually acess the internet. It reconnects to the router by
all traffict just dies and it's unable to do anything. trying a ping google.com
-c 4 reports that the host is unknown even though i'm supposedly connected to
the network.

This issue has been in it since a couple months back but it's just now that i'm
able to say with certainty that it's the package that is the problem. It's
either that or whatever package tells the OS to start routing through my
wireless adapter isn't doing its job. Since ethernet connections still work
just fine.



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools               0.98.5     tools for generating an initramfs
ii  linux-image-2.6.32-5-amd64 [l 2.6.32-28  Linux 2.6.32 for 64-bit PCs

-- no debconf information



--- End Message ---
--- Begin Message ---
On Fri, Dec 02, 2011 at 08:29:20PM -0600, Jonathan Nieder wrote:
> Hey,
> 
> macarthur wrote:
> > On 12/12/2010 08:25 PM, Ben Hutchings wrote:
> >> On Sat, 2010-12-11 at 19:37 -0500, macarthur wrote:
> 
> >>> After losing the wireless connection for whatever reason, i'm unable to
> >>> reconnect to it and actually acess the internet.
> [...]
> > I'm also using Gnome Network Manager, it comes back, if i press fn+f2 which
> > is the wireless button, or if i continually flip the switch ~8 times. it
> > then shows itself once more and lets me connect. And this even if the thing
> > says that it's enable network+wireless. It doesn't show itself at all.
> >
> > If there's any sort of information that'd help like a log of some kind i'd
> > be glad to provide it.
> 
> Ok, here's what we'll need to know in order to fix this:
> 
>  - Does a current (3.x.y) kernel reproduce the same trouble?  If not,
>    we can try some intermediate versions from snapshot.debian.org to
>    try to find the fix and apply it to squeeze.
> 
>    The only packages from outside squeeze that should be needed to test
>    this are the kernel image itself, linux-base, and initramfs-tools.
> 
>  - Unfortunately there have been some iwlwifi fixes recently upstream,
>    so if a 3.1.y kernel reproduces trouble, you should also try a kernel
>    from the 3.2 series before reporting it upstream.  These versions
>    should appear in experimental sooner or later, or if you have time to
>    build from source following the instructions from [1], that's even
>    better.
> 
>  - In any event, full output from "dmesg" (as an attachment) after
>    booting up with the most recent kernel you're able to test and
>    reproducing the problem would be useful.
> 
> Thanks and hope that helps,
> Jonathan

No further feedback, closing the bug.

Cheers,
        Moritz

--- End Message ---

Reply to: