From owner-freebsd-questions Thu Jun 22 7:29: 2 2000 Delivered-To: freebsd-questions@freebsd.org Received: from relay1.inwind.it (relay1.inwind.it [212.141.53.67]) by hub.freebsd.org (Postfix) with ESMTP id 863E137BAA6 for ; Thu, 22 Jun 2000 07:28:58 -0700 (PDT) (envelope-from bartequi@inwind.it) Received: from bartequi.ottodomain.org (212.141.78.123) by relay1.inwind.it; 22 Jun 2000 16:28:46 +0200 From: Salvo Bartolotta Date: Thu, 22 Jun 2000 15:30:38 GMT Message-ID: <20000622.15303800@bartequi.ottodomain.org> Subject: Re: CVSUP and hardware problem To: "FENIX" Cc: freebsd-questions@FreeBSD.ORG Reply-To: bartequi@neomedia.it In-Reply-To: References: X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 6/22/00, 2:40:58 PM, "FENIX" wrote=20 regarding CVSUP and hardware problem: > I have recently cvsup'ed my 4.0-INSTALL to 4.0-STABLE , after all was = done i > made a new kernel and , now it hangs on the boot , i got 2 NE2000=20 adapters > (ed0 ed1) and one 3com (xl) it all worked fine before the cvsup, but=20 now it > hangs on ed1 while booting, i haven't changed anything in the kernel=20 config > file i just made a new kernel with new sources (i also deed make clean= =20 for > the kernel), when i boot -c and disable ed1 it works fine . Does=20 someone > know why it's happening ? > Greets Fenix > ****************************** > |*****The Deamon Inside******| =20 > |=3D--=3D--=3D--=3D--=3D--=3D--=3D--=3D--=3D--=3D| > |May the source be with you !| > |=3D--=3D--=3D--=3D--=3D--=3D--=3D--=3D--=3D--=3D| > ****************************** Dear "Fenix", I seem to understand the following: a) you cvsup'ed your sources; b) you made your kernel WITHOUT first remaking your world. AFAICS, you built a kernel from **new** sources, all the rest=20 remaining **old**. That seems to be the problem. Workaround: 1) save a copy of your **old** kernel (e.g. kernel.safe) in order to=20 avoid overwriting it next time you make and install a kernel; 2) boot your old kernel, make world in two steps (buildworld and=20 installworld), and follow the procedure described in the handbook; OT: Remark I Under -CURRENT, a mechanism has been implemented to prevent this kind=20 of problems, ie in order to keep kernel & modules in sync. OT: Remark II In your "signature", you may wish to substitute "daemon" (or "daimon",=20 "Daemon", or even "DAEMON" -- your choice here:-))) for "Deamon". Best of luck, Salvo N.B. My "inwind" popmail is down. That's the reason for "Reply to". =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message