9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: venti+fossil problems on new install
Date: Thu, 21 Sep 2006 11:19:50 -0700	[thread overview]
Message-ID: <20060921111420.H25801@orthanc.ca> (raw)
In-Reply-To: <200609210750.aa89075@salmon.maths.tcd.ie>

> I think I've figured out part of my problem.  A closer look at FreeBSD's
> boot messages shows that the full path to the disk driver is
>
> atapci0: <Intel ICH6M SATA150 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 17 at device 31.2 on pci0
> ata0: <ATA channel 0> on atapci0

> I think that I am running into trouble with that `Intel ICH6M
> SATA150 controller'.  I assume that's not supported.

No, it works.  I have Plan 9 running on my D610 and it has no problem with 
the disk controller.  Cardbus and Ethernet on the other hand ...  (I have 
some cardbus driver patches from Charles and jmk that I'm slowly working 
my way through.)

The only difference between our setup is that I don't have a local venti, 
just a local fossil.  But I've pounded on the disk reasonably hard (lots 
of compiles) and haven't had any issues.

--lyndon


  parent reply	other threads:[~2006-09-21 18:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  6:50 John Stalker
2006-09-21  8:13 ` erik quanstrom
2006-09-21 18:19 ` Lyndon Nerenberg [this message]
2006-09-21 18:25   ` erik quanstrom
2006-09-21 18:51     ` jmk
2006-09-21 20:27       ` C H Forsyth
2006-09-21 20:47     ` Charles Forsyth
2006-09-21 20:56       ` jmk
2006-09-21 21:08         ` Charles Forsyth
2006-09-21 21:50           ` erik quanstrom
2006-09-21 22:00             ` Charles Forsyth
2006-09-21 22:16               ` erik quanstrom
2006-09-21 22:31                 ` Charles Forsyth
2006-09-21 22:31                 ` jmk
2006-09-21 23:22                   ` erik quanstrom
2006-09-21 23:28                     ` geoff
2006-09-21 23:47                       ` geoff
2006-09-22  0:05                         ` erik quanstrom
2006-09-22  0:24                           ` Russ Cox
2006-09-22  0:50                             ` erik quanstrom
2006-09-22  1:25                               ` jmk
2006-09-22  7:23                             ` John Stalker
2006-09-22 11:23                               ` erik quanstrom
2006-09-22 17:30                                 ` John Stalker
2006-09-22 17:45                                   ` erik quanstrom
2006-09-22 19:48                                     ` John Stalker
2006-09-22 20:09                                       ` erik quanstrom
2006-09-22 20:50                                         ` John Stalker
2006-09-22 21:06                                           ` erik quanstrom
2006-09-22  0:29                           ` jmk
2006-09-21 23:52                       ` erik quanstrom
2006-09-21 23:59                       ` erik quanstrom
2006-09-22  0:50                         ` geoff
2006-09-22 16:39                           ` erik quanstrom
2006-09-23  5:24 Zoran Kolic
2006-09-23  6:51 ` John Stalker
2006-09-23 10:34   ` erik quanstrom
2006-09-23 15:04     ` Russ Cox

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=20060921111420.H25801@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).