Date: Thu, 22 Jun 2000 17:23:21 +0200 From: "FENIX" <FENIX@FENIX.LOCALHOST.NL> To: <bartequi@neomedia.it> Cc: "FreeBSD Questions" <questions@FreeBSD.ORG> Subject: RE: CVSUP and hardware problem Message-ID: <NEBBKOIMOLKALNONLNCIAEAOCBAA.FENIX@FENIX.LOCALHOST.NL> In-Reply-To: <20000622.15303800@bartequi.ottodomain.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I did do Make World ! so .... ****************************** |*****The Daemon Inside******| |=--=--=--=--=--=--=--=--=--=| |May the source be with you !| |=--=--=--=--=--=--=--=--=--=| ****************************** +;-----Original Message----- +;From: owner-freebsd-questions@FreeBSD.ORG +;[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Salvo +;Bartolotta +;Sent: Thursday, June 22, 2000 5:31 PM +;To: FENIX +;Cc: freebsd-questions@FreeBSD.ORG +;Subject: Re: CVSUP and hardware problem +; +; +;>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< +; +;On 6/22/00, 2:40:58 PM, "FENIX" <FENIX@FENIX.LOCALHOST.NL> wrote +;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 +;adapters +;> (ed0 ed1) and one 3com (xl) it all worked fine before the cvsup, but +;now it +;> hangs on ed1 while booting, i haven't changed anything in the kernel +;config +;> file i just made a new kernel with new sources (i also deed make clean +;for +;> the kernel), when i boot -c and disable ed1 it works fine . Does +;someone +;> know why it's happening ? +; +;> Greets Fenix +;> ****************************** +;> |*****The Deamon Inside******| +;> |=--=--=--=--=--=--=--=--=--=| +;> |May the source be with you !| +;> |=--=--=--=--=--=--=--=--=--=| +;> ****************************** +; +; +;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 +;remaining **old**. That seems to be the problem. +; +; +; +;Workaround: +; +;1) save a copy of your **old** kernel (e.g. kernel.safe) in order to +;avoid overwriting it next time you make and install a kernel; +; +;2) boot your old kernel, make world in two steps (buildworld and +;installworld), and follow the procedure described in the handbook; +; +; +;OT: Remark I +;Under -CURRENT, a mechanism has been implemented to prevent this kind +;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", +;"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". +; +; +; +; +; +;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?NEBBKOIMOLKALNONLNCIAEAOCBAA.FENIX>