Bug #3443
closed
run -- Ralink Technology USB
0%
Description
NAME
run -- Ralink Technology USB IEEE 802.11a/g/n wireless network device
SYNOPSIS
To compile this driver into the kernel, place the following lines in your
kernel configuration file:
device ehci
device uhci
device ohci
device usb
device run
device wlan
device wlan_amrr
Firmware is also needed, and provided by:
device runfwAlternatively, to load the driver as a module at boot time, place the
following lines in loader.conf(5):
if_run_load="YES"
runfw_load="YES"I did not find "runfw_load" in /boot/defaults/loader.conf
So i tried to add it and reboot, i got this,
Feb 10 13:55:32 kernel: Root mount waiting for: usbus0
Feb 10 13:55:32 kernel: uhub0: 2 ports with 2 removable, self powered
Feb 10 13:55:32 kernel: Root mount waiting for: usbus0
Feb 10 13:55:32 kernel: ugen0.2: <Ralink> at usbus0
Feb 10 13:55:32 kernel: run0: <1.0> on usbus0
Feb 10 13:55:32 kernel: Root mount waiting for: usbus0
Feb 10 13:55:32 kernel: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address a0:f3:c1:0f:fb:f8
Feb 10 13:55:32 kernel: runfw: root not mounted yet, no way to load image
Feb 10 13:55:32 kernel: run0: failed loadfirmware of file runfw
Feb 10 13:55:32 kernel: run0: could not load 8051 microcode
Feb 10 13:55:32 kernel: device_attach: run0 attach returned 6
and I could not determin if device runfw is in kernel or not. but i wonder if the load of runfw delayed untill root is mounted, shal this fix it?
Updated by Chris Buechler about 10 years ago
- Status changed from New to Rejected
The run driver is included. It appears it doesn't work with your card. Probably no solution to that until our 2.2 release, based on FreeBSD 10, which has much improved wireless drivers.
Updated by Muhammed Ismail about 10 years ago
Mr.Chris as it is said in the FreeBSD Kernel Interfaces Manual
[[http://www.freebsd.org/cgi/man.cgi?query=run&apropos=0&sektion=4&manpath=FreeBSD+8.3-RELEASE&arch=default&format=html]]
i know we are on pfsense's bug tracker, but in m0n0wall's Repository
[[http://svn.m0n0.ch/wall/branches/freebsd8/build/kernelconfigs/M0N0WALL_GENERIC.i386]]
you will not find "device runfw" in kernel. and it is required to load firmware
in pfsense it should be loaded with
if_run_load="YES"
runfw_load="YES" which is not found!. and fails to load when adding it.
so it is a kernel issue missing device runfw
i beleive i made my point, and if i a miss understod something, please explaine.
Thanks
Updated by Muhammed Ismail about 10 years ago
I am wrong, i tested it with the tow options "Yes"
and the driver loaded and worked fine untill i connect my self to it's AP,
and then switched to another AP, same crash happend , you seem to be right, thanks
Updated by Vladimir Suhhanov about 10 years ago
OK. There is something else wrong, not just "freebsd 10" needed.
On boot I have that (newest on top)
Apr 17 18:39:17 kernel: device_attach: run0 attach returned 6
Apr 17 18:39:17 kernel: run0: could not load 8051 microcode
Apr 17 18:39:17 kernel: run0: failed loadfirmware of file runfw
Apr 17 18:39:17 kernel: runfw: root not mounted yet, no way to load image
Apr 17 18:39:17 kernel: run0: MAC/BBP RT3071 (rev 0x021C), RF RT3022 (MIMO 2T2R), address e8:4e:06:0f:21:6e
Apr 17 18:39:17 kernel: run0: <1.0> on usbus4
Apr 17 18:39:17 kernel: ugen4.2: <Ralink> at usbus4
Nothing works also. Ok. Fine. I re-plug the card (RT3072)... WOW, magic!
Apr 17 18:39:17 kernel: run0: firmware RT3071 loaded
Apr 17 18:39:17 kernel: run0: MAC/BBP RT3071 (rev 0x021C), RF RT3022 (MIMO 2T2R), address e8:4e:06:0f:21:6e
Apr 17 18:39:17 kernel: run0: <1.0> on usbus4
Apr 17 18:39:17 kernel: ugen4.2: <Ralink> at usbus4
Apr 17 18:39:17 kernel: ugen4.2: <Ralink> at usbus4 (disconnected)
I am not freebsd guru, but I don't believe that this is correct behavior on boot
Apr 17 18:39:17 kernel: runfw: root not mounted yet, no way to load image
Anyway the wifi card "works", but sometimes it crashes the kernel. I have tried another wifi cards too and it crashes also, but at least theay are working after reboot (different driver and hardware vendor). Looks like wifi is very unstable in freebsd 8.3?