Chad David wrote:
> Problem solved.
>
> cp GENERIC.hints DEBUG.hints
>
> Without them it isn't very happy... did I miss this as a requirement
> somewhere, or is my hardware/timing just a little funky?
Yes, you were not reading the commit messages or UPDATING or -current.
You should have a /boot/
Problem solved.
cp GENERIC.hints DEBUG.hints
Without them it isn't very happy... did I miss this as a requirement
somewhere, or is my hardware/timing just a little funky?
Chad
On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote:
>
> >None of this has any bearing on the proble
>None of this has any bearing on the problem, which was caused by a bug
>in gensetdefs.pl. Please update your source tree and rebuild your
>kernel.
Eek. I had the gensetdefs.pl problem too, but my machine just seemed to
lock. He says his machine does go on running.
I have been pretty tied up l
"Rogier R. Mulhuijzen" <[EMAIL PROTECTED]> writes:
> Have you tried removing the 'makeoptions' line and using 'config -g
> ' instead?
> [...]
> Also, when you copy the GENERIC file to another name, do you update the
> ident line?
None of this has any bearing on the problem, which was caused by
>
>If I copy GENERIC to DEBUG and recompile the kernel it will not
>boot properly copy the file back to GENERIC and everything
>seems fine?
>
>I have searched the archives and read UPDATING, but nothing jumps
>out at me.
>
>Does anybody have any idea where I could look next?
>
>Chad
>
>On Sun
In reply to my own post (which nobody has replied to, perhaps
because I never actually phrased a question :-) )... I have found
that if the kernel config file is named GENERIC, it will boot
just fine; otherwise, I loose the console. I have done a
cvsup tonight as well as a make world and many di
