public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robboy, David G" <david.g.robboy@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] 2.4.4 stability on Lions
Date: Wed, 23 May 2001 21:54:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005664@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005642@msgid-missing>

> 
> Thanks Asit.  Is there a way to temporarily disable the on 
> board NIC?  Our
> installer always defaults to eth0 for network installs.  As 
> luck would have
> it, the e100 modules get loaded before our add in 3com.

If you build a kernel with the 3com driver linked in (not a module), and
don't configure in the e100, it should work.  I just did that with a Tulip
card and it's working.

David

> -----Original Message-----
> From: Michael Madore [mailto:mmadore@turbolinux.com]
> Sent: Wednesday, May 23, 2001 1:54 PM
> To: Mallick, Asit K
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] 2.4.4 stability on Lions
> 
> 
> Thanks Asit.  Is there a way to temporarily disable the on 
> board NIC?  Our
> installer always defaults to eth0 for network installs.  As 
> luck would have
> it, the e100 modules get loaded before our add in 3com.
> 
> On Wed, May 23, 2001 at 01:06:21PM -0700, Mallick, Asit K wrote:
> > Mike,
> > 
> > A workaround should be implemented and I will need to 
> investigate on this.
> > In the mean time you can use an add-on Intel 10/100 
> ethernet card and this
> > problem is not present.
> > 
> > Thanks,
> > Asit
> > 
> > 
> > > -----Original Message-----
> > > From: Michael Madore [mailto:mmadore@turbolinux.com]
> > > Sent: Wednesday, May 23, 2001 11:23 AM
> > > To: David Mosberger
> > > Cc: linux-ia64@linuxia64.org
> > > Subject: Re: [Linux-ia64] 2.4.4 stability on Lions
> > > 
> > > 
> > > What I meant to say was it gets violently ill. ;-)
> > > 
> > > You are correct, it "get's stuck"  It is the same problem 
> > > that was discussed
> > > on the list in February.
> > > 
> > > On Wed, May 23, 2001 at 11:21:25AM -0700, David Mosberger wrote:
> > > > >>>>> On Wed, 23 May 2001 09:43:10 -0700, Michael Madore 
> > > <mmadore@turbolinux.com> said:
> > > > 
> > > >   Michael> Well, almost everything.  I still have the 
> > > problem with the
> > > >   Michael> onboard e100 network adapter.  This is the 
> problem where
> > > >   Michael> transferring certain files via nfs causes nfs to die.
> > > > 
> > > > Die or "get stuck"?  It shouldn't die.
> > > > 
> > > > 	--david
> > > 
> > > -- 
> > > Mike Madore
> > > Senior Software Engineer
> > > TurboLinux, Inc.
> > > (650)228-5203
> > > 
> > > _______________________________________________
> > > Linux-IA64 mailing list
> > > Linux-IA64@linuxia64.org
> > > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> > > 
> > 
> > 
> > _______________________________________________
> > Linux-IA64 mailing list
> > Linux-IA64@linuxia64.org
> > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 
> -- 
> Mike Madore
> Senior Software Engineer
> TurboLinux, Inc.
> (650)228-5203
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 



  parent reply	other threads:[~2001-05-23 21:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 18:18 [Linux-ia64] 2.4.4 stability on Lions Michael Madore
2001-05-22 19:25 ` McCaffity, Ray
2001-05-22 21:06 ` Matt_Domsch
2001-05-22 21:57 ` Michael Madore
2001-05-22 22:33 ` Wiegrefe, Don J
2001-05-22 22:43 ` Michael Madore
2001-05-23  1:34 ` Matt_Domsch
2001-05-23 16:43 ` Michael Madore
2001-05-23 18:21 ` David Mosberger
2001-05-23 18:23 ` Michael Madore
2001-05-23 20:06 ` Mallick, Asit K
2001-05-23 20:53 ` Michael Madore
2001-05-23 21:54 ` Robboy, David G [this message]
2001-05-23 22:26 ` Michael Madore

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=marc-linux-ia64-105590693005664@msgid-missing \
    --to=david.g.robboy@intel.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox