public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4] forcedeth
Date: Sun, 09 Nov 2003 15:47:26 +0100	[thread overview]
Message-ID: <3FAE537E.4060907@colorfullife.com> (raw)
In-Reply-To: <1068387273.14427.13.camel@midux>

Markus Hästbacka wrote:

>usually when I boot up it mount's the remote filesystems, now it just
>failed, and I tryed to ping lan/internet IP's they failed. And I noticed
>that none of my cards were working. this is the output of lspci for the
>card that works without forcedeth support in kernel and does not work if
>forcedeth is enabled: 
>01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>RTL-8139/8139C/8139C+ (rev 10)
>That's the main card that I use for lan/internet. ifconfig in the other
>hand told me that I had two working cards. first on had ip 192.168.0.2
>(that's right) and the new card had 192.168.1.1.
>
Please compare the mac addresses listed by ifconfig: I guess that the 
nics changed their names, the nforce chip is now eth0 and the realtek is 
eth1, or vice versa.

--
    Manfred


  reply	other threads:[~2003-11-09 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09  9:47 [PATCH 2.4] forcedeth Manfred Spraul
2003-11-09 14:14 ` Markus Hästbacka
2003-11-09 14:47   ` Manfred Spraul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-08  5:47 Carl-Daniel Hailfinger
2003-11-08  8:54 ` Christoph Hellwig
2003-11-08 10:51   ` Krzysztof Halasa
2003-11-08 17:55   ` Jeff Garzik
2003-11-08 20:23     ` Carl-Daniel Hailfinger
2003-11-09  0:15     ` Zwane Mwaikambo
2003-11-08 17:39 ` Jeff Garzik
2003-11-08 20:26 ` Markus Hästbacka
2003-11-08 20:59   ` Valdis.Kletnieks
2003-11-08 21:38     ` Markus Hästbacka
2003-11-09 12:36   ` Carl-Daniel Hailfinger
2003-11-09 14:07     ` Markus Hästbacka

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=3FAE537E.4060907@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midian@ihme.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox