From owner-freebsd-bugs Mon Oct 19 13:49:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17635 for freebsd-bugs-outgoing; Mon, 19 Oct 1998 13:49:12 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17627 for ; Mon, 19 Oct 1998 13:49:09 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA25198; Mon, 19 Oct 1998 14:48:37 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810192048.OAA25198@panzer.plutotech.com> Subject: Re: pciconf does not report unloaded devices under 3.x-RELEASE, as well as the kernel, which causes modload failure In-Reply-To: <199810192041.NAA07912@george.lbl.gov> from Jin Guojun at "Oct 19, 98 01:41:12 pm" To: jin@george.lbl.gov (Jin Guojun) Date: Mon, 19 Oct 1998 14:48:37 -0600 (MDT) Cc: bugs@FreeBSD.ORG, se@mi.uni-koeln.de X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jin Guojun wrote... > Ken, > > The patch does fix pciconf problem, but modload still fails, any idea? [ ... ] > # modload -v -ezatm_mod /lkm/znatmdrv.o > modload: error initializing module: Device not configured Sorry, dunno why it doesn't work. Someone more familiar with modload will have to tackle that one... Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message