em driver problem on vmware

[Kevin Lo]

Hi Rick,

The FreeBSD -current works fine for me with the newest em(4) 
under the VMware player.

	Kevin

On Friday, 2010-10-29 at 19:22 -0700, Ricky Charlet wrote:
> Thanks Jack,
> 
>                 The failure is that ifconfig is unaware of em0.  My em0 is not configured, so link partners are also unaware of it.
> ifconfig em0
> ifconfig: interface em0 does not exist
> 
> and you already have my dmes stuff on em0 (which I am now up to agreeing looks positive and would not indicate a problem)
> 
> 
> My amalgamated file is a private combination of some 8.1, some 9.0, some stuff a cohort did.  We have been motivated to 'upgrade' from e1000 in 8.0 to a newer/modified e1000 because of our desire to incorporate the altq patches.
> 
>                 For the curious and the diligent, the e1000/if_em.c file I am using is attached.
> 
> Ricky
> 
> 
> From: Jack Vogel [mailto:jfvogel at gmail.com]
> Sent: Friday, October 29, 2010 7:13 PM
> To: Ricky Charlet
> Cc: freebsd-net at freebsd.org
> Subject: Re: em driver problem on vmware
> 
> I remember seeing the same thing when running a FreeBSD guest on
> Linux/KVM, its informational, the code will enable said bits right after
> it says that.
> 
> So, the focus should be on the data, you are saying the delivered
> driver in 8.0 out of the box works and which driver exactly are you
> trying to use, my last checked in?
> 
> More on the failure,  does it ping, does its link partner see anything,
> etc, etc..
> 
> Jack
> 
> On Fri, Oct 29, 2010 at 6:27 PM, Ricky Charlet <RCharlet at adaranet.com<mailto:RCharlet at adaranet.com>> wrote:
> FYI,
> That dmesg output I get from my franken-driver on vmware is exactly the same output I get from the *working* bsd80Release on vmware:
> 
> ------------cut--------------------
> [root at npx7511 /usr/src/sys/dev/e1000]# dmesg | grep em0
> em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x2000-0x203f 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-------------------
> 
> 
> So I don't think the clue is hiding in dmesg.
> 
> ---
> Ricky Charlet
> Adara Networks
> USA 408-433-4942
> 
> -----Original Message-----
> From: owner-freebsd-net at freebsd.org<mailto:owner-freebsd-net at freebsd.org> [mailto:owner-freebsd-net at freebsd.org<mailto:owner-freebsd-net at freebsd.org>] On Behalf Of Ricky Charlet
> Sent: Friday, October 29, 2010 5:07 PM
> To: freebsd-net at freebsd.org<mailto:freebsd-net at freebsd.org>
> Subject: em driver problem on vmware
> 
> 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------------
> 
>        Now, I certainly may have done something wrong with my code switch (just copied over the sys/dev/e1000 directory from 8.1 and defined drbr_needs_enqueue in if_var.h). I'll start double checking.
> 
>        But, on the other hand, has anyone seen the new em driver working/failing on a vmware vm?
> 
> 
> Thanks
> 
> 
> ---
> Ricky Charlet
> Adara Networks
> USA 408-433-4942
> 
> _______________________________________________
> freebsd-net at freebsd.org<mailto: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<mailto:freebsd-net-unsubscribe at freebsd.org>"
> _______________________________________________
> freebsd-net at freebsd.org<mailto: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<mailto:freebsd-net-unsubscribe at freebsd.org>"
> 
> _______________________________________________
> 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"