Date: Tue, 15 May 2007 18:33:41 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: hackers@freebsd.org, Darren Reed <darrenr@hub.freebsd.org> Subject: Re: Experiences with 7.0-CURRENT and vmware. Message-ID: <200705151833.42372.jhb@freebsd.org> In-Reply-To: <20070510111326.GA94093@hub.freebsd.org> References: <20070510111326.GA94093@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 10 May 2007 07:13:26 am Darren Reed wrote: > > I'm using FreeBSD 7.0-CURRENT under vmware and there are a few issues. > > First, time. > hint.hw.acpi.disabled="1" > This appears to make _no_ difference to time keeping on FreeBSD 7 > and nor does it seem to have any impact on ACPI being loaded. Do > I need to recompile a new kernel without it or is there a new way > to disable ACPI? The tunable is 'hint.acpi.0.disabled=1' man 4 acpi > Second, networking. > Prior to FreeBSD-7, the driver to use inside vmware workstation > was lnc. It has worked and contiues to work great. No problemo. > FreeBSD-7 uses the "em" driver. To put it simply, it sucks in > comparison. When things really get bad I start seeing "em0: watchdog > timeout" messages on the console. I looked and I don't see a lnc > driver anywhere. Is there another alternative (le?) driver that > I can use in place of em, if so, how? le(4) is the newer lnc(4). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705151833.42372.jhb>