date : 26, Feb (driver's also same)
conclusion:
setting 802.11a ad-hoc,=20
5Ghz channel is different.
and iwconfig wlanX rate [more than 24Mbps] : disconnected!
and when I testing, performance was terrible. so often stalled.
so, I made 'mod_timer' comment in base.c (calibration section) and then
performance was increased.
BUT also when I set more than 24Mb, disconnected.=20
but until now, only atheros driver supports 802.11a with ad-hoc. thanks=
=2E :-)
hmm...
soon or later, we'll test ralink chipset.
--
--
Have a Wonderful Day~~!!
=B1=E8=BF=B5=C8=AF (James-Youngwhan Kim)
[email protected]
[email protected]
+82-42-863-0340
+82-10-6753-0987
HTVC 3106 KAIST, 373-1 Guseong-dong, Yuseong-gu,
Daejon, Republic of Korea
305-701
yes...^^ forgot it.
current environment :
vanilla kernel 2.6.23.16
compat wireless 2.6 driver (date : Dec, 2007)
chipset : AR5414
3com 3CRDAG675B
loading module, dmesg:
-----------------------------------------------------------------------=
-----
---------------------
ath5k_pci 0000:02:0b.0: registered as 'phy0'
ath5k phy0: Device only partially supported.
phy0: Selected rate control algorithm 'simple'
ath5k phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)
net wlan2: device_rename: sysfs_create_symlink failed (-17)
udev: renamed network interface wlan0 to wlan2
ADDRCONF(NETDEV_UP): wlan2: link is not ready
-----------------------------------------------------------------------=
-----
--------------------
-----Original Message-----
=46rom: bruno randolf [mailto:[email protected]]=20
Sent: Tuesday, February 26, 2008 3:07 PM
To: [email protected]
Cc: [email protected]
Subject: Re: ath5k : test
hello =B1=E8=BF=B5=C8=AF!
thanks for the report, however it's very important to tell us which
hardware you are using. see the output of dmesg after ath5k is loaded a=
nd
please include that in the next report.
bruno
On Tuesday 26 February 2008 14:22:58 =B1=E8=BF=B5=C8=AF wrote:
> date : 26, Feb (driver's also same)
>
> conclusion:
>
> setting 802.11a ad-hoc,
>
> 5Ghz channel is different.
>
> and iwconfig wlanX rate [more than 24Mbps] : disconnected!
>
> and when I testing, performance was terrible. so often stalled.
>
> so, I made 'mod_timer' comment in base.c (calibration section) and=20
> then performance was increased.
>
> BUT also when I set more than 24Mb, disconnected.
>
> but until now, only atheros driver supports 802.11a with ad-hoc. than=
ks.
> :-)
>
> hmm...
> soon or later, we'll test ralink chipset.
>
>
> --
> --
> Have a Wonderful Day~~!!
> =B1=E8=BF=B5=C8=AF (James-Youngwhan Kim)
> [email protected]
> [email protected]
> +82-42-863-0340
> +82-10-6753-0987
> HTVC 3106 KAIST, 373-1 Guseong-dong, Yuseong-gu, Daejon, Republic of=
=20
> Korea
> 305-701
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess"
> in the body of a message to [email protected] More majordomo=20
> info at http://vger.kernel.org/majordomo-info.html
hello =B1=E8=BF=B5=C8=AF!
thanks for the report, however it's very important to tell us which har=
dware=20
you are using. see the output of dmesg after ath5k is loaded and please=
=20
include that in the next report.
bruno
On Tuesday 26 February 2008 14:22:58 =B1=E8=BF=B5=C8=AF wrote:
> date : 26, Feb (driver's also same)
>
> conclusion:
>
> setting 802.11a ad-hoc,
>
> 5Ghz channel is different.
>
> and iwconfig wlanX rate [more than 24Mbps] : disconnected!
>
> and when I testing, performance was terrible. so often stalled.
>
> so, I made 'mod_timer' comment in base.c (calibration section) and th=
en
> performance was increased.
>
> BUT also when I set more than 24Mb, disconnected.
>
> but until now, only atheros driver supports 802.11a with ad-hoc. than=
ks.
> :-)
>
> hmm...
> soon or later, we'll test ralink chipset.
>
>
> --
> --
> Have a Wonderful Day~~!!
> =B1=E8=BF=B5=C8=AF (James-Youngwhan Kim)
> [email protected]
> [email protected]
> +82-42-863-0340
> +82-10-6753-0987
> HTVC 3106 KAIST, 373-1 Guseong-dong, Yuseong-gu,
> Daejon, Republic of Korea
> 305-701
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess"
> in the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html