Date: Sat, 01 Feb 2003 15:36:21 -0800 From: "Kevin Oberman" <oberman@es.net> To: Oliver Brandmueller <ob@e-Gitt.NET> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Question about devd concept Message-ID: <20030201233621.916935D04@ptavv.es.net> In-Reply-To: Your message of "Sat, 01 Feb 2003 19:20:12 %2B0100." <20030201182012.GC97784@e-Gitt.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Sat, 1 Feb 2003 19:20:12 +0100 > From: Oliver Brandmueller <ob@e-Gitt.NET> > 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. I have two Xircom cards, an old RE-100 16-bit card and a newer RBEM-56 CardBus Ethernet/modem card. The former uses if_xe and the latter uses if_dc. The behavior is very inconsistent. If I have if_xe loaded at boot, the RE-100 comes up fine. It has the annoying watchdog timeout and then comes up fine. If I insert the card into the running system, it also works, but prints out a failure to load the driver since the driver is already present. But it I don't have the drive in the kernel when I insert the card, it fails to initialize. The CardBus unit seems to only work when the driver is loaded at boot time and then the Ethernet part simply works. Unfortunately, the modem does not as the devices are not created in /dev by devfs. (I suspect I can get this working once I get devfs figured out a bit better.) But, I still need to execute /etc/paccard_ether before the Ethernet is usable. If I insert the card into a running system, I just get continuous watchdog timeouts and can't do much until I eject the card. I hope to have some time Monday to sit down and try as many combinations of card insertions/ejections and driver loading as possible to see if I can see a clear pattern to the operation of these cards. Maybe that will provide a pointer as to where things are breaking down in both of our cases. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030201233621.916935D04>