Re: [pfSense Support] Hardware not supported
2011/1/25 İhsan Doğan : > Hello, > > I've bought recently a Shuttle XPC-35 and unfortunately this hardware > does not run with FreeBSD 8.1, but it does with FreeBSD 8.2. > > Are there any plans to run pfSense 2.0 with FreeBSD 8.2? > No. Changing versions causes lots of fallout, 2.0 will be 8.1. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] Hardware not supported
Hello, I've bought recently a Shuttle XPC-35 and unfortunately this hardware does not run with FreeBSD 8.1, but it does with FreeBSD 8.2. Are there any plans to run pfSense 2.0 with FreeBSD 8.2? Ihsan -- ih...@dogan.chhttp://blog.dogan.ch/ - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] pfSense 2.0, upgrade to this morning's snap problem
On Mon, Jan 24, 2011 at 7:42 PM, Dimitri Rodis wrote: > After an upgrade to this morning's snap, I received the following > after the upgrade/reboot (it's what's on my PuTTY atm): > > > > Syncing OpenVPN settings...done. > > Starting syslog...done. > > Configuring firewall..done. > > Starting PFLOG...done. > > Setting up gateway monitors...done. > > Synchronizing user settings...done. > > Starting webConfigurator...done. > > Configuring CRON...done. > > Starting OpenNTP time client...done. > > Starting DHCP service...done. > > Starting DNS forwarder...done. > > Configuring firewall..done. > > kernel trap 12 with interrupts disabled > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x8 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc094d130 > > stack pointer = 0x28:0xc27d1b84 > > frame pointer = 0x28:0xc27d1ba4 > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags= resume, IOPL = 0 > > current process = 11 (swi4: clock) > > trap number = 12 > > panic: page fault > > cpuid = 0 > > Uptime: 25s > > Cannot dump. Device not defined or unavailable. > > Automatic reboot in 15 seconds - press a key on the console to abort > > --> Press a key on the console to reboot, > > --> or switch off the system now. > > >If you have a bridge setup please upgrade to the 2nd next snapshot. > > >-- >Ermal I did have ports bridged on this device, yes. For some reason, the device would still not boot even if I booted back to the original slice using the boot menu on the console---I ended up having to reflash my CF card and then it booted (but the config is still default). Then again, I don't know that I rebooted ever since I configured the bridge Thanks Ermal. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] pfSense 2.0, upgrade to this morning's snap problem
On Mon, Jan 24, 2011 at 7:42 PM, Dimitri Rodis wrote: > After an upgrade to this morning’s snap, I received the following after the > upgrade/reboot (it’s what’s on my PuTTY atm): > > > > Syncing OpenVPN settings...done. > > Starting syslog...done. > > Configuring firewall..done. > > Starting PFLOG...done. > > Setting up gateway monitors...done. > > Synchronizing user settings...done. > > Starting webConfigurator...done. > > Configuring CRON...done. > > Starting OpenNTP time client...done. > > Starting DHCP service...done. > > Starting DNS forwarder...done. > > Configuring firewall..done. > > kernel trap 12 with interrupts disabled > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x8 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc094d130 > > stack pointer = 0x28:0xc27d1b84 > > frame pointer = 0x28:0xc27d1ba4 > > code segment = base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = resume, IOPL = 0 > > current process = 11 (swi4: clock) > > trap number = 12 > > panic: page fault > > cpuid = 0 > > Uptime: 25s > > Cannot dump. Device not defined or unavailable. > > Automatic reboot in 15 seconds - press a key on the console to abort > > --> Press a key on the console to reboot, > > --> or switch off the system now. > > If you have a bridge setup please upgrade to the 2nd next snapshot. -- Ermal - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org