From owner-freebsd-stable Tue Mar 21 22:37:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 80DD837C155 for ; Tue, 21 Mar 2000 22:37:41 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA51822; Wed, 22 Mar 2000 01:37:11 -0500 (EST) Date: Wed, 22 Mar 2000 01:37:10 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: mmercer@ipass.net, mmercer@nortelnetworks.com, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003220559.OAA23262@tasogare.imasy.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, Mitsuru IWASAKI wrote: > Subject: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... > > How did you fix this? I'm having the same problem but in 5-CURRENT... Mr. Mercer emailed me in private and reconfigured his card manually. If you're having the same problems then please provide me with the following. - Output of a verbose boot. - The configuration of your machine. (devices, resources etc.) - The output of 'ident /sys/dev/ep/*', or if you're installing a snapshot, the exact version of the snapshot. Your problem is likely due to pilot error but if this is gonna be a common problem then I should probably make the driver a little smarter. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message