> Well, you want to try things in this order:
>
>
> 1/ rebuild a kernel without VIMAGE and try again, while you're at it
> enable debug options like the KDTRACE hooks and such.
>
> makeoptions DEBUG=-g # Build kernel with gdb(1) debug
> symbols
> options KDB
On 6/28/11 4:25 PM, Espartano wrote:
> On Tue, Jun 28, 2011 at 4:09 AM, Damien Fleuriot wrote:
>>
>> You need to define a dump device then, so that you may extract the
>> kernel's crash dump for analysis.
>
>
> I don't know if there is enought free space to allocate a kernel dump
> file into the
On Tue, Jun 28, 2011 at 4:09 AM, Damien Fleuriot wrote:
>
> You need to define a dump device then, so that you may extract the
> kernel's crash dump for analysis.
I don't know if there is enought free space to allocate a kernel dump
file into the Alix board's cf card, I will see if it is possibl
On 6/27/11 11:34 PM, Espartano wrote:
> Hi People I'm having a problem with my Alix board model 2d3
> (http://pcengines.ch/alix2d3.htm) , Yesterday I compiled and installed
> NanoBSD into my alix board using FreeBSD 8.2 RELEASE, today when i
> tried to configure network interfaces and pf firewall
Hi People I'm having a problem with my Alix board model 2d3
(http://pcengines.ch/alix2d3.htm) , Yesterday I compiled and installed
NanoBSD into my alix board using FreeBSD 8.2 RELEASE, today when i
tried to configure network interfaces and pf firewall to do nat over
the wireless network I got this
