From: "Tvrtko A. Uršulin" <tvrtko@croadria.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Network interface problem
Date: Wed, 11 Feb 2004 11:59:12 +0100 [thread overview]
Message-ID: <200402111159.12024.tvrtko@croadria.com> (raw)
In-Reply-To: <E1Aqrpl-0006QZ-00@wisbech.cl.cam.ac.uk>
On Wednesday 11 February 2004 11:43, Keir Fraser wrote:
> > This is from normal linux:
> >
> > Feb 10 16:08:47 xen kernel: Broadcom Gigabit Ethernet Driver bcm5700 with
> > Broadcom NIC Extension (NI
> > CE) ver. 6.2.17 (07/14/03)
> > Feb 10 16:08:47 xen kernel: eth0: HP NC7760 Gigabit Server Adapter found
> > at mem fe000000, IRQ 12, no
> > de addr 000802f7c1fa
> > Feb 10 16:08:47 xen kernel: eth0: Broadcom BCM5703 Integrated Copper
> > transceiver found
> > Feb 10 16:08:47 xen kernel: eth0: Scatter-gather ON, 64-bit DMA ON, Tx
> > Checksum ON, Rx Checksum ON,
> > 802.1Q VLAN ON, NAPI ON
>
> This isn't output from the standard Linux tg3 driver, which is what
> Xen uses. In fact, I don't think this driver is included in Linux
> 2.4.24. Are you runnign a different Linux version, or did you install
> this driver from another source?
Yes, you are right. :) This is the output for 2.4.21-SuSE kernel. But
previously, on the same server I was running vanilla 2.4.24 (+ grsec) and I
am 100% sure both cards were operational because they were heavily used.
Because I made a clean install for the purpose of trying Xen, I have never
bothered to compile own kernel because it is not needed.
If you need the actual output I can compile the kernel and provide it. But if
you only need the proof that both cards are working can you trust my word for
it?
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-11 10:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 10:05 Network interface problem Tvrtko A. Uršulin
2004-02-11 10:13 ` Rolf Neugebauer
2004-02-11 10:15 ` Keir Fraser
2004-02-11 10:34 ` Tvrtko A. Uršulin
2004-02-11 10:43 ` Keir Fraser
2004-02-11 10:59 ` Tvrtko A. Uršulin [this message]
2004-02-11 11:01 ` Keir Fraser
2004-02-11 11:46 ` Tvrtko A. Uršulin
2004-02-11 11:57 ` Keir Fraser
2004-02-11 12:14 ` Tvrtko A. Uršulin
2004-02-11 12:25 ` Ian Pratt
2004-02-11 12:40 ` Ian Pratt
2004-02-11 12:53 ` Tvrtko A. Uršulin
2004-02-11 13:40 ` Keir Fraser
2004-02-11 13:54 ` Keir Fraser
2004-02-17 5:32 ` stevegt
2004-02-17 7:44 ` Keir Fraser
2004-02-11 13:56 ` Tvrtko A. Uršulin
2004-02-11 13:57 ` Keir Fraser
2004-02-11 10:51 ` Rolf Neugebauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200402111159.12024.tvrtko@croadria.com \
--to=tvrtko@croadria.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.