From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <drwho@infidigm.net>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl@lists.infradead.org>
Subject: Re: QCA ar9375 in Ubuntu 14.04 beta 2 not working
Date: Wed, 18 Jun 2014 11:35:22 +0300 [thread overview]
Message-ID: <87k38eehth.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <63ed0fb1a4c098dd260f249546408de5.squirrel@www.infidigm.net> (drwho@infidigm.net's message of "Tue, 17 Jun 2014 17:19:30 -0400")
<drwho@infidigm.net> writes:
>> I just sent patches to add ar6004 hw3.0 support. If you can, please
>> test those and give feedback.
>
> Ok, I rebuilt the Ubuntu kernel with your 6 patches,
>
> sudo modprobe ath6kl_usb
> insert ar9375
>
> At first I was getting an error about not being able find the firmware
> file, so I renamed your fw-5.bin to fw.ram.bin.
You should not rename the firmware file, it will break everything if you
do that. This is what you should see:
[ 364.432845] usb 2-1.4: new high-speed USB device number 4 using ehci-pci
[ 364.510168] usb 2-1.4: New USB device found, idVendor=0cf3, idProduct=9375
[ 364.510232] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 364.510289] usb 2-1.4: Product: USBWLAN
[ 364.510346] usb 2-1.4: Manufacturer: Qualcomm Atheros.
[ 364.510430] usb 2-1.4: SerialNumber: 12345678
[ 364.835598] ath6kl: ar6004 hw 3.0 usb fw 3.5.0.349-1 api 5
[ 364.835710] ath6kl: firmware supports: 64bit-rates,map-lp-endpoint,ratetable-mcs15,no-ip-checksum
My first guess is that something went wrong in the kernel compilation
and the new patches are not actually applied. Double check that you
really have the new hw3.0 support in place, for example by adding few
printks and making sure that you see them in dmesg.
--
Kalle Valo
next prev parent reply other threads:[~2014-06-18 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 21:19 QCA ar9375 in Ubuntu 14.04 beta 2 not working drwho
2014-06-18 8:35 ` Kalle Valo [this message]
2014-06-18 20:31 ` drwho
2014-06-23 13:40 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2014-04-09 15:27 drwho
2014-06-17 10:20 ` Kalle Valo
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=87k38eehth.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl@lists.infradead.org \
--cc=drwho@infidigm.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 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).