From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Barkle <barkle@gmx.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RTL 8185
Date: Mon, 25 May 2009 22:14:15 +0100 [thread overview]
Message-ID: <3ace41890905251414v75544ed4o7bafdb3cdc170d1d@mail.gmail.com> (raw)
In-Reply-To: <4A1B00E7.5070801@gmx.net>
On Mon, May 25, 2009 at 9:34 PM, Barkle <barkle@gmx.net> wrote:
> Have a look in the appended file "dmesg_2009-05-25.txt" and it's not wlan0,
> it's phy0.
> I hope, I haven't cut off too much .
You have removed almost everything that might be useful... e.g. it is
not possible to tell even if you have a 32-bit CPU or a 64-bit CPU for
sure (although it *looks* like a 64-bit system), dual core/SMP or
single CPU, and what else is on your PCI bus. Is that really
necessary??? Very few people are telepathic, you know... at least I
don't know of any.
> There is no more reaktion, no change by pressing num-lock, caps-lock or
> scroll-lock. No answer on a ping. What I didn't tested is the "magic SysRq".
And any last minute syslog, etc in your log files after you power-cycle?
> wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -W
> -dd
If you are not using any encryption (WEP/WPA, etc), there is no need
to run wpa_supplicant. Also, what's in /var/log/wpa_supplicant.log ?
In fact you should shutdown network manager and wpa_suplicant and
probably dbus as well.
> No entry in the syslog
Again you have edited away your CPU type, and, since you are trying to
see what's wrong with your wireless device, you really should disable
dhcp against your wired networking interface.
> OK, no I didn't tried the compat-wireless so far..
> It will take a while, when I got an result of the change.
Please gIve compat-wireless a go.
You have edited away any useful info in your dmesg and syslog, so
there is nothing to tell. Why did you do that?
next prev parent reply other threads:[~2009-05-25 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 19:28 RTL 8185 Barkle
2009-05-25 6:15 ` Hin-Tak Leung
2009-05-25 20:34 ` Barkle
2009-05-25 21:14 ` Hin-Tak Leung [this message]
2009-05-25 22:53 ` Barkle
2009-05-26 5:58 ` Hin-Tak Leung
2009-05-26 16:23 ` Barkle
2009-05-26 23:01 ` Barkle
2009-05-26 23:51 ` Hin-Tak Leung
2009-05-27 6:09 ` Barkle
2009-05-27 8:21 ` Hin-Tak Leung
2009-05-27 19:35 ` Barkle
2009-05-27 20:17 ` Larry Finger
2009-05-27 21:04 ` Barkle
2009-05-27 22:04 ` Larry Finger
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=3ace41890905251414v75544ed4o7bafdb3cdc170d1d@mail.gmail.com \
--to=hintak.leung@gmail.com \
--cc=barkle@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.