From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SATA controller found by kernel but not 9load
Date: Tue, 20 Nov 2007 22:03:03 -0500 [thread overview]
Message-ID: <0794fde844d9d71f0de4ca4dc6356431@quanstro.net> (raw)
In-Reply-To: <509071940711201841y67064b22t830244a2f8b9fb56@mail.gmail.com>
> I'm beginning to suspect that the kernels on the CD in /386 don't
> match their descriptions in /sys/src/9/pc. Maybe it's simply timing as
> things die, but I can't get them to show me there ever being a fossil
> process.
>
> I have three SATA hard disks attached. Plan 9 identifies them as
> sdE[013]; the BIOS identifies them as Channel 2 Master, Channel 3
> Master, and Channel 3 Slave (which would lead me to expect sdE[023] or
> sdE0+sdF[01]). I also have an IDE cdrom on sdC0 (Channel 0 Master in
> the BIOS).
> Anthony
master/slave/channel doesn't make asense for sata. it's all
point-to-point. all sata drives attached to a single hba will
show up as the same drive letter, in your case E, the first sata
drive letter.
in any case, i think you are right. it is a timing issue. since ahci drives
are hot-pluggable, the drive might not be available immediately on boot.
i'll take a look. i'm not sure if fossil needs more patience or sdiahci
needs to force disks up sooner. perhaps a combination of the two.
- erik
next prev parent reply other threads:[~2007-11-21 3:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 3:35 Anthony Sorace
2007-11-20 10:20 ` Gorka Guardiola
2007-11-20 14:24 ` Anthony Sorace
2007-11-20 14:34 ` erik quanstrom
2007-11-21 1:13 ` Anthony Sorace
2007-11-21 1:20 ` erik quanstrom
2007-11-21 2:41 ` Anthony Sorace
2007-11-21 3:03 ` erik quanstrom [this message]
2007-11-21 13:26 ` erik quanstrom
2007-11-22 4:30 ` Anthony Sorace
2007-11-22 12:33 ` erik quanstrom
2007-11-22 13:03 ` erik quanstrom
2007-11-27 4:09 ` Anthony Sorace
2007-11-21 1:33 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=0794fde844d9d71f0de4ca4dc6356431@quanstro.net \
--to=quanstro@quanstro.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).