[Bug 194336] AR9300 pci wireless card not working
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336 --- Comment #24 from Adrian Chadd--- Hi! We need a new bug created for the regulatory domain entry for canada. The reference driver I have does more for FCC6: * need to check eeprom REG_EXT_FCC bits for REG_EXT_FCC_CH_144 and whatever the heck ah_config.ath_hal_ch144 gets loaded with to see if we /can/ use the device in this regdomain EnumRd: FCC6_FCCA = 0x14, /* Canada for AP only*/ FCC6_WORLD = 0x23, /* Australia for AP only*/ FCC6= 0x0610, /* Canada & Australia */ FCC7= 0x0710, /* Same as FCC6 but with higher power */ Then RegDomainPairs: {FCC6_FCCA, FCC6, FCCA, NO_REQ, NO_REQ, PSCAN_DEFER, 0 }, {FCC7_FCCA, FCC7, FCCA, NO_REQ, NO_REQ, PSCAN_DEFER, 0 }, {FCC6_WORLD,FCC6, WORLD, NO_REQ, NO_REQ, PSCAN_DEFER, 0 }, Then Countries: {CTRY_ARGENTINA2, FCC6_WORLD,"AR", "ARGENTINA2", YES, NO, NO, YES, YES, YES, YES, 7000 }, {CTRY_AUSTRALIA2, FCC6_WORLD,"AU", "AUSTRALIA2", YES, YES, YES, YES, YES, YES, YES, 7000 }, {CTRY_CANADA2, FCC6_FCCA, "CA", "CANADA2",YES, YES, YES, YES, YES, YES, YES, 7000 }, {CTRY_UNITED_STATES2, FCC6_FCCA, "US", "UNITED STATES2", YES, YES, YES, YES, YES, YES, YES, 7000 }, .. then the actual regdomain entries: {FCC6, FCC, DFS_FCC3, PSCAN_FCC, NO_REQ, BM(F8_5180_5240, F5_5260_5320, F1_5500_5580, F2_5660_5720, F6_5745_5825, -1, -1, -1, -1, -1, -1, -1), BM(T7_5210_5210, T3_5250_5290, T2_5760_5800, -1, -1, -1, -1, -1, -1, -1, -1, -1), BM(T7_5200_5200, T1_5240_5240, T2_5280_5280, T1_5765_5805, -1, -1, -1, -1, -1, -1, -1, -1), BMZERO, BMZERO, CHAN_TURBO_G_BMZERO }, {FCC7, FCC, DFS_FCC3, PSCAN_FCC, NO_REQ, BM(F11_5180_5240, F8_5260_5320, F2_5500_5580, F3_5660_5720, F6_5745_5825, -1, -1, -1, -1, -1, -1, -1), BM(T11_5210_5210, T5_5250_5290, T2_5760_5800, -1, -1, -1, -1, -1, -1, -1, -1, -1), BM(T9_5200_5200, T2_5240_5240, T3_5280_5280, T1_5765_5805, -1, -1, -1, -1, -1, -1, -1, -1), BMZERO, BMZERO, CHAN_TURBO_G_BMZERO }, so it is a little more complicated. :-P -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
[Bug 194336] AR9300 pci wireless card not working
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336 --- Comment #23 from Adrian Chadd--- https://wiki.freebsd.org/dev/ath%284%29/Debugging has information about debugging. You need to use -i wlan0 (after creating wlan0) for it to work. -adrian -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Problem reports for freebsd-wireless@FreeBSD.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- New |206801 | iwn(4) page fault on netif restart Open|154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open|163312 | [panic] [ath] kernel panic: page fault with ath0 Open|166190 | [ath] TX hangs and frames stuck in TX queue Open|166357 | [ath] 802.11n TX stall when the first frame in th Open|169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open|169433 | [iwn] iwn(4) doesn't support 6235 chip. 7 problems total for which you should take action. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
[Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206112 Felix Palmenchanged: What|Removed |Added CC||fe...@palmen-it.de --- Comment #2 from Felix Palmen --- Hi Simone, as I'm experiencing the exact same issue here, are there any news? And, could you please show the patch making it work for you? TIA, Felix -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"