Re: Today's wireless update - TL;DR - please test -HEAD
Hello, Aleksandr. You wrote 20 ноября 2012 г., 2:24:09: AR> Lev, it seems it's time for you to get some dual-11n-nic router (like AR> f.e. DIR-825) and join to mips community :) I'm afraid, it doesn't have enough performance for my wired traffic, and have router and AP as different devices is not what I like. -- // Black Lion AKA Lev Serebryakov ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
On 19 November 2012 14:24, Aleksandr Rybalko wrote: > > Hi guys! > > Lev, it seems it's time for you to get some dual-11n-nic router (like > f.e. DIR-825) and join to mips community :) Please! That works really well! Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
On Mon, 19 Nov 2012 12:21:18 -0800 Adrian Chadd wrote: > That's right. The atheros devices have one MAC and one radio. There > was a module which used one MAC and two radios (one 2ghz and one 5ghz) > but only one was active at a time. since there was only one MAC, you > couldn't even do dual-band concurrent operation with that. > > There's nothing _stopping_ a manufacturer putting two NICs on one > board. There's some dual-AR9220 boards out there which have two > AR9220's on a single mini-PCI card. But they require a slightly > modified board - the second NIC has its IDSEL pin on another (unused? > gpio?) mini-PCI pin. So if you plug it into a normal device you only > see one AR9220. Yes, FreeBSD-HEAD runs on the particular dev board and > drives those NICs correctly. > > So far, I don't think anyone has made a public, "correct" dual band > single NIC - which involves putting a PCI or PCIe bridge chip on a > card, as well as two AR9xxx chips. Hi guys! Lev, it seems it's time for you to get some dual-11n-nic router (like f.e. DIR-825) and join to mips community :) > > > Adrian > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscr...@freebsd.org" -- Aleksandr Rybalko ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
That's right. The atheros devices have one MAC and one radio. There was a module which used one MAC and two radios (one 2ghz and one 5ghz) but only one was active at a time. since there was only one MAC, you couldn't even do dual-band concurrent operation with that. There's nothing _stopping_ a manufacturer putting two NICs on one board. There's some dual-AR9220 boards out there which have two AR9220's on a single mini-PCI card. But they require a slightly modified board - the second NIC has its IDSEL pin on another (unused? gpio?) mini-PCI pin. So if you plug it into a normal device you only see one AR9220. Yes, FreeBSD-HEAD runs on the particular dev board and drives those NICs correctly. So far, I don't think anyone has made a public, "correct" dual band single NIC - which involves putting a PCI or PCIe bridge chip on a card, as well as two AR9xxx chips. Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
Hello, Adrian. You wrote 20 ноября 2012 г., 0:12:54: AC> No, you need two cards. Sorry, but anything else in hostap mode is AC> just plain madness. AC> It's possible to do other dirty hacks (eg make p2p work, multiple AC> station VAPs, each on different channels) but that's not currently how AC> net80211 works. So, if (BIG IF) it is possible, it will be channel hoping anyway? Hardware doesn't support working on two channels with two raidomodules (I mean, 9380, I know that 9280 doesn't support that), am I right? Channel hoping is not interesting solution anyway :) And thank you for all your work and effort! -- // Black Lion AKA Lev Serebryakov ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
No, you need two cards. Sorry, but anything else in hostap mode is just plain madness. It's possible to do other dirty hacks (eg make p2p work, multiple station VAPs, each on different channels) but that's not currently how net80211 works. Adrian On 19 November 2012 12:09, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 19 ноября 2012 г., 23:57:23: > > AC> Nope, because there's no ETA at the present moment on when I've > AC> cleared all the hurdles for an open source AR9380 HAL. > To be honest, I don't understand clear boundary between HAL and > driver, if we speak about only one (family of) device. > > And I repeat my informal question: will it be possible to create > dual-band AP with these cards, which will work in both bands at same > time with oinly one card and one used slot on motherboard? Now you > need two physically separate cards to achieve this... > > -- > // Black Lion AKA Lev Serebryakov > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
Hello, Adrian. You wrote 19 ноября 2012 г., 23:57:23: AC> Nope, because there's no ETA at the present moment on when I've AC> cleared all the hurdles for an open source AR9380 HAL. To be honest, I don't understand clear boundary between HAL and driver, if we speak about only one (family of) device. And I repeat my informal question: will it be possible to create dual-band AP with these cards, which will work in both bands at same time with oinly one card and one used slot on motherboard? Now you need two physically separate cards to achieve this... -- // Black Lion AKA Lev Serebryakov ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
Nope, because there's no ETA at the present moment on when I've cleared all the hurdles for an open source AR9380 HAL. On the flip side, the driver side is almost done. All that I have to do now is PAPRD training calibration support and MSI handling; then it's _just_ the HAL. So if someone wanted to take ath9k's ath9k_hw code and make a HAL out of it.. (It would be kind of evil to see things go Atheros HAL -> ath9k -> FreeBSD HAL, but hey if that's what has to happen..) Adrian On 19 November 2012 11:55, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 19 ноября 2012 г., 6:41:33: > > AC> I'm rather stoked at the notion of being able to build a dual-band, > AC> 3x3 AP using FreeBSD. :-) > dual-band simultaneously? > > It looks like I bought my new WiFi card too early :) > > -- > // Black Lion AKA Lev Serebryakov > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Today's wireless update - TL;DR - please test -HEAD
Hello, Adrian. You wrote 19 ноября 2012 г., 6:41:33: AC> I'm rather stoked at the notion of being able to build a dual-band, AC> 3x3 AP using FreeBSD. :-) dual-band simultaneously? It looks like I bought my new WiFi card too early :) -- // Black Lion AKA Lev Serebryakov ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Current problem reports assigned to freebsd-wireless@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/173711 wireless powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171394 wireless [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/16
Re: kern/173711: powerd kills ath on the Asus EeePC 1005HA
On 19 Nov 2012, at 00:01, Ian Smith wrote: > On Mon, 19 Nov 2012, rpa...@freebsd.org wrote: > >> Synopsis: powerd kills ath on the Asus EeePC 1005HA >> >> Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless >> Responsible-Changed-By: rpaulo >> Responsible-Changed-When: Mon Nov 19 06:45:12 UTC 2012 >> Responsible-Changed-Why: >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=173711 > > "No PRs Matched Query". I've never seen that before. Looks like something is broken with the website. I've informed the admins. Regards, -- Rui Paulo ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: kern/173711: powerd kills ath on the Asus EeePC 1005HA
On Mon, 19 Nov 2012, rpa...@freebsd.org wrote: > Synopsis: powerd kills ath on the Asus EeePC 1005HA > > Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless > Responsible-Changed-By: rpaulo > Responsible-Changed-When: Mon Nov 19 06:45:12 UTC 2012 > Responsible-Changed-Why: > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=173711 "No PRs Matched Query". I've never seen that before. cheers, Ian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
