From: Bernhard Reiter <ockham@raz.or.at>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k/PCI 168C:002C
Date: Mon, 01 Feb 2010 21:32:27 +0100 [thread overview]
Message-ID: <1265056347.3610.100.camel@razor> (raw)
In-Reply-To: <20100201113620.52ahuc39ws8scow4-cebfxv@webmail.spamcop.net>
thanks for your hints! unfortunately, as you expected, simply adding the
PCI id doesn't do the trick. seems like a couple of people tried it
already:
http://forum.ubuntuusers.de/topic/atheros-ar5b95-geht-unter-unr-9-10-nicht/
(in German).
i haven't tried madwifi yet, though.
regards,
bernhard
Am Montag, den 01.02.2010, 11:36 -0500 schrieb Pavel Roskin:
> Quoting Bernhard Reiter <ockham@raz.or.at>:
>
> > hi,
> >
> > i'm currently setting up karmic (64bit) an asus eeepc 1005p, and i've
> > found the following in the debian wiki:
> > http://wiki.debian.org/DebianEeePC/Model/1005P
> > i'm giving this laptop to another person on wednesday, but until then, i
> > might try to compile the ath9k module with the suggested addition of
> > that PCI id.
>
> You can add the ID at the runtime:
>
> echo "168c 002c" > /sys/bus/pci/drivers/ath9k/new_id
>
> > unfortunately, i haven't really found anything on how to do this (in a
> > least-invasive fashion). i've looked
> > into /usr/src/linux-headers-2.6.31-17/drivers/net/wireless/ath/ath9k,
> > but there's only a Kconfig and a Makefile, but no sources.
>
> You should be able to compile compat-wireless on Ubuntu. Then you can
> modify ath9k in the compat-wireless sources. But I'm not optimistic.
> The wiki link suggests that further changes to the driver are needed.
>
> You can also try MadWifi trunk to support the device. It should
> compile out-of-box. You can use the same trick to add the ID, just
> replace "ath9k" with "ath_pci".
>
next prev parent reply other threads:[~2010-02-01 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 15:52 ath9k/PCI 168C:002C Bernhard Reiter
2010-02-01 16:04 ` John W. Linville
2010-02-01 16:36 ` Pavel Roskin
2010-02-01 20:32 ` Bernhard Reiter [this message]
2010-02-01 21:23 ` Pavel Roskin
2010-02-04 0:44 ` Bernhard Reiter
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=1265056347.3610.100.camel@razor \
--to=ockham@raz.or.at \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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).