From: Stefan Assmann <sassmann@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>, ali@internetdog.org
Subject: Re: r8712u issue
Date: Mon, 18 Jul 2011 09:49:00 +0200 [thread overview]
Message-ID: <4E23E56C.9000202@redhat.com> (raw)
In-Reply-To: <4E205984.5040803@lwfinger.net>
On 15.07.2011 17:15, Larry Finger wrote:
> On 07/15/2011 09:42 AM, Stefan Assmann wrote:
>> Hi Larry,
>>
>> I'm wondering if you're looking into any issues concerning the
>> driver. The problem I'm currently facing is that the driver does not
>> recognize any network disconnects. So whenever the network goes down the
>> driver will still report it's connected and thus doesn't reconnect when
>> the network is up again.
>>
>> Btw I'm using a 0bda:8172 usb adapter with 2.6.39.
>> Thanks for your help!
>
> I need more details. What distro? How are you controlling the network? If
> NetworkManager, what version?
The system is a headless debian squeeze with a self build vanilla 2.6.39
kernel. The network is handled by debian scripts I just added the following
to /etc/network/interfaces:
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
No NM involved.
> When this situation occurs, what is output to the dmesg log?
Sorry, I don't have the output at hand but IIRC basically nothing special
occurred in dmesg. The interface even keeps it's IP although the wireless
was long gone.
>
> I do not see this situation on my system/device. Whenever the connection is
> dropped, NM reconnects.
>
> There are a recent patches that might have an effect. Can you build your own kernel?
Sure, just let me know what to test.
Ccing Ali Bahar to this reply, since he has seen something similar.
Ali, if I can help with testing please let me know. And no rush in case
you're busy with something else atm. I appreciate the help.
Stefan
next prev parent reply other threads:[~2011-07-18 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E2051F3.20103@redhat.com>
2011-07-15 15:15 ` r8712u issue Larry Finger
2011-07-16 15:15 ` Ali Bahar
2011-07-18 7:49 ` Stefan Assmann [this message]
2011-07-18 8:27 ` Ali Bahar
2011-07-18 8:46 ` Stefan Assmann
2011-07-18 9:01 ` Ali Bahar
2011-07-18 14:53 ` Larry Finger
2011-07-18 15:01 ` Stefan Assmann
2011-07-18 15:44 ` Larry Finger
2011-07-19 13:24 ` Stefan Assmann
2011-07-19 13:28 ` Ali Bahar
2011-07-19 16:06 ` Larry Finger
2011-07-19 16:16 ` Ali Bahar
2011-07-19 17:16 ` Stefan Assmann
2011-07-19 17:32 ` Ali Bahar
2011-07-19 17:38 ` Stefan Assmann
2011-07-19 17:45 ` Larry Finger
2011-07-19 17:51 ` Ali Bahar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E23E56C.9000202@redhat.com \
--to=sassmann@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=ali@internetdog.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.