Thank you for your feedback! :)
Am 22.07.2014 14:38, schrieb Hosam Hittini:
I could get it to work by compiling backports-3.15.1-1.tar.xz package,
there is no need to recompile a whole kernel
I first extracted the source files, then used “make defconfig-ath9k”
Then, thanks to your suggestions
I could get it to work by compiling backports-3.15.1-1.tar.xz package, there is
no need to recompile a whole kernel
I first extracted the source files, then used “make defconfig-ath9k”
Then, thanks to your suggestions I used “make menuconfig” to changes some
settings, the following are the ones
Hi Hosam,
currently no one can give you good answer on it. If you can do some
research on this issue and give some feedback or even fix it, it will be
awesome.
Am 12.07.2014 00:21, schrieb Hosam Hittini:
I managed to change the CRDA settings by getting backports
package
Where to compile with these two options?
I tried chaining the “n” to “y” in drivers/net/wireless/ath/Kconfig for the
options you mentioned in backports package
http://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.15.1/
Then make defconfig-ath9k
then make, then make install
After
I managed to change the CRDA settings by getting backports package
http://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.15.1/,
modifying the db.txt and forcing the driver to follow my db.txt
This how my db.txt looks like
country 00:
(2402 - 2482 @ 20), (N/A, 20)
Am 09.07.2014 07:47, schrieb Hosam Hittini:
I’m afraid you are right
I have the following modules running
ath9k_htc 85879 0
ath9k_common 13619 1 ath9k_htc
ath9k_hw 429197 2 ath9k_common,ath9k_htc
ath19187 3
Janusz suggested compiling the kernel with the following options
CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS=y
CONFIG_ATH_REG_DYNAMIC_USER_CERT_TESTING=y
Yours Sincerely,
Eng. Hosam Hittini
M: +971 555 655 878
ae.linkedin.com/in/hhittini/
On Jul 9, 2014, at 12:50 PM, Oleksij Rempel
Hello there,
I have this dual band wireless adapter
https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
and it uses AR9280 chipset for the 5GHz communication
It’s using ath9k driver; I have Ubuntu 13.10 running 3.11 kernel and the
adapter worked
Am 08.07.2014 08:20, schrieb Hosam Hittini:
Hello there,
I have this dual band wireless
adapter
https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
and it uses AR9280 chipset for the 5GHz communication
It’s using ath9k driver; I have Ubuntu
Am 08.07.2014 09:48, schrieb Hosam Hittini:
Is it a driver limitation or a firmware limitation?
Because in theory, configuring the AP on the two bands is not different
at all
It is suggestion provided by EEPROM, so driver is free to fallow it. If
you will force the driver not to fallow it, and
On 8 July 2014 08:20, Hosam Hittini h.hitt...@gmail.com wrote:
Hello there,
I have this dual band wireless adapter
https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
and it uses AR9280 chipset for the 5GHz communication
It’s using ath9k
Am 08.07.2014 13:37, schrieb Janusz Dziedzic:
On 8 July 2014 08:20, Hosam Hittini h.hitt...@gmail.com wrote:
Hello there,
I have this dual band wireless adapter
https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
and it uses AR9280 chipset for
I’m afraid you are right
I have the following modules running
ath9k_htc 85879 0
ath9k_common 13619 1 ath9k_htc
ath9k_hw 429197 2 ath9k_common,ath9k_htc
ath19187 3 ath9k_common,ath9k_htc,ath9k_hw
mac80211 513247 2
13 matches
Mail list logo
