Re: Duo core enable/support help.
Hello Lane! I'm a frequent reader to /usr/src/UPDATING But whenever I need to update or upgrade only, since years! Also I knew very well whats KERNCONF! i just wanted to know and make sure of the duo core options, and i searched the NOTES file, didnot find anything about it. Thank you for your short problematic answer :) by the way, After recompiling the kernel and From my dmesg ACPI APIC Table: INTEL D11020M FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 SMP: AP CPU #1 Launched! - But I still have few dmesg errors, these are the lines, acpi0: INTEL D11020M on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21 acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: ACPI CPU Throttling on cpu0 cpu1: ACPI CPU on acpi0 acpi_perf1: ACPI CPU Frequency Control on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_perf1: ACPI CPU Frequency Control on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_throttle1: ACPI CPU Throttling on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_button0: Power Button on acpi0 and usb2: waiting for BIOS to give up control usb2: timed out waiting for BIOS usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: ATI SB400 USB 2.0 controller on ehci0 usb2: USB revision 2.0 Any easy problematic ideas? :) Thank you ---Marwan First read /usr/src/UPDATING. Really. No, really. I mean read it :) And, since no one expects you to really, really read it, I'll give you some shortcuts. First, look for the word KERNCONF in /usr/src/UPDATING Read all of the language around every occurence of that word (KERNCONF). Then, when you are ready, do this: make buildkernel KERNCONF=SMP make installkernel KERNCONF=SMP Then reboot. Note here that I'm giving you the shortest possible route, which may be problematic for you. You really must become familiar with /usr/src/UPDATING. Anyway, after the reboot, you should type: cat /var/log/messages | grep -i launch if you see the terms CPU1 Launched! then you've got yourself an SMP kernel. Good Luck! lane _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Duo core enable/support help.
On Tuesday 05 December 2006 06:14, you wrote: Hello Lane! I'm a frequent reader to /usr/src/UPDATING But whenever I need to update or upgrade only, since years! Also I knew very well whats KERNCONF! i just wanted to know and make sure of the duo core options, and i searched the NOTES file, didnot find anything about it. Thank you for your short problematic answer :) by the way, After recompiling the kernel and From my dmesg ACPI APIC Table: INTEL D11020M FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 SMP: AP CPU #1 Launched! - But I still have few dmesg errors, these are the lines, acpi0: INTEL D11020M on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21 acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: ACPI CPU Throttling on cpu0 cpu1: ACPI CPU on acpi0 acpi_perf1: ACPI CPU Frequency Control on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_perf1: ACPI CPU Frequency Control on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_throttle1: ACPI CPU Throttling on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_button0: Power Button on acpi0 and usb2: waiting for BIOS to give up control usb2: timed out waiting for BIOS usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: ATI SB400 USB 2.0 controller on ehci0 usb2: USB revision 2.0 Any easy problematic ideas? :) Thank you ---Marwan First read /usr/src/UPDATING. Really. No, really. I mean read it :) And, since no one expects you to really, really read it, I'll give you some shortcuts. First, look for the word KERNCONF in /usr/src/UPDATING Read all of the language around every occurence of that word (KERNCONF). Then, when you are ready, do this: make buildkernel KERNCONF=SMP make installkernel KERNCONF=SMP Then reboot. Note here that I'm giving you the shortest possible route, which may be problematic for you. You really must become familiar with /usr/src/UPDATING. Anyway, after the reboot, you should type: cat /var/log/messages | grep -i launch if you see the terms CPU1 Launched! then you've got yourself an SMP kernel. Good Luck! lane _ Marwan, Please don't top post because follow to hard it's I'm guessing here: The acpi messages such as acpi_bus_number: can't get _ADR acpi_perf0: failed in PERF_STATUS attach may be appearing because these features are not yet fully supported. Check on man acpi to learn how to selectively disable acpi functions. The read is rather short, and you may ultimately decide that it's better left alone. As long as these errors don't repeat then it is likely the selected features are simply disabled by the kernel (or not loaded, or however acpi works :) Regarding the acpi errors AND the usb error: Do you detect any diminished performance? Are you unable to mount drives and/or other devices? lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Duo core enable/support help.
On 2006-12-05 12:14, Marwan Sultan [EMAIL PROTECTED] wrote: Hello Lane! I'm a frequent reader to /usr/src/UPDATING But whenever I need to update or upgrade only, since years! Also I knew very well whats KERNCONF! i just wanted to know and make sure of the duo core options, and i searched the NOTES file, didnot find anything about it. If this is what you are asking, then yes, an SMP-capable kernel will discover the two cores of your Intel Core Duo as separate CPUs. On my Toshiba Satellite laptop, this shows up in /var/run/dmesg.boot: % Copyright (c) 1992-2006 The FreeBSD Project. % Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 % The Regents of the University of California. All rights reserved. % FreeBSD is a registered trademark of The FreeBSD Foundation. % FreeBSD 7.0-CURRENT #0: Mon Dec 4 15:30:38 EET 2006 % [EMAIL PROTECTED]:/home/build/obj/home/build/src/sys/KOBE % WARNING: WITNESS option enabled, expect reduced performance. % Timecounter i8254 frequency 1193182 Hz quality 0 % CPU: Genuine Intel(R) CPU T2400 @ 1.83GHz (1828.77-MHz 686-class CPU) % Origin = GenuineIntel Id = 0x6e8 Stepping = 8 % Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE % Features2=0xc1a9SSE3,MON,VMX,EST,TM2,XTPR,b15 % Cores per package: 2 % real memory = 528089088 (503 MB) % avail memory = 507101184 (483 MB) % ACPI APIC Table: TOSHIB 750 % FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs % cpu0 (BSP): APIC ID: 0 % cpu1 (AP): APIC ID: 1 % [...] Then, each core works as a separate CPU, as expected :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Duo core enable/support help.
Hello Gurus, I just had Intel 102, duo core, fresh freebsd 6.1r installed. but i have been told that i have to enable duo core thing in kernel what should i have there? only options SMP ? what about the /usr/src/sys/i386/conf/SMP file? shall i copy the options to MYKERNEL ? in shortwords what should i do to enable duo core and fix my bugs, here is the dmesg output, with lot of thanks. 192# dmesg Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE-p10 #0: Tue Dec 5 02:55:13 AST 2006 admin@:/usr/obj/usr/src/sys/MYKERNEL ACPI APIC Table: INTEL D11020M Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) D CPU 3.40GHz (3400.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf64 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe49dSSE3,RSVD2,MON,DS_CPL,EST,CNTX-ID,CX16,b14,b15 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 937070592 (893 MB) avail memory = 907821056 (865 MB) ioapic0: Changing APIC ID to 4 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: INTEL D11020M on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21 acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff iomem 0xfff0-0x on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 5.0 (no driver attached) atapci0: ATI IXP400 SATA150 controller port 0x3068-0x306f,0x3084-0x3087,0x3060-0x3067,0x3080-0x3083,0x3030-0x303f mem 0x60207600-0x602077ff irq 23 at device 17.0 on pci0 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 atapci1: ATI IXP400 SATA150 controller port 0x3058-0x305f,0x307c-0x307f,0x3050-0x3057,0x3078-0x307b,0x3020-0x302f mem 0x60207400-0x602075ff irq 22 at device 18.0 on pci0 ata4: ATA channel 0 on atapci1 ata5: ATA channel 1 on atapci1 ohci0: ATI SB400 USB Controller irq 19 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: ATI SB400 USB Controller on ohci0 usb0: USB revision 1.0 uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: ATI SB400 USB Controller irq 19 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: ATI SB400 USB Controller on ohci1 usb1: USB revision 1.0 uhub1: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: ATI SB400 USB 2.0 controller irq 19 at device 19.2 on pci0 ehci0: [GIANT-LOCKED] usb2: waiting for BIOS to give up control usb2: timed out waiting for BIOS usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: ATI SB400 USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered pci0: serial bus, SMBus at device 20.0 (no driver attached) atapci2: ATI IXP400 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 20.1 on pci0 ata0: ATA channel 0 on atapci2 ata1: ATA channel 1 on atapci2 pci0: multimedia at device 20.2 (no driver attached) isab0: PCI-ISA bridge at device 20.3 on pci0 isa0: ISA bus on isab0 pcib2: ACPI PCI-PCI bridge at device 20.4 on pci0 pci2: ACPI PCI bus on pcib2 rl0: RealTek 8139 10/100BaseTX port 0x1100-0x11ff mem 0x6100-0x61ff irq 21 at device 2.0 on pci2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:16:76:6e:fc:08 vr0: VIA VT6105 Rhine III 10/100BaseTX port 0x1000-0x10ff mem 0x6000-0x60ff irq 16 at device 3.0 on pci2 miibus1: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:15:e9:82:36:b6 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED]
Re: Duo core enable/support help.
On Monday 04 December 2006 18:40, Marwan Sultan wrote: Hello Gurus, I just had Intel 102, duo core, fresh freebsd 6.1r installed. but i have been told that i have to enable duo core thing in kernel what should i have there? only options SMP ? what about the /usr/src/sys/i386/conf/SMP file? shall i copy the options to MYKERNEL ? in shortwords what should i do to enable duo core and fix my bugs, here is the dmesg output, with lot of thanks. Marwan, First read /usr/src/UPDATING. Really. No, really. I mean read it :) And, since no one expects you to really, really read it, I'll give you some shortcuts. First, look for the word KERNCONF in /usr/src/UPDATING Read all of the language around every occurence of that word (KERNCONF). Then, when you are ready, do this: make buildkernel KERNCONF=SMP make installkernel KERNCONF=SMP Then reboot. Note here that I'm giving you the shortest possible route, which may be problematic for you. You really must become familiar with /usr/src/UPDATING. Anyway, after the reboot, you should type: cat /var/log/messages | grep -i launch if you see the terms CPU1 Launched! then you've got yourself an SMP kernel. Good Luck! lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Duo core enable/support help.
On Tue, 05 Dec 2006 00:40:50 +, in sentex.lists.freebsd.questions you wrote: Hello Gurus, I just had Intel 102, duo core, fresh freebsd 6.1r installed. but i have been told that i have to enable duo core thing in kernel what should i have there? only options SMP ? what about the /usr/src/sys/i386/conf/SMP file? shall i copy the options to MYKERNEL ? If your kernel is called MYKERNEL, yes, just add options SMP to the file and then cd /usr/src ; make buildkernel make installkernel and reboot. ---Mike Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 [EMAIL PROTECTED], (http://www.tancsa.com) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Duo core enable/support help.
Mike Tancsa wrote: On Tue, 05 Dec 2006 00:40:50 +, in sentex.lists.freebsd.questions you wrote: Hello Gurus, I just had Intel 102, duo core, fresh freebsd 6.1r installed. but i have been told that i have to enable duo core thing in kernel what should i have there? only options SMP ? what about the /usr/src/sys/i386/conf/SMP file? shall i copy the options to MYKERNEL ? If your kernel is called MYKERNEL, yes, just add options SMP to the file and then cd /usr/src ; make buildkernel make installkernel and reboot. ---Mike Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 [EMAIL PROTECTED], (http://www.tancsa.com) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, I just got through this same problem myself. If I may, allow me to add this suggestion. Once you cp your own copy of GENERIC kernel; cd to /usr/src make buildkernel KERNCONF=YOUR_KERNEL_NAME make installkernel KERNCONF=YOUR_KERNEL_NAME Make sure that the KERNCONF is in UPPERCASE! Otherwise it will default to GENERIC. Trust me on this one. -- Rev. Z. Wade Hampton [EMAIL PROTECTED] Dedicated to those Rangers who laid down their lives; so that lesser men could be free to cry peace, when there was none. Author unknown ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
