From: Rolf Neugebauer <rolf.neugebauer@intel.com>
To: "Tvrtko A. Uršulin" <tvrtko@croadria.com>
Cc: rolf.neugebauer@intel.com, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net
Subject: Re: Network interface problem
Date: Wed, 11 Feb 2004 10:51:33 +0000 [thread overview]
Message-ID: <1076496692.8073.7.camel@wyvis> (raw)
In-Reply-To: <200402111134.51797.tvrtko@croadria.com>
On Wed, 2004-02-11 at 10:34, Tvrtko A. Uršulin wrote:
> On Wednesday 11 February 2004 11:15, Keir Fraser wrote:
> > > More problems:
> > >
> > > My server has onboard tg3, and additional 3c905 network card. While
> > > booting xen outputs:
> > >
> > > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> > > 00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
> > > tg3.c:v2.3 (November 5, 2003)
> > > tg3: Could not obtain valid ethernet address, aborting.
> > >
> > > And 3c905 becomes eth0 while tg3 is unavailable. What am I doing wrong?
> >
> > Does normal Linux 2.4.24 boot okay?
>
> Yes, both cards working just fine.
>
> > If not, it's a driver problem.
>
> What about that 'only one active ethernet card' Rolf Neugebauer said?
I don't think this is a problem. As keir pointed out there appears to be
a driver problem.
My comment was related to selecting which of the _detected_ ethernet
interface xen should use. Xen seem to have a problem with detecting your
tg3 card properly.
Rolf
[this time sending from an email address which is actually subscribed to
the mailing list...]
-------------------------------------------------------
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
prev parent reply other threads:[~2004-02-11 10:51 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
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 [this message]
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=1076496692.8073.7.camel@wyvis \
--to=rolf.neugebauer@intel.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=tvrtko@croadria.com \
--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.