Re: [Soekris] FreeBSD/amd64 on Net6501 working!
On 12/13/2011 04:33 AM, Matt Dainty wrote: * Soren Kristensen so...@soekris.com [2011-12-11 10:00:05]: ACPI is on my long list of things to do, I'll better move it up, the basic ACPI stuff needed is not that complicated. The ACPI Power is really complicated, but I have no plan to support that, as active power management is not something you want or need on a always on platform Would the ACPI Power support also cover the CPU speed/power throttling? ACPI can be used to provide CPU P-state throttling, but in the case of Intel CPUs, I think SpeedStep is probably a better/easier way to go. Most OSes support it, as long as they can identify the CPU. On FreeBSD, the eist driver already sees that the CPUs support SpeedStep, but doesn't attach due to not having the CPU in its configuration table. -nick Matt -- n...@desert.net - all messages cryptographically signed signature.asc Description: OpenPGP digital signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] FreeBSD/amd64 on Net6501 working!
On 12/10/2011 06:07 AM, Denis Fortin wrote: On 2011-12-08 08:55, Aragon Gouveiaara...@phat.za.net wrote: On 12/07/11 23:00, Soren Kristensen wrote: I don't have the knowledge to find out where and why FreeBSD stops, but if some FreeBSD hacker can go down and tell me why, I will do what I can do fix it if the BIOS need a little adjustment Considering all the ACPI error messages, I guess it's a problem there somewhere. The freebsd-acpi@ mailing list is a good place to seek ACPI wizards. :) If I try to boot FreeBSD 9.0-RC2 in verbose mode with amd64 and i386 and compare the boot messages side-by-side, there are as many error messages about ACPI with the (successful) i386 boot than with the (failed) amd64 boot. The amd64 boot ends with the following lines: panic: No usable event timer found! cpuid = 0 KDB: stack backtrace: #0 0x80867e4e at kdb_backtrace+0x5e #1 0x80832ab7 at panic+0x187 #2 0x80b5250b at cpu_initclocks_bsp+0x3cb #3 0x807e9ec0 at initclocks+0x20 #4 0x807e7507 at mi_startup+0x77 #5 0x8029f6ec at btext+0x2c Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort Whereas the i386 boot goes on at this same spot with: lapic: Divisor 2, Frequency 50001280 Hz Timecounters tick every 1.000 msec Somehow, the LAPIC timer is reported with the i386 boot thus: MPTable: Soekris net6501 Event timer LAPIC quality 400 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 but not on the amd64 boot. Also, the i386 reports early on: MP Configuration Table version 1.4 found at 0xc00fe110 and *not* the amd64 boot. Anyway, just some preliminary information in case it triggers an Ah-ha! with some of the list members. I was able to boot FreeBSD/amd64 9.0-RC3 just now. The key was to enable mptable and atpic support in the kernel. device atpic # Optional legacy pic support device mptable# Optional MPSPEC mptable support I also removed device acpi, but that may not have been necessary. -nick Cheers, Denis F. ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- n...@desert.net - all messages cryptographically signed signature.asc Description: OpenPGP digital signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] FreeBSD/amd64 on Net6501 working!
On 12/10/2011 11:04 PM, Denis Fortin wrote: On 2011-12-11 01:54, Nicholas Esborn wrote: I was able to boot FreeBSD/amd64 9.0-RC3 just now. The key was to enable mptable and atpic support in the kernel. device atpic # Optional legacy pic support device mptable # Optional MPSPEC mptable support I also removed device acpi, but that may not have been necessary. -nick This is excellent news. Based on your input and what I had found earlier, I made a couple of FreeBSD 9.0-RC3 kernels to play with the options, and I found that device mptable is needed for the FreeBSD/amd64 kernel to boot on the net6501. Anyway, it's good to know that we'll be able to build and use 64-bit kernels... but I doubt we can get device mptable enabled in GENERIC at this late stage of the 9.0 release cycle (we are at RC3). From what I have seen, mptable and atpic support are both designated as legacy capabilities on FreeBSD. The FreeBSD developers may not want to re-enable them in GENERIC. Support for non-ACPI configurations could become increasingly tenuous. With luck, the required options will remain available for some time to come, but it seems like an ACPI BIOS would be a very positive development for the longevity of the Net6501 with modern operating systems. -nick Cheers, Denis, for...@acm.org PS. Now onwards to find out why my USB 3.0 PCIe card is not working as expected. -- n...@desert.net - all messages cryptographically signed signature.asc Description: OpenPGP digital signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] FreeBSD/amd64 on Net6501
On 12/07/2011 07:33 AM, Soren Kristensen wrote: Hi Niuck, Nicholas Esborn wrote: Hello, I am having no luck getting FreeBSD/amd64 8.2-RELEASE to boot on the Net6501. FreeBSD/i386 8.2-RELEASE works fine, but if possible I'd like to run amd64 in this machine's intended role. I've seen reports that 64-bit Linux and OpenBSD have been booted successfully, but not FreeBSD. Has anyone gotten this working? Have you updated to newest BIOS ? The dmesg looks like an old BIOS, unless it's FreeBSD-64 that don't like something Soren, Thanks for your reply. This was with 1.41: comBIOS ver. 1.41 20111201 Copyright (C) 2000-2011 Soekris Engineering. Thanks, -nick Best Regards, Soren Kristensen CEO Chief Engineer Soekris Engineering, Inc. The kernel initializes as seen below, then it just stops. I've tried disabling ACPI, APIC, MSI, and MSIX in various combinations. The boot output changes a bit, particularly with regard to interrupts, but nothing I have tried has altered where the kernel stops. Also, I don't seem to be able to break into the debugger. For the following dmesg, ACPI, APIC, MSI, and MSIX are at defaults. KDB: debugger backends: ddb KDB: current backend: ddb ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309) Copyright (c) 1992-2011 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 8.2-RELEASE-p2 #0: Thu Dec 1 16:42:39 MST 2011 n...@kerberos.desert.net:/usr/obj/usr/src/sys/NET6501 amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Genuine Intel(R) CPU@ 1.60GHz (1600.01-MHz K8-class CPU) Origin = GenuineIntel Id = 0x20661 Family = 6 Model = 26 Stepping = 1 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=0x40e3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 2147352576 (2047 MB) avail memory = 2060894208 (1965 MB) kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. pcib0:Host to PCI bridge pcibus 0 on motherboard pci0:PCI bus on pcib0 pcib1:PCI-PCI bridge irq 10 at device 23.0 on pci0 pci1:PCI bus on pcib1 pcib2:PCI-PCI bridge irq 10 at device 0.0 on pci1 pci2:PCI bus on pcib2 pci2:unknown at device 0.0 (no driver attached) pci2:network, ethernet at device 0.1 (no driver attached) pci2:unknown at device 0.2 (no driver attached) ohci0:OHCI (generic) USB controller mem 0xab00-0xabff irq 9 at device 2.0 on pci2 ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ohci1:OHCI (generic) USB controller mem 0xac00-0xacff irq 9 at device 2.1 on pci2 ohci1: Could not allocate irq device_attach: ohci1 attach returned 6 ohci2:OHCI (generic) USB controller mem 0xad00-0xadff irq 9 at device 2.2 on pci2 ohci2: Could not allocate irq device_attach: ohci2 attach returned 6 ehci0:EHCI (generic) USB 2.0 controller mem 0xae00-0xaeff irq 9 at device 2.3 on pci2 ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 pci2:serial bus, USB at device 2.4 (no driver attached) pci2:base peripheral, SD host controller at device 4.0 (no driver attached) pci2:base peripheral, SD host controller at device 4.1 (no driver attached) ahci0:AHCI SATA controller port 0x1020-0x103f mem 0xa0004400-0xa00047ff irq 11 at device 6.0 on pci2 ahci0: unable to map interrupt device_attach: ahci0 attach returned 6 ohci3:OHCI (generic) USB controller mem 0xa0004800-0xa00048ff irq 10 at device 8.0 on pci2 ohci3: Could not allocate irq device_attach: ohci3 attach returned 6 ohci4:OHCI (generic) USB controller mem 0xa0004900-0xa00049ff irq 10 at device 8.1 on pci2 ohci4: Could not allocate irq device_attach: ohci4 attach returned 6 ohci5:OHCI (generic) USB controller mem 0xa0004a00-0xa0004aff irq 10 at device 8.2 on pci2 ohci5: Could not allocate irq device_attach: ohci5 attach returned 6 ehci1:EHCI (generic) USB 2.0 controller mem 0xa0004b00-0xa0004bff irq 10 at device 8.3 on pci2 ehci1: Could not allocate irq device_attach: ehci1 attach returned 6 pci2:unknown at device 10.0 (no driver attached) pci2:simple comms, UART at device 10.1 (no driver attached) pci2:simple comms, UART at device 10.2 (no driver attached) pci2:simple comms, UART at device 10.3 (no driver attached) pci2:simple comms, UART at device 10.4 (no driver attached) pci2:unknown at device 12.0 (no driver attached) pci2:serial bus at device 12.1 (no driver attached) pci2:serial bus at device 12.2 (no driver
Re: [Soekris] FreeBSD/amd64 on Net6501
On 12/07/2011 03:11 PM, Aragon Gouveia wrote: On 12/07/11 23:00, Soren Kristensen wrote: I don't have the knowledge to find out where and why FreeBSD stops, but if some FreeBSD hacker can go down and tell me why, I will do what I can do fix it if the BIOS need a little adjustment Considering all the ACPI error messages, I guess it's a problem there somewhere. The freebsd-acpi@ mailing list is a good place to seek ACPI wizards. :) ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech Hmm... I've read suggestions that FreeBSD/amd64 requires ACPI, but the Net6501 doesn't seem to have any ACPI BIOS resources. Perhaps it might not be possible to get it running. Are there any plans to release an ACPI BIOS for the Net6501? Thanks, -nick -- n...@desert.net - all messages cryptographically signed signature.asc Description: OpenPGP digital signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
