Date: Wed, 22 Mar 2000 08:38:07 -0500 From: Keith Stevenson <k.stevenson@louisville.edu> To: "Matthew N. Dodd" <winter@jurai.net> Cc: "Michael E. Mercer" <mmercer@ipass.net>, Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Message-ID: <20000322083807.C8858@osaka.louisville.edu> In-Reply-To: <Pine.BSF.4.21.0003220746480.50194-100000@sasami.jurai.net> References: <38D8BC46.7BBC0FF9@ipass.net> <Pine.BSF.4.21.0003220746480.50194-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 22, 2000 at 07:48:22AM -0500, Matthew N. Dodd wrote: > > Boot DOS. > > Get the 3c509 driver/util disk. > > Run '3C5X9CFG'. > > No drivers or booting of windows required. > I saw a similar problem when I upgraded from 3.4-RELEASE to 5.0-CURRENT. My ep card started fine under 3.4, but choked with the eeprom messages when booting my new current kernel. I was able to get my card working by booting into the kernel configuration tool (boot -c) and disabling all of the other network devices which were compiled in. (This was with a generic kernel.) Once I had done that, the ep driver was able to work with my card. (Strangely enough, the ep driver doesn't appear anywhere in the kernel config screen.) Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000322083807.C8858>