Difference between revisions of "Talk:Wireless Testing"

From PC-BSD Wiki
Jump to: navigation, search
(Page edits to make: new section)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
----
 +
 +
I have ordered the Asus Nano USB-N10 WiFi which uses the urtwn(4)[http://www.freebsd.org/cgi/man.cgi?query=urtwn&sektion=4] driver. It's supposed to be supported according to FreeBSD 10.1 hardware notes: [https://www.freebsd.org/releases/10.1R/hardware.html] Once it arrives I'll do testing and add my results to this Wiki page.
 +
 +
-possnfiffer
 +
----
 +
Sounds good. Glad to hear about involvement/initiative :)
 +
 +
--[[User:Tigersharke|Tigersharke]] ([[User talk:Tigersharke|talk]]) 18:03, 12 March 2015 (PDT)
 +
----
 +
So when I went to checkout the Asus but ended up looking at all the urtwn(4)[http://www.freebsd.org/cgi/man.cgi?query=urtwn&sektion=4] devices listed on the hardware release notes. I ended up purchasing the TP-LINK TL-WN723N v3.0 and am impressed with it's quick association time, it connected moments after the kernel printed the message that it was UP then it got the link. All I needed to configure was to add two lines to my /boot/loader.conf . Good thing they were listed in the man page. A quick note on this device, the driver must not support reading the signal strength, the status is unknown in the PC BSD utility for WiFi. Also, I had to run the command listed at the top of /boot/loader.conf so don't forget to do that if you want to get one of these. Now I need to go add it to the page of supported devices :)
 +
 +
--[[User:Possnfiffer|Possnfiffer]] ([[User talk:Possnfiffer|talk]]) 22:19 17 March 2015 (MST)
 +
----
 +
 
----
 
----
  
Line 24: Line 39:
  
 
Where 'this' as a link is used for a pastebin location that contains things such as lines to add to loader.conf, the content ought to be txtboxed (if possible, otherwise inline) instead of the link.
 
Where 'this' as a link is used for a pastebin location that contains things such as lines to add to loader.conf, the content ought to be txtboxed (if possible, otherwise inline) instead of the link.
 +
 +
== test for prior edit error ==
 +
 +
test

Latest revision as of 21:31, 17 March 2015


I have ordered the Asus Nano USB-N10 WiFi which uses the urtwn(4)[1] driver. It's supposed to be supported according to FreeBSD 10.1 hardware notes: [2] Once it arrives I'll do testing and add my results to this Wiki page.

-possnfiffer


Sounds good. Glad to hear about involvement/initiative :)

--Tigersharke (talk) 18:03, 12 March 2015 (PDT)


So when I went to checkout the Asus but ended up looking at all the urtwn(4)[3] devices listed on the hardware release notes. I ended up purchasing the TP-LINK TL-WN723N v3.0 and am impressed with it's quick association time, it connected moments after the kernel printed the message that it was UP then it got the link. All I needed to configure was to add two lines to my /boot/loader.conf . Good thing they were listed in the man page. A quick note on this device, the driver must not support reading the signal strength, the status is unknown in the PC BSD utility for WiFi. Also, I had to run the command listed at the top of /boot/loader.conf so don't forget to do that if you want to get one of these. Now I need to go add it to the page of supported devices :)

--Possnfiffer (talk) 22:19 17 March 2015 (MST)



I am surprised no one has used this discussion page to talk about stuff in the wireless section. Even if you have doubts something works. Well for the first post I will confirm on x86 bwn-firmware-kmod works for bcm4311. I will try later on on amd64 arch of pcbsd when i reinstall the os for tutorial purposes (and that will be when i get a decent manual focusing camera that is good on close ups (even extreme ones)). Unless you like to share another method of doing so without rewiteing on my /dev/ada0 . Well until later!

-bebuxe


I have tested the ndis driver for RTL8185 on i386. Don't use the most recent version of the driver, I could not get it to work. Instead use XP version 1.10, It is 290,944 bytes in size. Could not get it to automatically initialize the device at boot time, I have to manually load it. I'll be looking into remedying that. You might also have to manually configure your network settings as the graphical network manager did not work for me. I'll be testing it on amd64 once I download and install it. Until then Happy Wireless Configuring!

Just finished setting up amd64 system. XP64 driver version 1.10 does work (using it now). Driver is 385,536 bytes in size (before conversion). Follow the same procedures as the i386 driver to set it up.

-ikreos


[edit] Double fault panic with NDIS drivers

In case you encounter double fault panic when loading NDIS drivers that most likely point to small KSTACK_PAGES. Some Windows NDIS(r) drivers expect much bigger stack. On FreeBSD i386 KSTACK_PAGES is only 2, on FreeBSD amd64 it is 4. Increasing it to 12 and recompiling kernel(not just ndis modules) should be enough.

To change KSTACK_PAGES in your custom kernel add following line:

option KSTACK_PAGES 12

[edit] Page edits to make

Where 'this' as a link is used for a pastebin location that contains things such as lines to add to loader.conf, the content ought to be txtboxed (if possible, otherwise inline) instead of the link.

[edit] test for prior edit error

test

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox