Looking for 3x3 Atheros NICs using ath9k driver.
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
I got some WPEA-127N modules direct from SparkLAN, and they're great. Small quantity wasn't a problem, but I did order them with the prospect of a larger purchase later in the year.
http://sparklan.com/product.php?func=view&prod_id=181
-Brian
Quoted 28 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
Thanks,
Ben--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 10 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Quoted 6 lines
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
I've ordered from Oxfordtec a few times:
Quoted 14 lines · Pat Erley
Quoted 13 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Quoted 6 lines
Quoted 3 lines
Anyone know of any others that are available to the public in small quantities?
I've ordered from Oxfordtec a few times:
Thanks, I just ordered one of the industrial versions of that NIC.
I also found a possible source for the sparklan. Doesn't say they are out of stock, but maybe they just don't keep track on their web page...
http://www.embeddedworks.net/psummary.php?mn=sparklan&mid=sparklan211
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
The AR9160/SR71-A should be supported by ath9k. They're just 2x2 stream devices using 3 radios.
What do you mean by "not even supported" ?
If the SR71-A isn't working for you then please email the ath9k list and I'll take a look. I have a bunch of SR71-A hardware here to tinker with.
Adrian
Quoted 28 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
Thanks,
Ben--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
well i'm also having troubles in injecting traffic at 11n rates over a raw interface, instead everything is working fine if I try to inject traffic at 11bga rates. I'm using the patch recently posted by matteo croce in order to specify 11n mcs codes.
the card that i;m using is exactly an sr71a. I hear that packet injection is working fine for people using the ubiquiti rocket M devices.
R.
Il 03/05/2011 08:13, Adrian Chadd ha scritto:
Quoted 47 lines
The AR9160/SR71-A should be supported by ath9k. They're just 2x2 stream devices using 3 radios.
What do you mean by "not even supported" ?
If the SR71-A isn't working for you then please email the ath9k list and I'll take a look. I have a bunch of SR71-A hardware here to tinker with.
Adrian
Quoted 19 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
Thanks,
BenQuoted 9 lines
--
Ben Greear<[email protected]>
Candela Technologies Inc http://www.candelatech.com--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 31 lines
-------------------------------------------------------- Roberto Riggio, Ph.D. CREATE-NET Network& Security Solutions for Pervasive Computing Systems (iNSPIRE) Senior Researcher Via alla Cascata 56/D - 38123 Povo Trento (Italy) e-mail: [email protected] Tel: (+39) 0461 408400 - interno/extension 708 Fax: (+39) 0461 421157 www.create-net.org/~rriggio -------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited according to the Italian Law 196/2003 of the Legislature. If you received this in error, please contact the sender and delete the material from any computer. Le informazioni contenute in questo messaggio di posta elettronica e nei file allegati sono da considerarsi strettamente riservate. Il loro utilizzo e' consentito esclusivamente al destinatario del messaggio, per le finalita' indicate nel messaggio stesso. Qualora riceveste questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla cancellazione del messaggio stesso dal Vostro sistema. Trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalita' diverse, costituisce comportamento contrario ai principi dettati dal D. Lgs. 196/2003.
Then there's something wrong with the patch. Where's the latest version of it?
ath9k worked fine with the SR71A the last time I checked (which was admittedly 8 weeks ago now.)
Adrian
Quoted 104 lines · Roberto Riggio
well i'm also having troubles in injecting traffic at 11n rates over a raw interface,
instead everything is working fine if I try to inject traffic at 11bga rates. I'm using
the patch recently posted by matteo croce in order to specify 11n mcs codes.the card that i;m using is exactly an sr71a. I hear that packet injection is working
fine for people using the ubiquiti rocket M devices.R.
Il 03/05/2011 08:13, Adrian Chadd ha scritto:
Quoted 46 lines
The AR9160/SR71-A should be supported by ath9k. They're just 2x2 stream devices using 3 radios.
What do you mean by "not even supported" ?
If the SR71-A isn't working for you then please email the ath9k list and I'll take a look. I have a bunch of SR71-A hardware here to tinker with.
Adrian
Quoted 24 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
Thanks,
Ben--
Ben Greear<[email protected]>
Candela Technologies Inc http://www.candelatech.comQuoted 6 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlQuoted 5 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html--
--------------------------------------------------------
Roberto Riggio, Ph.D.
CREATE-NET
Network& Security Solutions for Pervasive Computing Systems (iNSPIRE) Senior Researcher
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: [email protected]
Tel: (+39) 0461 408400 - interno/extension 708
Fax: (+39) 0461 421157
www.create-net.org/~rriggio
--------------------------------------------------------The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited according to the Italian Law 196/2003 of the Legislature. If you received this in error, please contact the sender and delete the material from any computer.
Le informazioni contenute in questo messaggio di posta elettronica e nei file allegati sono da considerarsi strettamente riservate. Il loro utilizzo e' consentito esclusivamente al destinatario del messaggio, per le finalita' indicate nel messaggio stesso. Qualora riceveste questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla cancellazione del messaggio stesso dal Vostro sistema. Trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalita' diverse, costituisce comportamento contrario ai principi dettati dal D. Lgs. 196/2003.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 8 lines · Adrian Chadd
The AR9160/SR71-A should be supported by ath9k. They're just 2x2 stream devices using 3 radios.
What do you mean by "not even supported" ?
If the SR71-A isn't working for you then please email the ath9k list and I'll take a look. I have a bunch of SR71-A hardware here to tinker with.
The ath9k didn't even recognize the NIC, and lspci showed some 5xxx chipset.
Other SR71-A NICs work just fine, so it's just a subset that is broken. I'll put it in a system later today and get you a verbose lspci listing.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 8 lines · Adrian Chadd
The AR9160/SR71-A should be supported by ath9k. They're just 2x2 stream devices using 3 radios.
What do you mean by "not even supported" ?
If the SR71-A isn't working for you then please email the ath9k list and I'll take a look. I have a bunch of SR71-A hardware here to tinker with.
Here's the lspci for the SR71-A that doesn't work with ath9k:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
Subsystem: Atheros Communications Inc. Device ee1c
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 15
Region 0: Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] #80 [0000]
Capabilities: [80] #00 [0000]
The only visual difference we saw is that there is a chip labeled AR9160-AC1E on the one above, and the ones that work have instead: AR9160-BC1A
The SR71-A that *does* work, works very well for us. The problem is just that we cannot be sure of what we are receiving when we order stuff because the name is the same for both NICs.
Thanks,
Ben
Quoted 39 lines
Adrian
Quoted 19 lines · Ben Greear
Hello!
We are trying to find some Atheros NICs that support 3x3 MIMO, but we are having a hard time.
We mistakenly ordered some Ubiquity SR71-A NICs, but those aren't even supported by ath9k it seems (visible chipset is AR9160-AC1E). There are some other SR71 NICs that *do* work (AR9160-BC1A), but hard to order that specific version.
Sparklan seems to make one based on AR9380, but they are not in stock any place we could find.
Anyone know of any others that are available to the public in small quantities?
Thanks,
BenQuoted 9 lines
--
Ben Greear<[email protected]>
Candela Technologies Inc http://www.candelatech.com--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 5 lines · Ben Greear
Here's the lspci for the SR71-A that doesn't work with ath9k:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
Subsystem: Atheros Communications Inc. Device ee1c
... ee1c? Err, that isn't right. Not by a very, very long shot.
What board are you putting this into?
Quoted 1 line
From FreeBSD on a RSPRO (ar71xx mips):
ath0@pci0:0:17:0: class=0x028000 card=0x40820777 chip=0x0027168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
class = network
That definitely, positively is the same AC1A revision that you have. It even does 11n(ag) too. Honest. I've seen it. :-)
This and the previous AR93xx "0xabcd" device id post is starting to sound a lot like something's not waking up the PCI bus and/or chip "right" in order to get the PCI vendor id init'ed from the EEPROM..
Adrian
Quoted 19 lines · Adrian Chadd
Quoted 5 lines · Ben Greear
Here's the lspci for the SR71-A that doesn't work with ath9k:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
Subsystem: Atheros Communications Inc. Device ee1c... ee1c? Err, that isn't right. Not by a very, very long shot.
What board are you putting this into?
Quoted 1 line
From FreeBSD on a RSPRO (ar71xx mips):
ath0@pci0:0:17:0: class=0x028000 card=0x40820777 chip=0x0027168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
class = network
Quoted 6 lines
That definitely, positively is the same AC1A revision that you have. It even does 11n(ag) too. Honest. I've seen it. :-)
This and the previous AR93xx "
0xabcd" device id post is starting to sound a lot like something's not waking up the PCI bus and/or chip "right" in order to get the PCI vendor id init'ed from the EEPROM..
Well, I put in one NIC, it works fine, I put in the other, and it doesn't.
Same system, reproducible on other systems from same manufacturer (Lanner, LEC 2010E).
Haven't tried it on a totally different motherboard. I'll send you this broken NIC if you want...I'm too tight on time to hack on it now...
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 27 lines · Ben Greear
Quoted 19 lines · Adrian Chadd
Quoted 5 lines · Ben Greear
Here's the lspci for the SR71-A that doesn't work with ath9k:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
Subsystem: Atheros Communications Inc. Device ee1c... ee1c? Err, that isn't right. Not by a very, very long shot.
What board are you putting this into?
Quoted 1 line
From FreeBSD on a RSPRO (ar71xx mips):
ath0@pci0:0:17:0: class=0x028000 card=0x40820777 chip=0x0027168c rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
class = networkQuoted 6 lines
That definitely, positively is the same AC1A revision that you have. It even does 11n(ag) too. Honest. I've seen it. :-)
This and the previous AR93xx "
0xabcd" device id post is starting to sound a lot like something's not waking up the PCI bus and/or chip "right" in order to get the PCI vendor id init'ed from the EEPROM..
Quoted 7 lines
Well, I put in one NIC, it works fine, I put in the other, and it doesn't.
Same system, reproducible on other systems from same manufacturer (Lanner, LEC 2010E).
Haven't tried it on a totally different motherboard. I'll send you this broken NIC if you want...I'm too tight on time to hack on it now...
So, you were right. I put this NIC in another system (VIA C3) and it comes up as AR9160 and loads ath9k driver just fine.
00:0c.0 Network controller: Atheros Communications Inc. AR9160 802.11abgn Wireless PCI Adapter (rev 01)
Subsystem: Device 0777:4082
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18
Memory at f6000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath9k
Kernel modules: ath9k
Thanks,
Ben
Quoted 4 lines
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
On 7 May 2011 06:53, Ben Greear <[email protected]> wrote:
[top post]
Ok, there's likely some PCI init bugs going on here; would someone with more background in this please take a look?
Adrian
Quoted 43 lines
Quoted 11 lines
Quoted 3 lines
This and the previous AR93xx "
0xabcd" device id post is starting to sound a lot like something's not waking up the PCI bus and/or chip "right" in order to get the PCI vendor id init'ed from the EEPROM..Well, I put in one NIC, it works fine, I put in the other, and it doesn't.
Same system, reproducible on other systems from same manufacturer (Lanner, LEC 2010E).
Haven't tried it on a totally different motherboard. I'll send you this broken NIC if you want...I'm too tight on time to hack on it now...
So, you were right. ?I put this NIC in another system (VIA C3) and it comes up
as AR9160 and loads ath9k driver just fine.00:0c.0 Network controller: Atheros Communications Inc. AR9160 802.11abgn Wireless PCI Adapter (rev 01)
? ? ? ?Subsystem: Device 0777:4082
? ? ? ?Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18 ? ? ? ?Memory atf6000000(32-bit, non-prefetchable) [size=64K] ? ? ? ?Capabilities: [44] Power Management version 2
? ? ? ?Kernel driver in use: ath9k
? ? ? ?Kernel modules: ath9kThanks,
BenQuoted 4 lines
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc ?http://www.candelatech.com--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo at vger.kernel.org
More majordomo info at ?http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · Adrian Chadd
On 7 May 2011 06:53, Ben Greear<[email protected]> wrote:
[top post]
Ok, there's likely some PCI init bugs going on here; would someone with more background in this please take a look?
I haven't had a chance to try this on the Atom system with the latest 39-rc6+ kernels.. I'll try that on Monday.
The VIA system was running 39-rc6+, btw.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 7 lines · Ben Greear
Quoted 2 lines
Ok, there's likely some PCI init bugs going on here; would someone with more background in this please take a look?
I haven't had a chance to try this on the Atom system with the latest 39-rc6+ kernels.. ?I'll try that on Monday.
The VIA system was running 39-rc6+, btw.
Thanks!
I do hope it's not ath9k. :-)
Adrian
Quoted 42 lines · Ben Greear
Quoted 28 lines · Ben Greear
Quoted 20 lines · Adrian Chadd
Quoted 6 lines · Ben Greear
Here's the lspci for the SR71-A that doesn't work with ath9k:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless
Network Adapter (rev 01)
Subsystem: Atheros Communications Inc. Device ee1c... ee1c? Err, that isn't right. Not by a very, very long shot.
What board are you putting this into?
Quoted 1 line
From FreeBSD on a RSPRO (ar71xx mips):
ath0@pci0:0:17:0: class=0x028000 card=0x40820777 chip=0x0027168c rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
class = networkQuoted 6 lines
That definitely, positively is the same AC1A revision that you have. It even does 11n(ag) too. Honest. I've seen it. :-)
This and the previous AR93xx "
0xabcd" device id post is starting to sound a lot like something's not waking up the PCI bus and/or chip "right" in order to get the PCI vendor id init'ed from the EEPROM..Quoted 8 lines
Well, I put in one NIC, it works fine, I put in the other, and it doesn't.
Same system, reproducible on other systems from same manufacturer (Lanner, LEC 2010E).
Haven't tried it on a totally different motherboard. I'll send you this broken NIC if you want...I'm too tight on time to hack on it now...
So, you were right. I put this NIC in another system (VIA C3) and it comes up
as AR9160 and loads ath9k driver just fine.
Quoted 8 lines
00:0c.0 Network controller: Atheros Communications Inc. AR9160 802.11abgn Wireless PCI Adapter (rev 01)
Subsystem: Device 0777:4082
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18 Memory atf6000000(32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath9k
Kernel modules: ath9k
The NIC is still showing up funky on the other system (Atom), even with the same 39-rc6+ kernel.
This NIC is reliably showing up wrong on in this system, and the other is reliably showing up well, so I think the problem must be with the NIC or perhaps the ath9k driver.
If anyone has any suggestions for how to debug this further, I'm interested...
Thanks,
Ben
Quoted 10 lines
Thanks,
BenQuoted 4 lines
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 7 lines · Ben Greear
The NIC is still showing up funky on the other system (Atom), even with the same 39-rc6+ kernel.
This NIC is reliably showing up wrong on in this system, and the other is reliably showing up well, so I think the problem must be with the NIC or perhaps the ath9k driver.
When you say "other NIC", you mean "BC1A" revision, rather than "AC1E" ?
Quoted 2 lines
If anyone has any suggestions for how to debug this further, I'm interested...
Can you try (much) earlier kernels? Ignore ath9k; ath9k shouldn't be needed for the card device id to be setup on PCI bus reset or whenever specifically it happens.
Adrian
Quoted 9 lines · Adrian Chadd
Quoted 7 lines · Ben Greear
The NIC is still showing up funky on the other system (Atom), even with the same 39-rc6+ kernel.
This NIC is reliably showing up wrong on in this system, and the other is reliably showing up well, so I think the problem must be with the NIC or perhaps the ath9k driver.
Quoted 8 lines
When you say "other NIC", you mean "BC1A" revision, rather than "AC1E" ?
Quoted 2 lines
If anyone has any suggestions for how to debug this further, I'm interested...
Can you try (much) earlier kernels? Ignore ath9k; ath9k shouldn't be needed for the card device id to be setup on PCI bus reset or whenever specifically it happens.
I tried a stock F14 .35 kernel, same problem.
I tried booting a .29 kernel, but F14 won't boot
on so old of a kernel.
Current plan is to just stick it in one of the VIA systems that it functions in and use it for testing..and never buy any more of those SR71-A NICs.
The sparklan 127N 3x3 pci-e seems to be working very well, so I plan to start using them instead.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Unex make SR-71 NICs which are guaranteed to use the BC1 generation of AR9160. They sell a normal and high powered dual-band version.
I've got both here and they both work remarkably well.
It's a shame we can't easily get to the bottom of what's going on, I'd like to try and figure out what's going on with waking up these atheros NICs on power-on. I'd hate for this to be the first indication of a wider problem later on (especially if any Osprey's are detecting as device 0xabcd, which from what I've been told shouldn't be happening..)
Adrian
Quoted 7 lines · Ben Greear
Quoted 6 lines · Adrian Chadd
Quoted 4 lines · Ben Greear
The NIC is still showing up funky on the other system (Atom), even with the
same 39-rc6+ kernel.
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
This NIC is reliably showing up wrong on in this system, and the other is reliably showing up well, so I think the problem must be with the NIC or perhaps the ath9k driver.
When you say "other NIC", you mean "BC1A" revision, rather than "AC1E" ?
Quoted 2 lines
If anyone has any suggestions for how to debug this further, I'm interested...
I found something interesting: In a third system, the NIC also fails when in the pci <-> mini-pci adapter card, but it works
when plugged directly to the motherboard mini-pci slot. So, in two of the three systems with on-board mini-pci, it works, and in two of the three systems it fails when using the adapter board. So, I assume the problem must be related to a bad interaction with the adapter board.
Could be that the bug is entirely in the adapter board..though of course other NICs work fine in that adapter board....
Thanks,
Ben
Quoted 21 lines
Quoted 4 lines
Can you try (much) earlier kernels? Ignore ath9k; ath9k shouldn't be needed for the card device id to be setup on PCI bus reset or whenever specifically it happens.
I tried a stock F14 .35 kernel, same problem.
I tried booting a .29 kernel, but F14 won't boot
on so old of a kernel.Current plan is to just stick it in one of the VIA systems that it functions in and use it for testing..and never buy any more of those SR71-A NICs.
The sparklan 127N 3x3 pci-e seems to be working very well, so I plan to start using them instead.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com