All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Barkle <barkle@gmx.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RTL 8185
Date: Wed, 27 May 2009 00:51:41 +0100	[thread overview]
Message-ID: <3ace41890905261651l1cd3742bu5ac1af6f631798f3@mail.gmail.com> (raw)
In-Reply-To: <4A1C74C1.7060600@gmx.net>

On Wed, May 27, 2009 at 12:01 AM, Barkle <barkle@gmx.net> wrote:
> Barkle schrieb:
>>
>> Hin-Tak Leung schrieb:
>>>
>>> I am asking to a 2nd time - try compat-wireless.
>>
>> When I compile compat-wireless, I get an error
>>
> After commenting out in the file "config.mk" the line
> #CONFIG_MAC80211_LEDS=y

Hmm, your kernel config did not seem to have LEDS_TRIGGER defined.
That's a problem with non-distro custom-rolled kernel... For that
matter, which bits of the kernel did you build as modules and which
compiled in? I guess I need the output of these two commands:

    lsmod
    find /lib/modules/`uname -r`/updates

> the code compiles without an error.
> Then "make install", reboot and "wpa_supplicant -Dwext -iwlan0
> -c/etc/wpa_supplicant/wpa_supplicant.conf -W -dd" => kernel freeze.

Hmm, can you *not* run wpa_supplicant? This is about the 3rd time I
asked - if you are not using encryption, you don't need
wpa_supplicant. You should be doing just 'ifconfig wlan0 up', and
'ifconfig wlan0' and 'iwconfig wlan0' and see what they say. And do
*not* do it in X - if there is any last minute crash message, it would
be in the text console and you should be better doing these in
run-level 3.

> What else can I do?
> Where can I see which version of the driver are used?

There isn't really a 'version' for the driver - it entered the kernel
about a year and half ago, and only a few people had worked on it
since, and not in any major way.

  reply	other threads:[~2009-05-26 23:51 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
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 [this message]
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=3ace41890905261651l1cd3742bu5ac1af6f631798f3@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.