All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: ramdisk as root filesystem causes eth carrier errors -- SOLVED  (interesting issue)
Date: Tue, 07 Aug 2001 11:31:33 -0400	[thread overview]
Message-ID: <3B7009D5.32491B59@nortelnetworks.com> (raw)


A while back I posted an issue about getting carrier errors on eth1 when using
ramdisk as root filesystem, but it working perfectly when using an nfs-mounted
root filesystem.

Well, it seems that the culprit is the tulip driver.  After replacing it with
the latest and greatest from scyld, the problem seems to have gone away. 
Apparently some of the tulip drivers had issues with reporting full duplex when
the chip was really only at half duplex.

I am still at a loss to explain why the problem only showed up when using a
ramdisk root filesystem, when the identical kernel and an identical nfs-mounted
filesystem worked perfectly.  Anyone have any ideas?

Chris



-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

                 reply	other threads:[~2001-08-07 15:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B7009D5.32491B59@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.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 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.