Finished: CALL FOR TESTERS Ralink wireless run(4) usb driver for FreeBSD

ericturgeon

Well-Known Member

Reaction score: 65
Messages: 367

PseudoCylon said:
The driver is included in 8.1-RELEASE. If you have just done standard installation,
# kldload if_run
will load the driver.

If you need 11n support, the driver is posted at the first thread.
Yes but how to configure it to work.

On my rc.conf.
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator
Developer

Reaction score: 2,841
Messages: 11,319

PseudoCylon, is there a man page in the works yet? I see that run(4) is not yet available in 8.1-STABLE / 9-CURRENT as of today.
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

@ericturgeon
ericturgeon said:
Yes but how to configure it to work.
Nothing special. Please see this post and freebsd hand book.
ericturgeon said:
On my rc.conf.
It depends how you want to set up. Basically, following 2 lines in /etc/rc.conf would do the trick
Code:
wlans_run0="wlan0"
ifconfig_wlan0="DHCP"
the freebsd hand book explains well.


@DutchDaemon, The moderator
DutchDaemon said:
PseudoCylon, is there a man page in the works yet? I see that run(4) is not yet available in 8.1-STABLE / 9-CURRENT as of today.
Actually, there is a man page in head tree
http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/run.4
I don't why it isn't in 8.1 nor in online man page. Currently, installing 9-CURRENT is the only way to see the man page.

-- update Jan. 12, 2011 --
man pages have been commit to the HEAD
http://svn.freebsd.org/viewvc/base?view=revision&revision=217289
 

ericturgeon

Well-Known Member

Reaction score: 65
Messages: 367

@PseudoCylon

I have already try this in /etc/rc.conf.
Code:
wlans_run0="wlan0"
ifconfig_wlan0="DHCP"
and I have put thi in my /boot/loader.conf.
Code:
if_run_load="YES"
It doesn't work. That's why I say the Handbook don't cover my case.
 

ericturgeon

Well-Known Member

Reaction score: 65
Messages: 367

I have to put this in my /boot/loader.conf to have my wireless to work.
Code:
if_run_load="YES"
runfw_load="YES"
Problem solve.
 

Nollo

Member

Reaction score: 1
Messages: 33

PseudoCylon said:
Unfortunately no.
The driver supports some of Ralink chips, but RTL8192 is a Realtek chip (as far as I know).
ah yes sorry, I posted here because someone spoke about this chipset in page 2
 

Dein

New Member


Messages: 4

Good day PseudoCylon,

I have several questions:

1. First of all, I want to test 802.11n driver version, but all links on the first page are broken.
2. I have next difficalties with your driver under 8.1-Release and 8.2-Prerelease version when connecting to AP:
a. On AMD64 machine - "Kernel panic: fatal trap 12" without dump.
b. On x86 machine - I got connection terminated without reason or case "a".

My hostap.conf
Code:
hw_mode=g
interface=wlan0
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
debug=3
#channel=6
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel
#### IEEE 802.11 related config ####
ssid=freebsd1
macaddr_acl=0
auth_algs=1
#### IEEE 802.1X related config ####
ieee8021x=0
#### WPA/IEEE 802.11i config #####
wpa=3
wpa_passphrase=11111111
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
WBR,
Dein
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

Hi,
Dein said:
1. First of all, I want to test 802.11n driver version, but all links on the first page are broken.
Please try this link instead.
11n beta
It is beta because it might stall during high traffic.
Dein said:
2. I have next difficalties with your driver under 8.1-Release and 8.2-Prerelease version when connecting to AP:
a. On AMD64 machine - "Kernel panic: fatal trap 12" without dump.
b. On x86 machine - I got connection terminated without reason or case "a".

My hostap.conf
Can you give me more deatil what you are doing with what commands you issue? I suppose "connecting to AP" means you are using the driver as client. Then you don't need /etc/hostapd.conf.

As far as I know, the driver causes panic when try to create the wlan without loading firmware. When failed to load firmware, it will print
Code:
run0: could not load 8051 microcode
Did you compiled firmware into kernel or loading it as a module?
 

okeeblow

Member

Reaction score: 14
Messages: 33

runfw(4) claims:

To compile this module into the kernel, place the following line in your
kernel configuration file:

"device runfw"

This will include two firmware images, RT2870 and RT3071, inside the kernel.
But this does not seem to be a valid kernel configuration directive.

Code:
config: Error: device "runfw" is unknown
config: 1 errors
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
Unfortunately, the platform I'm building for does not use loader, so I have no other way to load it at boot.
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

okeeblow said:
Code:
config: Error: device "runfw" is unknown
config: 1 errors
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
Unfortunately, the platform I'm building for does not use loader, so I have no other way to load it at boot.
Please add following to src/sys/conf/files
Code:
runfw.c				optional runfw							\
	compile-with	"${AWK} -f $S/tools/fw_stub.awk runfw:runfw -mrunfw -c${.TARGET}"	\
	no-implicit-rule before-depend local							\
	clean		"runfw.c"
runfw.fwo			optional runfw							\
	dependency	"runfw"									\
	compile-with	"${LD} -b binary -d -warn-common -r -d -o ${.TARGET} runfw"		\
	no-implicit-rule									\
	clean		"runfw.fwo"
runfw				optional runfw							\
	dependency	"$S/contrib/dev/run/rt2870.fw.uu"					\
	compile-with	"uudecode -o ${.TARGET} $S/contrib/dev/run/rt2870.fw.uu"		\
	no-obj no-implicit-rule									\
	clean		"runfw"
You can put the code anywhere, but next to the line
Code:
dev/usb/wlan/if_run.c		optional run
would be easier to remember in the future.

I have re-submitted all the changes. This would be committed soon.

-- update Jan. 12, 2011 --
The change has been commit to the HEAD
http://svn.freebsd.org/viewvc/base?view=revision&revision=217288
 

okeeblow

Member

Reaction score: 14
Messages: 33

That worked, Thanks :)


I'm getting panics when I try to connect to my hostap network, though. I'll post this here unsure if it's a problem with the driver or a problem with the freebsd-arm kernel. My adapter is a TP-LINK TL-WN321G. I bought it since it was supposed to be a rum() device, but the one I got is RT3070.

Code:
pochan# uname -a
FreeBSD pochan 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #9: Wed Dec 15 01:09:57 EST 2010     nicole@Emi.cooltrainer.org:/usr/obj/arm/usr/
src/sys/DOCKSTAR-COOLTRAINER  arm
Code:
ugen0.5: <Ralink> at usbus0
run0: <1.0> on usbus0
run0: MAC/BBP RT3070 (rev 0x0201), RF RT2020 (MIMO 1T1R), address d8:5d:4c:98:3b:7f
run0: firmware RT2870 loaded

pochan# usbconfig -u 0 -a 5 dump_device_desc                      
ugen0.5: <802.11 g WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x0000 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x148f 
  idProduct = 0x2070 
  bcdDevice = 0x0101 
  iManufacturer = 0x0001  <Ralink>
  iProduct = 0x0002  <802.11 g WLAN>
  iSerialNumber = 0x0003  <1.0>
  bNumConfigurations = 0x0001
Code:
pochan# ifconfig wlan0 create wlandev run0 wlanmode hostap
wlan0: Ethernet address: d8:5d:4c:98:3b:7f
pochan# ifconfig wlan0 inet 172.16.0.2 netmask 255.240.0.0 ssid FreeBSD-Kirkwood channel 11

pochan# ifconfig wlan0
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether d8:5d:4c:98:3b:7f
        inet 172.16.0.2 netmask 0xfff00000 broadcast 172.31.255.255
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
        status: running
        ssid FreeBSD-Kirkwood channel 11 (2462 MHz 11g) bssid d8:5d:4c:98:3b:7f
        country US authmode OPEN privacy OFF txpower 0 scanvalid 60
        protmode CTS wme dtimperiod 1 -dfs


Code:
vm_fault(0xc0cc9254, 0, 1, 0) -> 1
Fatal kernel mode data abort: 'Translation Fault (P)'
trapframe: 0xc8413d8c
FSR=00000017, FAR=0000000c, spsr=20000013
r0 =c1bba000, r1 =00000000, r2 =00000000, r3 =00001908
r4 =00000000, r5 =c1bba000, r6 =c1bba000, r7 =c19e7c00
r8 =c19ee778, r9 =c09c97c0, r10=c19db000, r11=00000000
r12=c0ce2100, ssp=c8413dd8, slr=c09c9818, pc =c0ae6cd8

panic: Fatal abort
Uptime: 16m8s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

Sorry for taking long.

Can you try these?

If it doesn't work, please show me out put of% ifconfig(without wlan0), and /etc/rc.conf (if you are using nat), /etc/hostapd.conf (if you are using).
 

okeeblow

Member

Reaction score: 14
Messages: 33

Code:
vm_fault(0xc0cc93d4, 0, 1, 0) -> 1
Fatal kernel mode data abort: 'Translation Fault (P)'
trapframe: 0xc8413d8c
FSR=00000017, FAR=0000000c, spsr=20000013
r0 =c1adb000, r1 =00000000, r2 =00000000, r3 =00001908
r4 =00000000, r5 =c1adb000, r6 =c1adb000, r7 =c19e7c00
r8 =c19ee778, r9 =c09c9350, r10=c19db000, r11=00000000
r12=c0ce2280, ssp=c8413dd8, slr=c09c93a8, pc =c0ae6ca0

panic: Fatal abort
Uptime: 8m55s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
rc.conf
Code:
swapfile="/usr/swap0"

hostname="pochan"
gateway_enable="YES"

ifconfig_mge0="up"
ifconfig_ue0="DHCP"
wlans_run0="wlan0"
create_args_wlan0="wlanmode hostap"
ifconfig_wlan0="up ssid FreeBSD-Kirkwood channel 11"

ntpd_enable="YES"
ntpd_flags="-g"

sshd_enable="YES"
fsck_y_enable="YES"
background_fsck="NO"
force_fsck="YES"
force_fsck_list="/"

postfix_enable="YES"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"
I believe this may be a more general problem on the ARM architecture, since I've received mail from people having the same problem with a rum controller. I filed a PR a while ago.
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

okeeblow said:
I believe this may be a more general problem on the ARM architecture, since I've received mail from people having the same problem with a rum controller. I filed a PR a while ago.
Sounds like it if the same problem occurs with rum(4).

Can you show me the output of followings? (assuming everything is compiled into kernel)% objdump -h [FILE]/where/your_kernel/is/[/FILE]kernel | grep text (The kernel doesn't have to be on Dockstar to run the command.)% objdump -S --start-address=0xc8413d88 --stop-address=0xc8413da0 [FILE]/where/your_kernel/is/[/FILE]kernel(-'S' is uppercase)

I'll try to find a workaround if possible. (Usually it is too far from the driver.)
 

okeeblow

Member

Reaction score: 14
Messages: 33

Code:
[root@Emi#/root]objdump -h /usr/obj/arm/usr/src/sys/DOCKSTAR-COOLTRAINER/kernel.bin|grep text           
objdump: /usr/obj/arm/usr/src/sys/DOCKSTAR-COOLTRAINER/kernel.bin: File format not recognized
[root@Emi#/root]objdump -S /usr/obj/arm/usr/src/sys/DOCKSTAR-COOLTRAINER/kernel.bin
objdump: /usr/obj/arm/usr/src/sys/DOCKSTAR-COOLTRAINER/kernel.bin: File format not recognized
Code:
pochan# objdump -h kernel.bin 
objdump: kernel.bin: File format not recognized
pochan# objdump -S --start-address=0xc8413d88 --stop-address=0xc8413da0 kernel.bin
objdump: kernel.bin: File format not recognized
On both architectures. I uploaded it if you'd like to take a look: http://cooltrainer.org/kernel.bin
 

vhapkin

New Member


Messages: 19

PseudoCylon said:
-- Update on Jan 29, 2010 --

The run(4) driver has been committed to FreeBSD 9-CURRENT.

The driver works with
RT2700U == RT2770 MAC/BBP + RT2720 (1T2R) or RT2750 (dual-band 1T2R) radio
RT2800U == RT2870 MAC/BBP + RT2820 (2T3R) or RT2850 (dual-band 2T3R) radio
RT3000U == RT3070 MAC/BBP + RT3020 (1T1R), RT3021 (1T2R) or RT3022 (2T2R) single-band radio
list of known devices are posted at thread #3
...
The driver is included in 8.1-RELEASE.

For the latest development (11n support), try following files.

for 9-CURRENT rev 211314 or newer,
11n_beta2

for 8.1-RELEASE and 9-CURRENT older than rev 211314
8.1_REL

for 8.0-RELEASE users
8.0_REL_eos,
or run-8.0-REL_final.tar.bz2 << You can click this.
Support for this release has been ended. Please upgrade to 8.1 if practical.

[NB]
Under heavy traffic, Tx may stall. If you experience this issue, please apply patches for EHCI-hangs.
You need to re-build kernel, but with KERNFAST,# make buildkernel KERNCONF=[i]YOUR_CONF[/i] KERNFAST=1
it should take only a few minutes.
Patched files, sys/dev/usb/controller/ehci.h and sys/dev/usb/controller/ehci.c, are included in 8.1_REL version.

for 7.2 users View attachment 739 << You can click this.
The final version
I have upgraded all my boxes to 8.0 or CURRENT, so I cannot do anything for 7.2 driver. "Final" means no more update, not complete. But it supports STA mode and h/w encryption. Hope this is good enough until upgrading to 8.

Thank you for testing and reporting problems.

-- Followings are original post. Left it here for log purpose --
Hello every one!

I'm porting run (ru'N' not ru'M') driver View attachment 426, and I've made it work (-encryption). Actually, I'm posting this by using that driver. You can find a list of supported devices here.
http://www.openbsd.org/cgi-bin/man.cgi?query=run&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=amd64&format=html

It hasn't support encryption yet and has some issues, but I thought it is better than nothing and decided to share. If anyone want to try it out, download tar ball and read README in it.

I'm planning to make encryption work. But, I am an ex-MECHANICAL engineer and I installed very first FreeBSD little over a year ago. So, don't expect too much. It will take several weeks. Or, you can help me out.


-- updated on Nov 10, 2009 --
Now, the driver for CURRENT (and 8 RC) is available at thread #28 (One posted here is for 7.)

-- updated on Nov. 28, 2009 --
-- FIX -- FIX -- FIX -- View attachment 500
Some packet loss/drop and memory leak were identified and fixed. (The perfomance has been improved, too.) Details are on RELEASE_NOTES included.

For those wondering about HOSTAP support, here is the word from the original author. (If you don't know who he is, check how many wireless drivers he has written.)
http://old.nabble.com/Re:-Linksys-WUSB600N-and-Access-Point-p21332878.html
I was looking forward to HOSTAP mode by myself. I might play with it, but don't hope for miracles.
Could you please add support of rt3090 to driver?
 

HighTower

New Member


Messages: 17

Hello,

I have problems with RAlink RT3070 card... (LR802UKN2)

tried with driver from FreeBSD 8.2-PRERELEASE #4: Fri Jan 14 20:26:35 sources
also tried http://gitorious.org/run/run/archive-tarball/8.1_REL and http://gitorious.org/run/run/archive-tarball/11n_beta2
results are the same...
I want to create AccessPoint, but can't... also I can't use it as wireless client ((
what I do:

kldload runfs - ok
kldload if_run - ok
Code:
run0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether 00:0d:f0:8d:54:f4
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
ifconfig wlan0 create wlandev run0 wlanmode hostap
Code:
wlan0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:0d:f0:8d:54:f4
        media: IEEE 802.11 Wireless Ethernet autoselect <hostap> (autoselect <hostap>)
        status: no carrier
        ssid "" channel 1 (2412 MHz 11b)
        country US authmode OPEN privacy OFF txpower 0 scanvalid 60 wme
        dtimperiod 1 -dfs bintval 0
hostap is supported
ifconfig wlan0 list caps
Code:
drivercaps=d85c501<STA,IBSS,HOSTAP,SHSLOT,SHPREAMBLE,MONITOR,MBSS,WPA1,WPA2,WME,WDS>
cryptocaps=1b<WEP,TKIP,AES_CCM,TKIPMIC>
htcaps=f057e<CHWIDTH40,GREENFIELD,SHORTGI20,SHORTGI40,DELBA>
make open accesspoint:
ifconfig wlan0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap mode 11g channel 1
Code:
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:0d:f0:8d:54:f4
        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
        status: running
        ssid freebsdap channel 1 (2412 MHz 11g) bssid 00:0d:f0:8d:54:f4
        country US authmode OPEN privacy OFF txpower 0 scanvalid 60
        protmode CTS wme dtimperiod 1 -dfs
And now I have wireless led blinking very fast and that's all... No accesspoints can be found by other devices... What I do wrong?
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

@okeeblow
okeeblow said:
On both architectures. I uploaded it if you'd like to take a look: http://cooltrainer.org/kernel.bin
Is there file named kernel.o?
And just in case, can you check if virsion of src/sys/net80211/ieee80211_amrr.c is
Code:
__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_amrr.c,v 1.4.2.3 2010/11/20 12:22:02 bschmidt Exp $");
@vhapkin
vhapkin said:
Could you please add support of rt3090 to driver?
Sorry. It is PCIe based chipset. Cannot just add. It would be a separate driver.

@HighTower
HighTower said:
make open accesspoint:
ifconfig wlan0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap mode 11g channel 1
Can you issue 'inet' separately?# ifconfig wlan0 netmask 255.255.255.0 ssid freebsdap mode 11g channel 1then# ifconfig wlan0 inet 192.168.0.1The driver has problem restarting some 3070 chipset, so give 'inet' at the end. Hope this is the case.
 

HighTower

New Member


Messages: 17

PseudoCylon said:
Can you issue 'inet' separately?# ifconfig wlan0 netmask 255.255.255.0 ssid freebsdap mode 11g channel 1then# ifconfig wlan0 inet 192.168.0.1The driver has problem restarting some 3070 chipset, so give 'inet' at the end. Hope this is the case.
I've tried as you wrote after reboot, unfortunately result is the same... wireless led on device blinking very fast, but no ap with "freebsdap" name and my mac is seen..

Also now I observe another problem, after rebooting, loafing if_run module and creading wlan I can't recieve list of APs in range!
[CMD=]ifconfig wlan0 up scan[/CMD]
return nothing.. it is in "run" stage for a long with not output...

initally, then I just installed 8.1 with generic kernel on this device I was able to scan and recieve APs list in range...
 

okeeblow

Member

Reaction score: 14
Messages: 33

PseudoCylon said:
@okeeblowIs there file named kernel.o?
There doesn't appear to be:

Code:
[root@Emi#src]cp /usr/obj/arm/usr/src/sys/DOCKSTAR-COOLTRAINER/kernel.
kernel.bin*           kernel.gz.tramp*      kernel.gz.tramp.bin*  kernel.tramp*         kernel.tramp.bin*
And just in case, can you check if virsion of src/sys/net80211/ieee80211_amrr.c is
Code:
__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_amrr.c,v 1.4.2.3 2010/11/20 12:22:02 bschmidt Exp $");
I have
Code:
__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_amrr.c,v 1.4.2.3.2.1 2010/12/21 17:09:25 kensmith Exp $");
 

JackMiles

New Member


Messages: 8

Hello. I have some problem with my Dlink DWA-140 device.

OS 8.1 release.
Driver is standard from 8.1 release, or from your site http://gitorious.org/run/run/trees/8.1_REL, doesnt matter, happens everywhere.

Device detects as:
Code:
run0: <Ralink 11n adapter, class 0/0, rev. 2.00/1.01, addr 2> on usbus1
run0: MAC/BBP RT3071 (rev 0x0213), RF RT3022 (MIMO 2T2R), address 1c:af:f7:04:0c:9d
Setting up device in HOSTAP mode (auth doesnt matter)
Connecting a client to this hostap.
Starting traffic exchange (i start pings from cl to ap and from ap to cl).
Disconnecting a client.
Core dump...

Debug looks like this (much of megs cropped):

Code:
.............
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=148 rate=2 qid=0 phy=0
run_bulk_tx_callbackN: sending frame len=128 xferlen=152 @ index 0
run_bulk_tx_callbackN: transfer complete: 152 bytes @ index 0
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=140 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=120 xferlen=144 @ index 0
run_bulk_tx_callbackN: transfer complete: 144 bytes @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_drain_fifo: tx stat 0x00000023
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x810201a6
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x00000022
run_drain_fifo: tx stat 0x00000022
run_reset_livelock: debug reg 04000001
run_iter_func: ridx=16
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=148 rate=2 qid=0 phy=0
run_bulk_tx_callbackN: sending frame len=128 xferlen=152 @ index 0
run_bulk_tx_callbackN: transfer complete: 152 bytes @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_drain_fifo: tx stat 0x00000023
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x810201a6
run_update_beacon: cmdq_store=22
run_cmdq_cb: cmdq_exec=22 pending=1
run_updateprot: mode=9 prot=1 useprot=off
run_updateprot: htinfo=2 htprot=2
run_update_beacon_cb: chan=2GHz
run_update_beacon: cmdq_store=23
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=140 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=120 xferlen=144 @ index 0
run_bulk_tx_callbackN: transfer complete: 144 bytes @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_cmdq_cb: cmdq_exec=23 pending=1
run_updateprot: mode=9 prot=1 useprot=off
run_updateprot: htinfo=2 htprot=2
run_update_beacon_cb: chan=2GHz
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x00000022
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x810401ab
run_drain_fifo: tx stat 0x810201a6
run_update_beacon: cmdq_store=24
run_cmdq_cb: cmdq_exec=24 pending=1
run_updateprot: mode=9 prot=1 useprot=off
run_updateprot: htinfo=2 htprot=2
run_update_beacon_cb: chan=2GHz
run_update_beacon: cmdq_store=25
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=140 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=120 xferlen=144 @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_bulk_tx_callbackN: transfer complete: 144 bytes @ index 0
run_rx_frame: received RT2860_RX_L2PAD frame
run_tx: qos 0	qid 0	tid 0	qflags 4
run_tx: sending data frame len=116 rate=132 qid=0 phy=8104
run_bulk_tx_callbackN: sending frame len=96 xferlen=120 @ index 0
run_bulk_tx_callbackN: transfer complete: 120 bytes @ index 0
run_cmdq_cb: cmdq_exec=25 pending=1
run_updateprot: mode=9 prot=1 useprot=off
run_updateprot: htinfo=2 htprot=2
run_update_beacon: cmdq_store=26
run_update_beacon_cb: chan=2GHz
run_cmdq_cb: cmdq_exec=26 pending=1
run_updateprot: mode=9 prot=1 useprot=off
run_updateprot: htinfo=0 htprot=2
run_update_beacon_cb: chan=2GHz
run_drain_fifo: tx stat 0x810401ab


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address	= 0xc4bcb908
fault code		= supervisor read, page not present
instruction pointer	= 0x20:0xc4b3ac0a
stack pointer	        = 0x28:0xe68c2c6c
frame pointer	        = 0x28:0xe68c2ca0
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 0 (run0 taskq)
trap number		= 12
panic: page fault
cpuid = 0
Uptime: 4m40s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
It happens about 99,99% when there's some traffic between client and ap, and client disappears. It happens about 10% when there's no traffic and client disappears.

Sorry for by bad english.
 
OP
OP
PseudoCylon

PseudoCylon

Active Member

Reaction score: 19
Messages: 151

@HighTower
HighTower said:
[CMD=]ifconfig wlan0 up scan[/CMD]
return nothing.. it is in "run" stage for a long with not output...
'up' and 'scan' cause problem. Just using 'up' also creats the list.
HighTower said:
initally, then I just installed 8.1 with generic kernel on this device I was able to scan and recieve APs list in range...
If the driver works on 8.1 this might be caused by some changes in ieee80211 stack. Can you show me the debugging messages? After creating the wlan,
# wlandebug -i wlan0 debug+dumppkts+input+elemid+node+scan+output+stateYour kernel need to be compiled with IEEE08211_DEBUG option.
Or, try
# ifconfig wlan0 ssid freebsdap channel 1# ifconfig wlan0 inet 192.168.0.1you might get lucky.


@okeeblow
Can you try this patch? As you can see, this may fix panic with rum(4) as well.
http://svn.freebsd.org/viewvc/base?view=revision&revision=217511
If it won't work,
- can I get some debug messages? DDB or at least,# wlandebug -i wlan0 anylast a few lines before panic?
- can I have kernel.tramp and kernel.tramp.bin?


@JackMiles
Can you try this?
http://gitorious.org/run/run/trees/rssi_fix/dev/usb/wlan
 
Top