From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 17 13:11:08 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 01B94106566B for ; Sat, 17 Dec 2011 13:11:08 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 917F98FC15 for ; Sat, 17 Dec 2011 13:11:07 +0000 (UTC) Received: by eekc50 with SMTP id c50so4690614eek.13 for ; Sat, 17 Dec 2011 05:11:06 -0800 (PST) Received: by 10.14.123.130 with SMTP id v2mr1203290eeh.56.1324127466220; Sat, 17 Dec 2011 05:11:06 -0800 (PST) Received: from amy.lab.techwires.net (dslb-178-002-168-014.pools.arcor-ip.net. [178.2.168.14]) by mx.google.com with ESMTPS id x12sm14843428eef.9.2011.12.17.05.11.04 (version=SSLv3 cipher=OTHER); Sat, 17 Dec 2011 05:11:05 -0800 (PST) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-wireless@freebsd.org Date: Sat, 17 Dec 2011 14:11:05 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.0-PRERELEASE; KDE/4.7.3; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> In-Reply-To: <201112171258.56891.erichfreebsdlist@ovitrap.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112171411.05872.bschmidt@freebsd.org> Cc: 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 13:11:08 -0000 On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > Hi, > > 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 -- Bernhard