Date: Mon, 9 Dec 2002 15:28:09 -0700 From: "Thomas Connolly" <tpconnolly@frii.com> To: "'Kevin D. Kinsey, DaleCo, S.P.'" <kdk@daleco.biz>, <hawkeyd@visi.com>, "'Jack L. Stone'" <jackstone@sage-one.net> Cc: <freebsd-questions@freebsd.org> Subject: RE: Ethernet card problem Message-ID: <001201c29fd2$4190ea80$5608a8c0@ceesi.com> In-Reply-To: <01e101c29fcf$0d2d8990$fa00a8c0@DaleCoportable>
next in thread | previous in thread | raw e-mail | index | archive | help
This is exactly my situation, any ideas?? "If his NIC is *not* there when it's time to configure and start the d-load, it's a hardware/BIOS issue, or somebody's broke sysinstall(8).....or is there another option I'm missing?" Tom -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Kevin D. Kinsey, DaleCo, S.P. Sent: Monday, December 09, 2002 3:05 PM To: hawkeyd@visi.com; Jack L. Stone Cc: freebsd-questions@freebsd.org Subject: Re: Ethernet card problem OK, he's got a Kingston (generally dc driver) and is trying to do sysinstall and d-load over NIC. IME it doesn't matter what you pick in the "configuration" section of sysinstall --- whatever's first should work, because those are just old nonPNP ISA NIC drivers. After doing "kernel configuration in full-screen visual/CLI/skip" then sysinstall does an initial device probe, and when you get to "configure interface," it should be there. For the record, device miibus is enabled in -GENERIC kernel. If his NIC is *not* there when it's time to configure and start the d-load, it's a hardware/BIOS issue, or somebody's broke sysinstall(8).....or is there another option I'm missing? Kevin Kinsey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001201c29fd2$4190ea80$5608a8c0>