Wireless Testing - Revision history

Tigersharke at 19:59, 11 May 2013

2013-05-11T19:59:06Z

Nemysis: /* Table 3: Wireless Devices Known to Work */

2013-05-11T12:28:27Z

‎Table 3: Wireless Devices Known to Work

Nemysis: /* Table 3: Wireless Devices Known to Work */

2013-05-11T12:22:55Z

‎Table 3: Wireless Devices Known to Work

David Olesa: /* Table 3: Wireless Devices Known to Work */

2013-04-17T07:15:32Z

‎Table 3: Wireless Devices Known to Work

Drulavigne at 13:01, 12 April 2013

2013-04-12T13:01:26Z

Drulavigne at 13:00, 12 April 2013

2013-04-12T13:00:53Z

Vater at 05:13, 10 January 2013

2013-01-10T05:13:04Z

Drulavigne: /* Table 3: Wireless Devices Known to Work */

2013-01-09T15:02:11Z

‎Table 3: Wireless Devices Known to Work

Fbsduser: /* Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? */

2013-01-08T18:59:29Z

‎Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device?

Drulavigne: /* Table 4: Devices Needing Drivers */

2012-10-21T08:42:00Z

‎Table 4: Devices Needing Drivers

@@ Line 29: / Line 29: @@
 == Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? ==
-{| border=1
+{| class=spiffy_table
-|'''Device Name'''
+!Device Name
-|'''i386'''
+!i386
-|'''amd64'''
+!amd64
-|'''Comments'''
+!Comments
 |-
 |BCM4310
@@ Line 84: / Line 84: @@
 == Table 2: Existing Wireless Drivers That Do not Work Well ==
-{| border=1
+{| class=spiffy_table
-|'''Driver Name'''
+!Driver Name
-|'''i386'''
+!i386
-|'''amd64'''
+!amd64
-|'''PR Number'''
+!PR Number
-|'''Comments'''
+!Comments
 |-
 |rum
@@ Line 109: / Line 109: @@
 == Table 3: Wireless Devices Known to Work ==
-{| border=1
+{| class=spiffy_table
-|'''Device Name'''
+!Device Name
-|'''Driver'''
+!Driver
-|'''i386'''
+!i386
-|'''amd64'''
+!amd64
-|'''Comments'''
+!Comments
 |-
 |AR5001
@@ Line 176: / Line 176: @@
 The following interfaces need a FreeBSD driver:
-{| border=1
+{| class=spiffy_table
-|'''Device Name'''
+!Device Name
-|'''Driver Sources/Notes'''
+!Driver Sources/Notes
 |-
 |AR9287

@@ Line 162: / Line 162: @@
+|
+|
-|Works in 9.1
+|Should work in 8.3 and later
 |-
 |RLT8187B

@@ Line 157: / Line 157: @@
+|
 |Works in 9.0. Instructions for 8.2 at http://blog.cochard.me/2011/08/backporting-intel-prowireless-6205a.html
 |-
 |RLT8187B

@@ Line 124: / Line 124: @@
 |AR9285
 |ath
+|YES
 |YES
 |works in 9.1

← Older revision		Revision as of 13:01, 12 April 2013
Line 1:		Line 1:
	{{NavHome}}		{{NavHome}}
−
−	~~[[Hardware]]~~

	This area of the wiki is for those who wish to assist by reporting non-working wireless drivers or by testing new drivers. Both reporting and testing provides valuable information to the developers of wireless drivers. It also helps to ensure that PC-BSD® and FreeBSD provide support for the wireless devices used by their users.		This area of the wiki is for those who wish to assist by reporting non-working wireless drivers or by testing new drivers. Both reporting and testing provides valuable information to the developers of wireless drivers. It also helps to ensure that PC-BSD® and FreeBSD provide support for the wireless devices used by their users.

← Older revision		Revision as of 13:00, 12 April 2013
Line 1:		Line 1:
	{{NavHome}}		{{NavHome}}
		+
		+	[[Hardware]]
		+
	This area of the wiki is for those who wish to assist by reporting non-working wireless drivers or by testing new drivers. Both reporting and testing provides valuable information to the developers of wireless drivers. It also helps to ensure that PC-BSD® and FreeBSD provide support for the wireless devices used by their users.		This area of the wiki is for those who wish to assist by reporting non-working wireless drivers or by testing new drivers. Both reporting and testing provides valuable information to the developers of wireless drivers. It also helps to ensure that PC-BSD® and FreeBSD provide support for the wireless devices used by their users.

@@ Line 6: / Line 6: @@
 * [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]]: devices in this table do not have a FreeBSD driver yet. If your device requires you to run the '''ndisgen''' script to convert a Windows driver to a FreeBSD driver module, it belongs in this table. Such devices use ndis(4) as their driver name. The goal of this table is to determine which devices need a native FreeBSD driver.
-* [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]: devices in this table already have a FreeBSD driver, but there are problems with the driver e.g. certain features are unavailable or the driver crashes. The goal of this table is to provide information to developers so the driver can be fixed. This means that you should reference any existing PRs or other URLs containing a description of the problem. If a PR does not exist, consider submitting one; information on how to submit a useful PR can be found at [http://www.freebsd.org/doc/en/articles/problem-reports/article.html Writing FreeBSD Problem Reports].
+* [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]: devices in this table already have a FreeBSD driver, but there are problems with the driver e.g. certain features are unavailable or the driver crashes. The goal of this table is to provide information to developers so the driver can be fixed. This means that you should reference any existing PRs or other URLs containing a description of the problem. If a PR does not exist, consider submitting one; information on how to submit a useful PR can be found at {{Citelink|url=http://www.freebsd.org/doc/en/articles/problem-reports/article.html|txt=Writing FreeBSD Problem Reports}}.
 * [[#Table 3: Wireless Devices Known to Work | Table 3]]: devices in this table have a working FreeBSD driver, making it a quick reference to determine if a device is supported. If your device works and is not in the table, take a minute to create a wiki login account and add an entry for your device.
@@ Line 20: / Line 20: @@
 * If a FreeBSD driver does not exist, download a Windows driver for the device, run the interactive script '''ndisgen''' as the superuser, and see if you can successfully use the generated driver module. Add the results for your architecture (i386 or amd64) to [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]].
-'''Note:''' ndisgen currently does not support the NDIS 6.X API. In practical terms, this means that you should only try it on XP and 2003 drivers. Make sure you download and try to convert the correct driver for your architecture (32 or 64 bit). If you would like to help test the most recent version of ndisgen, follow [http://blog.pcbsd.org/2010/11/looking-for-ndis-testers-freebsd-and-pc-bsd/ these instructions].
+'''Note:''' ndisgen currently does not support the NDIS 6.X API. In practical terms, this means that you should only try it on XP and 2003 drivers. Make sure you download and try to convert the correct driver for your architecture (32 or 64 bit). If you would like to help test the most recent version of ndisgen, follow {{Citelink|url=http://blog.pcbsd.org/2010/11/looking-for-ndis-testers-freebsd-and-pc-bsd/|txt=these instructions}}.
-'''Note:''' report of ndisgen process causing a faulty situation. '''Description:''' Wireless is active, but when trying to connect to the network, the screen goes dark and the system stops responding. The black screen can be removed by restarting, but after reboot PC-BSD® does not enter the boot loader section. The system shows a prompt ''FreeBSD (Amnesia mode)''. '''Likely solution:''' [http://www.freebsd.org/cgi/query-pr.cgi?pr=165622&sourceid=opensearch FreeBSD problem report and patch] for "Unregistered use of FPU in kernel" panic caused by miniport driver adapted via ndisgen.
+'''Note:''' report of ndisgen process causing a faulty situation. '''Description:''' Wireless is active, but when trying to connect to the network, the screen goes dark and the system stops responding. The black screen can be removed by restarting, but after reboot PC-BSD® does not enter the boot loader section. The system shows a prompt ''FreeBSD (Amnesia mode)''. '''Likely solution:''' {{Citelink|url=http://www.freebsd.org/cgi/query-pr.cgi?pr=165622&sourceid=opensearch|txt=FreeBSD problem report and patch}} for "Unregistered use of FPU in kernel" panic caused by miniport driver adapted via ndisgen.
-'''Note to iwi(4) users:''' work is ongoing to improve this driver. Please see [http://people.freebsd.org/~bschmidt/iwi/ Bernhard Schmidt's iwi wiki] if you are interested in testing these changes.
+'''Note to iwi(4) users:''' work is ongoing to improve this driver. Please see {{Citelink|url=http://people.freebsd.org/~bschmidt/iwi/|txt=Bernhard Schmidt's iwi wiki}} if you are interested in testing these changes.
 == Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? ==
@@ Line 42: / Line 42: @@
 |YES
 |YES
-|Download this [http://dl.dropbox.com/u/1101857/%5Bwikidrivers.com%5D%20Broadcom_BCM43xx_5.100.235.19_win5x.exe WinXP] driver, add bcmwl5.inf and bcmwl5.sys (bcmwl564.sys if using the amd64 version of freebsd) as driver files and both bcm43xx.cat (bcm43xx64.cat for amd64) and bcmwlcoi.dll (bcmwlcoi64.dll for amd64) as firmware files (this is important, if you do not add them through the ndisgen interface you will get a kernel panic as soon as you kldload the bcmwl5_sys.ko or bcmwl564_sys.ko file), move all the generated *.ko files to /boot/modules, add [http://pastebin.com/bRPaBS7N this] to your /etc/rc.conf ([http://pastebin.com/qYR1wXs4 this] for amd64 users), and [http://pastebin.com/s2gBzVVQ this] to your /boot/loader.conf, add your wpa_supplicant.conf file to /etc and finally reboot the PC to get the drivers loaded and interfaces created.
+|Download this {{Citelink|url=http://dl.dropbox.com/u/1101857/%5Bwikidrivers.com%5D%20Broadcom_BCM43xx_5.100.235.19_win5x.exe|txt=WinXP}} driver, add bcmwl5.inf and bcmwl5.sys (bcmwl564.sys if using the amd64 version of freebsd) as driver files and both bcm43xx.cat (bcm43xx64.cat for amd64) and bcmwlcoi.dll (bcmwlcoi64.dll for amd64) as firmware files (this is important, if you do not add them through the ndisgen interface you will get a kernel panic as soon as you kldload the bcmwl5_sys.ko or bcmwl564_sys.ko file), move all the generated *.ko files to /boot/modules, add {{Citelink|url=http://pastebin.com/bRPaBS7N|txt=<!--please replace "this"-->this}} to your /etc/rc.conf ({{Citelink|url=http://pastebin.com/qYR1wXs4|txt=<!--please replace "this"-->this}} for amd64 users), and {{Citelink|url=http://pastebin.com/s2gBzVVQL|txt=<!--please replace "this"-->this}} to your /boot/loader.conf, add your wpa_supplicant.conf file to /etc and finally reboot the PC to get the drivers loaded and interfaces created.
 Note: The WinXP drivers mentioned above work only on FreeBSD 9.0RC3 and later, if you need to use FreeBSD 8.2 or 7.4 use the curtiebo's Win98 driver, also the drivers listed are extremelly sensitive to correct timing during installation and can brick your *BSD install, and are also very unstable and cause lots of kernel panics.
 |-
@@ Line 53: / Line 53: @@
 |YES
 |Not tested
-|Appears to be working, but not fully functional. Have had an issue where sometimes it will not connect on boot and I've had to reboot. Also it has serious issues with uploading. Using [http://zonetusa.net/media/import/ZEW16X2_DRxp.zip this driver]
+|Appears to be working, but not fully functional. Have had an issue where sometimes it will not connect on boot and I've had to reboot. Also it has serious issues with uploading. Using {{Citelink|url=http://zonetusa.net/media/import/ZEW16X2_DRxp.zipL|txt=<!--please replace "this"-->this driver}}
 |-
 |RTL8191SE
@@ Line 79: / Line 79: @@
-If a driver exists for your wireless device but the driver does not work well, add a description of the problem to [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]. Take a minute to [http://www.freebsd.org/cgi/query-pr-summary.cgi?query query the PR database] and add the PR number if one exists.
+If a driver exists for your wireless device but the driver does not work well, add a description of the problem to [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]. Take a minute to {{Citelink|url=http://www.freebsd.org/cgi/query-pr-summary.cgi?query|txt=query the PR database}} and add the PR number if one exists.
 == Table 2: Existing Wireless Drivers That Do not Work Well ==
@@ Line 214: / Line 214: @@
 === Mobile broadband ===
-[http://packages.ubuntu.com/precise/mobile-broadband-provider-info Mobile Broadband provider info]
+{{Citelink|url=http://packages.ubuntu.com/precise/mobile-broadband-provider-info|txt=Mobile Broadband provider info}}

@@ Line 125: / Line 125: @@
+|
 |YES
-|should work in 9.0 according to http://www.freebsd.org/cgi/query-pr.cgi?pr=148112
+|works in 9.1
 |-
 | Belkin 54G (F5D7050)

@@ Line 43: / Line 43: @@
 |YES
 |Download this [http://dl.dropbox.com/u/1101857/%5Bwikidrivers.com%5D%20Broadcom_BCM43xx_5.100.235.19_win5x.exe WinXP] driver, add bcmwl5.inf and bcmwl5.sys (bcmwl564.sys if using the amd64 version of freebsd) as driver files and both bcm43xx.cat (bcm43xx64.cat for amd64) and bcmwlcoi.dll (bcmwlcoi64.dll for amd64) as firmware files (this is important, if you do not add them through the ndisgen interface you will get a kernel panic as soon as you kldload the bcmwl5_sys.ko or bcmwl564_sys.ko file), move all the generated *.ko files to /boot/modules, add [http://pastebin.com/bRPaBS7N this] to your /etc/rc.conf ([http://pastebin.com/qYR1wXs4 this] for amd64 users), and [http://pastebin.com/s2gBzVVQ this] to your /boot/loader.conf, add your wpa_supplicant.conf file to /etc and finally reboot the PC to get the drivers loaded and interfaces created.
-Note: The WinXP drivers mentioned above work only on FreeBSD 9.0RC3 and later, if you need to use FreeBSD 8.2 or 7.4 use the curtiebo's Win98 driver.
+Note: The WinXP drivers mentioned above work only on FreeBSD 9.0RC3 and later, if you need to use FreeBSD 8.2 or 7.4 use the curtiebo's Win98 driver, also the drivers listed are extremelly sensitive to correct timing during installation and can brick your *BSD install, and are also very unstable and cause lots of kernel panics.
 |-
 |RTL8185

@@ Line 175: / Line 175: @@
 |AR9287
 |committed to HEAD May 26/11
 |-
 |BCM4322