From owner-freebsd-current Mon Feb 3 14:19:43 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E870D37B401 for ; Mon, 3 Feb 2003 14:19:40 -0800 (PST) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4096543F9B for ; Mon, 3 Feb 2003 14:19:40 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP id MUA74016; Mon, 03 Feb 2003 14:19:39 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 265E25D04; Mon, 3 Feb 2003 14:19:39 -0800 (PST) To: "M. Warner Losh" Cc: ob@e-Gitt.NET, freebsd-current@FreeBSD.ORG Subject: Re: Question about devd concept In-reply-to: Your message of "Sun, 02 Feb 2003 06:57:32 MST." <20030202.065732.108375307.imp@bsdimp.com> Date: Mon, 03 Feb 2003 14:19:39 -0800 From: "Kevin Oberman" Message-Id: <20030203221939.265E25D04@ptavv.es.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner, I hate Mondays, especially when I am the front-line network trouble person (cleverly called Person of the Week or POW). I have not had much time, but I can confirm that pccard_ether is NOT called when the card is already inserted at boot time and IS called when the card is inserted after the system is booted. But this still works! The card configures just fine. ??? I now am loading both if_xe and if_wi in the loader and this seems to have made things generally happy. I hope to try your recommended patch shortly, but the kernel takes quite a while to build on this rather old system with all of the debug stuff enabled. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 > Date: Sun, 02 Feb 2003 06:57:32 -0700 (MST) > From: "M. Warner Losh" > > In message: <20030201233621.916935D04@ptavv.es.net> > "Kevin Oberman" writes: > : > Date: Sat, 1 Feb 2003 19:20:12 +0100 > : > From: Oliver Brandmueller > : > Sender: owner-freebsd-current@FreeBSD.ORG > : > > : > Hi, > : > > : > I'm currently experimenting with 5-CURRENT on my Notebook an have a > : > question regarding the concept of devd. > : > > : > With 4-STABLE I had pccardd running. Whenever a pccard was inserted I > : > had pccardd starting the corresponding scripts. I have configured devd > : > to do so now (especially for my wavelan pccard). So far everything > : > works, except for one case: When the pccard is already inserted during > : > boot, devd does not recognize the card as newly inserted device (of > : > course, it's already there). So I have currently setup a script in > : > /usr/local/etc/rc.d which starts the script corresponding to the wavelan > : > pccard, if interface wi0 is found during boot. I think this cannot be > : > the considered solution for that problem? > : > > : > What am I missing about the concept of devd? > : > : While I think you have the concept down fine, the execution may still > : be a bit fuzzy in places. > : > : If the device is in place when the system boots, devd should not be > : required, as it should be probed in the traditional manner. But this > : does not seem to execute the added things that need to be done to > : bring up a new network interface. After the system is up I need to > : execute /etc/pccard_ether to get the interface on-line. > > Can you put a echo "I'm in pccard_ether" type line in > /etc/pccard_ether and see if that's being run at boot. Like I said in > my last response, I just confirmed that it is running on my machine. > > I've had some problems with CardBus cards on boot not probing, but > that's a different problem that I'm aware of and working on a solution > for and has nothing to do with devd. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message