All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hogan <jhogan22.liberty@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k WPA2-PEAP MSCHAPV2 Connectivity issue
Date: Fri, 20 Sep 2013 23:30:04 -0400	[thread overview]
Message-ID: <523D12BC.4060604@gmail.com> (raw)
In-Reply-To: <523B1CD1.1050207@rempel-privat.de>

I am up to try anything, but, at least in my case, this is not an error 
in the drive itself but is an error with the network. The schools' 
wireless network is rather old and needs to be updated, so I found a 
patch that was never implemented into ath9k and modified my own ath9k 
driver. I know that it is probably not the correct way to go about 
attacking the issue, but for school purposes, I need to at least have a 
working computer. My desktop has not been edited and I would like to 
continue using that to test and find a proper way of attacking the 
issue. As for now, here are my diffs

*** drivers/net/wireless/ath/ath9k/init.c.bak~    2013-09-20 
22:35:20.982551676 -0400
--- drivers/net/wireless/ath/ath9k/init.c    2013-09-20 
22:43:16.322997704 -0400
***************
*** 57,62 ****
--- 57,66 ----
   module_param_named(enable_diversity, ath9k_enable_diversity, int, 0444);
   MODULE_PARM_DESC(enable_diversity, "Enable Antenna diversity for 
AR9565");

+ int ath9k_modparam_disable_11n;
+ module_param_named(11n_disable, ath9k_modparam_disable_11n, int, 0444);
+ MODULE_PARM_DESC(11n_disable, "disable 11n functionality");
+
   bool is_ath9k_unloaded;
   /* We use the hw_value as an index into our private channel structure */

***************
*** 254,260 ****
       u8 tx_streams, rx_streams;
       int i, max_streams;

!     ht_info->ht_supported = true;
       ht_info->cap = IEEE80211_HT_CAP_SUP_WIDTH_20_40 |
                  IEEE80211_HT_CAP_SM_PS |
                  IEEE80211_HT_CAP_SGI_40 |
--- 258,268 ----
       u8 tx_streams, rx_streams;
       int i, max_streams;

!     if (ath9k_modparam_disable_11n)
!         ht_info->ht_supported = false;
!     else
!         ht_info->ht_supported = true;
!
       ht_info->cap = IEEE80211_HT_CAP_SUP_WIDTH_20_40 |
                  IEEE80211_HT_CAP_SM_PS |
                  IEEE80211_HT_CAP_SGI_40 |

  reply	other threads:[~2013-09-21  3:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 19:25 [ath9k-devel] ath9k WPA2-PEAP MSCHAPV2 Connectivity issue James Hogan
2013-09-08  4:27 ` Sujith Manoharan
2013-09-08 17:10   ` James Hogan
2013-09-09 12:28     ` Sujith Manoharan
2013-09-10  7:50       ` Holger Schurig
2013-09-10  8:05         ` Sujith Manoharan
2013-09-10  8:20           ` Holger Schurig
2013-09-11  1:03         ` James Hogan
2013-09-11  1:53           ` Sujith Manoharan
2013-09-11 22:04             ` James Hogan
2013-09-15 14:30             ` Holger Schurig
2013-09-19 15:01             ` James Hogan
2013-09-19 15:48               ` Oleksij Rempel
2013-09-19 15:48                 ` Oleksij Rempel
2013-09-21  3:30                 ` James Hogan [this message]
2013-09-21  3:40                   ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2013-10-28 14:34 Джонатан Вашингтон
2013-10-28 15:47 ` Sujith Manoharan
2013-10-28 16:20 ` Ben Greear
2013-11-01 20:53   ` Джонатан Вашингтон

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=523D12BC.4060604@gmail.com \
    --to=jhogan22.liberty@gmail.com \
    --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.