RE: em driver problem on vmware
- From: "Ricky Charlet" <RCharlet@xxxxxxxxxxxx>
- Date: Wed, 3 Nov 2010 21:53:02 -0700
FYI,
to close this thread off, I just had a build problem, I forgot to build e1000/if_lem.c. Did that and now it works.
So this becomes a success report of sorts... if anyone else is handcuffed (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@xxxxxxxxxxx [mailto:owner-freebsd-
net@xxxxxxxxxxx] 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@xxxxxxxxx]
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@xxxxxxxxxxx<mailto:jmallett@xxxxxxxxxxx>> 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@xxxxxxxxxxxx<mailto:RCharlet@xxxxxxxxxxxx>> wrote:
Hi Julie,[mailto:juli@xxxxxxxxxxxxxxxxxx<mailto:juli@xxxxxxxxxxxxxxxxxx>] On
My entire dmesg output is attached.
With much appreciation
Ricky
-----Original Message-----
From: juli@xxxxxxxxxxxxxxxxxx<mailto:juli@xxxxxxxxxxxxxxxxxx>
<RCharlet@xxxxxxxxxxxx<mailto:RCharlet@xxxxxxxxxxxx>>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
9.0,wrote:
Thanks Jack,em0 is not configured, so link partners are also unaware of it.
The failure is that ifconfig is unaware of em0. My
ifconfig em0agreeing looks positive and would not indicate a problem)
ifconfig: interface em0 does not exist
and you already have my dmes stuff on em0 (which I am now up to
My amalgamated file is a private combination of some 8.1, some
[mailto:jfvogel@xxxxxxxxx<mailto:jfvogel@xxxxxxxxx>]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.
file I am using is attached.
For the curious and the diligent, the e1000/if_em.c
Ricky
From: Jack Vogel
youSent: Friday, October 29, 2010 7:13 PMafter
To: Ricky Charlet
Cc: freebsd-net@xxxxxxxxxxx<mailto:freebsd-net@xxxxxxxxxxx>
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
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
<RCharlet@xxxxxxxxxxxx<mailto:RCharlet@xxxxxxxxxxxx><mailto:RCharlet@adtrying to use, my last checked in?anything,
More on the failure, does it ping, does its link partner see
etc, etc..
Jack
On Fri, Oct 29, 2010 at 6:27 PM, Ricky Charlet
aranet.com<mailto:RCharlet@xxxxxxxxxxxx>>> wrote:
exactlyFYI,
That dmesg output I get from my franken-driver on vmware is
0x203fthe 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-
onmem 0xd8940000-0xd895ffff,0xd8900000-0xd890ffff irq 18 at device 0.0
net@xxxxxxxxxxx><mailto:owner-freebsd-<mailto:owner-freebsd->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@xxxxxxxxxxx<mailto:owner-freebsd-
net@xxxxxxxxxxx<mailto:owner-freebsd-net@xxxxxxxxxxx><mailto:owner-net@xxxxxxxxxxx<mailto:net@xxxxxxxxxxx>> [mailto:owner-freebsd-
<mailto:owner->
Of Ricky Charletfreebsd-net@xxxxxxxxxxx<mailto:freebsd-net@xxxxxxxxxxx>>] On Behalf
net@xxxxxxxxxxx><mailto:freebsd-net@xxxxxxxxxxx<mailto:freebsd-Sent: Friday, October 29, 2010 5:07 PM
To: freebsd-net@xxxxxxxxxxx<mailto:freebsd-
net@xxxxxxxxxxx>>
amd64Subject: em driver problem on vmwarefreebsd8.1 (and an appropriate touch of if_var.h). I'm running an
Howdy,
I have freebsd80-release with an upgraded em0 driver from
203fon a vmware vm. And I see this in dmesg:
------------cut-------------
em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x2000-
0.0mem 0xd8940000-0xd895ffff, 0xd8900000-0xd890ffff irq 18 at device
net@xxxxxxxxxxx><mailto:freebsd-net@xxxxxxxxxxx<mailto:freebsd-on pci2
em0: Memory Access and/or Bus Master bits were not setswitch (just copied over the sys/dev/e1000 directory from 8.1 and
em0: [FILTER]
em0: Ethernet address: 00:0c:29:57:d7:7f
------------paste------------
Now, I certainly may have done something wrong with my code
defined drbr_needs_enqueue in if_var.h). I'll start double checking.
working/failing on a vmware vm?
But, on the other hand, has anyone seen the new em driver
Thanks
---
Ricky Charlet
Adara Networks
USA 408-433-4942
_______________________________________________
freebsd-net@xxxxxxxxxxx<mailto:freebsd-
net@xxxxxxxxxxx>> mailing list
unsubscribe@xxxxxxxxxxx<mailto:unsubscribe@xxxxxxxxxxx><mailto:freebsd-http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-
net-unsubscribe@xxxxxxxxxxx<mailto:freebsd-net-
unsubscribe@xxxxxxxxxxx>>"
net@xxxxxxxxxxx><mailto:freebsd-net@xxxxxxxxxxx<mailto:freebsd-_______________________________________________
freebsd-net@xxxxxxxxxxx<mailto:freebsd-
net@xxxxxxxxxxx>> mailing list
unsubscribe@xxxxxxxxxxx<mailto:unsubscribe@xxxxxxxxxxx><mailto:freebsd-http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-
net-unsubscribe@xxxxxxxxxxx<mailto:freebsd-net-
unsubscribe@xxxxxxxxxxx>>"
list
_______________________________________________
freebsd-net@xxxxxxxxxxx<mailto:freebsd-net@xxxxxxxxxxx> mailing
http://lists.freebsd.org/mailman/listinfo/freebsd-netunsubscribe@xxxxxxxxxxx<mailto:unsubscribe@xxxxxxxxxxx>"
To unsubscribe, send any mail to "freebsd-net-
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: net.inet.tcp.slowstart_flightsize in 8-STABLE
- Next by Date: Re: RFC: Updated ARP Queue patch...
- Previous by thread: Re: kern/151441: [iwi] iwi module not work properly using HP nc6220
- Next by thread: if_msk.c patch for yukon ec hanging
- Index(es):
Relevant Pages
|
