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 09:34:32 -0500 [thread overview]
Message-ID: <25d6bab9f893d88c9739b992399eaff0@quanstro.net> (raw)
In-Reply-To: <509071940711200624g24959235pec792d4496f0ed86@mail.gmail.com>
the problem with 9load is that it was written before i did
support for the sb600 chipset. i now have a machine with
that northbridge, but i haven't finished with 9load.
i'm working on it right now.
(p.s. if you feel brave, /n/sources/contrb/quanstro/9loadsb600)
- erik
> Geoff asked about *noahciload in my plan9.ini; no, it is not set. None
> of the *no variables are.
>
> Gorka asked about my bios: yes, my bios knows about it. I've not got
> any of the legacy compatibility stuff turned on, as my initial
> experiments showed it made them not detected by the kernel, either
> (although there are several modes, and I didn't try them all).
>
> I tried the bios loading (sdB0), but that was unproductive. No example
> is given, but from the description in the man page I'd expect it to
> parallel sdC0 and look like sdB0!9fat!9pcf. When 9load(8) says about
> sdB0 "partitions are understood", I'm assuming it means in the same
> way sdC0 understands them.
>
> What's interesting, though, is that giving it sdC0!cdboot!9pccd.gz has
> no effect when I use the on-disk 9load, either (which works fine using
> the one on the cd), with the distributed plan9.ini (which does have
> some *no variables set). More poking to do.
next prev parent reply other threads:[~2007-11-20 14:34 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 [this message]
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
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=25d6bab9f893d88c9739b992399eaff0@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).