From: "John W. Linville" <linville@tuxdriver.com>
To: "Gordon, Charles" <Charles.Gordon@digi.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Is there a bug in 2.6.29-rc8 support of Ad-Hoc mode?
Date: Wed, 26 May 2010 09:28:12 -0400 [thread overview]
Message-ID: <20100526132811.GA5823@tuxdriver.com> (raw)
In-Reply-To: <8DCC153EAFE67A4B990A840E829F704B017C658D5E6C@mtk-sms-exch01.digi.com>
On Wed, May 26, 2010 at 06:57:31AM -0500, Gordon, Charles wrote:
> I am trying to get a driver I'm developing to work with Ad-Hoc mode on
> Linux 2.6.29-rc8. I am running into a problem. I have traced it down
> to the routine ieee80211_scan_work. I use the following commands to
> start Ad-Hoc mode:
>
> ifconfig wlan0 down
> iwconfig wlan0 mode Ad-Hoc essid "AdHocID"
> ifconfig wlan0 up
FWIW, this should probably look more like the following:
ifconfig wlan0 down
iwconfig wlan0 mode Ad-Hoc
ifconfig wlan0 up
iwconfig wlan0 essid "AdHocID"
If that doesn't work, you may be experiencing some bug. But...
> Can someone either confirm that this is a known problem with
> 2.6.28-rc8, or tell me what my driver could be doing to cause this
> problem?
This kernel is ancient, even if you meant 2.6.29-rc8 like you
said originally. And it is not even an actual release version
(e.g. 2.6.29). I could be wrong, but I doubt there will be much
interest among the people here in working on the internals of such
an old kernel. Is there some reason you can't try something newer?
2.6.34 was just released...
Good luck!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-05-26 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 11:57 Is there a bug in 2.6.29-rc8 support of Ad-Hoc mode? Gordon, Charles
2010-05-26 13:28 ` John W. Linville [this message]
2010-05-26 15:07 ` Gordon, Charles
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 0:00 Charles Gordon
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=20100526132811.GA5823@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Charles.Gordon@digi.com \
--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).