From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hang at boot.
Date: Fri, 1 Apr 2005 19:31:17 +0100 [thread overview]
Message-ID: <7d3fb50c36a181cff273e6a72c34064e@quintile.net> (raw)
In-Reply-To: <BAY18-F12B417603644116697CEEC95380@phx.gbl>
The problem appears to be your Intel Gigabit ether card.
It may be as simple as adding support for the device id of your
card - looking at the source some cards are supported, some not
and yours is not listed; somone else on the list may be able to help more
or you could just experiment.
To get yourself going I suggest you swap the ether card for
an more boring 100Mb one, the wiki lists quite a few supported cards:
http://plan9.bell-labs.com/wiki/plan9/Supported_PC_hardware/index.html
-Steve
next prev parent reply other threads:[~2005-04-01 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1112378836.743.9fans@cse.psu.edu>
2005-04-01 18:12 ` Jean-Baptiste Campesato
2005-04-01 18:31 ` Steve Simon [this message]
2005-04-01 18:46 ` jmk
2005-04-01 19:36 ` Steve Simon
2005-04-01 19:45 ` jmk
2005-04-02 5:50 ` lucio
2005-04-01 22:00 ` Charles Forsyth
2005-04-01 22:26 ` Charles Forsyth
2005-04-01 20:29 Jean-Baptiste Campesato
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=7d3fb50c36a181cff273e6a72c34064e@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).