Re: Atheros 9271
is there any update on this wifi driver support? i just got one to try and make pfSense a Access Point. but it does not show up - 3rd usb wifi antena i have tried. Joseph ___ 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: Atheros 9271
from Adrian Chadd: THe bit(s) i don't want to really make work mostly involve the USB stuff. So, if you grab the USB drivers in sys/dev/usb/wlan/ and look at the netbsd/openbsd athn usb code, that right there is what would be good to start with. So, if you or someone could port the initial USB glue - attach, detach, upload firmware, send commands, receive commands - that'll be a big help. Now you make me curious why you don't want to work on the USB stuff: you may have a good reason, but I'm still curious. I can look through the source code even when not running NetBSD. NetBSD is much less stable than FreeBSD on my hardware. OpenBSD may possibly be stabler than NetBSD but is more crippled for lack of support for GPT and USB 3.0, meaning my running of OpenBSD is limited to live USB from liveusb-openbsd.sourceforge.net : plenty of space on sparsely occupied 16 GB USB 2.0 stick, but X and GNOME 3.8.3 don't start. This is the latest version, with OpenBSD 5.4. Earlier I had a kernel crash on FreeBSD 10-stable amd64, from just before RC1 release, preceded by trouble messages from dhclient in connection with rsu. make buildworld with TARGET=i386 went through successfully about 25 minutes before the crash, and subsequently I completed the build and installation of FreeBSD 10-stable i386 on 32 GB USB 3.0 stick. I posted a message about that kernel crash on freebsd-stable list, suspect instability in rsu driver, but evidence is not conclusive. I could try to improve by set hint.re.0.disabled=1 at loader prompt to keep the failing re0 out of the way. I once did that, and re0 was conspicuous by its absence from /var/run/dmesg.boot and from the output of running ifconfig without parameters. Tom ___ 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: Atheros 9271
I just don't want to be on the hook for supporting the USB side of things. I've been slowly writing an AR9170 USB driver. I am still having issues getting all of the USB stuff stable and bulletproof. The existing USB drivers for wifi aren't really paragons of virtue from a driver perspective. -a On 18 December 2013 01:26, Thomas Mueller mueller6...@bellsouth.net wrote: from Adrian Chadd: THe bit(s) i don't want to really make work mostly involve the USB stuff. So, if you grab the USB drivers in sys/dev/usb/wlan/ and look at the netbsd/openbsd athn usb code, that right there is what would be good to start with. So, if you or someone could port the initial USB glue - attach, detach, upload firmware, send commands, receive commands - that'll be a big help. Now you make me curious why you don't want to work on the USB stuff: you may have a good reason, but I'm still curious. I can look through the source code even when not running NetBSD. NetBSD is much less stable than FreeBSD on my hardware. OpenBSD may possibly be stabler than NetBSD but is more crippled for lack of support for GPT and USB 3.0, meaning my running of OpenBSD is limited to live USB from liveusb-openbsd.sourceforge.net : plenty of space on sparsely occupied 16 GB USB 2.0 stick, but X and GNOME 3.8.3 don't start. This is the latest version, with OpenBSD 5.4. Earlier I had a kernel crash on FreeBSD 10-stable amd64, from just before RC1 release, preceded by trouble messages from dhclient in connection with rsu. make buildworld with TARGET=i386 went through successfully about 25 minutes before the crash, and subsequently I completed the build and installation of FreeBSD 10-stable i386 on 32 GB USB 3.0 stick. I posted a message about that kernel crash on freebsd-stable list, suspect instability in rsu driver, but evidence is not conclusive. I could try to improve by set hint.re.0.disabled=1 at loader prompt to keep the failing re0 out of the way. I once did that, and re0 was conspicuous by its absence from /var/run/dmesg.boot and from the output of running ifconfig without parameters. Tom ___ 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: Atheros 9271
from Adrian Chadd: I just don't want to be on the hook for supporting the USB side of things. I've been slowly writing an AR9170 USB driver. I am still having issues getting all of the USB stuff stable and bulletproof. The existing USB drivers for wifi aren't really paragons of virtue from a driver perspective. I understand what you mean, considering console messages I get, copied to /var/log/messages, and in one case on 10-stable amd64, a kernel crash. Evidence is not conclusive on rsu(0) being responsible. Considering that re(4) does not connect on MSI Z77 MPOWER motherboard and leaves memory in an unstable state, it may be best to go to loader prompt when booting and set hint.re.0.disabled=1 get that out of the way. Without that precaution, messages leading to crash, from /var/log/messages (times in UTC): Dec 16 07:01:27 amelia4 dhclient[3219]: send_packet: Invalid argument Dec 16 07:01:27 amelia4 kernel: wlan0: link state changed to UP Dec 16 07:01:27 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:01:27 amelia4 devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Dec 16 07:01:31 amelia4 dhclient: New IP Address (wlan0): 192.168.0.101 Dec 16 07:01:31 amelia4 dhclient: New Subnet Mask (wlan0): 255.255.255.0 Dec 16 07:01:31 amelia4 dhclient: New Broadcast Address (wlan0): 192.168.0.255 Dec 16 07:01:31 amelia4 dhclient: New Routers (wlan0): 192.168.0.1 Dec 16 07:02:29 amelia4 dhclient: New IP Address (wlan0): 192.168.0.101 Dec 16 07:02:29 amelia4 dhclient: New Subnet Mask (wlan0): 255.255.255.0 Dec 16 07:02:29 amelia4 dhclient: New Broadcast Address (wlan0): 192.168.0.255 Dec 16 07:02:29 amelia4 dhclient: New Routers (wlan0): 192.168.0.1 Dec 16 07:02:30 amelia4 dhclient: New Routers (wlan0): 192.168.0.1 Dec 16 07:06:40 amelia4 kernel: wlan0: link state changed to DOWN Dec 16 07:06:43 amelia4 kernel: wlan0: link state changed to UP Dec 16 07:06:43 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:06:43 amelia4 devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Dec 16 07:07:20 amelia4 kernel: wlan0: link state changed to DOWN Dec 16 07:07:20 amelia4 kernel: wlan0: link state changed to UP Dec 16 07:07:20 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:07:20 amelia4 devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Dec 16 07:07:22 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:08:26 amelia4 kernel: wlan0: link state changed to DOWN Dec 16 07:08:29 amelia4 kernel: wlan0: link state changed to UP Dec 16 07:08:29 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:08:29 amelia4 devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Dec 16 07:08:47 amelia4 kernel: wlan0: link state changed to DOWN Dec 16 07:08:48 amelia4 dhclient[3219]: send_packet: Invalid argument Dec 16 07:08:56 amelia4 dhclient[3219]: send_packet: Network is down Dec 16 07:08:58 amelia4 kernel: wlan0: link state changed to UP Dec 16 07:08:58 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:08:58 amelia4 devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Dec 16 07:09:35 amelia4 kernel: wlan0: link state changed to DOWN Dec 16 07:09:38 amelia4 kernel: wlan0: link state changed to UP Dec 16 07:09:38 amelia4 dhclient[3219]: send_packet: No buffer space available Dec 16 07:09:38 amelia4 devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Dec 16 07:09:47 amelia4 kernel: wlan0: link state changed to DOWN Dec 16 07:09:56 amelia4 dhclient[3219]: send_packet: Invalid argument Dec 16 07:09:59 amelia4 dhclient[3219]: send_packet: Network is down Dec 16 07:10:04 amelia4 kernel: Kernel page fault with the following non-sleepable locks held: Dec 16 07:10:04 amelia4 kernel: exclusive sleep mutex rsu0 (network driver) r = 0 (0xfe0003298140) locked @ /usr/src/sys/dev/usb/usb_transfer.c:2184 Dec 16 07:10:04 amelia4 kernel: KDB: stack backtrace: Dec 16 07:10:04 amelia4 kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe07c2748440 Dec 16 07:10:04 amelia4 kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe07c27484f0 Dec 16 07:10:04 amelia4 kernel: witness_warn() at witness_warn+0x4a8/frame 0xfe07c27485b0 Dec 16 07:10:04 amelia4 kernel: trap_pfault() at trap_pfault+0x5a/frame 0xfe07c2748650 Dec 16 07:10:04 amelia4 kernel: trap() at trap+0x670/frame 0xfe07c2748870 Dec 16 07:10:04 amelia4 kernel: calltrap() at calltrap+0x8/frame 0xfe07c2748870 Dec 16 07:10:04 amelia4 kernel: --- trap 0xc, rip = 0x80700348, rsp = 0xfe07c2748930, rbp = 0xfe07c2748950 --- Dec 16 07:10:04 amelia4 kernel: ieee80211_tx_mgt_cb() at ieee80211_tx_mgt_cb+0x8/frame 0xfe07c2748950 Dec 16 07:10:04 amelia4 kernel: rsu_bulk_tx_callback() at rsu_bulk_tx_callback+0x107/frame 0xfe07c27489a0 Dec 16 07:10:04 amelia4 kernel: usbd_callback_wrapper() at usbd_callback_wrapper+0x5e4/frame 0xfe07c2748a00 Dec 16 07:10:04 amelia4 kernel:
Re: Atheros 9271
You should buy a cheap one for now, until someone writes the AR7010/AR9271 driver. -adrian From your wiki site on wiki.freebsd.org, Chipsets I won't be working on USB chipsets, in particular the AR7010+AR9280, AR9271 or the AR9170 chipset although if someone would like to work on these, I'll be happy to help them with it I've offered to help, but dang, no answer. Question is where I should start. I have programmed with C and i386 assembler but nothing as complex as a device driver. I have FreeBSD and NetBSD-current source trees and can compare the athn and other wireless driver parts as well as device re. I could also download Linux kernel sources. Tom ___ 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
Atheros 9271
I myself use Edimax EW-7811Un (urtwn driver) which works quite nicely with stable/10. Note that it's available only in stable/10 and head and requires non-free firmware module (already in base, but if you care about using only free software, you should look for something else) signature.asc Description: OpenPGP digital signature
Atheros 9271
Hello, So I have been thinking about starting driver development in FreeBSD. So I thought about porting some drivers from linux as a starting point. It will mainly be for the Atheros 9271 USB chip. So any comments or ideas or tips are welcome :) -- Pagarbiai, Jonas ___ 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: Atheros 9271
from Jonas Liepuonius thinker...@gmail.com: So I have been thinking about starting driver development in FreeBSD. So I thought about porting some drivers from linux as a starting point. It will mainly be for the Atheros 9271 USB chip. So any comments or ideas or tips are welcome :) -- Pagarbiai, Jonas I have MSI Z77 MPOWER motherboard with onboard AR9271 quasi-USB chip and would be glad to be a tester on FreeBSD-current. Bug in re driver makes this particular version of Realtek 8111E Ethernet not work in FreeBSD or OpenBSD as of 5.3, but good in NetBSD-current amd64 and Linux. I notice NetBSD and OpenBSD have athn driver which includes AR9271. On how I update FreeBSD source tree with no Internet access through FreeBSD, I built subversion from pkgsrc on a NetBSD-current amd64 USB-stick installation, and use that successfully. With GPT, NetBSD accesses FreeBSD partition with no problem reading disklabels. OpenBSD, from live USB (http://liveusb-openbsd.sourceforge.net/), can't read my hard drive at all, due to lack of GPT support. Tom ___ 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: Atheros 9271
THere are a bunch of supported 11n NICS in -HEAD and -10. You should buy a cheap one for now, until someone writes the AR7010/AR9271 driver. -adrian On 19 November 2013 14:53, Thomas Mueller mueller6...@bellsouth.net wrote: from Jonas Liepuonius thinker...@gmail.com: So I have been thinking about starting driver development in FreeBSD. So I thought about porting some drivers from linux as a starting point. It will mainly be for the Atheros 9271 USB chip. So any comments or ideas or tips are welcome :) -- Pagarbiai, Jonas I have MSI Z77 MPOWER motherboard with onboard AR9271 quasi-USB chip and would be glad to be a tester on FreeBSD-current. Bug in re driver makes this particular version of Realtek 8111E Ethernet not work in FreeBSD or OpenBSD as of 5.3, but good in NetBSD-current amd64 and Linux. I notice NetBSD and OpenBSD have athn driver which includes AR9271. On how I update FreeBSD source tree with no Internet access through FreeBSD, I built subversion from pkgsrc on a NetBSD-current amd64 USB-stick installation, and use that successfully. With GPT, NetBSD accesses FreeBSD partition with no problem reading disklabels. OpenBSD, from live USB (http://liveusb-openbsd.sourceforge.net/), can't read my hard drive at all, due to lack of GPT support. Tom ___ 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 ___ 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: Atheros 9271
THere are a bunch of supported 11n NICS in -HEAD and -10. You should buy a cheap one for now, until someone writes the AR7010/AR9271 driver. -adrian How do I find which 11n NICs are supported, or USB wireless adapters? It's very difficult to find in advance what the chipset is. Now I have Hiro H50191 USB wireless adapter, chipset RTL8191SU, driver rsu. FreeBSD-head recognized it, but I couldn't find any networks by scanning. Now my wireless router seems to be not working. I now access the Internet by plugging Ethernet cable direct from computer's Ethernet port to cable modem. This is good for Internet access for one computer at a time, and no wireless. I intend to try to set up again, watchful for making correct connections. I also just ordered and received a new TP-Link wireless router and would like to try that. But I still would want to participate in the testing of AR9271 driver when it is ready for testing. Tom ___ 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
