From: Pavel Roskin <proski@gnu.org>
To: javier.galvez@entel.upc.edu
Cc: linux-wireless@vger.kernel.org
Subject: Re: Using a Debian box as an AP with wireless testing and hostapd
Date: Mon, 29 Jun 2009 08:09:52 -0400 [thread overview]
Message-ID: <1246277392.21239.6.camel@mj> (raw)
In-Reply-To: <145d4e1a0906290200v4a45d83esf8eab021f6d094f9@mail.gmail.com>
On Mon, 2009-06-29 at 11:00 +0200, Javier Gálvez Guerrero wrote:
> Hi all,
>
> I'm trying to use my Debian box as an AP using the latest wireless
> testing kernel (2.6.30-wl) and a WiFi card Asus WL-138G v2 PCI but I'm
> experiencing a weird problem, hope you can guide me through it.
>
> First, I'll tell what and how I setup it. I downloaded the wireless
> testing kernel and installed it (make && make modules && make
> modules_install && make install), prepared the boot images and updated
> the grub; fine. Next I installed compat-wireless, wireless regdb,
> crda, libnl, hostapd and iw following this tutorial
> (http://acx100.erley.org/git.html), with slight modifications: install
> some missing packages (m2crypto, libgcrypt-dev and libssl-dev) and,
> after installing compat-wireless, 'make unload' as suggested by the
> 'make install' output.
You don't need compat-wireless with 2.6.30-wl. The whole point of
compat-wireless is to backport the latest drivers from the "-wl" kernel
to older kernels.
Please remove /lib/modules/2.6.30-wl and reinstall the kernel by running
"make modules_install install".
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-29 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <145d4e1a0906290158y4710d68ej270907f297335d42@mail.gmail.com>
2009-06-29 9:00 ` Using a Debian box as an AP with wireless testing and hostapd Javier Gálvez Guerrero
2009-06-29 12:09 ` Pavel Roskin [this message]
2009-06-29 14:05 ` Javier Gálvez Guerrero
2009-06-29 15:47 ` Javier Gálvez Guerrero
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=1246277392.21239.6.camel@mj \
--to=proski@gnu.org \
--cc=javier.galvez@entel.upc.edu \
--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 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).