Date: Wed, 3 Nov 2010 21:53:02 -0700 From: "Ricky Charlet" <RCharlet@adaranet.com> To: "Ricky Charlet" <RCharlet@adaranet.com>, Jack Vogel <jfvogel@gmail.com>, Juli Mallett <jmallett@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: RE: em driver problem on vmware Message-ID: <32AB5C9615CC494997D9ABB1DB12783C024C6FC072@SJ-EXCH-1.adaranet.com> In-Reply-To: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7F3@SJ-EXCH-1.adaranet.com> References: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7DF@SJ-EXCH-1.adaranet.com> <AANLkTimO30iVaH=AOCCFaWadtXaqzadxEmksFP9fzJ2A@mail.gmail.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7E3@SJ-EXCH-1.adaranet.com> <AANLkTikFg4vZurepJZH9wqbBNAk%2BN16yqLYmT-DbsPvA@mail.gmail.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7EA@SJ-EXCH-1.adaranet.com> <AANLkTindpORTuSFaAkfjhENaNnB%2BG7rAUMgv0fRD9C0Z@mail.gmail.com> <AANLkTinWbjLD=joGDd5%2BLWe7dfxTtDWqcLCM-5EB64L9@mail.gmail.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7F3@SJ-EXCH-1.adaranet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
FYI,
to close this thread off, I just had a build problem, I forgot to b=
uild e1000/if_lem.c. Did that and now it works.
So this becomes a success report of sorts... if anyone else is hand=
cuffed (like me) to 8.0 but you want the 8.1 e1000 driver (for altq), it is=
possible to port backwards.
However, everyone is by far better served if you can just straight =
away use 8.1.
---
Ricky Charlet
Adara Networks
USA 408-433-4942
> -----Original Message-----
> From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-
> net@freebsd.org] On Behalf Of Ricky Charlet
> Sent: Saturday, October 30, 2010 9:10 AM
> To: Jack Vogel; Juli Mallett
> Cc: FreeBSD Net
> Subject: RE: em driver problem on vmware
>
> Ah, Thanks for the direction. I'll take it as a self project from here.
> And I'll update this thread with my results hopefully by mid next week.
>
> Ricky
>
>
> From: Jack Vogel [mailto:jfvogel@gmail.com]
> Sent: Saturday, October 30, 2010 1:41 AM
> To: Juli Mallett
> Cc: Ricky Charlet; FreeBSD Net
> Subject: Re: em driver problem on vmware
>
> Uh, the emulated device in vmware is an OLD 82543 or something like
> that right?
> So, the e1000 driver in 8.1 is split into two parts, em and lem, its
> lem that has
> all the old pci support, so if you only pulled if_em then you dont
> have that code.
>
> Sounds like maybe you should just install 8.1 on your guest and avoid
> these
> kinds of problems.
>
> Regards,
>
> Jack
>
> On Fri, Oct 29, 2010 at 11:26 PM, Juli Mallett
> <jmallett@freebsd.org<mailto:jmallett@freebsd.org>> wrote:
> dmesg is not cleared at boot; your devices are not being detected,
> they merely showed up in a previous boot.
>
> On Fri, Oct 29, 2010 at 23:13, Ricky Charlet
> <RCharlet@adaranet.com<mailto:RCharlet@adaranet.com>> wrote:
> > Hi Julie,
> >
> > My entire dmesg output is attached.
> >
> > With much appreciation
> >
> > Ricky
> >
> >
> >
> >> -----Original Message-----
> >> From: juli@clockworksquid.com<mailto:juli@clockworksquid.com>
> [mailto:juli@clockworksquid.com<mailto:juli@clockworksquid.com>] On
> >> Behalf Of Juli Mallett
> >> Sent: Friday, October 29, 2010 8:01 PM
> >> To: Ricky Charlet
> >> Subject: Re: em driver problem on vmware
> >>
> >> Can you send me your full dmesg? You must be missing some relevant
> >> message, because the only circumstances under which you'd see the
> >> device attaching but then it wouldn't be present would also generate
> >> some error messages.
> >>
> >> On Fri, Oct 29, 2010 at 19:22, Ricky Charlet
> <RCharlet@adaranet.com<mailto:RCharlet@adaranet.com>>
> >> 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@gmail.com<mailto:jfvogel@gmail.com>]
> >> > Sent: Friday, October 29, 2010 7:13 PM
> >> > To: Ricky Charlet
> >> > Cc: freebsd-net@freebsd.org<mailto:freebsd-net@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@adaranet.com<mailto:RCharlet@adaranet.com><mailto:RCharlet@ad
> aranet.com<mailto:RCharlet@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@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@freebsd.org<mailto:owner-freebsd-
> net@freebsd.org><mailto:owner-freebsd-<mailto:owner-freebsd->
> >> net@freebsd.org<mailto:net@freebsd.org>> [mailto:owner-freebsd-
> net@freebsd.org<mailto:owner-freebsd-net@freebsd.org><mailto:owner-
> <mailto:owner->
> >> freebsd-net@freebsd.org<mailto:freebsd-net@freebsd.org>>] On Behalf
> Of Ricky Charlet
> >> > Sent: Friday, October 29, 2010 5:07 PM
> >> > To: freebsd-net@freebsd.org<mailto:freebsd-
> net@freebsd.org><mailto:freebsd-net@freebsd.org<mailto:freebsd-
> net@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@freebsd.org<mailto:freebsd-
> net@freebsd.org><mailto:freebsd-net@freebsd.org<mailto:freebsd-
> net@freebsd.org>> mailing list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> >> > To unsubscribe, send any mail to "freebsd-net-
> >>
> unsubscribe@freebsd.org<mailto:unsubscribe@freebsd.org><mailto:freebsd-
> net-unsubscribe@freebsd.org<mailto:freebsd-net-
> unsubscribe@freebsd.org>>"
> >> > _______________________________________________
> >> > freebsd-net@freebsd.org<mailto:freebsd-
> net@freebsd.org><mailto:freebsd-net@freebsd.org<mailto:freebsd-
> net@freebsd.org>> mailing list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> >> > To unsubscribe, send any mail to "freebsd-net-
> >>
> unsubscribe@freebsd.org<mailto:unsubscribe@freebsd.org><mailto:freebsd-
> net-unsubscribe@freebsd.org<mailto:freebsd-net-
> unsubscribe@freebsd.org>>"
> >> >
> >> >
> >> > _______________________________________________
> >> > freebsd-net@freebsd.org<mailto:freebsd-net@freebsd.org> mailing
> list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> >> > To unsubscribe, send any mail to "freebsd-net-
> >> unsubscribe@freebsd.org<mailto:unsubscribe@freebsd.org>"
> >> >
> >
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32AB5C9615CC494997D9ABB1DB12783C024C6FC072>