From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 20 08:50:09 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 E7F6B106564A; Tue, 20 Dec 2011 08:50:08 +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 B08648FC12; Tue, 20 Dec 2011 08:50:07 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.13]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBK8o4YY020954; Tue, 20 Dec 2011 01:50:06 -0700 From: Erich Dollansky To: PseudoCylon Date: Tue, 20 Dec 2011 15:49:56 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112190411.28991.erichfreebsdlist@ovitrap.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112201549.57990.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt 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: Tue, 20 Dec 2011 08:50:09 -0000 Hi, On Monday 19 December 2011 11:42:02 PseudoCylon wrote: > On Sun, Dec 18, 2011 at 2:11 PM, Erich Dollansky > wrote: > > Hi, > > > > On Sunday 18 December 2011 12:32:46 PseudoCylon wrote: > >> On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky > >> wrote: > >> > Hi, > >> > > >> > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: > >> >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > >> >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > >> >> > > >> >> > 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. :) > >> >> > > >> >> mmm... It seems "someone" is me. > >> >> > >> >> At the quick look, the firmware could be loaded during the init. Give > >> >> me a few days, I will try to change. > >> >> > >> > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. > >> > > >> Actually, it was quite straight forward. The patch follows. > >> > >> Also, a tarball is attached which include patch to man.4/run.4 and new > >> firmware. I don't know what has been changed, but I'd appreciate if > >> you try new firmware out. > > > > after installing the patch and rebooting the machine, the interface came up as expected. I could not test the new firmware as I did not find the location where to store it. > > > Good to hear. > > The original firmware is in /usr/src/sys/contrib/dev/run The easiest > way is over write the firmware, cd to /usr/src/sys/modules/runfw, > make, and install. The patched if_run will prints out firmware > version. Old one is 0.17, new one is 0.236 oh, I did not look at the obvious place as it looks like. I just install a new kernel with this firmware. I was off-line for some time for other technical reasons. If you hear nothing from me anymore, it works as expected. Erich