public inbox for gentoo-user-br@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thiago Nunes <thiagonunesrs@gmail.com>
To: gentoo-user-br@lists.gentoo.org
Subject: Re: [gentoo-user-br] Fwd: RTL8187/8189
Date: Tue, 9 Nov 2010 18:43:19 -0200	[thread overview]
Message-ID: <AANLkTinY-DYYH1u0sCXxA_bFS4FDeAGmPxrZ0W1YmcYT@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinrPsBPEUdKs9xCTnDZ1yMqUFS9y+0o69ncmidt@mail.gmail.com>

Posta teu lspci -k aqui.

2010/11/9 yermandu <yermandu@gmail.com>:
> Pessoal não consigo fazer minha placa wireless funcionar, estou bem
> desconfiado que ela não autentica com o roteador. Retirei a senha do
> roteador e ele da time out na conexão.
> No windows 7 x64 funciona normalmente.
> Meu se alguem tiver alguma sugestão ou souber como posso acolher mais
> informações sobre se ele está realmente autenticando e o que acontece quando
> não há senhas.
> Minha placa esta no whitelist do AP.
>
>
> Att.
>
> ---------- Forwarded message ----------
> From: Yermandu Patapitafious <yermandu.dev@gmail.com>
> Date: 2010/11/9
> Subject: Fwd: RTL8187/8189
> To: yermandu@gmail.com
>
>
> ---------- Forwarded message ----------
> From: Larry Finger <Larry.Finger@lwfinger.net>
> Date: 2010/11/9
> Subject: Re: RTL8187/8189
> To: Yermandu Patapitafious <yermandu.dev@gmail.com>
> Cc: linux-wireless@vger.kernel.org
>
>
> On 11/08/2010 09:25 PM, Yermandu Patapitafious wrote:
>> Hellow people, i buy an notebooks with the rtl8187b card.
>> I have heavyly test several ways to connect but the connection can not
>> be stabilize a connection.
>> I try with wep, wap, without pass. Nothing works with this card.
>>
>> Identify card
>>
>> # lsusb
>>
>> ```
>> Bus 002 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B
>> Wireless 802.11g 54Mbps Network Adapter
>> ```
>>
>> I wanna give the atention for ID Card: 0bda:**8189**
>>
>> This is not 0bda:8187 or 0bda:8197. Why i saying this? Because i
>> research in the web and discover some people can get work with
>> 0bda:8187 using linux kernel native module driver. But i can not
>> really make connection i think something wrong with this card or
>> module or maybe not, i dont know.
>
> Driver rtl8187 should work for this device.
>
>> When i set the AP with pass i got this error:
>>
>> # iwconfig wlan0 essid "MyEssid" key s:asciikey
>>
>> Error for wireless request "Set Encode" (8B2A) :
>>      SET failed on device wlan0 ; Invalid argument.
>>
>> Using wep, wap or nopass.
>
> AFAIK, that has never worked.
>
>> I subscribe the ht tps: //qa.  mandriva  .com/ show_bug.cgi?id= 39334
>> a bug open related with this problem. Recently we have a notice in
>> comment #11 to try use with ndiswrapper
>>
>> ```
>>
>> ndiswrapper -a 0bda:8197 net8187b
>>
>> ```
>> But i can not force to use 0bda:8197 instead 0bda:8189:
>
> Your device has the USB ID 0bda:8189. That is built into the device. You
> cannot
> force it to be anything else.
>
>> ```
>> # ndiswrapper -a 0bda:8197 net8187b
>> Driver 'net8187b' is already used for '0BDA:8197'
>>
>> # ndiswrapper -l
>> net8187b : driver installed
>>         device (0BDA:8189) present (alternate driver: rtl8187)
>> ```
>>
>> But this can not be donned, it persist to use 8189 and not 8197 as
>> related.
>>
>> I don't know anyone else with this same model of card, and how we can
>> do more tests. I hope someone can help us.
>>
>> Im using
>>
>> Linux  2.6.33.7-rt29 #7 SMP PREEMPT RT Tue Nov 2 23:41:52 BRST 2010
>> x86_64 Pentium(R) Dual-Core CPU T4200 @ 2.00GHz GenuineIntel GNU/Linux
>>
>> I test in the Ubuntu, Mandriva and Arch and no lucky. I try in Gentoo
>> too with kernel 2.6.36-wl+ (git version), same issues.
>
> It appears that you are not using NetworkManager. If that is true, then I
> think
> you should be preparing the correct ifcfg file for whatever distro you are
> using. The hexadecimal key for WEP should be there. A passphrase almost
> never
> works there. If you want to use WPA or WPA2, then you can use a phrase;
> however,
> you will need to install wpa_supplicant and the appropriate configuration
> file.
>
> To test is your device is working, get rid of ndiswrapper, allow rtl8187 to
> load, and (as root) run the command 'iwlist scan'. If you can see your AP,
> then
> the device is likely OK.
>
> You should pick one of the distros you mention, and post a request for
> wireless
> configuration on their help forum. I do not use any of them, and I'm not
> familiar with their specific configuration.
>
> I also recommend using NetworkManager. It makes wireless setup much easier.
>
> Larry
>
>
>
> --
> yermandu
>
>
>
> --
> yermandu [at] useplanta dot com dot br
>



  reply	other threads:[~2010-11-09 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTim5a_oFXqjMrcbcUipG5FijbUoFkYF6ri6zO7wg@mail.gmail.com>
     [not found] ` <4CD9474C.5010003@lwfinger.net>
     [not found]   ` <AANLkTikeau91Ey3bOH2fUMYLv35pf=JaxG2YMwwJNywJ@mail.gmail.com>
2010-11-09 18:01     ` [gentoo-user-br] Fwd: RTL8187/8189 yermandu
2010-11-09 20:43       ` Thiago Nunes [this message]
2010-11-09 22:51         ` yermandu
2010-11-10 17:55           ` Fernando Boaglio
2010-11-10 18:33             ` yermandu
2010-11-10 23:56               ` Fernando Boaglio

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=AANLkTinY-DYYH1u0sCXxA_bFS4FDeAGmPxrZ0W1YmcYT@mail.gmail.com \
    --to=thiagonunesrs@gmail.com \
    --cc=gentoo-user-br@lists.gentoo.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