From: "W. van den Akker" <listsrv@wilsoft.nl>
To: Jens Ott - Opteamax <jo@opteamax.de>, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] still same problem
Date: Sun, 18 Jan 2009 10:14:28 +0100 [thread overview]
Message-ID: <200901181014.29052.listsrv@wilsoft.nl> (raw)
In-Reply-To: <497288CA.5070404@opteamax.de>
On Sunday 18 January 2009, you wrote:
> Hi,
>
> I did not find the time to further investigate this issue. Well what I
> did today was compile the latest git-update and the latest hostapd. At
> least the machine does not crash that often, but with 802.11n I can't
> connect to the card ... but this might also be a problem with the card
> in my laptop. I hope I'll find the time to go on testing next week.
>
I have the same problem with my laptop. Cant make a connection if 802.11n
is enabled. I have tested with hostapd 0.6.7 and I didnt notice any changes.
Let me know if you have any progress.
gr,
Willem
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
parent reply other threads:[~2009-01-18 9:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <497288CA.5070404@opteamax.de>]
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=200901181014.29052.listsrv@wilsoft.nl \
--to=listsrv@wilsoft.nl \
--cc=jo@opteamax.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).