From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Vanilla Plan 9 or one of the flavors?
Date: Mon, 6 Jan 2014 12:29:33 -0500 [thread overview]
Message-ID: <4951.1389029373@lunacy.ugrad.cs.cmu.edu> (raw)
In-Reply-To: <00CD3410-7B8A-4120-8BE3-48FECDD0E19A@gmail.com>
> I mentioned this. I don't want to buy a new piece of hardware when
> I could fix the issue by using a different software stack, but if
> necessary, that's what I'll end up doing (buying the hardware).
Very frequently the problem is nothing more than missing case arms
in a couple of switch() statements. The most recent one I submitted
was:
http://plan9.bell-labs.com/sources/patch/applied/ether8169-macv34/
If you have a detailed PCI-device listing (obtainable via a BSD or
Linux live CD), it is pretty easy to figure out which driver should
be supporting your card and whether the reason it isn't is missing
case arms. If you've been around the block a few times it takes
an hour or two to diagnose, patch, test, and submit the patch to
Bell Labs.
However, if you're just getting started it can take you a week or
two of fussing, which may compare unfavorably with picking up a
known-good Ethernet card for $5 from eBay/NewEgg/etc. Having
a working Ethernet makes it easier for you to get started, and
once you're started you can go back and figure out what's wrong
with the built-in Ethernet.
Dave Eckhardt
next prev parent reply other threads:[~2014-01-06 17:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 2:02 Alex Jordan
2013-12-31 2:07 ` Alex Jordan
2013-12-31 4:33 ` erik quanstrom
2014-01-05 23:54 ` Alex Jordan
2014-01-06 0:03 ` Patryk Laurent
2014-01-06 4:03 ` Steven Stallion
2014-01-06 4:36 ` Lyndon Nerenberg
2014-01-06 4:41 ` Steven Stallion
2014-01-06 4:53 ` Lyndon Nerenberg
2014-01-06 5:01 ` Steven Stallion
2014-01-06 5:09 ` Lyndon Nerenberg
2014-01-06 5:13 ` andrey mirtchovski
2014-01-06 5:16 ` Steven Stallion
2014-01-06 5:28 ` Patryk Laurent
2014-01-06 5:12 ` Bruce Ellis
2014-01-06 15:35 ` a
2014-01-06 16:40 ` Aram Hăvărneanu
2014-01-06 16:54 ` Anthony Sorace
2014-01-06 17:21 ` lucio
2014-01-06 17:09 ` tlaronde
2014-01-06 17:25 ` lucio
2014-01-06 20:13 ` Kurt H Maier
2014-01-06 4:42 ` balaji
2014-01-06 20:05 ` Kurt H Maier
2014-01-06 7:08 ` Alex Jordan
2014-01-06 7:39 ` cinap_lenrek
2014-01-06 7:49 ` Alex Jordan
2014-01-06 10:48 ` Paul Clark
2014-01-06 17:29 ` Dave Eckhardt [this message]
2014-01-06 12:20 ` Richard Miller
2014-01-06 13:29 ` erik quanstrom
2014-01-07 6:58 ` Alex Jordan
2014-01-07 8:32 ` Andrés Domínguez
2014-01-07 14:00 ` erik quanstrom
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=4951.1389029373@lunacy.ugrad.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--cc=9fans@9fans.net \
/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).