Re: appropriate 64 bit version?
Justin Archer [EMAIL PROTECTED] wrote: Hi, I have just purchased a new Dell Server, to run with Plesk. I have just moved from an Apple XServe and seeing that OS X derived from FreeBSD, I felt that it was the best choice to start with. My only dilemma is, I am wanting to run the system in 64-bit, with using the Intel Quad 2.5Ghz Xeon, but I am unsure as to which version I should be downloading. For plesk, I need to use version 6.1 and had read somewhere that I would use the AMD 64-bit version, can you confirm if this is correct for an Intel processor? A descriptive subject line generally makes for more responses on mailing lists. The amd64 spec is the same as the EM64T spec that Intel uses. Thus the amd64 version of FreeBSD will work correctly on Intel Xeon CPUs. The version is called amd64 because AMD published their spec first. (FYI) -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: appropriate 64 bit version?
The version is called amd64 because AMD published their spec first. (FYI) the thing I have actually wondered is why i386 and amd64 are used as the naming convention instead of x86 and x86-64 or x64 -Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: appropriate 64 bit version?
On Fri, Jun 06, 2008 at 05:13:16PM -0400, Sean Cavanaugh wrote: The version is called amd64 because AMD published their spec first. (FYI) the thing I have actually wondered is why i386 and amd64 are used as the naming convention instead of x86 and x86-64 or x64 Just because someone thought of that at the time they were naming it. Actually, I think there was some thought that and64 and the Intel attempt would actually be different and so needed distinguishing. But, apparently the Intel differences didn't hold enough sway in the market place. jerry -Sean ___ 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]
How to run 32 bit FreeBSD compiled apps on 64 bit
I have a simple program say Hello world , i have compiled it on 32 bit FreeBSD and it dynamically links to libraries(I cannot make it statically linked due to some requirements), now when i run it on AMD64 i get ELF interpreter /libexec/ld-elf32.so.1 not found. How to fix it, i searched and found out i shud install lib32 on my 64 bit machine. How to install lib32's and from where ?? Thanks, Navneet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit FreeBSD compiled binary coredumps on 64 bit(amd) FreeBSD
Am Mittwoch, 20. Februar 2008 07:17:30 schrieb navneet Upadhyay: I am compiling the binary on 32 bit FreeBSD and running it on 64 (amd64)bit FreeBSD . FreeBSD says it is possible to do so. But my application core dumps . I investigated the reason which is as follows : The problem is in the call retval = sysctl(mib, 4, kp, sz, NULL, 0); where sz is size of kp and where kp is a structure of type kinfo_proc. The size of this structure on 32bit system is 768 and on 64 bit system is 1088. The call works on 32 bit system but when run on 64 bit system it coredumps , because of the size mismatch of kinfo_proc . If i hardcode the sz to 1088 then it works on amd64 systems , how do i deal with it. I am anticipating lot of coredumps like that, what is a generic solution for such kinds of problems. Without investigating further whether the structure up to byte 768 is different (wrt. structure member offsets, and thus wrt. to hardcoded constants in the binary file), which would be a real showstopper for the i386-emulation on amd64 (and thus I can't see it being that way), see the documentation of sysctl: RETURN VALUES Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS [ENOMEM] The length pointed to by oldlenp is too short to hold the requested value. So, basically, you should check in the call whether sysctl returned -1 (with errno set to ENOMEM), and enlarge the buffer if so, until it doesn't return -1 anymore. This should handle i386 and amd64 transparently (if the offsets up to byte 768 are equal/similar). In case you're trying to recompile the application on 64-bit, you should use sizeof() anyway to automatically adapt the initial buffer size reserved for the output buffer depending on the definition of the structure (which will also spare you pain if a FreeBSD upgrade changes the structure). -- Heiko Wundram Product Application Development ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit FreeBSD compiled binary coredumps on 64 bit(amd) FreeBSD
If i hardcode the sz to 1088 then it works on amd64 systems , how do i deal with it. I am anticipating lot of coredumps like that, what is a generic solution for such kinds of problems. to compile both versions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
Can anyone tell how do we handle this situation??? Is there any way or i have to compile my code on 64 bit machine?? what's a problem to compile on 64-bit machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
32 bit and 64 bit freebsd binary compatiblty
Binary compiled on 32 bit not running on 64 bit machine. Actually i am using *sysctl* call and the *kinfo_proc* structure from user.hin include/sys , size of structure on 32bit is 768 and on 64 bit is around 1180 and thats why the call is failing and application coredumping. Can anyone tell how do we handle this situation??? Is there any way or i have to compile my code on 64 bit machine?? Keep in mind there can be many such structure.. Thanks, Navneet On 2/19/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. This should not happen. I would blindly guess at a linking problem. Are you using any shared libraries that do not belong to the base system? Yes i am using few libs not built on FreeBSD but they work fine on 32 bit freeBSD , so in principle they shud have the same behavior on 64 one. I suppose you are aware that they have to be 32-Bit libraries as well, for your 32-Bit application to work? I didnt get what do you mean. Do you mean : I should install lib32 on freeBSD and then rebuild my applications in order to make it work on 32 and 64 bit systems . rite now I have built my app on 32 bit system (which is not having lib32 installed), it works on 32 bit freebsd but fails on 64 bit system. The app needs 32-Bit libraries tu run on 64 Bit. I suggest you link your program statically against libraries that are not part of the base system. That way everything should run just fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
Am Dienstag, 19. Februar 2008 15:08:12 schrieb Wojciech Puchar:
Can anyone tell how do we handle this situation???
Is there any way or i have to compile my code on 64 bit machine??
what's a problem to compile on 64-bit machine?
Ugh, there can be lots of problems, at least if the original programmers
weren't careful enough to avoid the many pitfalls of inter-architecture
development.
For example, in C, the long type is 32-bits wide on i386, and 64-bits wide on
amd64, whereas int is 32-bits wide on both.
Take the following code:
#include stdio.h
int main(int argc, char** argv)
{
int x;
unsigned long y = (unsigned long)x;
printf(%x\n,y);
return 0;
}
The formatting code %x expects an unsigned integer, but is given an unsigned
long (which is always big enough to fit an address, that's mandated by the C
standard, and so will contain the memory address of x). gcc only warns about
the non-matching format-string argument when run with -Wall.
On i386, this doesn't matter, as sizeof(int)==sizeof(long).
On amd64, this does matter, as printing a %x will only print the low-order
four bytes of the memory address, and not the upper four bytes, so that the
output string will no longer be unique for object x, depending on how the
virtual memory space is partitioned.
Now, I've seen quite a good deal of software who do stuff similar to this (at
least in spirit, by casting an address to an unsigned integer) to build
(hash) tables, and they all miserably fail when compiled on amd64, simply
because they presume that sizeof(int) == sizeof(long), which isn't true on
amd64 anymore.
If the OP's development team haven't taken care to avoid these pitfalls from
the start (which I guess they didn't, simply because they are only used to
developing on i386), they can be in for a real treat when trying to compile
_and run_ their application on amd64. I know I've had my fair share of
(re-)learning to do when initially compiling my (personal use) C++ programs
on amd64.
--
Heiko Wundram
Product Application Development
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
a machine will be required (always) , i think i figured it out , ineed to compile them using *amd64 *instead of i386 . On 2/19/08, Wojciech Puchar [EMAIL PROTECTED] wrote: Can anyone tell how do we handle this situation??? Is there any way or i have to compile my code on 64 bit machine?? what's a problem to compile on 64-bit machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
32 bit and 64 bit freebsd binary compatiblty
Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. Thanks, Navneet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
Am Montag, den 18.02.2008, 20:42 +0530 schrieb navneet Upadhyay: it and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. Thanks, Do you have the lib32's installed ? bye Norman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
navneet Upadhyay wrote: Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. This should not happen. I would blindly guess at a linking problem. Are you using any shared libraries that do not belong to the base system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
I checked in usr/local/ and didnt find the lib32 folder, so i guess they are nt installed . Why do i need them ? can u put some light on it ? On 2/18/08, Norman Maurer [EMAIL PROTECTED] wrote: Am Montag, den 18.02.2008, 20:42 +0530 schrieb navneet Upadhyay: it and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. Thanks, Do you have the lib32's installed ? bye Norman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
Yes i am using few libs not built on FreeBSD but they work fine on 32 bit freeBSD , so in principle they shud have the same behavior on 64 one. On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. This should not happen. I would blindly guess at a linking problem. Are you using any shared libraries that do not belong to the base system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
In response to navneet Upadhyay [EMAIL PROTECTED]: I checked in usr/local/ and didnt find the lib32 folder, so i guess they are nt installed . Why do i need them ? can u put some light on it ? I'm not sure of the details why you need them, but no ia32 program that I've seen runs properly on amd64 without. If you're running a release version, you can run sysinstall, then go to configuration - distributions and select to install. You can also build/install world and this should grab them by default. On 2/18/08, Norman Maurer [EMAIL PROTECTED] wrote: Am Montag, den 18.02.2008, 20:42 +0530 schrieb navneet Upadhyay: it and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. Thanks, Do you have the lib32's installed ? bye Norman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* no idea. i use it but rarely, having no problems. consider adding extra logs (printfs, etc.) to get know when it crashes and fill a problem report Any known reasons, do we have to compile binaries on 64 bit machine. you should, as is it not a problem but performance is much better. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
navneet Upadhyay wrote: On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. This should not happen. I would blindly guess at a linking problem. Are you using any shared libraries that do not belong to the base system? Yes i am using few libs not built on FreeBSD but they work fine on 32 bit freeBSD , so in principle they shud have the same behavior on 64 one. I suppose you are aware that they have to be 32-Bit libraries as well, for your 32-Bit application to work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Building Xorg as 32 Bit binaries on 64 Bit system?
Hi, I'm running FreeBSD 7 on an Athlon64 based machine with a 64 bit kernel. The machine is supposed to be a server (at home) so there's basically no Xorg involved. Now I want to monitor what the system is doing and I decided to install sysutils/conky from ports. The problem is that conky crashes with a BadDrawable error. I searched the net for some time and found evidence that conky might not work in 64 bit mode. I tried to recompile it - the entire Xorg packages - but every time I end up having 64 bit binaries. I have CPUTYPE and CFLAGS commented out in /etc/make.conf, but the problem seems to arise from the configure scripts used by Xorg. For example during make install clean on xproto configure states: checking build system type... amd64-portbld-freebsd7.0 checking host system type... amd64-portbld-freebsd7.0 checking for style of include used by make... GNU checking for amd64-portbld-freebsd7.0-gcc... cc I wonder if it's possible to somehow override the build system type information? Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
I didnt get what do you mean. Do you mean : I should install lib32 on freeBSD and then rebuild my applications in order to make it work on 32 and 64 bit systems . rite now I have built my app on 32 bit system (which is not having lib32 installed), it works on 32 bit freebsd but fails on 64 bit system. On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. This should not happen. I would blindly guess at a linking problem. Are you using any shared libraries that do not belong to the base system? Yes i am using few libs not built on FreeBSD but they work fine on 32 bit freeBSD , so in principle they shud have the same behavior on 64 one. I suppose you are aware that they have to be 32-Bit libraries as well, for your 32-Bit application to work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 32 bit and 64 bit freebsd binary compatiblty
navneet Upadhyay wrote: On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: On 2/18/08, Dominic Fandrey [EMAIL PROTECTED] wrote: navneet Upadhyay wrote: Hi , For our product we generally compile the binaries on 32 bit systems and use them for both 32 and 64 bit systems. like we have same binaries for 32 bit and 64 bit RHEL. We are porting the product to FreeBSD and when we tried the same, i.erunning binaries compiled on 32 bit FreeBSD 6.2 on 64 bit FreeBSD system they produce *core dump.* Any known reasons, do we have to compile binaries on 64 bit machine. This should not happen. I would blindly guess at a linking problem. Are you using any shared libraries that do not belong to the base system? Yes i am using few libs not built on FreeBSD but they work fine on 32 bit freeBSD , so in principle they shud have the same behavior on 64 one. I suppose you are aware that they have to be 32-Bit libraries as well, for your 32-Bit application to work? I didnt get what do you mean. Do you mean : I should install lib32 on freeBSD and then rebuild my applications in order to make it work on 32 and 64 bit systems . rite now I have built my app on 32 bit system (which is not having lib32 installed), it works on 32 bit freebsd but fails on 64 bit system. The app needs 32-Bit libraries tu run on 64 Bit. I suggest you link your program statically against libraries that are not part of the base system. That way everything should run just fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Synaptics Touchpad doesn't work on 64-bit FreeBSD
Hi, my Synaptics touchpad doesn't work on FreeBSD 200710 amd64. I've add hw.psm.synaptics_support=1 to my /boot/loader.conf and I've compiled x11-drivers/synaptics and x11-drivers/xf86-input-mouse. My dmesg says: psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 kldload: Unsupported file type kldload: Unsupported file type Xorg says: Synaptics Touchpad no synaptics event device found (checked 10 nodes) Synaptics Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device Synaptics Touchpad The touchpad worked fine on FreeBSD 200710 i386. Does anybody know what to do? Best greetings Thomas ___ 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 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]
Upgrading from an old athlon to a new 64 bit one.
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. I'm actually going to update serveral machines, both Current and RELENG. All of which are up to date. Hopefully there will be no major problems. I also plan to recompile all ports once I am able to build and install an AMD64 world and kernel. Right now all is working fine with todays, sources and kernel except they are compiled for Intel. Any other suggestions appreciated. Maybe someone might recommend upgrading the RELENG boxes to CURRENT first? Thanks, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading from an old athlon to a new 64 bit one.
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. I'm actually going to update serveral machines, both Current and RELENG. All of which are up to date. Hopefully there will be no major problems. I also plan to recompile all ports once I am able to build and install an AMD64 world and kernel. Right now all is working fine with todays, sources and kernel except they are compiled for Intel. Any other suggestions appreciated. Maybe someone might recommend upgrading the RELENG boxes to CURRENT first? 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]
Which build to use for Intel Core 2 Duo 64-bit?
Which build should I use to build a native 64-bit installation on an Intel Core 2 Duo (E6600)? Can I use the AMD64 build? Is there anything I should be careful when rebuilding from source after a cvsup? Can I just use the AMD64 build and CPUTYPE=nocona in /etc/make.conf ? Thanks in advance, Tom Veldhouse ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which build to use for Intel Core 2 Duo 64-bit?
Thomas T. Veldhouse wrote: Which build should I use to build a native 64-bit installation on an Intel Core 2 Duo (E6600)? AMD64 kernel, SMP variant. Specific compiler optimizations will not yield high enough benefits to be generally useful but it probably[*] won't hurt you. [*] There was a period when there was a bug in gcc which caused it to generate bad code for certain processor optimizations such as CPUTYPE=P4. signature.asc Description: OpenPGP digital signature
Re: Cannot Load FreeBSD 6.2 64 bit and maybe other versions as well
An update for some who may care. I tried loading Live Linux distros: Puppy, DSL and STD. They load fine but don't see a network interface. Also installed Fedora 5 Linux Distro and same - no ethernet interface seen. It has been a while but I recall that Windows XP pro will not boot. Anybody have any ideas on what to try next? I am pretty much spent. This is a new evaluation box and so I have no problems sending it back to the SuperMicro VAR. I want to figure this thing out just for the challenge of it. Know what I mean? Yudhvir = On 12/11/06, Y Sidhu [EMAIL PROTECTED] wrote: I am a newbie and have gone though past posts and have been looking at the last couple of weeks of posts go by. I have not seen anything similar to my problem. I cannot load an OS except under ACPI-Disabled. I can boot into safe mode, but cannot configure a working network interface. Therefore, I cannot send in a dmesg output. Here is some data I have gathered: Details a. SuperMicro X7DBR-8+ / X7DBR-I+ b. Intel 3.2 GHz Xeon dual core dual cpu, K8 class cpu c. BIOS - Phoenix (just upgraded to 1.2A from 1.1C) The upgrade has had no affect on this problem as far as I can tell. d. Dual Ethernet - Intel Pro/1000 Network Connection Version 6.2.9. em0 is IRQ 5 at device 0.0 on pci4. em1 is IRQ 11 at device 0.1 on pci4. Also, when I am booted in safe mode, in dmesg, there is an entry em IRQ 10 at device 2.0 on pci5. e. SCSI - Adaptec version 4.3. AIC 7902 Ultra 320, PCI-X ID=7 f. One 73 GB Seagate Cheetah 10K.7 SCSI hard drive, Model ST3207LC. I have tested this and another drive out without any media errors. The Adaptec adapter sees the drive and capacity fine. g. When I try to boot normally, the messages scroll by and the system freezes at: waiting 5 seconds for SCSI devices to settle h. When I disable ACPI either under the BIOS's settings or select Disable ACPI when loading FreeBSD, the system loads but I cannot get the ethernet interface to come up. ifconfig shows all the right values. I have also used route delete default and route add default ip of gateway - to no avail. There is a message which pops up saying em0: watchdog timeout - resetting Looking into dmesg output, I see: em0 link state changed to UP and em0 link state DOWN repeat over and over again. i. 1 GB ram and have tested it with memtest 86 without any errors. My Gut a. Something is causing a good old fashioned IRQ conflict. I have 1 drive and 1 cdrom on this machine. b. The SCSI ACPI79xx driver is not there or not loading Hoping I am looking for a nudge in the right direction. -- Yudhvir Singh Sidhu -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot Load FreeBSD 6.2 64 bit and maybe other versions as well
On 2006/12/12 11:42, Y Sidhu seems to have typed: a. SuperMicro X7DBR-8+ / X7DBR-I+ Seems that others have had problems with SuperMicro boards: http://www.freebsd.org/platforms/amd64/motherboards.html *** QUOTE *** Boots stock SMP kernel. UP kernel must be booted in safe mode *** END QUOTE *** Have you tried booting up the stock SMP kernel? Basically: boot into safe mode or single user mode cd /usr/src make buildkernel KERNCONF=SMP make installkernel KERNCONF=SMP reboot Assuming that you installed a developer version of FreeBSD (that includes the source code). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot Load FreeBSD 6.2 64 bit and maybe other versions as well
I am a newbie and have gone though past posts and have been looking at the last couple of weeks of posts go by. I have not seen anything similar to my problem. I cannot load an OS except under ACPI-Disabled. I can boot into safe mode, but cannot configure a working network interface. Therefore, I cannot send in a dmesg output. Here is some data I have gathered: Details a. SuperMicro X7DBR-8+ / X7DBR-I+ b. Intel 3.2 GHz Xeon dual core dual cpu, K8 class cpu c. BIOS - Phoenix (just upgraded to 1.2A from 1.1C) The upgrade has had no affect on this problem as far as I can tell. d. Dual Ethernet - Intel Pro/1000 Network Connection Version 6.2.9. em0 is IRQ 5 at device 0.0 on pci4. em1 is IRQ 11 at device 0.1 on pci4. Also, when I am booted in safe mode, in dmesg, there is an entry em IRQ 10 at device 2.0 on pci5. e. SCSI - Adaptec version 4.3. AIC 7902 Ultra 320, PCI-X ID=7 f. One 73 GB Seagate Cheetah 10K.7 SCSI hard drive, Model ST3207LC. I have tested this and another drive out without any media errors. The Adaptec adapter sees the drive and capacity fine. g. When I try to boot normally, the messages scroll by and the system freezes at: waiting 5 seconds for SCSI devices to settle h. When I disable ACPI either under the BIOS's settings or select Disable ACPI when loading FreeBSD, the system loads but I cannot get the ethernet interface to come up. ifconfig shows all the right values. I have also used route delete default and route add default ip of gateway - to no avail. There is a message which pops up saying em0: watchdog timeout - resetting Looking into dmesg output, I see: em0 link state changed to UP and em0 link state DOWN repeat over and over again. i. 1 GB ram and have tested it with memtest 86 without any errors. My Gut a. Something is causing a good old fashioned IRQ conflict. I have 1 drive and 1 cdrom on this machine. b. The SCSI ACPI79xx driver is not there or not loading Hoping I am looking for a nudge in the right direction. -- Yudhvir Singh Sidhu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 64-bit(EM64T) and Hyperthreading support
Hi, I just purchased a new Intel Pentium 4(3.06Ghz), 533 Mhz FSB, supporting EM64T (as written in the box). It has 1 MB cache size, package type = LGA 775, processor number = 524 Features: (as shown in the dropdown combo box when cpu speed =3.06, processor number = 524) http://processorfinder.intel.com/List.aspx?ProcFam=483sSpec=OrdCode= Enhanced Halt State (CIE) Enhanced Intel Speedstep Technology Execute Disable Bit Hyper-Threading Technology Intel EM64T Intel Thermal Monitor 2 Intel Virtualization Technology I wonder if I could benefit from these features when running AMD64 version. On i386 install, I just enabled SMP and the OS happilly reported 2 logical cpus, however, I'm not sure how I will build a particular application to benefit from this hyperthreading thing. There are certain knobs when configuring a particular application that says --enable-pthreads. Does it have something to do with this HT thing? Is it a bad idea to always pkg_add rather than make install?? Also, I'm concerned with EM64T. Let's say I installed the AMD64 version, those software I will be building via ports will pick up this EM64T thing, right?? No additional knobs? So they run faster? AMD64 is on tier 1 right? Are there any caveats? Will my mplayer, xawtv, and snd_hda patch work flawlessly just like it use to in i386? Howabout this hardware based Virtualization? 'You got any experience on making this work? I mean, running completely different operating system at once, like that of Xen, Virtuozzo, VMware etc. I will consult Intel's docs soon, in the meantime, any idea what are these? Enhanced Halt State (CIE) - Is this supported? Enhanced Intel Speedstep Technology - I think this has something to do with overclocking.. still need to check on their site. Execute Disable Bit - According to the wiki, it has something to do with countering buffer overflow attacks right? is this supported? Intel Thermal Monitor 2 - still have to check if mbmon will work on this one. That's all folks. Thanks! -mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 64-bit(EM64T) and Hyperthreading support
You Wrote: I wonder if I could benefit from these features when running AMD64 version. On i386 install, I just enabled SMP and the OS happilly reported 2 logical cpus, however, I'm not sure how I will build a particular application to benefit from this hyperthreading thing. Not all applications do. In fact, HyperThreading can cause lower performance in a lot of situations. Moreover it poses a (minor) security risk to your system. I also have read HyperThreading is disabled by default for that reason, but that might be old information. There are certain knobs when configuring a particular application that says --enable-pthreads. Does it have something to do with this HT thing? Is it a bad idea to always pkg_add rather than make install?? Using packages means the package is built for all CPU types and without optimizations. With ports you can use the optimized C-flags feature, which causes make to compile using all supported optimizations like SSE/SSE2, etc. Also, I'm concerned with EM64T. Let's say I installed the AMD64 version, those software I will be building via ports will pick up this EM64T thing, right?? Since Intel's EM64T is a shameless copy of AMD's AMD64 technology (without any mention to AMD64 in the docs) -- yes you should be able to run the FreeBSD AMD64 platform without any problems. Enhanced Intel Speedstep Technology - I think this has something to do with overclocking.. still need to check on their site. Nope, it will cause lower power drain by lowering the clock frequency and voltage when the processor is sitting idle. You'll need the cpufreq kernel loadable module installed (kldload /boot/kernel/cpufreq.ko) and run powerd iirc. But as far as i know Intel hasn't come to the level of Cool'N'Quiet in recent AMD processors. I'm not sure if the SpeedStep desktop processors can actually do voltage control. Good luck! - Veronica ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Plesk and FreeBSD 6.1 64-bit getting frustrating
Hello We were using Plesk on FreeBSD 5.4, i386, and had a lot of problem with qmail wich is crashing sometimes without any reason. We tried differend tips found on forums and disabling antivirus and modifying some script we managed to restart the crashed mail service by watchdog, but still the mail service crash more than ten times a day. The problem with crashing qmail was found not only on FreeBSD but on Linux too. So our learned lesson was: 1. don't try even to make it work if is not designed for your version of bsd, is a waste of time, 2. Plesk 7.5 is not as good as we thought, you might try Plesk 8, maybe is better, but, I still recommend you CPanel. Is difficult to work with closed source code, if a problem occurs you do not know what to do. Best Regards, ovidiu Dan Schultzer wrote: Hello I've got FreeBSD 6.1 installed on a Sun Fire X2100 server, and are trying to get plesk installed. But plesk isn't supported for FreeBSD 6.1 64-bit version yet, so it has been hard work to try trick it. Now I want to trick the uname command to show the version needed for plesk installation. Any one having an easy and pretty safe way to do this? This is the last try before I trash FreeBSD as it's pretty important that this server come up and running soon, though I love FreeBSD :( Also, I'm not member at this list so please mail / cc me directly. Thanks. Regards, Dan Schultzer ___ 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: Plesk and FreeBSD 6.1 64-bit getting frustrating
Hi Ovidiu Thanks for your information. Yeah, I've pretty much given up on this, so I'll use Suse instead and then later on, when I've more time, try get FreeBSD installed with a better CP. Thanks again. Regards, Dan Schultzer Den 17. sep 2006 kl. 13:19 skrev ovidiu ene: Hello We were using Plesk on FreeBSD 5.4, i386, and had a lot of problem with qmail wich is crashing sometimes without any reason. We tried differend tips found on forums and disabling antivirus and modifying some script we managed to restart the crashed mail service by watchdog, but still the mail service crash more than ten times a day. The problem with crashing qmail was found not only on FreeBSD but on Linux too. So our learned lesson was: 1. don't try even to make it work if is not designed for your version of bsd, is a waste of time, 2. Plesk 7.5 is not as good as we thought, you might try Plesk 8, maybe is better, but, I still recommend you CPanel. Is difficult to work with closed source code, if a problem occurs you do not know what to do. Best Regards, ovidiu Dan Schultzer wrote: Hello I've got FreeBSD 6.1 installed on a Sun Fire X2100 server, and are trying to get plesk installed. But plesk isn't supported for FreeBSD 6.1 64-bit version yet, so it has been hard work to try trick it. Now I want to trick the uname command to show the version needed for plesk installation. Any one having an easy and pretty safe way to do this? This is the last try before I trash FreeBSD as it's pretty important that this server come up and running soon, though I love FreeBSD :( Also, I'm not member at this list so please mail / cc me directly. Thanks. Regards, Dan Schultzer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Plesk and FreeBSD 6.1 64-bit getting frustrating
Hello I've got FreeBSD 6.1 installed on a Sun Fire X2100 server, and are trying to get plesk installed. But plesk isn't supported for FreeBSD 6.1 64-bit version yet, so it has been hard work to try trick it. Now I want to trick the uname command to show the version needed for plesk installation. Any one having an easy and pretty safe way to do this? This is the last try before I trash FreeBSD as it's pretty important that this server come up and running soon, though I love FreeBSD :( Also, I'm not member at this list so please mail / cc me directly. Thanks. Regards, Dan Schultzer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Clevo D900K and 64 bit FreeBSD support???
I've been looking into replacing my current laptop/desktop with a Clevo D900K, AMD-64 machine. I'm just curious if anyone out there has any experience getting FreeBSD up and running on this machine and at what capacity (card reader, 8.1 sound card, WLAN+Bluetooth, Hardware RAID, etc.) I was going to go with the Nvidia Quadro graphics card and am curious on the status of 64bit native nvidia drivers. I know it wasn't/isn't supported as of yet. Also I was hoping to take an existing i386 system and move it to the 64bit system. Can I by properly specifying the environment rebuild an i386 system to 64bit? Or am I better off/ have too install a fresh 64bit system? I would imagine this could tick off a few ports like portupgrade that would make rebuilding tricky at best. I've linked to and included the machine spec for those savy enough to look at the general hardware and know it's level of support. thanks, -brian http://www.clevo.com.tw/products/D900K.asp link might make the following look a little nicer D900K Specification CPU #12290; AMD AthlonTM 64 X2 Processor 3800+/4200+/4600+ #12288; (2.00~2.40GHz, 1MB L2 cache, socket 939) #12290; AMD AthlonTM 64 X2 Processor 4400+/4800+ #12288; (2.20~2.40GHz, 2MB L2 cache, socket 939) #12290; AMD AthlonTM 64 Processor FX-53/FX-55/FX-57 #12288; (2.40~2.80GHz, 1MB L2 cache, socket 939) #12290; AMD AthlonTM 64 Processor 3000+/3200+/3400+/3500+/3800+ #12288; (1.80~2.40GHz, 512KB L2 cache, socket 939) #12290; AMD AthlonTM 64 Processor 3700+/4000+ #12288; (2.20~2.40GHz, 1MB L2 cache, socket 939) Core Logic #12290;VIA K8T890CE + VT8237R Display #12290;17.1 WXGA (1440x900) TFT / 17.1 WSXGA+ (1680x1050) / 17.1 WUXGA (1920x1200) TFT Memory #12290;Two 64-bit wide DDR data channels #12290;Two 200-pin SODIMM sockets, supporting DDR 400 #12290;Expandable Memory up to 2GB, based on 256/512/1024MB SODIMM Module Video Controller #12290;(Option) nVIDIA QuadroTM Fx 2500 #12288;High performance graphic chip #12290;512MB DDRIII Video RAM on board #12290;256-bit video memroy interface #12290;PCI-Express x16 #12290;Fully DirectX 9.0 support #12290;Modular Design #12290;OpenGL support #12290;(Option) nVIDIA GeForceTM Go #12288;7900 GTX High performance #12288;graphic chip #12290;256MB DDRIII Video RAM on board #12290;256-bit video memroy interface #12290;PCI-Express x16 #12290;Fully DirectX 9.0 support #12290;Modular Design #12290;H.264 encode support #12288; (HD-DVD/BD-DVD playback) #12290;(Option) nVIDIA GeForceTM Go 7900 #12288;GTX High performance graphic chip #12290;512MB DDRIII Video RAM on board #12290;256-bit video memroy interface #12290;PCI-Express x16 #12290;Fully DirectX 9.0 support #12290;Modular Design #12290;H.264 encode support #12288; (HD-DVD / BD-DVD playback) Storage #12290;One changeable Primary 2.5 HDD 9.5mm(H) #12290;Serial ATA HDD support #12290;Supporting Master mode IDE ATA-100/133 (Ultra DMA) #12290;One changeable Primary Bay for 12.7mm(H) DVD-ROM / Combo / DVD-Dual Driver #12290;(Option) One external USB 1.44MB Floppy Disk Drive #12290;(Option) One changeable Secondary 2.5 HDD 9.5mm(H) #12290;(Option) One changeable Secondary Bay for 12.7mm(H) DVD-ROM / Combo / DVD-Dual Driver Keyboard#12290;Full size keyboard, with Numeric Pad, Multi-Language support #12290;Built-in Touchpad with scrolling function Sound System#12290;AC'97 2.2 Compliant Interface #12290;3D stereo enhanced sound system #12290;Virtual 8-channel audio output #12290;Sound-Blaster PROTM compatible #12290;S/PDIF Digital output #12290;SRS (Sound Retrieval System® ) / WOW 3D sound technology #12290;1x Built-in Microphone #12290;4x Built-in Speakers #12290;1x Built-in Sub woofer #12290;1x Built-in Audio DJ Console for music CD (MP3 format compatible) I/O Ports #12290;4x USB 2.0 ports #12290;2x Mini IEEE1394a ports #12290;1x S-Video jack for TV output (HDTV support) #12290;1x Serial port #12290;1x Parallel port (LPT1), supporting ECP/EPP #12290;1x Infrared Transfer port #12290;1x DVI port #12290;1x PS/2 port #12290;1x Headphone jack #12290;1x Microphone jack #12290;1x S/PDIF output jack #12290;1x Line-in jack for Audio input #12290;1x RJ-45 port for LAN #12290;1x RJ-11 port for Modem #12290;1x DC-In jack #12290;1x CATV input jack (optional function with TV-Tuner module) #12290;1x S-Video jack for Video input (optional function with TV-Tuner module) Slot#12290;Built-in 10-in-1 Card Reader (MS/MS Pro/SD/MMC/CF/SM/MicroDrive/MS DUO/Mini SD/RSMMC) #12290;1x Type II PCMCIA socket Communication #12290;Infrared Transfer : 115.2Kbps SIR/4Mbps FIR, IrDA 1.1 compliant #12290;10/100/1000BASE-T Fast Ethernet onboard #12290;Integrated V.90/56K Azalia Modem (V.92 compliant) #12290;(Option) 802.11b/g MiniPCI Wireless LAN Module #12290;(Option) BluetoothTM Class II V2.0 Module, combo with 802.11b/g Wireless LAN Module #12290;(Factory option) 1.3M-pixel Video Camera module Power #12290;Full Range 220W AC adapter - AC input 100~240V, 47~63Hz
Re: Intel 64bit / AMD 64 bit advantage
ke han wrote: On Aug 28, 2006, at 4:03 AM, Wojciech Puchar wrote: 32 vs 64 bits does not give you any raw performance boost for most apps. The yes it will. FreeBSD/amd64 works at least 10% faster than FreeBSD/i386 on athlon64 machine, when i386 version were recompiled for P4. With default FreeBSD/i386 - it will be at least 30%. just because it's not just 64-bit addresses, but twice the registers (r8-r15) allowing C compiler to generate more efficient code. For now AMD64 is the fastest and cheapest architecture - at least with AMD processors, not intel clones. (YES now intel makes clones of AMD processors) I stand corrected ;-)...This is good info, thanks. However, to the original post, you will not see 10-30 % performance difference on your email or file sharing between an Intel Celeron and AMD Opteron. These types of apps are Disk and Network IO bound. Spend your money on redundancy/fail-over of hard drive and power supply. Also choosing a well regarded NIC is important. ke han ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks a million for this info, this saved he good bunch of money, which I can use better some were else :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel 64bit / AMD 64 bit advantage
Generally speaking, mail and file server are not RAM intensive. A 32 proc can directly address 4GB RAM (2**32). FreeBSD allows you to address more than 4GB on a 32 bit proc but limited to 4GB max per process. The actual per process limit will be a bit less, I think. A 64 bit proc can get you 2**64 bits of directly addressable RAM and therefore a much higher per process setting. But if your aren't investing in huge amounts of RAM, you are not getting much benefit from 64 over 32 bit proc. Anyway, there is no benefit to running a mail or file server on 64 bit process ors unless you must have more than 4GB total diectly addressable RAM or any single process must get near the 4GB threshold. 32 vs 64 bits does not give you any raw performance boost for most apps. The exception are mathematically intensive apps which would benefit from handling very large integers or floats as 64 bits in one go instead of breaking down into more than one process cycle to push through the same numbers. A mail or file server does no come close to needing this kind of 64 bit math. A mail and file server is Hard drive and network intensive, NOT RAM intensive. Spend your money on things like Hardware RAID and redundant power supplies, not 64 bit over 32 bits. have a good day, ke han On Aug 25, 2006, at 10:56 PM, Martin Miedema wrote: I hope that I'm not starting some sort of holy war with this question, but here I'll go. I'm planning to set-up some e-mail / file servers running FreeBSD 6.1 in the near future and I'm wondering if it will be worth the cost to use 64 but CPU's for this. Also I would like to know which brand CPU would be best for these applications. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [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: Intel 64bit / AMD 64 bit advantage
32 vs 64 bits does not give you any raw performance boost for most apps. The yes it will. FreeBSD/amd64 works at least 10% faster than FreeBSD/i386 on athlon64 machine, when i386 version were recompiled for P4. With default FreeBSD/i386 - it will be at least 30%. just because it's not just 64-bit addresses, but twice the registers (r8-r15) allowing C compiler to generate more efficient code. For now AMD64 is the fastest and cheapest architecture - at least with AMD processors, not intel clones. (YES now intel makes clones of AMD processors) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel 64bit / AMD 64 bit advantage
On Aug 28, 2006, at 4:03 AM, Wojciech Puchar wrote: 32 vs 64 bits does not give you any raw performance boost for most apps. The yes it will. FreeBSD/amd64 works at least 10% faster than FreeBSD/ i386 on athlon64 machine, when i386 version were recompiled for P4. With default FreeBSD/i386 - it will be at least 30%. just because it's not just 64-bit addresses, but twice the registers (r8-r15) allowing C compiler to generate more efficient code. For now AMD64 is the fastest and cheapest architecture - at least with AMD processors, not intel clones. (YES now intel makes clones of AMD processors) I stand corrected ;-)...This is good info, thanks. However, to the original post, you will not see 10-30 % performance difference on your email or file sharing between an Intel Celeron and AMD Opteron. These types of apps are Disk and Network IO bound. Spend your money on redundancy/fail-over of hard drive and power supply. Also choosing a well regarded NIC is important. ke han ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Intel 64bit / AMD 64 bit advantage
I hope that I'm not starting some sort of holy war with this question, but here I'll go. I'm planning to set-up some e-mail / file servers running FreeBSD 6.1 in the near future and I'm wondering if it will be worth the cost to use 64 but CPU's for this. Also I would like to know which brand CPU would be best for these applications. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thursday 22 June 2006 17:06, pete wright wrote: Did you try to build/install a 32bit version of VNC? Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. -pete How do you do cross-compilation on amd64? I looked through the mailing list archives and couldn't find a method. Also, VNC, slow as it is, tends to be faster than running X apps directly, at least over high-latency networks. NX runs rings around both of them, though. -- Jonathan Fosburgh AIX and Storage Administrator UT MD Anderson Cancer Center Houston, TX pgpNDUVUVewrD.pgp Description: PGP signature
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
screen? /usr/port/sysutils/screen My users need up to 20 instances of a graphical analysis package which has a text-based control window that spawns two graphical windows. They run a window manager with 24 virtual desktops, each running an instance of this program. As much as I love screen (I use it constantly for sysadmin-type work and I have mutt running constantly on one of my screens), it doesn't quite fulfill our needs for this task. What about xorg-dmx? It seems. it's provide what you need :) Does it test someone? -- Best regards, Arseny Nasokin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
On 21/06/06 Nikolas Britton said: The consensus seems to be that FreeBSD/amd64 is a tad slower then FreeBSD/i386 because it has to deal with 32 extra bits. The primary reason to use FreeBSD/amd64 seems to be if you need greater then 4GB of RAM. This should give you the speed boost your looking for: CPUTYPE?=pentium2 CFLAGS+= -mtune=nocona COPTFLAGS+= -mtune=nocona Put that in /etc/make.conf and recompile ports/kern/world. Cool, thanks. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgp0yeHMhLcFM.pgp Description: PGP signature
Re: migrating to 64-bit
On 6/23/06, Michael P. Soulier [EMAIL PROTECTED] wrote:
On 21/06/06 Nikolas Britton said:
The consensus seems to be that FreeBSD/amd64 is a tad slower then
FreeBSD/i386 because it has to deal with 32 extra bits. The primary
reason to use FreeBSD/amd64 seems to be if you need greater then 4GB
of RAM.
This should give you the speed boost your looking for:
CPUTYPE?=pentium2
CFLAGS+= -mtune=nocona
COPTFLAGS+= -mtune=nocona
Put that in /etc/make.conf and recompile ports/kern/world.
Cool, thanks.
Mike
Yea it looks weird but I've benchmarked it:
-march=pentium2 + -mtune=pentium3
-march=pentium2 + -mtune=pentium4
-march=pentium2 + -mtune=prescott
-march=pentium2 + -mtune=nocona
All are equal to or better then -march={your_real_cpu} alone, which is
weird because -march=cputype implies -mtune=cputype. My gcc settings
also produce safer (less buggy) code at compile time and safely
optimizes code that would otherwise ignore the CPUTYPE option in
make.conf... YMMV.
--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Does anyone run VNC with 64-bit FreeBSD (amd64)?
G'day everyone, I recently had to replace a disk and took the opportunity to upgrade from 5-stable to 6-stable. I also changed from the 32-bit to the 64-bit version. I have a dual Opteron server. VNC installed from ports (4.2.1) doesn't work on the 64-bit machine. The same version installed on my home machine (32-bit) with the .vnc directory copied over exactly from my work 64-bit machine runs fine. So in what sense does it fail If I create a blank .vnc/xstartup, then I get the usual grey screen. Then if I try and run X commands on that display, some work, like xsetroot -solid blue, but others, xterm, icewm, twm, etc don't. 130~/.vnc$ icewm -display :9 IceWM: using /home/xx/.icewm for private configuration files X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Value in failed request: 0x0 Serial number of failed request: 9 Current serial number in output stream: 10 131~/.vnc$ xterm -display :9 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x21 Serial number of failed request: 41 Current serial number in output stream: 49 If they are in the xstartup file they give the exact same errors in the vnc log file. I was only running them interactively above to troubleshoot it. Google has failed me for once, so I seek your experience and advice... Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On 6/22/06, Greg Lane [EMAIL PROTECTED] wrote: G'day everyone, I recently had to replace a disk and took the opportunity to upgrade from 5-stable to 6-stable. I also changed from the 32-bit to the 64-bit version. I have a dual Opteron server. VNC installed from ports (4.2.1) doesn't work on the 64-bit machine. The same version installed on my home machine (32-bit) with the .vnc directory copied over exactly from my work 64-bit machine runs fine. So in what sense does it fail If I create a blank .vnc/xstartup, then I get the usual grey screen. Then if I try and run X commands on that display, some work, like xsetroot -solid blue, but others, xterm, icewm, twm, etc don't. 130~/.vnc$ icewm -display :9 IceWM: using /home/xx/.icewm for private configuration files X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Value in failed request: 0x0 Serial number of failed request: 9 Current serial number in output stream: 10 131~/.vnc$ xterm -display :9 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x21 Serial number of failed request: 41 Current serial number in output stream: 49 If they are in the xstartup file they give the exact same errors in the vnc log file. I was only running them interactively above to troubleshoot it. Google has failed me for once, so I seek your experience and advice... Greg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 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: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thu, Jun 22, 2006 at 04:04:34PM +0300, Alex Savovski [EMAIL PROTECTED] wro I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On Thu, Jun 22, 2006 at 11:29:15AM -0500, Jonathan Fosburgh [EMAIL PROTECTED] wrote: VNC (tightvnc included) as well as NXWindows (IMHO, much better than VNC) are based on old versions of XFree86 that don't support AMD64. I have had some success running the i386 package of tightvnc and starting only twm from the xstartup script. Some applications (just about anything using gtk) crash the VNC server, and some (KDE) work all right. YMMV. I have tried to make NXWindows work on amd64 but there is just too much patching that needs to be done for my meager skills. Thanks for the info. I had figured something like this. I installed the 64-bit system anticipating a future memory upgrade from the current 4GB to 8GB. However, VNC is essential for various members of my group, as is ports/devel/root (which doesn't compile on amd64) and there is some of our own (also essential) custom software which is not 64-bit clean. Since this holds up a number of people from their work and my patching skills are VERY meager, I will have to roll back to the 32-bit OS. Thanks again! Greg P.S. Yes, I should have tested more before the upgrade. I did some tests, but obviously not enough! In my defence, I was hastened by the disk dying and the need to get the machine back up and running. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On 6/22/06, Greg Lane [EMAIL PROTECTED] wrote: On Thu, Jun 22, 2006 at 03:06:46PM -0700, pete wright [EMAIL PROTECTED] wrote: Did you try to build/install a 32bit version of VNC? Thanks for the suggestion. I thought about doing that, but there is still other essential software that is not 64-bit clean and our entire group needs this machine back up ASAP since currently we are sitting on our hands doing nothing till I get it back up. If I had a spare machine I could potentially spend some time getting this sorted. But we don't have a spare machine, we don't have any money to buy one, there is only me to fix it, and I have to get some real work done the usual story. hmm, so there is no way to run the app's which are not 64bit clean in 32bit mode in your environment? Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. What about the other 10%? We use VNC because it saves state for those of my users who work from multiple locations, at home, at work and some are even based overseas. They don't want to restart up to 20 windows every time they logon. Remote access in this form is essential for their productivity. screen? /usr/port/sysutils/screen I hope this is taken as friendly advice to save you work -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thu, Jun 22, 2006 at 03:06:46PM -0700, pete wright [EMAIL PROTECTED] wrote: Did you try to build/install a 32bit version of VNC? Thanks for the suggestion. I thought about doing that, but there is still other essential software that is not 64-bit clean and our entire group needs this machine back up ASAP since currently we are sitting on our hands doing nothing till I get it back up. If I had a spare machine I could potentially spend some time getting this sorted. But we don't have a spare machine, we don't have any money to buy one, there is only me to fix it, and I have to get some real work done the usual story. Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. What about the other 10%? We use VNC because it saves state for those of my users who work from multiple locations, at home, at work and some are even based overseas. They don't want to restart up to 20 windows every time they logon. Remote access in this form is essential for their productivity. Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thu, Jun 22, 2006 at 04:15:47PM -0700, pete wright [EMAIL PROTECTED] wrote: hmm, so there is no way to run the app's which are not 64bit clean in 32bit mode in your environment? I did test one of them. It works, but I don't have time to mess with all of them, and finding the 32-bit libraries and putting them in the right place took me forever. I am afraid I am not a great programmer... However, I can quickly do a reinstall safely since I have a recent backup and all my /data and /home file systems are on separate disks I can just unplug. It comes down to a how much time do I have to spare issue and in the end the machine has to be back up today. I already have my own instant-server meta-port that installs all my standard ports. It only takes a couple of hours and I can do some other work while I wait. Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. What about the other 10%? We use VNC because it saves state for those of my users who work from multiple locations, at home, at work and some are even based overseas. They don't want to restart up to 20 windows every time they logon. Remote access in this form is essential for their productivity. screen? /usr/port/sysutils/screen My users need up to 20 instances of a graphical analysis package which has a text-based control window that spawns two graphical windows. They run a window manager with 24 virtual desktops, each running an instance of this program. As much as I love screen (I use it constantly for sysadmin-type work and I have mutt running constantly on one of my screens), it doesn't quite fulfill our needs for this task. I hope this is taken as friendly advice to save you work No drama! Friendly advice is always gratefully received. Especially if it is aimed at saving me work! Unfortunately I think rolling back the OS is the least work for me at this point in time. Thanks again, I do appreciate the advice. Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On 6/22/06, Greg Lane [EMAIL PROTECTED] wrote: On Thu, Jun 22, 2006 at 04:04:34PM +0300, Alex Savovski [EMAIL PROTECTED] wro I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On Thu, Jun 22, 2006 at 11:29:15AM -0500, Jonathan Fosburgh [EMAIL PROTECTED] wrote: VNC (tightvnc included) as well as NXWindows (IMHO, much better than VNC) are based on old versions of XFree86 that don't support AMD64. I have had some success running the i386 package of tightvnc and starting only twm from the xstartup script. Some applications (just about anything using gtk) crash the VNC server, and some (KDE) work all right. YMMV. I have tried to make NXWindows work on amd64 but there is just too much patching that needs to be done for my meager skills. Thanks for the info. I had figured something like this. I installed the 64-bit system anticipating a future memory upgrade from the current 4GB to 8GB. However, VNC is essential for various members of my group, as is ports/devel/root (which doesn't compile on amd64) and there is some of our own (also essential) custom software which is not 64-bit clean. Since this holds up a number of people from their work and my patching skills are VERY meager, I will have to roll back to the 32-bit OS. Did you try to build/install a 32bit version of VNC? Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
Michael P. Soulier wrote: On 20/06/06 Andy Reitz said: I believe that ia64 refers to the Itanium port of FreeBSD, and I'm not sure of the i386 version will install on Itanium. Are you referring to the AMD64/EMT-64 port of FreeBSD? It's a 64-bit P4. My i386 5.4 install works fine. Mike That processor is EM64T. It falls into AMD64/EM64T category instead of IA64. Cheers, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
On 6/20/06, Michael P. Soulier [EMAIL PROTECTED] wrote: On 20/06/06 Andy Reitz said: I believe that ia64 refers to the Itanium port of FreeBSD, and I'm not sure of the i386 version will install on Itanium. Are you referring to the AMD64/EMT-64 port of FreeBSD? It's a 64-bit P4. My i386 5.4 install works fine. IA64 = Itanium, Itanium2 = FreeBSD/ia64 EM64T = Intel CPUs with AMD64 (P4, Xeon, etc.) = FreeBSD/amd64 AMD64 = Opteron, Athlon 64, Turion 64, Sempron 64 = FreeBSD/amd64 http://en.wikipedia.org/wiki/EM64T Why do you need to run in 64-bit mode? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
On 21/06/06 Nikolas Britton said: IA64 = Itanium, Itanium2 = FreeBSD/ia64 EM64T = Intel CPUs with AMD64 (P4, Xeon, etc.) = FreeBSD/amd64 AMD64 = Opteron, Athlon 64, Turion 64, Sempron 64 = FreeBSD/amd64 http://en.wikipedia.org/wiki/EM64T Why do you need to run in 64-bit mode? I'm asking that myself. I'd like to do comparisons with and without 64-bit support. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpstMGQgaaaU.pgp Description: PGP signature
Re: migrating to 64-bit
On 6/21/06, Michael P. Soulier [EMAIL PROTECTED] wrote: On 21/06/06 Nikolas Britton said: IA64 = Itanium, Itanium2 = FreeBSD/ia64 EM64T = Intel CPUs with AMD64 (P4, Xeon, etc.) = FreeBSD/amd64 AMD64 = Opteron, Athlon 64, Turion 64, Sempron 64 = FreeBSD/amd64 http://en.wikipedia.org/wiki/EM64T Why do you need to run in 64-bit mode? I'm asking that myself. I'd like to do comparisons with and without 64-bit support. The consensus seems to be that FreeBSD/amd64 is a tad slower then FreeBSD/i386 because it has to deal with 32 extra bits. The primary reason to use FreeBSD/amd64 seems to be if you need greater then 4GB of RAM. This should give you the speed boost your looking for: CPUTYPE?=pentium2 CFLAGS+= -mtune=nocona COPTFLAGS+= -mtune=nocona Put that in /etc/make.conf and recompile ports/kern/world. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
On 6/21/06, Michael P. Soulier [EMAIL PROTECTED] wrote: On 21/06/06 Nikolas Britton said: IA64 = Itanium, Itanium2 = FreeBSD/ia64 EM64T = Intel CPUs with AMD64 (P4, Xeon, etc.) = FreeBSD/amd64 AMD64 = Opteron, Athlon 64, Turion 64, Sempron 64 = FreeBSD/amd64 http://en.wikipedia.org/wiki/EM64T Why do you need to run in 64-bit mode? I'm asking that myself. I'd like to do comparisons with and without 64-bit support. The consensus seems to be that FreeBSD/amd64 is a tad slower then FreeBSD/i386 because it has to deal with 32 extra bits. The primary reason to use FreeBSD/amd64 seems to be if you need greater then 4GB of RAM. This should give you the speed boost your looking for: CPUTYPE?=pentium2 CFLAGS+= -mtune=nocona COPTFLAGS+= -mtune=nocona Put that in /etc/make.conf and recompile ports/kern/world. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
migrating to 64-bit
Hello, I recently got an ia64 box at work, and I threw my i386 freebsd 5.4 on it. Now, is there a way to rebuild world with 64-bit support from there? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgp58oKUJ6qiZ.pgp Description: PGP signature
Re: migrating to 64-bit
On Tue, 20 Jun 2006, Michael P. Soulier wrote: Hello, I recently got an ia64 box at work, and I threw my i386 freebsd 5.4 on it. Now, is there a way to rebuild world with 64-bit support from there? Hi Mike, I believe that ia64 refers to the Itanium port of FreeBSD, and I'm not sure of the i386 version will install on Itanium. Are you referring to the AMD64/EMT-64 port of FreeBSD? -Andy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
--- Michael P. Soulier [EMAIL PROTECTED] wrote: Hello, I recently got an ia64 box at work, and I threw my i386 freebsd 5.4 on it. Now, is there a way to rebuild world with 64-bit support from there? Thanks, Mike Everything I've tested runs slower in 64-bit mode (mainly because of kernel clunkiness), so if you don't need the long pointers you might want to re-think your proposed adventure. I believe that since everything is bigger in 64-bit mode, things fall out of the cpu cache a lot faster, and there is a significant different in performance in and out of the cache. DT __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: migrating to 64-bit
On 20/06/06 Andy Reitz said: I believe that ia64 refers to the Itanium port of FreeBSD, and I'm not sure of the i386 version will install on Itanium. Are you referring to the AMD64/EMT-64 port of FreeBSD? It's a 64-bit P4. My i386 5.4 install works fine. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpnBnLwRnmBt.pgp Description: PGP signature
ports net-snmp to support 64-bit snmp counter
Hi All
I am running freebsd 4.11 release and want to have
net-snmp to support 64 bit counter
I deinstall the net-snmp but don't know how to
re-complie the port to support
--enable-mfd-rewrites
I changed the Makefile and recomplied it and it
doesn't work
snmpwalk -v 2c -c x localhost ifHighSpeed
IF-MIB::ifHighSpeed = No Such Object available on this
agent at this OID
Thank you for your help
CONFIGURE_ARGS+=--enable-shared --enable-internal-md5
\
--enable-mfd-rewrites \
--with-mib-modules=${_NET_SNMP_MIB_MODULES} \
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports net-snmp to support 64-bit snmp counter
In the last episode (May 03), adrian kok said: I am running freebsd 4.11 release and want to have net-snmp to support 64 bit counter FreeBSD's internal network counters are 32-bit, so it won't help you. -- Dan Nelson [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: ports net-snmp to support 64-bit snmp counter
Dear Nelson Thank you for your mail Do you know and have experience how to solve this Gigabit speed, net-snmp, and overflows issue? http://lists.ee.ethz.ch/mrtg/msg30587.html Thank you again --- Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (May 03), adrian kok said: I am running freebsd 4.11 release and want to have net-snmp to support 64 bit counter FreeBSD's internal network counters are 32-bit, so it won't help you. -- Dan Nelson [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: ports net-snmp to support 64-bit snmp counter
In the last episode (May 04), adrian kok said: Dear Nelson Thank you for your mail Do you know and have experience how to solve this Gigabit speed, net-snmp, and overflows issue? http://lists.ee.ethz.ch/mrtg/msg30587.html What I do instead of querying the servers directly, is query the switch ports they are plugged into. I use Cisco and HP switches and they have supported 64-bit SNMP counters for years. For servers attached to unmanaged switches, I poll their 32-bit counters every minute and accept that I can't graph very high traffic rates. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
linux compatibility on 64 bit FreeBSD 5.4 and 6.0
Gentlemen, I have spent several days reading all the documentation I can find but no reference to my problem. linux compatibility: # kldload linux# OR linux_enable=YES both work on my FreeBSD 5.4 32 bit athlon. On my opteron and athlon64 machines with FreeBSD 5.4 or 6.0 (both 64 bit versions) the linux_enable=YES in rc.conf has no effect, whilst # kldload linux gives kldload: can't load linuxkldload: can't load linux: File exists kldstat confirms that no linux.ko is present I would be grateful for any advice as I have a 64 bit linux binary that i need to run Thanking you, Philip Lavers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Questions on SMP and 64 bit
I'm buying a new computer, and am thinking of the new dual core AMD X2. I'm not sure I want to run 64 bit kernel yet, because of driver support and things like flash, and video, etc.. Will this processor still be as fast as a 32 bit if I use i386 kernel? Do I have to use a SMP kernel? Is there one available for i386? Should I just get a 32 bit single core, if that's the kernel I'm going to run? The main things I want that I don't think are easy to set up would be flash, mplayer and nVidia 3D driver. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
64 Bit Questions
I have a couple questions about the AMD64 Project. 1. They page mentions that there is multiprocessor support. Does this include the dual core processors? Will the OS dispatch processes and threads to each core? 2. While the OS will use the 64 bit mode, will the applications still run in the compatibly mode? Will the applications still only use 32 bits. 3. Also, will the OS take advantage of being 64 bit and load itself into memory higher than the 32 bit addressable mark so that my 32 bit applications can use the lower part? 4. If I enable 64 bit compilation on GCC prior to installing a port, will the port then be 64 bit enabled? 5. If I stall an IDE and write my own applications on a 64 bit machine, can a 32 bit machine still run them? Thank you in advance for your response and time. Anthony DeMatteo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64 Bit Questions
Le 18/01/2006 à 17:40:00-0500, Anthony Dematteo a écrit I have a couple questions about the AMD64 Project. 1. They page mentions that there is multiprocessor support. Does this include the dual core processors? Will the OS dispatch processes and threads to each core? I only can answer this question : I've try to install FreeBSD 6.0-Release AMD64 on dual opteron 275 (dual core). Everething work fine and we have 4 proc in the OS. Unfortunaly I do not have the chance to launch 4 big process to see the thread performance. For example I known on dual-core PowerPC Apple Macintosh time(4 x proccess)=time(1x process) [For the same process of course) Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. Heure local/Local time: Thu Jan 19 00:52:28 CET 2006 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64 Bit Questions
On 2006-01-18 17:40, Anthony Dematteo [EMAIL PROTECTED] wrote: I have a couple questions about the AMD64 Project. 1. They page mentions that there is multiprocessor support. Does this include the dual core processors? Will the OS dispatch processes and threads to each core? Not sure if I'm the right person to answer this in great technical detail, but I think the answer is 'yes' to both questions. 2. While the OS will use the 64 bit mode, will the applications still run in the compatibly mode? Not necessarily. By default the base system and any applications you compile yourself will be 64-bit too. The installed compiler and toolchain support building 32-bit binaries too, if you manually compile things yourself, but you don't have to if you don't feel like doing it. Will the applications still only use 32 bits. No, 64-bit applications can use the full 64-bit address range. 3. Also, will the OS take advantage of being 64 bit and load itself into memory higher than the 32 bit addressable mark so that my 32 bit applications can use the lower part? I'm not sure if I understand the question correctly, but why does the specific 'place' in the virtual 64-bit address space matter to an application? Some may argue that depending on such low level information is broken behavior and should be fixed in the application. 4. If I enable 64 bit compilation on GCC prior to installing a port, will the port then be 64 bit enabled? Ports do not support cross-compiling, as far as I know. If you build on a 64-bit machine, you get 64-bit binaries. If you build on a 32-bit machine, you get 32-bit binaries. 5. If I stall an IDE and write my own applications on a 64 bit machine, can a 32 bit machine still run them? No. The 64-bit binaries refer to registers, addresses and other parts of the 64-bit architecture that are not available in 32-bit hardware. The other way around works fine though. The 64-bit versions of FreeBSD include 32-bit libraries and runtime support too, so you can run 32-bit binaries seamlessly. In fact, this is exactly what enabled me to run a 32-bit binary of CMUCL, and experiment with LISP now that I've started learning about it: [EMAIL PROTECTED]:/home/keramida$ uname -v FreeBSD 7.0-CURRENT #0: Mon Jan 16 17:28:28 EET 2006 \ [EMAIL PROTECTED]:/home/build/obj/home/build/src/sys/FLAME [EMAIL PROTECTED]:/home/keramida$ which lisp /usr/local/bin/lisp [EMAIL PROTECTED]:/home/keramida$ file `!!` file `which lisp` /usr/local/bin/lisp: ELF 32-bit LSB executable, Intel 80386, \ version 1 (FreeBSD), for FreeBSD 6.0 (600100), \ dynamically linked (uses shared libs), not stripped [EMAIL PROTECTED]:/home/keramida$ lisp ; Loading #P/home/keramida/init.lisp. CMU Common Lisp 19c Release (19C), running on flame.pc With core: /usr/local/lib/cmucl/lib/lisp.core Dumped on: Wed, 2005-11-30 01:04:28+02:00 on boomerang See http://www.cons.org/cmucl/ for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error installing FreeBSd 5.3 AMD 64 bit-Highpoint 1820A
Steven Hartland wrote: Sounds like u have followed the install guide with the drivers. I couldn't get that to work ( without ACPI ) I had to install with ACPI but this was 5.4-RELEASE but using the 5.3 driver from highpoints site as there wasn't a 5.4 driver available. 1. Boot from cd 2. got to boot prompt, load the driver from floppy 3. unplug the floppy ( must to this as floppy under amd64 is broken ) 4. boot the kernel and install. Notes: 1. I was using a RAID 5 array 5 disks * 400Gb. 2. Create the array using 16 k stripe or the performance will be poor. - Original Message - From: Amandeep [EMAIL PROTECTED] I am instalaling FreeBSD 5.3 AMD 64 bit with 6- 200GB drives. Using Higpoint 1820A controller and doing RAID 10. I am using drivers for the card from Highpoint Web. The problem is when I make the partitions and the machine tries to format the partitions it says: unable to find device node for /dev/da0s1b under /dev! and then it comes out. Any ideas what is going on. Also tried making two slices no luck. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.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] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] Hi all, Ok, The 3ware and Highpoint works fine with 4GB of RAM. But I can hook another 4GB wiht 3ware and it works fine wiht 8GB but thats not the case for Highpoint. Highpoint dont work with installation of 4GB and then inserting 4GB. And it works fine wiht ACPi disables and floppy is present. Aman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Error installing FreeBSd 5.3 AMD 64 bit-Highpoint 1820A
Hi all, I am instalaling FreeBSD 5.3 AMD 64 bit with 6- 200GB drives. Using Higpoint 1820A controller and doing RAID 10. I am using drivers for the card from Highpoint Web. The problem is when I make the partitions and the machine tries to format the partitions it says: unable to find device node for /dev/da0s1b under /dev! and then it comes out. Any ideas what is going on. Also tried making two slices no luck. Thanks in advance. A ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error installing FreeBSd 5.3 AMD 64 bit-Highpoint 1820A
Hi guys, Anyone??? Amandeep wrote: Hi all, I am instalaling FreeBSD 5.3 AMD 64 bit with 6- 200GB drives. Using Higpoint 1820A controller and doing RAID 10. I am using drivers for the card from Highpoint Web. The problem is when I make the partitions and the machine tries to format the partitions it says: unable to find device node for /dev/da0s1b under /dev! and then it comes out. Any ideas what is going on. Also tried making two slices no luck. Thanks in advance. A ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers 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: Error installing FreeBSd 5.3 AMD 64 bit-Highpoint 1820A
Sounds like u have followed the install guide with the drivers. I couldn't get that to work ( without ACPI ) I had to install with ACPI but this was 5.4-RELEASE but using the 5.3 driver from highpoints site as there wasn't a 5.4 driver available. 1. Boot from cd 2. got to boot prompt, load the driver from floppy 3. unplug the floppy ( must to this as floppy under amd64 is broken ) 4. boot the kernel and install. Notes: 1. I was using a RAID 5 array 5 disks * 400Gb. 2. Create the array using 16 k stripe or the performance will be poor. - Original Message - From: Amandeep [EMAIL PROTECTED] I am instalaling FreeBSD 5.3 AMD 64 bit with 6- 200GB drives. Using Higpoint 1820A controller and doing RAID 10. I am using drivers for the card from Highpoint Web. The problem is when I make the partitions and the machine tries to format the partitions it says: unable to find device node for /dev/da0s1b under /dev! and then it comes out. Any ideas what is going on. Also tried making two slices no luck. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.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: Error installing FreeBSd 5.3 AMD 64 bit-Highpoint 1820A
Hello, I think it's a question for the highpoint support. It's their product and their driver. Here are some instant hints: - read the PDF carefully and follow the instructions strictly - use the BIOS in the tarball; nothing else!! Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
64 bit FreeBSD for number crunching
Hi I am considering building a dual Opteron number-cruncher using FreeBSD 5.3 instead of Linux, and I have three questions which I haven't been able to find answers to on the site. 1) Will I be able to link reliably against Linux libraries when the source isn't available e.g. Some of those ones here... http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_8796_11869% 5E11880,00.html 2) Is there any performance penalty to (1) if I can. 3) Is the 64 bit AMD port of FreeBSD stable? Many thanks for your time Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/_/ _/_/_/ Hopkins Research Ltd _/_/ _/_/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com _/_/ _/ _/ _/_/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64 bit FreeBSD for number crunching
On Mon, Nov 29, 2004 at 12:44:12PM +, Michael Hopkins, Hopkins Research wrote: 3) Is the 64 bit AMD port of FreeBSD stable? Yes, remarkably so. Kris pgpZj8CScgJmj.pgp Description: PGP signature
Intel Xeon 64 Bit Hardware Question
Will FreeBSD 5.3 Run on this Hardware Configuration CPU Network Cards I would also like to Hardware Raid 5 with the Intel Raid Card Would this be seamless to FreeBSD? 5U Intel SC5300 Rack Mount Black Dual Intel CPU Xeon 3GHz CPU, 64-bit, 1mb cache Intel Gigabit Ethernet x 2 2 GB ECC memory 4 144GB (raid 5) and 1 144GB SCSI Hot Spare so a total of 5 drives Intel Server MB Built in Video Intel SCSI Raid 5 controller CD-ROM / Floppy PS2 Mouse / Keyboard -- Sean Murphy Network Technician California Institute of the Arts [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
advice 64 bit architecture
hi everyone. i just want to know if anyone has had any major issues running freebsd on 64bit architecture. i am wanting to buy a asus a8v deluxe - 939 via k8t800 pro motherboard with a amd athlon64 939 3500+ chip. If anyone has any experience, id love to listen to your do's and don'ts. thanks!!! ams Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice 64 bit architecture
eodyna wrote: hi everyone. i just want to know if anyone has had any major issues running freebsd on 64bit architecture. i am wanting to buy a asus a8v deluxe - 939 via k8t800 pro motherboard with a amd athlon64 939 3500+ chip. If anyone has any experience, id love to listen to your do's and don'ts. thanks!!! ams Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I tried to put 5.3beta7 on my brothers and had 2 main problems. The wireless network card was not supported. When I tried to use ndiscvt I just got an error saying if_ndis.ko could not be loaded. It is the linksys wmp54gv4 pci card. The issue that would get you is when I compiled x, startx failed about not being able to init fonts. I am sure that could have been easily fixed, but for my brother the killer was wireless. Other than that it was smooth, be sure to read /ports/UPDATING about lib changes. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64-bit arithmetic in scripts?
Dan Nelson has kindly explained everything:
In the last episode (Oct 01), Andrew said:
Thanks! I haven't thought about using expr.
How come that my expr(1) manpage has nothing to say about -e option?
In fact my expr(1) does not accept it. I have FreeBSD 4.10. I've
just
looked into a current manpage from www.freebsd.org, and it says
something about 4.x compatibility.
What is the best way to go if I need to write scripts now, but I'm
planning to switch to 5.x later? Can I upgrade expr(1) now? If not,
what should I do?
In 4.x, expr does 64-bit math by default. Apparently POSIX requires
that expr use whatever the systems' signed long size is, so the
default was changed for 5.x, and -e was added to get the old
behaviour.
If you want your script to work on both, you'll have to do a feature
test. I started out just testing expr and expr -e, but it sort of
grew... The following script will check the shell's math, two ways of
calling expr, and finally fall back on calling bc. As long as you
just
use the basic math operators, quote your *'s, and put spaces between
everything, all the methods should be compatible, and your script will
work on any bourne-compatible shell :)
#! /bin/sh
if [ x$(( 65536 * 65536 )) = x4294967296 ] ; then
shellarith() { echo $(( $@ )) ; }
MATH=shellarith
else
if [ x`expr 65536 * 65536` = x4294967296 ] ; then
MATH=expr
else
if [ x`expr -e 65536 * 65536 2/dev/null` = x4294967296 ] ;
then
MATH=expr -e
else
if [ x`echo 65536 * 65536 | bc` = x4294967296 ] ; then
bcfunc() { echo $@ | bc ; }
MATH=bcfunc
else
echo Can't do 64-bit math noway nohow
fi
fi
fi
fi
echo Using $MATH
bigval=`$MATH 65536 * 65536`
echo $bigval
Thank you very much! I think, I'll just assign MATH=expr and change it
to something else when I need it.
Best regards,
Andrew P.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
64-bit arithmetic in scripts?
Hi, I'm counting traffic with ipfw and shell scripts. Is there a way to use more than 32-bit numbers in shell arithmetic? Regards, Andrew P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64-bit arithmetic in scripts?
In the last episode (Sep 30), Andrew said: I'm counting traffic with ipfw and shell scripts. Is there a way to use more than 32-bit numbers in shell arithmetic? POSIX only requires signed long support in the shell, but FreeBSD's expr command has a -e flag that will let it do 64-bit math: $ echo $(( 65536*65536 )) 0 $ echo $(expr 65536 * 65536) 0 $ echo $(expr -e 65536 * 65536) 4294967296 bash, ksh93 (but not pdksh), and zsh's shell arithmetic are all 64-bit, also. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64-bit arithmetic in scripts?
Dan Nelson wrote: In the last episode (Sep 30), Andrew said: I'm counting traffic with ipfw and shell scripts. Is there a way to use more than 32-bit numbers in shell arithmetic? POSIX only requires signed long support in the shell, but FreeBSD's expr command has a -e flag that will let it do 64-bit math: $ echo $(( 65536*65536 )) 0 $ echo $(expr 65536 * 65536) 0 $ echo $(expr -e 65536 * 65536) 4294967296 bash, ksh93 (but not pdksh), and zsh's shell arithmetic are all 64-bit, also. Thanks! I haven't thought about using expr. How come that my expr(1) manpage has nothing to say about -e option? In fact my expr(1) does not accept it. I have FreeBSD 4.10. I've just looked into a current manpage from www.freebsd.org, and it says something about 4.x compatibility. What is the best way to go if I need to write scripts now, but I'm planning to switch to 5.x later? Can I upgrade expr(1) now? If not, what should I do? Thanks again and regards, Andrew P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 64-bit arithmetic in scripts?
In the last episode (Oct 01), Andrew said:
Thanks! I haven't thought about using expr.
How come that my expr(1) manpage has nothing to say about -e option?
In fact my expr(1) does not accept it. I have FreeBSD 4.10. I've just
looked into a current manpage from www.freebsd.org, and it says
something about 4.x compatibility.
What is the best way to go if I need to write scripts now, but I'm
planning to switch to 5.x later? Can I upgrade expr(1) now? If not,
what should I do?
In 4.x, expr does 64-bit math by default. Apparently POSIX requires
that expr use whatever the systems' signed long size is, so the
default was changed for 5.x, and -e was added to get the old behaviour.
If you want your script to work on both, you'll have to do a feature
test. I started out just testing expr and expr -e, but it sort of
grew... The following script will check the shell's math, two ways of
calling expr, and finally fall back on calling bc. As long as you just
use the basic math operators, quote your *'s, and put spaces between
everything, all the methods should be compatible, and your script will
work on any bourne-compatible shell :)
#! /bin/sh
if [ x$(( 65536 * 65536 )) = x4294967296 ] ; then
shellarith() { echo $(( $@ )) ; }
MATH=shellarith
else
if [ x`expr 65536 * 65536` = x4294967296 ] ; then
MATH=expr
else
if [ x`expr -e 65536 * 65536 2/dev/null` = x4294967296 ] ; then
MATH=expr -e
else
if [ x`echo 65536 * 65536 | bc` = x4294967296 ] ; then
bcfunc() { echo $@ | bc ; }
MATH=bcfunc
else
echo Can't do 64-bit math noway nohow
fi
fi
fi
fi
echo Using $MATH
bigval=`$MATH 65536 * 65536`
echo $bigval
--
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: support 64 bit CPU
On Sun, 1 Aug 2004, [iso-8859-1] adrian kok wrote: Hi all Can freebsd run on 64 bit CPU? Thank you very much Which 64bit CPU? Rus -- e: [EMAIL PROTECTED] : t: 1-888-327-6330 http://www.jvds.com - Root on your own box http://www.vpscolo.com - Your next hosting company http://jvdsblog.jvds.com - The Life of a Web Host Owner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: support 64 bit CPU
On Sun, Aug 01, 2004 at 07:32:01PM +0800, adrian kok wrote: Can freebsd run on 64 bit CPU? Yes. Take your pick of AMD64, UltraSparc, Alpha, IA64 and then there's a bunch of other architectures in progress, including MIPS and PPC. But I'm perplexed as to why you need to ask here when this information is displayed quite prominently right on the front page of the FreeBSD website. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpNxZlTqOfRJ.pgp Description: PGP signature
Re: [OT] 64-bit PCI in 32-bit slots??? crazy??
Bill Moran wrote: I'm inheriting some hardware. These boards have 64-bit PCI SATA cards jammed in 32-bit PCI slots. Oddly enough, the boxen boot and start Linux (which will be replaced with FreeBSD when I'm done) I guess my question is hardware-related. I mean, I can't believe this worked! Has anyone else seen/done this? Is this as crazy as it seems to me? Please check out this site: http://www.pcisig.com/specifications/pcix_20/ As you will see, PCI-X is up to 533MHz bus speeds now and the standard is still backwards compatible with PCI. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[OT] 64-bit PCI in 32-bit slots??? crazy??
I'm inheriting some hardware. These boards have 64-bit PCI SATA cards jammed in 32-bit PCI slots. Oddly enough, the boxen boot and start Linux (which will be replaced with FreeBSD when I'm done) I guess my question is hardware-related. I mean, I can't believe this worked! Has anyone else seen/done this? Is this as crazy as it seems to me? -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] 64-bit PCI in 32-bit slots??? crazy??
In the last episode (Jul 30), Bill Moran said: I'm inheriting some hardware. These boards have 64-bit PCI SATA cards jammed in 32-bit PCI slots. Oddly enough, the boxen boot and start Linux (which will be replaced with FreeBSD when I'm done) I guess my question is hardware-related. I mean, I can't believe this worked! Has anyone else seen/done this? Is this as crazy as it seems to me? Nope; you can put 64-bit cards in 32-bit slots as long as the card has the notch in the right place so it fits over one end of the slot. You can also put 32-bit cards in 64-bit slots. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] 64-bit PCI in 32-bit slots??? crazy??
On Fri, Jul 30, 2004 at 04:32:30PM -0400, Bill Moran wrote: I'm inheriting some hardware. These boards have 64-bit PCI SATA cards jammed in 32-bit PCI slots. Oddly enough, the boxen boot and start Linux (which will be replaced with FreeBSD when I'm done) I guess my question is hardware-related. I mean, I can't believe this worked! Has anyone else seen/done this? Is this as crazy as it seems to me? -- Bill Moran I have a friend that is using a 64 bit SCSI card (29160 adaptec if memory serves) and it's backwards compatable with 32 bit slots Josh Paetzel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
