Date: Tue, 18 Apr 2006 12:51:11 -0400 From: "Jonathan Noack" <noackjr@alumni.rice.edu> To: "Evren Yurtesen" <yurtesen@ispro.net.tr> Cc: James Long <stable@museum.rain.com>, freebsd-stable@freebsd.org Subject: Re: CPUTYPE=athlon-xp and loader Message-ID: <444518FF.10300@alumni.rice.edu> In-Reply-To: <44448CEF.6070701@ispro.net.tr> References: <20060417120045.B89BD16A4E1@hub.freebsd.org> <20060417222323.GA26669@ns.museum.rain.com> <44448CEF.6070701@ispro.net.tr>
next in thread | previous in thread | raw e-mail | index | archive | help
Evren Yurtesen wrote: > James Long wrote: >>> Date: Sun, 16 Apr 2006 17:43:58 +0300 >>> From: Evren Yurtesen <yurtesen@ispro.net.tr> >>> Subject: CPUTYPE=athlon-xp and loader >>> To: freebsd-stable@freebsd.org >>> Message-ID: <4442582E.9030507@ispro.net.tr> >>> >>> Hello, >>> >>> I have a problem which I have found out from mailing lists that some >>> other people had. However there is no clear solution. >>> >>> The CPUTYPE=athlon-xp in make.conf breaks /boot/loader that system >>> instant reboots. I am using 6-stable and from what I can see the >>> problem goes back till about 5.3... Sometime between Oct 12-15, 2005 >>> >>> http://archive.netbsd.se/?ml=freebsd-current&a=2004-10&m=435817 >>> >>> I wonder if this will ever be fixed or I shouldnt use >>> CPUTYPE=athlon-xp anymore on FreeBSD because of this? >>> >>> Thanks, >>> Evren >> >> I don't propose this as a solution, but as far as I know, the best >> practice is: >> >> CPUTYPE?=athlon-xp >> >> Note the question mark. >> >> I don't know that this will solve your problem, just pointing out >> the correct syntax, for whatever CPUTYPE you decide to use. > > Doesnt the ? mean that it should be set if it is not set yet? I can give > it a try to this, next time I build world however I dont think that it > will compile loader without cputype athlon-xp set so... Huh? CPUTYPE is optional. Everything should compile and work without it. > I just thought that loader doesnt need to be so optimized anyhow. It is > more important that it loads at boot and there are people on this list > who has problems with the optimizations and I found some more on google. > So the best is to either fix the code in loader or do not optimize it. Yeah, like me. I was the one who originally reported this problem. But over a year ago there was an attempt to fix the code by not optimizing it. This resolved the problem for me. -Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444518FF.10300>