From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <509071940711200624g24959235pec792d4496f0ed86@mail.gmail.com>
Date: Tue, 20 Nov 2007 09:24:56 -0500
From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] SATA controller found by kernel but not 9load
In-Reply-To: <599f06db0711200220m24c424acrf3d7ca58b6040f8a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <509071940711191935n72d0ae6fv2f17458446142e27@mail.gmail.com>
	<599f06db0711200220m24c424acrf3d7ca58b6040f8a@mail.gmail.com>
Topicbox-Message-UUID: 026a63d6-ead3-11e9-9d60-3106f5b1d025

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.