Re: Upgrading from an old athlon to a new 64 bit one.
Quoting Garrett Cooper [EMAIL PROTECTED]: [EMAIL PROTECTED] wrote: Quoting RW [EMAIL PROTECTED]: On Thu, 28 Jun 2007 10:12:39 -0500 [EMAIL PROTECTED] wrote: 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. amd64 and i386 are different platforms in the same sense that sparc64 and ppc are different platforms. An AMD 64 is not back-compatible to pentium pro code when it's in 64-bit mode. Whilst 32-bit binaries can be run on the amd64 platform, they need special handling, you can't just mix-and-match world and kernel platforms. Thanks, RW. I had assumed that and had hoped to run my make buildworld, make buildkernel, mergemaster, make installkernel and make installworld then upgrade all ports. The problem is that I haven't been able to figure out, how to build using all amd64. Again very dumb on my part, I'm sure. ed As RW has said before it's possible. However, it's better and no doubt quicker to go about starting from scratch. -Garrett Hi Garrett, I have decided to do that one machine at a time but for now I'm just going to keep all as is. It seems to be working fine on both current and releng with the standard intel compilation. I just ordered a new machine that I will setup with current amd64 for evaluation and then decide after I've actually used it. Thanks to all for helping me get my feet back on the ground. have a great weekend, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
[EMAIL PROTECTED] wrote: Quoting RW [EMAIL PROTECTED]: On Thu, 28 Jun 2007 10:12:39 -0500 [EMAIL PROTECTED] wrote: 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. amd64 and i386 are different platforms in the same sense that sparc64 and ppc are different platforms. An AMD 64 is not back-compatible to pentium pro code when it's in 64-bit mode. Whilst 32-bit binaries can be run on the amd64 platform, they need special handling, you can't just mix-and-match world and kernel platforms. Thanks, RW. I had assumed that and had hoped to run my make buildworld, make buildkernel, mergemaster, make installkernel and make installworld then upgrade all ports. The problem is that I haven't been able to figure out, how to build using all amd64. Again very dumb on my part, I'm sure. ed As RW has said before it's possible. However, it's better and no doubt quicker to go about starting from scratch. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
Quoting RW [EMAIL PROTECTED]: On Wed, 27 Jun 2007 14:54:52 -0500 [EMAIL PROTECTED] 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
On Thu, Jun 28, 2007 at 10:12:39AM -0500, [EMAIL PROTECTED] wrote: Quoting RW [EMAIL PROTECTED]: On Wed, 27 Jun 2007 14:54:52 -0500 [EMAIL PROTECTED] 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. No, you do not *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. It probably will not work very well. The compiler on an i386 system does not know how to create amd64 code. It is not configured to be a crosscompiler - it will only compile to native i386 code. There is not really any support for switching from i386 to amd64 by source code. It can apparently be done if you know what you are doing but it is not trivial and not documented. The normal build system assumes that you are doing a native build by default. It is possible to build for a different system, but then you first need to build the necessary cross-tools (compiler, linker, assembler, etc.) and then use that to build the rest of the system. 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. Why don't you just keep running the i386 version of FreeBSD ? Is there some particular reason you want to use the amd64 version ? 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. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
On Thu, 28 Jun 2007 10:12:39 -0500 [EMAIL PROTECTED] wrote: 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. amd64 and i386 are different platforms in the same sense that sparc64 and ppc are different platforms. An AMD 64 is not back-compatible to pentium pro code when it's in 64-bit mode. Whilst 32-bit binaries can be run on the amd64 platform, they need special handling, you can't just mix-and-match world and kernel platforms. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
Quoting RW [EMAIL PROTECTED]: On Thu, 28 Jun 2007 10:12:39 -0500 [EMAIL PROTECTED] wrote: 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. amd64 and i386 are different platforms in the same sense that sparc64 and ppc are different platforms. An AMD 64 is not back-compatible to pentium pro code when it's in 64-bit mode. Whilst 32-bit binaries can be run on the amd64 platform, they need special handling, you can't just mix-and-match world and kernel platforms. Thanks, RW. I had assumed that and had hoped to run my make buildworld, make buildkernel, mergemaster, make installkernel and make installworld then upgrade all ports. The problem is that I haven't been able to figure out, how to build using all amd64. Again very dumb on my part, I'm sure. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
Quoting Erik Trulsson [EMAIL PROTECTED]: On Thu, Jun 28, 2007 at 10:12:39AM -0500, [EMAIL PROTECTED] wrote: Quoting RW [EMAIL PROTECTED]: On Wed, 27 Jun 2007 14:54:52 -0500 [EMAIL PROTECTED] 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. No, you do not *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. It probably will not work very well. The compiler on an i386 system does not know how to create amd64 code. It is not configured to be a crosscompiler - it will only compile to native i386 code. There is not really any support for switching from i386 to amd64 by source code. It can apparently be done if you know what you are doing but it is not trivial and not documented. The normal build system assumes that you are doing a native build by default. It is possible to build for a different system, but then you first need to build the necessary cross-tools (compiler, linker, assembler, etc.) and then use that to build the rest of the system. 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. Why don't you just keep running the i386 version of FreeBSD ? Is there some particular reason you want to use the amd64 version ? Hi Erik, Ignorance, I assume, is my only excuse? At least thanks to your patience and explanation, I understand and am somewhat less ignorant;) Originally, I had ordered these and I was promised that they were dual core and I had to pay in advance. When they finally arrived, I found that they were standard AMD Athlon 3800+ and no x2 so it looks like I was had but that will be another story. Then it would have made sense to change to 64 bit. For the moment my problem is solved and I'll stay with 32 bit for now. Thanks, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
On Wed, Jun 27, 2007 at 02:50:30PM -0500, [EMAIL PROTECTED] 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. I have configured a slightly modified sys/amd64/conf/GENERIC kernel and was going to build it as a test only to find out that a simple make buildkernel KERNCONF=AMD doesn't find /sys/amd64/conf/AMD. There is an old reference in UPDATING from 5.0 that didn't work either. The other question is on today's make world all seems to still be compiled ELF 32-bit LSB executable, Intel 80386 so I am sure missing something very simple. It is possible to cross-build for amd64, but you'll need a seperate partition to put the 64-bit environment on. Look at the mailing list archives. This question has come up before. But to keep things simple, I'd advise you to backup your files, configuration files from /etc and possible /usr/ports/distfiles, reinstall from an amd64 CD and then rebuild your kernel, world and ports to your liking. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpE5Lad6GZcr.pgp Description: PGP signature
Re: Upgrading from an old athlon to a new 64 bit one.
Quoting Roland Smith [EMAIL PROTECTED]: On Wed, Jun 27, 2007 at 02:50:30PM -0500, [EMAIL PROTECTED] 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. I have configured a slightly modified sys/amd64/conf/GENERIC kernel and was going to build it as a test only to find out that a simple make buildkernel KERNCONF=AMD doesn't find /sys/amd64/conf/AMD. There is an old reference in UPDATING from 5.0 that didn't work either. The other question is on today's make world all seems to still be compiled ELF 32-bit LSB executable, Intel 80386 so I am sure missing something very simple. It is possible to cross-build for amd64, but you'll need a seperate partition to put the 64-bit environment on. Look at the mailing list archives. This question has come up before. But to keep things simple, I'd advise you to backup your files, configuration files from /etc and possible /usr/ports/distfiles, reinstall from an amd64 CD and then rebuild your kernel, world and ports to your liking. Hi Roland. Boy am I glad that I asked. That is probably the last thing I would have done. Plus thanks for the answer, I must not have done a proper search. I hope that the apps will run after reinstalling. I assume that the source tree will somehow recognize that I will be building world and the kernel on a AMD64. I'm downloading a copy of disk2 from FreeBSD now. Have a great day. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from an old athlon to a new 64 bit one.
On Wed, 27 Jun 2007 14:54:52 -0500 [EMAIL PROTECTED] 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. 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
