Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Jun 2000 15:30:38 GMT
From:      Salvo Bartolotta <bartequi@inwind.it>
To:        "FENIX" <FENIX@FENIX.LOCALHOST.NL>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: CVSUP and hardware problem
Message-ID:  <20000622.15303800@bartequi.ottodomain.org>
In-Reply-To: <NEBBKOIMOLKALNONLNCIEEAJCBAA.FENIX@FENIX.LOCALHOST.NL>
References:  <NEBBKOIMOLKALNONLNCIEEAJCBAA.FENIX@FENIX.LOCALHOST.NL>

next in thread | previous in thread | raw e-mail | index | archive | help
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 6/22/00, 2:40:58 PM, "FENIX" <FENIX@FENIX.LOCALHOST.NL> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000622.15303800>