Date: Tue, 29 Apr 2003 12:48:29 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: CARTER Anthony <a.carter@cordis.lu> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: URGENT HELP REQUIRED Message-ID: <XFMail.20030429124829.jhb@FreeBSD.org> In-Reply-To: <A2DF56E8BC9B964884DD1A7C9C812C0F0130142D@mail.intrasoft.lu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29-Apr-2003 CARTER Anthony wrote: > I DID compile with make.conf containing CPU_TYPE=p4... > > maybe an avenue...how do I fix without destroying everything? I AM on a PIII > box (thought it was PIV). :( > > Thanks, a little wiser... Might I suggest that you run -stable for a while until you are a bit more familiar with FreeBSD? The deprecation of DRM_LINUX was clearly pointed out on the cvs-all@ when it happend, and people tracking current really should be reading cvs-all@. Also, being able to identify what CPU your system has from the dmesg is a rather basic task: > dmesg | grep -A 2 ^CPU CPU: Intel Pentium III (696.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,MMX,FXSR,SSE> Finally, specifically with regards to CPUTYPE=p4, gcc is known to have some problems with -march=p4 even on P4 machines as has been discussed on current@ several times in the past few months. Following the threads on current@ is a rather good idea when tracking -current much like tracking cvs-all@. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20030429124829.jhb>