Upgrading from an old athlon to a new 64 bit one.

eculp at unixmania.com eculp at unixmania.com
Thu Jun 28 15:12:43 UTC 2007


Quoting RW <fbsd06 at mlists.homeunix.com>:

> On Wed, 27 Jun 2007 14:54:52 -0500
> eculp at unixmania.com wrote:
>
>> I have just stuck the disks from an old AMD Athlon(tm)  (1333.39-MHz
>> 686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor
>> 3800+ (2387.78-MHz 686-class CPU).  I am still building a daily
>> kernel with the old configuration and all is well.  Of course the
>> old configuration was/is i386.  Now I need to compile for 64 bit
>> apps.
>
> Are you sure about that? there are few compelling reasons to go to
> 64-bit, if you already have a working system. As far as performance is
> concerned, it may go either way.

Hi RW,

I probably didn't explain very well.  I'll try again.

The machines that I am updating are all athlon 32 bit machines, which  
I have been doing a daily cvsup, buildworld, buildkernel,  
installkernel, installworld and weekly portupgrade for several years.   
I just removed the disks from one that is running current and another  
that is running RELENG, both still running kernels cvsup-ed and  
compiled yesterday as well as userland.  The ports are also up to date.

What I am trying to do is compile an amd64 kernel, install it and see  
what happens ;) I can always go back to the generic kernel compiled in  
sys/i386.
If all were to go well, I would then recompile all my ports.

My problem is that when I created a sys/amd64/conf/AMD (just a generic  
kernel with PF added) file and went to /usr/src and tried make  
buildkernel KERNCONF=AMD it didn't find the kernel configuration file.  
  I tried with paths, etc. and no luck.  I also see that my daily  
compiles and installs have not changed userland programs.   
/usr/bin/file shows:

c++:              ELF 32-bit LSB executable, Intel 80386, version 1  
(FreeBSD), dynamically linked (uses shared libs), stripped

Using c++ and an example.  I assume it should give a 64-bin executable  
if it were.  This particular file was built and installed this morning.

The bottom line is that I'm totally ignorant as to this change and  
have been doing some really dumb searches in that I haven't found what  
I'm missing.  I'm convenced that it is something braindead simple but  
I am still looking.

The good news is that both the current and RELENG boxes are working  
well with all as before.

Again any suggestions or even flames with more information are appreciated.

ed

>> Right now all is
>> working fine with todays, sources and kernel except they are compiled
>> for Intel.
>
> They are compiled for i386; Intel and AMD both produce CPUs for both
> platforms.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>



More information about the freebsd-questions mailing list