Re: Kernel Compile Fail
On 12/25/12 10:09, Fabian Wenk wrote: Hello Joseph On 25.12.2012 15:32, Joseph A. Nagy, Jr wrote: snip 'make buildkernel kernconf=ALEX-LAPTOP' 'make installkernel kernconf=ALEX-LAPTOP' I am not sure if 'kernconf=' will work too or if it needs to be in uppercase letters. Alternatively you could set the following line in /etc/make.conf: KERNCONF=ALEX-LAPTOP I did not think of kernconf having to be in upper-case letters, though that is how the handbook shows it (it never states that part has to be caps like the kernel name). And then in /usr/src/ you only need to use 'make buildkernel' and 'make installkernel'. That would be nice, I'll give it a go. alex@alex-laptop# cd /usr/src/sys/amd64/conf alex@alex-laptop# ls ALEX-LAPTOP DEFAULTSGENERIC GENERIC.hints Makefile NOTES XENHVM I'm not quite sure what to expect now. This looks correct. Did you also adjust the 'ident' line in your ALEX-LAPTOP file from GENERIC to ALEX-LAPTOP? I'm certain I did, I can double-check though. I am not sure if the - in the kernel name will work. I do remember having problems building a kernel with a number in the name. But this was more then 10 years ago, but I still avoid it and do use only letters. So it is probably better to just use ALEXLAPTOP instead of ALEX-LAPTOP. That name worked when I was running this laptop on i386 but I could shorten it to without the hyphen. I was just trying to keep it like my hostname (alex-laptop.localhost). -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: Kernel Compile Fail
On 12/25/12 10:09, Fabian Wenk wrote: snip I am not sure if 'kernconf=' will work too or if it needs to be in uppercase letters. Alternatively you could set the following line in /etc/make.conf: KERNCONF=ALEX-LAPTOP Indeed, this has to be in caps (just thought I'd follow up with that). Again, thanks for all the help! -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: Kernel Compile Fail
On 12/16/12 17:43, Joseph A. Nagy, Jr wrote: I started my kernel compile with my custom settings[0] but it's failing at one point[1] and while I think I know why, I'd like a second opinion. [0]: http://codepad.org/EZTCVMZC [1]: http://codepad.org/58GFHGnE First, I'd like to thank everyone who helped me get my kernel building and answered all my questions. I have really appreciated the help. I compiled my custom kernel (or so I thought), but 'uname -a' shows it compiled with a generic kernel? FreeBSD alex-laptop 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Mon Dec 24 20:06:49 CST 2012 root@alex-laptop:/usr/obj/usr/src/sys/GENERIC amd64 Whereas in the past, it showed my custom kernel config in the above path. I was running i386 before, does that make a difference? Or did I miss a step somewhere? when building and installing, I issued: 'make buildkernel kernconf=ALEX-LAPTOP' 'make installkernel kernconf=ALEX-LAPTOP' Based on the instructions found in the handbook. alex@alex-laptop# cd /usr/src/sys/amd64/conf alex@alex-laptop# ls ALEX-LAPTOP DEFAULTSGENERIC GENERIC.hints Makefile NOTES XENHVM I'm not quite sure what to expect now. -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: CPU upgrade vs CPUTYPE
Cross-posting reply to amd64@ for relevance and to get answers from those smart gents. On 12/18/12 23:17, Toomas Aas wrote: Hello! We have a small server running FreeBSD 8.3 amd64 with Intel Pentium D 945 CPU. As the motherboard/CPU combo is getting rather old, we are considering an upgrade to new motherboard with Xeon E3-1230 CPU. We currently have these CPU settings in /etc/make.conf: CPUTYPE?=nocona in kernel configuration: cpu HAMMER this is the only possible setting in the kernel conf for amd64 as I was told. This was why (and might answer the make.conf question as well: from b.f.: Leave it alone. The choices for the cpu directive in the kernel config file, as described in config(5) and listed in src/sys/conf/options.arch (the only choice for amd64 is HAMMER), have nothing to do with the choices available for the CPUTYPE variable (which you may want to change to suit your hardware -- these are the architecture-dependent options available for the -march and -mtune directives of your compiler that are also recognized by bsd.cpu.mk), or with the cpu descriptions printed during boot. As for the rest of your questions, I leave them in the hands of those more knowledgeable than I. HTH Almost all the software is built from ports, few bits compiled directly from source. Base system is maintained by buildworld. Can we expect the software compiled with above CPU settings to run without problems on the Xeon E3? We had a chance recently to try a temporary motherboard/CPU swap in this server, replacing the CPU with Core i3-2xxx and there were some 'signal 11' errors, but I'm not sure whether this was due to incompatible CPUTYPE or something else. Thanks in advance, -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Kernel Compile Fail
I started my kernel compile with my custom settings[0] but it's failing at one point[1] and while I think I know why, I'd like a second opinion. [0]: http://codepad.org/EZTCVMZC [1]: http://codepad.org/58GFHGnE -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: Kernel Compile Fail
On 12/16/12 17:52, chr...@ultimatedns.net wrote: I started my kernel compile with my custom settings[0] but it's failing at one point[1] and while I think I know why, I'd like a second opinion. [0]: http://codepad.org/EZTCVMZC [1]: http://codepad.org/58GFHGnE Greetings, It would probably be more helpful to others to assist, if you at least mentioned your target install -- laptop, ACTUAL CPU, etc. I notice some of the options you include, are typically targeted to laptops, which leads me to believe this is a laptop. But no way to be sure. Best wishes. --Chris Sorry, didn't think that mattered. Toshiba Satellite L455D AMD Sempron(tm) SI-42 (2099.25-MHz K8-class CPU) If you need my pciconf -v, you can find it here: http://pastebin.com/C1Rundaq -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: cpu setting in kernel options file
On 12/15/12 00:21, b.f. wrote: The really important bit being the first line. Could I put K8 and gcc/clang be okay with it? Or should I leave the cpu line in my kernel conf file alone? Leave it alone. The choices for the cpu directive in the kernel config file, as described in config(5) and listed in src/sys/conf/options.arch (the only choice for amd64 is HAMMER), have nothing to do with the choices available for the CPUTYPE variable (which you may want to change to suit your hardware -- these are the architecture-dependent options available for the -march and -mtune directives of your compiler that are also recognized by bsd.cpu.mk), or with the cpu descriptions printed during boot. b. Thanks! -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
cpu setting in kernel options file
Hi All,
I know this question has been asked before[0] so I just want
clarification. It was stated back then that HAMMER is the only cpu type
for amd64, but later on someone points to /usr/share/mk/bsd.cpu.mk where
I found:
. elif ${MACHINE_CPUARCH} == amd64
. if ${CPUTYPE} == prescott
and, closer to my own specific processor:
. elif ${CPUTYPE} == opteron || ${CPUTYPE} == athlon64 || \
${CPUTYPE} == k8
from my /var/run/dmesg.boot I find:
CPU: AMD Sempron(tm) SI-42 (2099.25-MHz K8-class CPU)
Origin = AuthenticAMD Id = 0x200f31 Family = 11 Model = 3
Stepping = 1
Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
Features2=0x2001SSE3,CX16
AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!
AMD Features2=0x1319LAHF,ExtAPIC,CR8,Prefetch,OSVW,SKINIT
The really important bit being the first line. Could I put K8 and
gcc/clang be okay with it? Or should I leave the cpu line in my kernel
conf file alone?
[0]:
http://lists.freebsd.org/pipermail/freebsd-amd64/2009-February/011914.html
--
Yours in Christ,
Joseph A Nagy Jr
Whoever loves instruction loves knowledge, But he who hates correction
is stupid. -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original content CopyFree (F) under the OWL http://owl.apotheon.org
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
