Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!uakari.primate.wisc.edu!zazen!doug.cae.wisc.edu!dinda From: dinda@cae.wisc.edu (Dinda Peter) Newsgroups: comp.unix.bsd Subject: Re: WD Ethernet Card not found on warmboot Message-ID: <1992Aug21.171828.14323@doug.cae.wisc.edu> Date: 21 Aug 92 22:18:28 GMT References: <1992Aug19.165319.14767@doug.cae.wisc.edu> <714317431.111@eyrie.img.com.au> Organization: U of Wisconsin-Madison College of Engineering Lines: 14 In article <714317431.111@eyrie.img.com.au> athos@eyrie.img.com.au (David Burren) writes: >I also have an Elite16 Combo (it's the 8013E with AUI, BNC, & UTP) and >see exactly the same symptoms. No ideas yet, just another "me too!"... > >This is in a system that's evolved from a 16 MHz 386SX through a 20 MHz >386DX to a 40 MHz 386DX. Using a mono display, A1540, floppy, & serial. >The we device has never so far been detected on warm-boot. Every solution I've gotten so far is to "recompile the kernel." I really wonder why Unix *still* doesn't have installable device drivers. The Novell Netware Requester for OS/2 is updated by just copying over the new device drivers - there's even a PM program that'll do it for you. DOS has had installable device drivers (device=) since 2.0. Is there a fundamental reason why Unix hasn't/will not support this?