linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: TK <tobutaz@gmail.com>
To: "Felipe Maya" <fmay@cetuc.puc-rio.br>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RaLink RT2500 802.11g Cardbus/mini-PCI
Date: Wed, 2 Apr 2008 13:54:03 +0200	[thread overview]
Message-ID: <20080402135403.7fa54310@localhost> (raw)
In-Reply-To: <36899.201.36.161.238.1207134354.squirrel@mamao.cetuc.puc-rio.br>

Le Wed, 2 Apr 2008 08:05:54 -0300 (BRT),
"Felipe Maya" <fmay@cetuc.puc-rio.br> a =C3=A9crit :
> filename:     =20
> /lib/modules/2.6.23.1/kernel/drivers/net/wireless/rt2x00/rt2500pci.ko
> license:        GPL
> description:    Ralink RT2500 PCI & PCMCIA Wireless LAN driver.
> version:        2.0.8
> author:         http://rt2x00.serialmonkey.com
> srcversion:     C8DB886C372334BFB58A7F5
> alias:          pci:v00001814d00000201sv*sd*bc*sc*i*
> depends:        rt2x00pci,rt2x00lib,mac80211,eeprom_93cx6
> vermagic:       2.6.23.1 SMP mod_unload 686 4KSTACKS

Don't tell me, tell the list.
Even then, I am not sure this is enough info to help you, since there
are no obvious error messages.
Maybe this is simply ad-hoc mode being broken in rt2x00, I think this
code is too new. You could try with a way more recent kernel
(the wireless-testing tree suggested above), or check that the legacy
driver does ad-hoc (I think it does).

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2008-04-02 11:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080402001213.7b879a73@localhost>
     [not found] ` <36899.201.36.161.238.1207134354.squirrel@mamao.cetuc.puc-rio.br>
2008-04-02 11:54   ` TK [this message]
2008-04-02 12:47     ` RaLink RT2500 802.11g Cardbus/mini-PCI Ivo Van Doorn
2008-03-31 21:41 Felipe Maya
2008-03-31 22:10 ` Ivo van Doorn
2008-03-31 22:28   ` Felipe Maya
2008-04-01  8:51     ` Ivo Van Doorn
2008-04-01 22:11       ` TK
2008-04-02 11:19       ` Felipe Maya
2008-04-01 18:01   ` Thomas Bächler
2008-04-01 18:09     ` Ivo van Doorn
2008-04-02  9:13       ` Thomas Bächler
2008-04-02 10:21       ` Thomas Bächler
2008-04-02 17:32         ` Ivo van Doorn
2008-04-10 22:07           ` Thomas Bächler
2008-04-12 10:46             ` Ivo van Doorn
2008-04-12 17:54               ` Thomas Bächler
2008-04-13  7:41                 ` Johannes Berg
2008-04-13  8:07                   ` Johannes Berg
2008-04-13  8:31                     ` Thomas Bächler
2008-04-13 10:11                       ` Johannes Berg
2008-04-13 10:20                         ` Thomas Bächler
     [not found]                         ` <1ba2fa240804130936o21f08b50jd35658a495a66eb4@mail.gmail.com>
2008-04-13 17:42                           ` Johannes Berg
2008-04-14 11:39                       ` Ivo van Doorn
2008-04-14 17:37                         ` Thomas Bächler
2008-04-14 17:47                           ` Ivo van Doorn

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=20080402135403.7fa54310@localhost \
    --to=tobutaz@gmail.com \
    --cc=fmay@cetuc.puc-rio.br \
    --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).