It appears you made a copy of GENERIC without changing anything. You need to open the file P200MMX in your favorite editor, and change the "ident" line to whatever you want your kernel to identify itself as. As far as the kernel and kernel.old being the same size, that's expected as you haven't change any configuration at all.

I suspect that if you type "uname -a", you'll see generic, but you'll also see towards the end something like:

Code:

root@<your hostname here>:/usr/obj/usr/src/sys/P200MMX

__________________
I just saved a bunch of money on my car insurance by fleeing the scene of the accident!

It appears you made a copy of GENERIC without changing anything. You need to open the file P200MMX in your favorite editor, and change the "ident" line to whatever you want your kernel to identify itself as. [/CODE]

I've done exactly what you describe above. I did copy GENERIC to P200MMX, and then edited a lot in P200MMX. (I also changed the ident line to P200MMX, and finally I didn't forget to save the file P200MMX.)

Quote:

Originally Posted by cajunman4life

I suspect that if you type "uname -a", you'll see generic, but you'll also see towards the end something like:

Code:

root@your hostname:/usr/obj/usr/src/sys/P200MMX

uname -a shows:

Code:

root@<my hostname here>:/usr/obj/usr/src/sys/GENERIC i386

At the moment I'm unable to show you the kernel configuration file, because I don't know yet how to transfer it to my Win PC, which I'm using now. However I used the directions in 8.5 The Configuration File only. (I used conservative settings intended for a simple workstation, not a server or anything fancy). As said, there were no error warnings during the whole process.

(I don't know whether it is of any importance, but I just noticed that I forgot to add the "machine i386" line to P200MMX. It wasn't in GENERIC either though.)

Also, IIRC the MMX was i586-class, so you should be able to remove i386 and i486 from your config file. I have a P-MMX 200MHz myself, unfortunately it's disconnected from KVM/network/etc, and I don't have the energy to connect it right now (read: I'm being lazy). However, I didn't build a custom kernel on this machine (as it would take forever to build). I used freebsd-update to make sure I had the latest security patches, and left it at that.

__________________
I just saved a bunch of money on my car insurance by fleeing the scene of the accident!

(I don't know whether it is of any importance, but I just noticed that I forgot to add the "machine i386" line to P200MMX. It wasn't in GENERIC either though.)

This line is not needed, and the build system really should have complained about it being included twice. The FreeBSD 7.0 kernel build system automatically includes the contents of /usr/src/sys/<arch>/conf/DEFAULTS into the kernel config file. "machine i386" is in the DEFAULTS file. Anything in that file, does not need to (and should not) be in the kernel config file.

Also, with any CPU newer than an i386, you should remove the cpu i386 line. For any CPU newer than an i486, you should remove the cpu i386 and cpu i486 lines.

But, for all other x86 CPUs (Pentium, PPro, P2, P3, P4, Athlons, etc), you should keep the cpu i586 line (and add cpu i686 if appropriate). There are a bunch of memory operations that are included by the i586 option that speed things up on everything since the Pentium.

The P200MMX kernel is installed successfully now. The kernel has shrunk to 3464821 bytes, which is nice compared to GENERIC's original 9219468 bytes. The PC is running fine. I still don't know what went wrong at the first try though.