On 05/29/2013 07:52 PM, Mark Stodola wrote:
> On 5/29/2013 7:45 PM, Yasha Karant wrote:
>> Does anyone know if there is a SL 6 x86-64 driver for a TP Link
>> TC-WDN4800 IEEE 802.11 NIC?  This WNIC was purchased (with a return
>> possible) before anyone checked if there is an EL 6 driver.
>>
>> From the Centos list:
>>
>> https://www.centos.org/modules/newbb/viewtopic.php?topic_id=40278&forum=58
>>
>>
>> The result is a null return which, unfortunately, tells me that the WiFi
>> card is not supported by any of the Linux kernels available for CentOS 6.
>>
>> end quote
>>
>> Does anyone have a URL for a list by vendor WNIC name/model (e.g.,
>> TC-WDN4800) as to which WNICs are supported under SL6?
>>
>> Thanks,
>>
>> Yasha Karant
> Yasha,
>
> A quick google found this:
> http://wikidevi.com/wiki/TP-LINK_TL-WDN4800
>
> If you have the same vendor/device ID, odds are the ath9k driver will do
> the trick.
> I'm guessing the "TC" was a typo and you have a "TL".
> Product page here:
> http://www.tp-link.us/products/details/?categoryid=1683&model=TL-WDN4800
>
> If you can't find a working ath9k for it, I suggest contacting the
> ELrepo group to get a package built if possible.  They already have an
> ath9k_htc, not sure what the htc stands for though.
>
> -Mark

Mark,

Thanks -- it was a typo and I did a corrected resend (that eventually 
will show up), but the SMTP (and IMAP) email server at my university 
crashed right after I sent it (in my Sent IMAP folder, but not actually 
sent).  (The administrative IT group is switching from a Sun Solaris 
open systems email server to a MS Windows Exchange server, without any 
redundant failover server, evidently resulting in service interruptions. 
  Our present IT group totally will not use open systems environments, 
including any type of enterprise linux, such as SL, but insists on 
proprietary closed source systems with only proprietary vendor support 
on proprietary hardware platforms.  Our research computing, not done 
within the IT group, does not follow this approach -- we use open 
systems with a mix of commodity and proprietary hardware, and we support 
it ourselves.)

I found reference to the ELrepo package, and comments that the driver 
worked (and one comment that some release of the ath9 driver did not 
function) -- but I have not found a binary RPM.  As ELrepo proponents do 
seem to appear on this email list, could one of them kindly point me to 
the correct driver RPM?  Note that there appears to be two RPMs needed: 
  a driver RPM and a firmware RPM.

Yasha