Re: [pfSense] Compile on Sun v215
On Dec 9, 2013 6:37 PM, "Adam Hunt" wrote: > > What parts of pfSense are so arch dependent. One would expect being based on FreeBSD would make it quite portable. > > > On Mon, Dec 9, 2013 at 3:25 PM, Jim Thompson wrote: >> >> it would be a lot of work. >> >> There was some work done back in history on a MIPS port. It never >> actually finished. >> >> There is very little interest in a SPARC port, though, as Adam >> allowed, nobody would really mind, other than the consequences of what >> to call it, and how to explain the support model for it, etc. >> >> Jim >> >> >> On Mon, Dec 9, 2013 at 3:46 PM, Adam Hunt wrote: >> > pfSense only supports x86 and amd64 architectures. Though, I suppose if you >> > wanted to port it to SPARC nobody would mind. >> > >> > >> > On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson wrote: >> >> >> >> Unlikely. >> >> >> >> -- Jim >> >> >> >> > On Dec 9, 2013, at 4:07, Denny Fuchs wrote: >> >> > >> >> > hi, >> >> > >> >> > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD 8/98 >> >> > runs without any problems, so the only question is, if it does make sense to >> >> > compile pfsense on that hosts. >> >> > >> >> > Ram: 12GB >> >> > >> >> > # cat /proc/cpuinfo >> >> > cpu: TI UltraSparc IIIi (Jalapeno) >> >> > fpu: UltraSparc IIIi integrated FPU >> >> > pmu: ultra3i >> >> > prom: OBP 4.22.33 2007/06/18 12:47 >> >> > type: sun4u >> >> > ncpus probed: 2 >> >> > ncpus active: 2 >> >> > D$ parity tl1: 0 >> >> > I$ parity tl1: 0 >> >> > cpucaps: >> >> > flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 >> >> > Cpu0ClkTck: 59a53800 >> >> > Cpu1ClkTck: 59a53800 >> >> > MMU Type: Cheetah+ >> >> > State: >> >> > CPU0:online >> >> > CPU1:online >> >> > >> >> > cu denny >> >> > >> >> > Adam, As I found when I tried to do a custom build for Nokia IP380 (a Pentium III, so it is x86, but it requires removing USB support from the kernel in order to boot successfully for some reason) and a custom build with Hyper-V kernel extensions, there are really three problems. 1. Build System. As Jim said, you need to get the build system working properly. I would have thought this would be fairly easy in my case, given that I was making pretty much a single kernel change to each build, but it turned out to be much more difficult. 2. Updates. Even once you have a working build system, you need to take every released pfSense update and rebuild it for yourself. You could likely automate that on your build system, but there's no guarantee that you will be able to build future updates without needing to tweak anything and/or assist the build system itself. 3. Packages. You may have to copy the package server and hottest your own version for any packages that you care about. Moshe ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Problems with Realtek 8168/8111 nic
On 13-12-09 06:47 PM, Adrian Zaugg wrote: The only suspicious thing I see on the failing box are some of such messages: kernel: pid 37699 (php), uid 0: exited on signal 11 (core dumped) They are not in an obvious relation to an ethernet event. Spurious signal 11 (SEGV) messages tend to indicate faulty hardware, in my experience. Most typically, bad or marginal RAM. That can in turn be caused by bad or marginal power - both the PSU and the circuitry on the motherboard. Although this may sound bizarre, check your motherboard(s) for bulging or leaking capacitors. It's entirely possible that the increased power draw as both CPU and Ethernet interface start to get busier is enough to cause a transient error. I've seen many motherboard with bad capacitors that work fine at idle and fail under load due to increased power draw. Of course, this may not be your problem at all, but it's worth eliminating. Remember that when it comes to failing components, replacing a suspect piece of hardware with an identical piece of hardware of roughly the same age (e.g. you have a spare in storage) does NOT prove anything - particularly with faulty capacitors, hardware can develop faults while sitting in a box on a shelf. -- -Adam Thompson athom...@athompso.net ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Problems with Realtek 8168/8111 nic
Hi Peter If you test with load, do you get a steady stream? Did you test in both directions: to and from your box? I see the same symptoms, but I can provoke them to happen under load. Bizarre is, that sending data from the pfsense box works fine, I see a steady stream of 55-57MB/s. In the opposite direction sending from my host to the pfsense box peaks in 10-25MB/s and drops to zero for some seconds repeatedly. No matter if I use a direct cable or different switches. This happens with two both of my gateways, which are the same ibase fw7404 boxes (embedded systems, not possible to change nics). CPU load is at around 25% only. A different box with the same pfsense version and the same ethernet chip (RTL-8111e Chip rev. 0x2c80) doesn't show this behavior. I played around with the system tuneables too (switch on and off tso, ...), but with no success. The only suspicious thing I see on the failing box are some of such messages: kernel: pid 37699 (php), uid 0: exited on signal 11 (core dumped) They are not in an obvious relation to an ethernet event. Indeed help would be very much appreciated. Regards, Adrian. Am 07.12.13 19:50 schrieb Peter Merritt: > Randomly, sometimes hours or days apart one of the realtek nics on my > system will stop responding, dropping connection. The error message is > > > > re1: watchdog timeout > > re1: Stopping TXQ timed out. > > > > This has happened on 3 different mother boards now all with realtek > nics. ( hard to find an itx board with another kind of nic) > > > > I does not see to be a load based problem, as I did some testing of the > connection with nc to see if I could make it fail. re0 is not connected > right now. Any help would be greatly appreciated. > > Peter > > > > > > Dmesg follows > > > > Copyright (c) 1992-2012 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.3-RELEASE-p11 #0: Wed Sep 11 18:51:23 EDT 2013 > > root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 > amd64 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz (1496.61-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model = 3a > Stepping = 9 > > Features=0xbfebfbff > > Features2=0x5bae3bf > AMD Features=0x28100800 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 2147483648 (2048 MB) > avail memory = 1904844800 (1816 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 2 > ioapic0 irqs 0-23 on motherboard > wlan: mac acl policy registered > ipw_bss: You need to read the LICENSE file in > /usr/share/doc/legal/intel_ipw/. > ipw_bss: If you agree with the license, set > legal.intel_ipw.license_ack=1 in /boot/loader.conf. > module_register_init: MOD_LOAD (ipw_bss_fw, 0x804a5da0, 0) error 1 > ipw_ibss: You need to read the LICENSE file in > /usr/share/doc/legal/intel_ipw/. > ipw_ibss: If you agree with the license, set > legal.intel_ipw.license_ack=1 in /boot/loader.conf. > module_register_init: MOD_LOAD (ipw_ibss_fw, 0x804a5e40, 0) error 1 > ipw_monitor: You need to read the LICENSE file in > /usr/share/doc/legal/intel_ipw/. > ipw_monitor: If you agree with the license, set > legal.intel_ipw.license_ack=1 in /boot/loader.conf. > module_register_init: MOD_LOAD (ipw_monitor_fw, 0x804a5ee0, 0) > error 1 > kbd1 at kbdmux0Copyright (c) 1992-2012 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.3-RELEASE-p11 #0: Wed Sep 11 18:51:23 EDT 2013 > > root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 > amd64 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz (1496.61-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model = 3a > Stepping = 9 > > Features=0xbfebfbff > > Features2=0x5bae3bf > AMD Features=0x28100800 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 2147483648 (2048 MB) > avail memory = 1904844800 (1816 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 2 > ioapic0 irqs 0-23 on motherboard > wlan: mac acl policy registered > ipw_bss: You need to read the LICENSE file in > /usr/share/doc/legal/intel_ipw/. > ipw_bss: If you agree with the license, set > legal.intel_ipw.license_ack=1 in /boot/loader.conf. > module_register_ini
Re: [pfSense] Compile on Sun v215
the build system is really where the trouble is. after that, you would need to figure out the installer. On Mon, Dec 9, 2013 at 5:36 PM, Adam Hunt wrote: > What parts of pfSense are so arch dependent. One would expect being based on > FreeBSD would make it quite portable. > > > On Mon, Dec 9, 2013 at 3:25 PM, Jim Thompson wrote: >> >> it would be a lot of work. >> >> There was some work done back in history on a MIPS port. It never >> actually finished. >> >> There is very little interest in a SPARC port, though, as Adam >> allowed, nobody would really mind, other than the consequences of what >> to call it, and how to explain the support model for it, etc. >> >> Jim >> >> >> On Mon, Dec 9, 2013 at 3:46 PM, Adam Hunt wrote: >> > pfSense only supports x86 and amd64 architectures. Though, I suppose if >> > you >> > wanted to port it to SPARC nobody would mind. >> > >> > >> > On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson wrote: >> >> >> >> Unlikely. >> >> >> >> -- Jim >> >> >> >> > On Dec 9, 2013, at 4:07, Denny Fuchs wrote: >> >> > >> >> > hi, >> >> > >> >> > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD >> >> > 8/98 >> >> > runs without any problems, so the only question is, if it does make >> >> > sense to >> >> > compile pfsense on that hosts. >> >> > >> >> > Ram: 12GB >> >> > >> >> > # cat /proc/cpuinfo >> >> > cpu: TI UltraSparc IIIi (Jalapeno) >> >> > fpu: UltraSparc IIIi integrated FPU >> >> > pmu: ultra3i >> >> > prom: OBP 4.22.33 2007/06/18 12:47 >> >> > type: sun4u >> >> > ncpus probed: 2 >> >> > ncpus active: 2 >> >> > D$ parity tl1: 0 >> >> > I$ parity tl1: 0 >> >> > cpucaps: >> >> > flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 >> >> > Cpu0ClkTck: 59a53800 >> >> > Cpu1ClkTck: 59a53800 >> >> > MMU Type: Cheetah+ >> >> > State: >> >> > CPU0:online >> >> > CPU1:online >> >> > >> >> > cu denny >> >> > >> >> > >> >> > ___ >> >> > List mailing list >> >> > List@lists.pfsense.org >> >> > http://lists.pfsense.org/mailman/listinfo/list >> >> ___ >> >> List mailing list >> >> List@lists.pfsense.org >> >> http://lists.pfsense.org/mailman/listinfo/list >> > >> > >> > >> > ___ >> > List mailing list >> > List@lists.pfsense.org >> > http://lists.pfsense.org/mailman/listinfo/list >> > >> ___ >> List mailing list >> List@lists.pfsense.org >> http://lists.pfsense.org/mailman/listinfo/list > > > > ___ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list > ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Compile on Sun v215
What parts of pfSense are so arch dependent. One would expect being based on FreeBSD would make it quite portable. On Mon, Dec 9, 2013 at 3:25 PM, Jim Thompson wrote: > it would be a lot of work. > > There was some work done back in history on a MIPS port. It never > actually finished. > > There is very little interest in a SPARC port, though, as Adam > allowed, nobody would really mind, other than the consequences of what > to call it, and how to explain the support model for it, etc. > > Jim > > > On Mon, Dec 9, 2013 at 3:46 PM, Adam Hunt wrote: > > pfSense only supports x86 and amd64 architectures. Though, I suppose if > you > > wanted to port it to SPARC nobody would mind. > > > > > > On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson wrote: > >> > >> Unlikely. > >> > >> -- Jim > >> > >> > On Dec 9, 2013, at 4:07, Denny Fuchs wrote: > >> > > >> > hi, > >> > > >> > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD 8/98 > >> > runs without any problems, so the only question is, if it does make > sense to > >> > compile pfsense on that hosts. > >> > > >> > Ram: 12GB > >> > > >> > # cat /proc/cpuinfo > >> > cpu: TI UltraSparc IIIi (Jalapeno) > >> > fpu: UltraSparc IIIi integrated FPU > >> > pmu: ultra3i > >> > prom: OBP 4.22.33 2007/06/18 12:47 > >> > type: sun4u > >> > ncpus probed: 2 > >> > ncpus active: 2 > >> > D$ parity tl1: 0 > >> > I$ parity tl1: 0 > >> > cpucaps: > >> > flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 > >> > Cpu0ClkTck: 59a53800 > >> > Cpu1ClkTck: 59a53800 > >> > MMU Type: Cheetah+ > >> > State: > >> > CPU0:online > >> > CPU1:online > >> > > >> > cu denny > >> > > >> > > >> > ___ > >> > List mailing list > >> > List@lists.pfsense.org > >> > http://lists.pfsense.org/mailman/listinfo/list > >> ___ > >> List mailing list > >> List@lists.pfsense.org > >> http://lists.pfsense.org/mailman/listinfo/list > > > > > > > > ___ > > List mailing list > > List@lists.pfsense.org > > http://lists.pfsense.org/mailman/listinfo/list > > > ___ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list > ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Issue Creating New VLAN Interfaces
Replying to let everyone know how this was resolved. Issue persisted in upgrade to 2.1. Problem is caused when a VLAN was deleted, pfSense seems to replace that interface in the Interface Groups page to the default interface. This caused routing to completely break for us. The work around is to manually delete the default interface from the interface group. Hopefully this will help some poor soul in the future. -Martin From: list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org] On Behalf Of Martin Fuller Sent: Tuesday, December 03, 2013 1:48 PM To: list@lists.pfsense.org Subject: [pfSense] Issue Creating New VLAN Interfaces Hello All, This is my first post to this mailing list so please let me know if I break protocol, not sure where to turn at the moment. I'm running pfSense 2.0.1 (amd64) and I'm no longer able to add new VLANs to the firewall. I go to Interfaces > (assign) > VLANs > Add (interfaces_vlan_edit.php) to add a new VLAN, but as soon as I click save the firewall completely stops routing traffic, causing all my hosts to become invisible to the world. I am still able to interface with the firewall itself, and removing the new VLAN and rebooting seems to fix the problem, but I don't know why I can no longer add VLANs as I have been doing. The VLAN Tag I am adding is "58", I don't think I'm hitting a hard limit but putting this here anyway. Please let me know if anyone has any ideas, I would greatly appreciate some suggestions. Regards, Martin Fuller ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Compile on Sun v215
it would be a lot of work. There was some work done back in history on a MIPS port. It never actually finished. There is very little interest in a SPARC port, though, as Adam allowed, nobody would really mind, other than the consequences of what to call it, and how to explain the support model for it, etc. Jim On Mon, Dec 9, 2013 at 3:46 PM, Adam Hunt wrote: > pfSense only supports x86 and amd64 architectures. Though, I suppose if you > wanted to port it to SPARC nobody would mind. > > > On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson wrote: >> >> Unlikely. >> >> -- Jim >> >> > On Dec 9, 2013, at 4:07, Denny Fuchs wrote: >> > >> > hi, >> > >> > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD 8/98 >> > runs without any problems, so the only question is, if it does make sense >> > to >> > compile pfsense on that hosts. >> > >> > Ram: 12GB >> > >> > # cat /proc/cpuinfo >> > cpu: TI UltraSparc IIIi (Jalapeno) >> > fpu: UltraSparc IIIi integrated FPU >> > pmu: ultra3i >> > prom: OBP 4.22.33 2007/06/18 12:47 >> > type: sun4u >> > ncpus probed: 2 >> > ncpus active: 2 >> > D$ parity tl1: 0 >> > I$ parity tl1: 0 >> > cpucaps: >> > flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 >> > Cpu0ClkTck: 59a53800 >> > Cpu1ClkTck: 59a53800 >> > MMU Type: Cheetah+ >> > State: >> > CPU0:online >> > CPU1:online >> > >> > cu denny >> > >> > >> > ___ >> > List mailing list >> > List@lists.pfsense.org >> > http://lists.pfsense.org/mailman/listinfo/list >> ___ >> List mailing list >> List@lists.pfsense.org >> http://lists.pfsense.org/mailman/listinfo/list > > > > ___ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list > ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Compile on Sun v215
pfSense only supports x86 and amd64 architectures. Though, I suppose if you wanted to port it to SPARC nobody would mind. On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson wrote: > Unlikely. > > -- Jim > > > On Dec 9, 2013, at 4:07, Denny Fuchs wrote: > > > > hi, > > > > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD 8/98 > runs without any problems, so the only question is, if it does make sense > to compile pfsense on that hosts. > > > > Ram: 12GB > > > > # cat /proc/cpuinfo > > cpu: TI UltraSparc IIIi (Jalapeno) > > fpu: UltraSparc IIIi integrated FPU > > pmu: ultra3i > > prom: OBP 4.22.33 2007/06/18 12:47 > > type: sun4u > > ncpus probed: 2 > > ncpus active: 2 > > D$ parity tl1: 0 > > I$ parity tl1: 0 > > cpucaps: > flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 > > Cpu0ClkTck: 59a53800 > > Cpu1ClkTck: 59a53800 > > MMU Type: Cheetah+ > > State: > > CPU0:online > > CPU1:online > > > > cu denny > > > > > > ___ > > List mailing list > > List@lists.pfsense.org > > http://lists.pfsense.org/mailman/listinfo/list > ___ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list > ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
[pfSense] Problems with Realtek 8168/8111 nic
Randomly, sometimes hours or days apart one of the realtek nics on my system will stop responding, dropping connection. The error message is re1: watchdog timeout re1: Stopping TXQ timed out. This has happened on 3 different mother boards now all with realtek nics. ( hard to find an itx board with another kind of nic) I does not see to be a load based problem, as I did some testing of the connection with nc to see if I could make it fail. re0 is not connected right now. Any help would be greatly appreciated. Peter Dmesg follows Copyright (c) 1992-2012 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.3-RELEASE-p11 #0: Wed Sep 11 18:51:23 EDT 2013 root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz (1496.61-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model = 3a Stepping = 9 Features=0xbfebfbff Features2=0x5bae3bf AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1904844800 (1816 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0 irqs 0-23 on motherboard wlan: mac acl policy registered ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_bss_fw, 0x804a5da0, 0) error 1 ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_ibss_fw, 0x804a5e40, 0) error 1 ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_monitor_fw, 0x804a5ee0, 0) error 1 kbd1 at kbdmux0Copyright (c) 1992-2012 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.3-RELEASE-p11 #0: Wed Sep 11 18:51:23 EDT 2013 root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz (1496.61-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model = 3a Stepping = 9 Features=0xbfebfbff Features2=0x5bae3bf AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1904844800 (1816 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0 irqs 0-23 on motherboard wlan: mac acl policy registered ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_bss_fw, 0x804a5da0, 0) error 1 ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_ibss_fw, 0x804a5e40, 0) error 1 ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_monitor_fw, 0x804a5ee0, 0) error 1 kbd1 at kbdmux0 cryptosoft0: on motherboard padlock0: No ACE support. acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xf000-0xf03f mem 0xf780-0xf7bf,0xe000-0xefff irq 16 at device 2.0 on pci0 pci0: at device 22.0 (no driver attached) ehci0: mem 0xf7d08000-0xf7d083ff irq 16 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: on ehci0 pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 re0: port 0xe000-0xe0ff mem 0xf7c0-0xf7c00fff
Re: [pfSense] Compile on Sun v215
Unlikely. -- Jim > On Dec 9, 2013, at 4:07, Denny Fuchs wrote: > > hi, > > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD 8/98 runs > without any problems, so the only question is, if it does make sense to > compile pfsense on that hosts. > > Ram: 12GB > > # cat /proc/cpuinfo > cpu: TI UltraSparc IIIi (Jalapeno) > fpu: UltraSparc IIIi integrated FPU > pmu: ultra3i > prom: OBP 4.22.33 2007/06/18 12:47 > type: sun4u > ncpus probed: 2 > ncpus active: 2 > D$ parity tl1: 0 > I$ parity tl1: 0 > cpucaps: flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 > Cpu0ClkTck: 59a53800 > Cpu1ClkTck: 59a53800 > MMU Type: Cheetah+ > State: > CPU0:online > CPU1:online > > cu denny > > > ___ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
[pfSense] Compile on Sun v215
hi, I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD 8/98 runs without any problems, so the only question is, if it does make sense to compile pfsense on that hosts. Ram: 12GB # cat /proc/cpuinfo cpu : TI UltraSparc IIIi (Jalapeno) fpu : UltraSparc IIIi integrated FPU pmu : ultra3i prom: OBP 4.22.33 2007/06/18 12:47 type: sun4u ncpus probed: 2 ncpus active: 2 D$ parity tl1 : 0 I$ parity tl1 : 0 cpucaps : flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2 Cpu0ClkTck : 59a53800 Cpu1ClkTck : 59a53800 MMU Type: Cheetah+ State: CPU0: online CPU1: online cu denny signature.asc Description: Message signed with OpenPGP using GPGMail ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
