From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Netgear N150 driver for 2.6.32-5-686 debian problem
Date: Mon, 27 Jun 2011 13:02:52 -0400 [thread overview]
Message-ID: <4E08B7BC.4060907@gnu.org> (raw)
In-Reply-To: <loom.20110624T192021-669@post.gmane.org>
On 06/24/2011 01:31 PM, V Sivaraman wrote:
>
> Dear all,
>
> I have debian 6.0 squeezee 2.6.32-5-686.
>
> I have Netgear N 150 [Atheros ar9271] usb device.
> I have istalled ar9271.fw in appopriate directory.
> I down loaded compat-wireless driver.
> when i run "make" the .o files get generted from
> the kernel 2.6.33 and onwards like compat_2.6.33.o; 2.6.34.o and
> corresponding .ko files etc.
> But it does not make compat_2.6.32.o and .ko files.
> Due to this the appropriate module does not get loaded.
> How can I that makes it difficult for the module?
Describe the problem's symptoms, not your guesses
http://www.catb.org/~esr/faqs/smart-questions.html#symptoms
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2011-06-27 17:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 19:41 [ath9k-devel] ath9k problem - no interface Błażej Kaczorowski
2010-06-16 20:24 ` Pavel Roskin
2010-06-16 20:31 ` Błażej Kaczorowski
2010-06-17 6:49 ` Błażej Kaczorowski
2010-06-17 7:54 ` Błażej Kaczorowski
2011-06-24 17:31 ` [ath9k-devel] Netgear N150 driver for 2.6.32-5-686 debian problem V Sivaraman
2011-06-27 17:02 ` Pavel Roskin [this message]
2011-06-28 7:01 ` Mohammed Shafi
2011-06-28 13:40 ` Sivaraman V
2011-06-28 14:50 ` Pavel Roskin
2011-06-28 15:02 ` Mohammed Shafi
2011-06-28 15:54 ` Sivaraman V
2011-06-29 9:25 ` Mohammed Shafi
2011-06-29 16:43 ` Sivaraman V
2011-06-29 20:58 ` Pavel Roskin
2011-06-30 4:53 ` Mohammed Shafi
2011-06-30 5:06 ` Mohammed Shafi
2011-07-03 13:02 ` Sivaraman V
2011-07-03 15:02 ` Pavel Roskin
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=4E08B7BC.4060907@gnu.org \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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.