All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Schlemmer <keinstein_junior@gmx.net>
To: linux-wireless@vger.kernel.org
Subject: Re: rtl8187b Problem with tx level
Date: Mon, 31 Aug 2009 18:51:49 +0200	[thread overview]
Message-ID: <h7gv36$tu0$1@ger.gmane.org> (raw)
In-Reply-To: <4A9BF11D.1060205@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Larry Finger schrieb:
> There may be additional info following this.
> 
> In looking at my copy of the r8187 driver code, I see some branches
> that may not be in our driver, but I need to see what ID info their
> driver sees.

Hm… the output is attached. It seems not to be very informative to me. 
But maybe you can read more.

> Have a good vacation.

Thank you very much.

Tobias

[-- Attachment #2: kernel-log-r8187.txt --]
[-- Type: text/plain, Size: 3503 bytes --]

[  168.274893] usb 3-1: new high speed USB device using ehci_hcd and address 4
[  168.414599] usb 3-1: configuration #1 chosen from 1 choice
[  168.475975] ieee80211_crypt: registered algorithm 'NULL'
[  168.483909] ieee80211_crypt: registered algorithm 'CCMP'
[  168.491680] ieee80211_crypt: registered algorithm 'WEP'
[  168.495562] ieee80211_crypt: registered algorithm 'TKIP'
[  168.535959] r8187msh: module license 'Proprietary' taints kernel.
[  168.536038] r8187msh: no version for "notify_wx_assoc_event" found: kernel tainted.
[  168.558140] 
[  168.558142] Linux kernel driver for RTL8187/RTL8187B based WLAN cards
[  168.558146] Copyright (c) 2004-2005, Andrea Merello
[  168.558148] rtl8187: Initializing module
[  168.558149] rtl8187: Wireless extensions version 22
[  168.558150] rtl8187: Initializing proc filesystem
[  168.635246] rtl8187: Reported EEPROM chip is a 93c46 (1Kbit)
[  168.860244] rtl8187: Card MAC address is 00:16:44:fb:52:6d
[  169.198241] rtl8187: PAPE from CONFIG2: 0
[  169.235989] rtl8187: EEPROM Customer ID: 00
[  169.235990] 
[  169.236472] rtl8187: Driver probe completed
[  169.236473] 
[  169.236490] usbcore: registered new interface driver rtl8187
[  286.804391] NET: Registered protocol family 17
[  287.149124] rtl8187: Card successfully reset
[  295.619702] WIRELESS_MODE_G
[  295.690942] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  360.727206] rtl8180_close process 
[  360.727219] rtl8180_down process 
[  360.740307] rtl8187: Mangement RX process aborted due to explicit shutdown
[  361.191136] rtl8187: Card successfully reset
[  369.966180] WIRELESS_MODE_G
[  370.061948] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  370.479245] Linking with deleted
[  370.636366] Linking with deleted
[  370.735865] Linking with deleted
[  373.286377] Linking with deleted
[  373.345154] Associated successfully
[  373.345161] Using G rates
[  373.406594] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  374.169721] alg name:CCMP
[  376.210329] padlock: VIA PadLock not detected.
[  376.959471] alg name:TKIP
[  383.529746] wlan0: no IPv6 routers present
[  383.817734] rtl8180_close process 
[  383.817741] rtl8180_down process 
[  383.830149] rtl8187: Mangement RX process aborted due to explicit shutdown
[  384.727525] rtl8187: Card successfully reset
[  393.528271] WIRELESS_MODE_G
[  393.598464] Linking with deleted
[  393.599752] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  393.821712] Linking with deleted
[  394.014709] Linking with deleted
[  394.070779] Associated successfully
[  394.070785] Using G rates
[  394.128104] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  394.495577] Linking with deleted
[  394.553274] Associated successfully
[  394.553280] Using G rates
[  394.561075] rtl8180_close process 
[  394.561077] rtl8180_down process 
[  394.576644] rtl8187: Mangement RX process aborted due to explicit shutdown
[  394.992566] rtl8187: Card successfully reset
[  403.365152] WIRELESS_MODE_G
[  403.451719] Linking with deleted
[  403.613717] Linking with deleted
[  403.675288] Associated successfully
[  403.675294] Using G rates
[  403.827342] Linking with deleted
[  403.983464] Linking with deleted
[  404.039909] Associated successfully
[  404.039915] Using G rates
[  413.531913] wlan0: no IPv6 routers present
[  419.261156] Linking with deleted
[  419.409459] Linking with deleted
[  419.470723] Associated successfully
[  419.470729] Using G rates
[  420.238284] alg name:CCMP
[  420.238308] alg name:TKIP

  reply	other threads:[~2009-08-31 16:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 20:44 rtl8187b Problem with tx level Tobias Schlemmer
2009-08-30 23:00 ` Larry Finger
2009-08-31  9:59   ` Tobias Schlemmer
2009-08-31 15:49     ` Larry Finger
2009-08-31 16:51       ` Tobias Schlemmer [this message]
2009-08-31 17:55 ` Hin-Tak Leung
2009-08-31 18:02   ` Luis R. Rodriguez
2009-08-31 18:32     ` Hin-Tak Leung
2009-08-31 18:41       ` Luis R. Rodriguez
2009-08-31 18:57         ` Hin-Tak Leung
2009-08-31 21:10           ` Larry Finger
2009-08-31 21:18             ` Gábor Stefanik
2009-08-31 21:38               ` Larry Finger
2009-08-31 23:16                 ` Hin-Tak Leung
2009-09-01 13:13                   ` John W. Linville
2009-09-01 16:37                   ` Larry Finger
2009-09-02 10:28                     ` Hin-Tak Leung
2009-08-31 23:37               ` Luis R. Rodriguez
2009-08-31 23:46                 ` Gábor Stefanik
2009-08-31 23:56                   ` Luis R. Rodriguez
2009-09-01  0:21                     ` Greg KH

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='h7gv36$tu0$1@ger.gmane.org' \
    --to=keinstein_junior@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.