From owner-freebsd-current@FreeBSD.ORG Thu Mar 3 11:46:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9395A1065674; Thu, 3 Mar 2011 11:46:13 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B9A188FC0A; Thu, 3 Mar 2011 11:46:12 +0000 (UTC) Received: by fxm19 with SMTP id 19so1127204fxm.13 for ; Thu, 03 Mar 2011 03:46:11 -0800 (PST) Received: by 10.223.119.68 with SMTP id y4mr1361281faq.104.1299152771834; Thu, 03 Mar 2011 03:46:11 -0800 (PST) Received: from jessie.localnet (p5B2ECF94.dip0.t-ipconnect.de [91.46.207.148]) by mx.google.com with ESMTPS id f24sm517302fak.0.2011.03.03.03.46.09 (version=SSLv3 cipher=OTHER); Thu, 03 Mar 2011 03:46:10 -0800 (PST) Sender: Bernhard Schmidt From: Bernhard Schmidt To: erob@gthcfoundation.org Date: Thu, 3 Mar 2011 12:45:51 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.32-28-generic; KDE/4.4.5; i686; ; ) References: <4D66C4CB.1060207@2egos.de> <201103030845.09198.hselasky@c2i.net> <4D6F7ADC.809@gthcfoundation.org> In-Reply-To: <4D6F7ADC.809@gthcfoundation.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201103031245.52178.bschmidt@freebsd.org> Cc: freebsd-current@freebsd.org, Hans Petter Selasky Subject: Re: urtw0: could not allocate USB transfers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bschmidt@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2011 11:46:13 -0000 On Thursday, March 03, 2011 12:26:20 Etienne Robillard wrote: > On 03/03/11 02:45 AM, Hans Petter Selasky wrote: > > > >>>> I forwarded this thread on -current. > >>>> > >>>> Please also find below a stack trace produced with option KDB_UNATTENDED > >>>> for the rt28700 driver (if_rt28700). > >>>> > >>>> On another side note, I have not being able to load > >>>> the runfw firmware module anymore after having updated > >>>> the src tree for 8.2-STABLE ? > >>>> > >>>> $ sudo kldload /boot/kernel/runfw.ko > >>>> kldload: can't load /boot/kernel/runfw.ko: Exec format error > >>>> > >>> Here is your real error in dmesg: > >>> > >>>> KLD runfw.ko: depends on firmware - not available or version mismatch > >>>> linker_load_file: Unsupported file type > >>>> > >>> You need to kldload firmware.ko or make sure 'device firmware' is in your > >>> kernel config. > >>> > >> Hi, > >> > >> Many thanks. This explains the change of behavior attempting to kldload > >> runfw.ko > >> without the firmware assist module. :) > >> > >> However I find strange that run(4) requires such a firmware to be preloaded > >> when the rt2870 driver doesn't require it! > >> > >> Cheers, > >> > > > > Maybe that's due to a missing MODULE_DEPEND() line in the .c file of urtw0. > > > > --HPS > > > > > > Hi, > > Thanks for the input. I realize the urtw(4) and the pseudo rt2870 drivers > may be missing a MODULE_DEPEND macro but this issue is not as annoying > than the repeated page faults happening when the card is trying > to reassociate itself with a router. urtw(4) has no firmware, run(4) has the appropriate depend line. The rt2870 driver is not in-tree, contact the maintainter. > I also noticed the same (random) page faults with the run(4) driver as > well but since I don't use a driver > requiring a external firmware to be loaded, I would prefer fixing the > errors in the generic > wireless code happening unconditionally with run(4), rt2870, and > possibly urtw(4). Plus, > a external firmware seems not necessary for using at least the TEW-644UB > wireless adapter! You should by now have noticed that you can't use a Realtek driver with a Ralink chipset, or the other way around. So please stop calling both broken in one mail. Also, again, the rt2870 driver isn't in-tree, contact the maintainer. -- Bernhard