All of lore.kernel.org
 help / color / mirror / Atom feed
From: rick@dgii.com (Rick Richardson)
To: ultralinux@vger.kernel.org
Subject: Re: Still no go with the happy meal on the scsi/hme card on sun ultra 10
Date: Wed, 18 Nov 1998 23:25:52 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-91148320602842@msgid-missing> (raw)

Stephan van Hienen writes...
> tried the new cvs kernel (2.1.128)
> 
> but still get timeouts on the happy meal eth0 card in my kernel
> 
> eth1 (onboard happy meal)
> eth2,eth3 (dec 450)
> work ok
> 
> this was on the list before, but i hoped it was fixed
> 
> som1 is looking at this ?
> 
> i can look for things here, but since i'm not a programmer myself, i can't
> try to fix it :(


I just tried to load UP1.1 on an Ultra 30.  This particular ultra
30 has a broken onboard ethernet controller, so we have a scsi/hme
card in it.

The tftpboot (boot /pci@1f,4000/pci@4/SUNW,hme@0,1) works (yippee,
first time we've gotten even this far on an Ultra 30) and we get to
the install screens.

But thats it.  The ethernet driver keeps complaining that "Link down,
Cable problem?" when it tries to access the NFS mirror.  But of course
there is no cable problem, since the tftpboot process worked fine.

So I guess I can confirm that there seems to be something wrong with
the ethernet driver, if that helps.

Unfortunately, I *am* a programmer, but I can't do anything to help
this situation until I get at least one of these confounded Ultra's
loaded in the first place.

-Rick

-- 
Rick "The Hack" Richardson  rick@dgii.com http://RickRichardson.freeservers.com

             reply	other threads:[~1998-11-18 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-18 23:25 Rick Richardson [this message]
1998-11-19 13:50 ` Still no go with the happy meal on the scsi/hme card on sun ultra 10 David S. Miller

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-ultrasparc-91148320602842@msgid-missing \
    --to=rick@dgii.com \
    --cc=ultralinux@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.