linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogerio Luz Coelho <rogluz.news@gmail.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	linux-wireless@vger.kernel.org,
	Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Subject: Re: RTL 8187b - naughty behaviour
Date: Sat, 24 Apr 2010 07:47:53 -0300	[thread overview]
Message-ID: <l2z917a57cb1004240347jcd95308bp5be3b66c8638907d@mail.gmail.com> (raw)
In-Reply-To: <k2s69e28c911004231316u7fd3118qe971919ed8a433d7@mail.gmail.com>

2010/4/23 Gábor Stefanik <netrolller.3d@gmail.com>:
> 2010/4/22 Rogerio Luz Coelho <rogluz.news@gmail.com>:
>> 2010/4/11 Gábor Stefanik <netrolller.3d@gmail.com>:
>>> 2010/4/10 Rogerio Luz Coelho <rogluz.news@gmail.com>:
>>>> 2010/4/10 Gábor Stefanik <netrolller.3d@gmail.com>:
>>>>> On Sat, Apr 10, 2010 at 2:07 PM, Rogerio Luz Coelho
>>>>> <rogluz.news@gmail.com> wrote:
>>>>>> 2010/4/3 Rogerio Luz Coelho <rogluz.news@gmail.com>:
>>>>>>> 2010/4/3 Larry Finger <Larry.Finger@lwfinger.net>:
>>>>>>>> On 04/03/2010 11:49 AM, Rogerio Luz Coelho wrote:
>>>>>>>>>
>>>>>>>>> I have a MS-Win7 instalation on this Laptop and it works 100% even at
>>>>>>>>> longer distances than you report,even with walls in between.
>>>>>>>>>
>>>>>>>>> Will do the tcpperf test as soon as I get home. There are other with
>>>>>>>>> the same problem with my exact chip here in Brasil , that is because
>>>>>>>>> one of our leading Laptop vendors uses this config.
>>>>>>>>
>>>>>>>> What is the exact make and model of the device? It might be difficult
>>>>>>>> for me to get one in the US, but one of the rtl8187 developers lives in
>>>>>>>> Brazil. He should be able to find one.
>>>>>>>>
>>>>>>>
>>>>>>> It愀 a POSITIVO R430L - Core 2 Duo 4GB RAM
>>>>>>>
>>>>>>>
>>>>>>>>> Does it matter that the USB port used in this setting is a connected
>>>>>>>>> to a USB HUB and then to the mother board?
>>>>>>>>
>>>>>>>> Is the hub passive, or is it powered? If the hub is good and not
>>>>>>>> underpowered, it should be OK.
>>>>>>>>
>>>>>>>>> More details and tests will come your way in a day or two ... will
>>>>>>>>> reinstall Mandriva 2010 and do some tests with older kernels.
>>>>>>>>
>>>>>>>> If you can download an openSUSE 11.2 Live CD and burn it, you would not
>>>>>>>> even have to do an installation. That one has a 2.6.31 kernel.
>>>>>>>>
>>>>>>>> Larry
>>>>>>
>>>>>>
>>>>>> Downloaded and installed:
>>>>>>
>>>>>> OpenSuse 11.2 - LiveCD  result: Gnome Network-Manager tells me there
>>>>>> is connection but no ping resposes, Firefox complains about conections
>>>>>> errors.
>>>>>>
>>>>>> Mandriva 2010.0 (kernel 2.6.31-12) result: concection comes and goes
>>>>>> ... generally the first boot of the day connects, but it lasts less
>>>>>> than 5min. The error code is the "deauthentication by local reason
>>>>>> (reason=3) again.
>>>>>>
>>>>>> MS-Win7 : connects and is as fast as ever.
>>>>>>
>>>>>> -- Any other suggestions?
>>>>>>
>>>>>> Rogerio
>>>>>>
>>>>>> PS: Will give OpenSuse a HD install atempt and will try to debug the
>>>>>> Mandriva for some time, future tries involve Debian Stable (old
>>>>>> kernel) and some Fedora (any suggestions?) and the NDISwrapper drive
>>>>>> in a Debian Testing (the Distro I need working)
>>>>>
>>>>> Hi,
>>>>>
>>>>> Please also test Realtek's official r8187b driver. If possible, please
>>>>> do an mmiotrace on that driver.
>>>>
>>>> Ok ... The official Realtek is only for 32bits systems right ? ( At
>>>> least the guys at Realtek support told me so... ) and this mmiotrace
>>>> can be accomplished how? Is it a program, a command, a debug message
>>>> in some form? Sorry, as I said earlier I am NOT a kernel programer.
>>>>
>>>> Rogerio
>>>>
>>>
>>> You need to enable MMIO tracing support in your kernel config, and
>>> recompile your kernel (assuming it is not enabled already - distros
>>> usually disable the entire tracing framework by default). Then:
>>> -Mount debugfs to /debug. (Usually it is mounted by default, but some
>>> distros like to mount it @ /sys/kernel/debug instead - remount it to
>>> /debug.)
>>> -"echo mmiotrace > /debug/tracing/current_tracer"
>>> -"cat /debug/tracing/trace_pipe >  trace.txt &" - at this point, tracing begins.
>>> -Load r8187b and connect.
>>> -"echo "Driver loaded!" > /debug/tracing/trace_marker"
>>> -"echo nop > /debug/tracing/current_tracer" - tracing ends here.
>>>
>>> Do this for rtl8187 as well.
>>> After each trace, check if "grep -i lost trace.txt" returns anything.
>>> If it does, enlarge the trace buffer and retry:
>>> -"cat /debug/tracing/trace_buffer_kb"
>>> -"echo [BUFSIZE] > /debug/tracing/trace_buffer_kb", where [BUFSIZE] is
>>> recommended to be about twice the number returned by the previous
>>> command.
>>
>> I installed a vanilla kernel 2.6.32.11 , config to rum mmio , but my
>> rtl818x modules are loaded by default and the modprobe -r command
>> doesn't seem to change this ... any ideas ?
>>
>> Rogerio
>
> Did you build rtl8187 as a module? Otherwise modprobe -r can do nothing.
>

Will check this ... but it seems to be a module ...If I have rtl8187
and rtl8187b in the blacklist will I be able to load them manually?

Rogerio



>>
>>
>>>
>>> Repeat these steps until the "lost events" warning disappears. Once
>>> you find the right BUFSIZE for one driver, you can use the same size
>>> for the other one too.
>>>
>>> Hth,
>>> Gábor
>>>
>>> --
>>> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>>>
>>
>
>
>
> --
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>

  reply	other threads:[~2010-04-24 10:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 13:56 RTL 8187b - naughty behaviour Rogerio Luz Coelho
2010-04-03 16:00 ` Larry Finger
2010-04-03 16:49   ` Rogerio Luz Coelho
2010-04-03 16:58     ` Larry Finger
2010-04-03 17:00       ` Rogerio Luz Coelho
2010-04-03 17:04         ` Rogerio Luz Coelho
2010-04-03 17:33           ` Larry Finger
2010-04-03 17:52             ` Rogerio Luz Coelho
2010-04-10 12:07         ` Rogerio Luz Coelho
2010-04-10 18:50           ` Gábor Stefanik
2010-04-10 19:40             ` Rogerio Luz Coelho
2010-04-11 13:35               ` Gábor Stefanik
2010-04-22 20:45                 ` Rogerio Luz Coelho
2010-04-23 20:16                   ` Gábor Stefanik
2010-04-24 10:47                     ` Rogerio Luz Coelho [this message]
2010-04-24 13:59                       ` Larry Finger
2010-06-03 15:40                 ` Rogerio Luz Coelho
2010-08-08 22:22                   ` Rogerio Luz Coelho
2010-08-09  1:43                     ` Larry Finger
2010-08-11  0:03                       ` Rogerio Luz Coelho
2010-08-11  0:23                         ` Thadeu Lima de Souza Cascardo
2010-08-11  2:51                           ` Larry Finger
2010-04-04  0:20       ` Hin-Tak Leung
2010-04-05  0:53         ` Rogerio Luz Coelho
2010-04-05  1:50           ` Gábor Stefanik
2010-04-05  3:12             ` Rogerio Luz Coelho
2010-04-05  3:43               ` Gábor Stefanik
2010-04-03 20:03   ` Gus Wirth
2010-04-03 21:40     ` Larry Finger
2010-05-06 17:36   ` seno
2010-05-06 18:20     ` Larry Finger
2010-05-14 20:12       ` seno
2010-05-14 20:20       ` seno

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=l2z917a57cb1004240347jcd95308bp5be3b66c8638907d@mail.gmail.com \
    --to=rogluz.news@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    /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).