From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 17 23:44:52 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32ADC106566C for ; Sat, 17 Dec 2011 23:44:52 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id 083958FC1C for ; Sat, 17 Dec 2011 23:44:51 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.7]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBHNinaC025144; Sat, 17 Dec 2011 16:44:50 -0700 From: Erich Dollansky To: Bernhard Schmidt Date: Sun, 18 Dec 2011 06:45:14 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112171411.05872.bschmidt@freebsd.org> In-Reply-To: <201112171411.05872.bschmidt@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112180645.14868.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, PseudoCylon Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2011 23:44:52 -0000 Hi, On Saturday 17 December 2011 20:11:05 Bernhard Schmidt wrote: > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > > > > I have a simple problem with this Zyxel wireless adaptor. I am not able to use it directly after a reboot. The interface becomes only available after I unplug it and plug it in again. > > > > I believe that this is the crucial message: > > > > run0: could not load 8051 microcode > > > > As I have said, it all works as expected after I plugged it in again. > > > > Here is my dmesg with the messages regarding the device. The first part is from the boot and the remaining is from the replugging. > > > > run0: <1.0> on usbus1 > > run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 > > runfw: root not mounted yet, no way to load image > > run0: failed loadfirmware of file runfw > > run0: could not load 8051 microcode > > device_attach: run0 attach returned 6 > > run0: <1.0> on usbus1 > > run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 > > run0: firmware RT2870 loaded > > > > I think that the explanation is so simple but I do not see it. > > run(4) tries to load the firmware on attach at which point the root > filesystem isn't yet mounted. Actually I think the prefered behaviour > is to load it during init, not sure this is possible for run(4) > though. Someone should check this. :) > > As a workaround you can add runfw_load="YES" to /boot/loader.conf this made it work. You seem to be German. You know then the line 'den Wald vor lauter Baeumen ...' Thanks for your help. Erich > > -- > Bernhard > >