w is to just get -CURRENT up and running.
>
> Any ideas?
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
=+=+=+=+=+=+=
access, if somebody would be willed trying to
> troubleshoot one or both of these problems.
>
> A comconsole would also be possible.
>
> BTW, -current on my Server is stable. Its only the laptop,
> where those panics hap
Because of our network setup, fxp0 does not have any ip address bound to it.
Check your logs, like I said, something else is causing the problem.
Lanny
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Lanny Baron
Proud to be 100% FreeBSD
http://www.FreeBSDsystems.COM
Toll Free: 1.877.963.1900
Looks like I made a mistake.
Sorry for any inconvenience the advice may have caused.
Regards,
Lanny
On Thu, 2003-09-25 at 01:13, Greg 'groggy' Lehey wrote:
> On Thursday, 25 September 2003 at 1:12:21 -0400, Lanny Baron wrote:
> > On Wed, 2003-09-24 at 22:42, Greg 'grog
l as well as a module.
> >
> > In neither case does ifconfig show a sl0 device.
>
> IIRC it doesn't show now until it's configured.
>
> Greg
> --
> See complete headers for addr
__
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-smp
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Lanny Baron
Proud to be 100% FreeBSD
http://www.FreeBSDsystems.COM
=+=+=+=+=+=+=+=+=+=+=+=+=+=
Victor,
You have something messed up. Did you update the bios correctly? Look
at your kernel as well.
We use the westville for several Servers and it boots multi-processor
just fine. In fact, the hyperthreading works and when booting you should
see 4 cpu's come up.
Cheers,
Lanny Baron
y for your help,
Lanny Baron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
