em driver problem on vmware

[Jack Vogel]

pciconf -l

If you got a printf from the driver its VERY odd that it says the interface
does not exist :)

Jack


On Fri, Oct 29, 2010 at 7:03 PM, Ricky Charlet <RCharlet at adaranet.com>wrote:

>
>
> > -----Original Message-----
> > From: juli at clockworksquid.com [mailto:juli at clockworksquid.com] On
> > Behalf Of Juli Mallett
> > Sent: Friday, October 29, 2010 6:55 PM
> > To: Ricky Charlet
> > Cc: freebsd-net at freebsd.org
> > Subject: Re: em driver problem on vmware
> >
> > On Fri, Oct 29, 2010 at 17:07, Ricky  Charlet <RCharlet at adaranet.com>
> > wrote:
> > > Howdy,
> > >        I have freebsd80-release with an upgraded em0 driver from
> > freebsd8.1 (and an appropriate touch of if_var.h). I'm running an amd64
> > on a  vmware vm.  And I see this in dmesg:
> > >
> > > ------------cut-------------
> > > em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x2000-203f
> > mem 0xd8940000-0xd895ffff, 0xd8900000-0xd890ffff irq 18 at device 0.0
> > on pci2
> > > em0: Memory Access and/or Bus Master bits were not set
> > > em0: [FILTER]
> > > em0: Ethernet address: 00:0c:29:57:d7:7f
> > > ------------paste------------
> > >
> > >        But, on the other hand, has anyone seen the new em driver
> > working/failing on a vmware vm?
> >
> > "Memory Access and/or Bus Master bits were not set" is not a fatal
> > error, it is correctable, indeed that is printed out when it is
> > corrected; that is not something to worry about in and of itself as
> > such, are you actually having a problem or just concerned because you
> > saw that in dmesg?
>
>
>  It is truly not working. I agree those lines in dmesg are good and
> indicate em0 is ready. but `ifconfig` does not see em0.
>
>
> ---
> Ricky Charlet
> Adara Networks
> USA 408-433-4942
>
>
>
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>