On Thu, Feb 02, 2006 at 01:58:46PM +0100, Marius Strobl wrote: > > The NetBSD version is known to work with the VMWare LANCE (it > > actually also has the same workaround as lnc(4) for a bug in the > > emulation) so I think the ported version also will. I haven't > > given that a try so far however and only tested it with real PCI > > hardware as my main goal is to get it into RELENG_6 as soon as > > possible in order to get it into 6.1 (without replacing lnc(4) in > > the default config). If someone could give it a try with VMWare so > > I don't need to get a copy and probably a Windows installation > > that would be really great though. > > The FreeBSD le(4) also works with the VMWare LANCE for i386 UP. I > can't give it a try for SMP or amd64 (but should also work just fine > for these). The latter is probably interesting as lnc(4) doesn't > work on amd64 according to sys/amd64/conf/GENERIC. >
The le(4) works fine for low network loads, however I get device timeout messages on the console when I try to transfer a file from the vmware image to the host os (or another vmware image) with the "host only networking". This is with vmware 5.5.1 and FreeBSD/i386 running CURRENT with sources updated yesterday. The host os is running Linux. It should also be noted that I am experiencing the same, or at least a similar proble, with the lnc(4) driver. The console message says "device timeout -- resetting" For the record, running freebsd amd64 in vmware 5.5 will give you a "Intel PRO/1000" (if_em) card and not the lance card. And this works without any problems at all. -- Morten Rodal "A supercomputer is a device for turning compute-bound problems into I/O bound problems." -- Ken Batcher (Goodyear Aerospace)
pgpvh7QDJVrAJ.pgp
Description: PGP signature
