Re: Effects of CPUTYPE
[image removed] Re: Effects of CPUTYPE Wojciech Puchar to: freebsd-questions, parish 2008-06-11 20:31 Sent by: [EMAIL PROTECTED] In my personal opinion, the small gain you get is more than overwhelmed by the big pain you get from setting CPUTYPE. I'm setting CPUTYPE on all of my machines for many years, without the slightest problems. No pain at all. They're all kinds of different processors, c3-2 (VIA), athlon64, and so on. In some cases the difference is very noticable. exactly like me. i set it everywhere, no problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I had the opposite problem: I could not build the world/kernel until I set CPUTYPE to c3-2 (or c3). It was a brand new VIA EDEN-EX 1.5GHz with no other things installed but a copy of the 7.0-RELEASE-p1 source. (I did not have compile problems when I installed the 6.2 on a similar machine) I set CPUTYPE in /etc/make.conf. I think it is only used by the gcc compiler so it will probably only make a difference if you compile ports or from source. Compiling the kernel/world with CPUTYPE=c3-2 I think I see an improved boot time. I do not know of other gains as the server idles most of the time so I do not really care as long as it is stable. I never did try to time the kernel and world builds. :-) Torben Medmindre andet er angivet ovenfor: / Unless Otherwise Stated Above: IBM Danmark A/S Nymøllevej 91 2800 Kongens Lyngby, Danmark CVR nr.: 65305216 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Effects of CPUTYPE
Jonathan Chen wrote: Mark Ovens wrote: Trying to identify why I should be having all these problems I've been looking for anything that may be specific to my machine. One thing I've come up with is the fact that I have CPUTYPE?=athlon-mp in /etc/make.conf on both 6.3 and 7.0. In my personal opinion, the small gain you get is more than overwhelmed by the big pain you get from setting CPUTYPE. I'm setting CPUTYPE on all of my machines for many years, without the slightest problems. No pain at all. They're all kinds of different processors, c3-2 (VIA), athlon64, and so on. In some cases the difference is very noticable. Having said that, it's certainly worth trying whether your problems are gone when you compile without that setting. Do you have any other unusual settings, such as non-standard CFLAGS or anything? BTW, I once was bitten by a similar problem, when building software failed in strange ways, it turned out I had a bad variable in my environment that was picked up by some build scripts. Maybe it's worth a try to run your ports builds with a clean environment (env -), or try to install binary packages instead of building ports yourself, in order to narrow down where the problem is. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Python tricks is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure wink. -- Tim Peters ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Effects of CPUTYPE
In my personal opinion, the small gain you get is more than overwhelmed by the big pain you get from setting CPUTYPE. I'm setting CPUTYPE on all of my machines for many years, without the slightest problems. No pain at all. They're all kinds of different processors, c3-2 (VIA), athlon64, and so on. In some cases the difference is very noticable. exactly like me. i set it everywhere, no problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Effects of CPUTYPE
On Thu, June 5, 2008 00:24, Jonathan Chen wrote: In my personal opinion, the small gain you get is more than overwhelmed by the big pain you get from setting CPUTYPE. Thanks Jonathan. I think I'll reinstall my 7.0 system from scratch and install the apps from packages rather than build from ports and see if that solves the problems. The thing is that the main serious use for this box is managing my digital photos - over 12GB of them - and it is getting increasingly difficult with the apps I choose to use becoming unreliable. I've really got to the point where I'm considering switching to Linux as I've tried Mandriva and all the apps I use that I'm having problems with on FreeBSD work just fine under Linux. I don't want to switch - I've been using FreeBSD for ~13 years (since 2.0.5) but since I ditched Windows nearly 2 years ago I need reliability. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Effects of CPUTYPE
For months now I've been having ever increasing problems with software (ports) stopping working - or not working properly; xorg, digikam, jalbum, etc. The problems are the same on 6.3-STABLE and a brand new, clean install of 7.0. Searching mailing lists and Google makes me think that a lot of these problems are specific to my system. Trying to identify why I should be having all these problems I've been looking for anything that may be specific to my machine. One thing I've come up with is the fact that I have CPUTYPE?=athlon-mp in /etc/make.conf on both 6.3 and 7.0. I understand that this optimizes compilation for that CPU but can this potentially cause problems? Is this a possible cause of strange problems? All my ports are built from source rather than from packages so are built with this option. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Effects of CPUTYPE
On Wed, Jun 04, 2008 at 11:14:14PM +0100, Mark Ovens wrote: Trying to identify why I should be having all these problems I've been looking for anything that may be specific to my machine. One thing I've come up with is the fact that I have CPUTYPE?=athlon-mp in /etc/make.conf on both 6.3 and 7.0. In my personal opinion, the small gain you get is more than overwhelmed by the big pain you get from setting CPUTYPE. -- Jonathan Chen [EMAIL PROTECTED] -- Opportunity does not knock, it presents itself when you beat down the door - W.E. Channing ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Effects of CPUTYPE
On Wed, 04 Jun 2008 23:14:14 +0100 Mark Ovens [EMAIL PROTECTED] wrote: For months now I've been having ever increasing problems with software (ports) stopping working - or not working properly; xorg, digikam, jalbum, etc. ... I understand that this optimizes compilation for that CPU but can this potentially cause problems? Is this a possible cause of strange problems? All my ports are built from source rather than from packages so are built with this option. I think it's unlikely, but it's easy enough to eliminate. From the ports you mention, xorg does seem to be holding a smoking gun. If you have any unnecessary features enabled in xorg.conf, I'd turn them off. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]