9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] SATA controller found by kernel but not 9load
Date: Mon, 19 Nov 2007 22:35:23 -0500	[thread overview]
Message-ID: <509071940711191935n72d0ae6fv2f17458446142e27@mail.gmail.com> (raw)

I'm trying to install a new system and I've run into a problem: the
SATA controller is recognized fine by the kernel, but not by 9load.
The kernel tells me:

#S/sdE: ahci: port 0xe0000000: hba sss 0; ncs 31; coal 1; mports 3;
led 1; clo 1; ems 0
#S/sdE: sb600: sata-II with 4 ports

but 9load has nothing at all to say about it. Once I'm up with a
kernel (say, loaded off the CD which is still attached to (p)ATA and
works fine with 9load), I can access it without issue. In the normal
kernel, this is handled by sdiahci.c, which seems to be an older
version in 9load.

How straight-forward is it to move the kernel version of the driver
into 9load? I don't suppose anyone's already looked at that for this
device?

As an aside: how space-constrained are the kernels used for install
currently? It would be very nice to have fs(3) in there so an install
can be done with mirrored disks, rather than having to retrofit it
after the fact.
Anthony


             reply	other threads:[~2007-11-20  3:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  3:35 Anthony Sorace [this message]
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
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=509071940711191935n72d0ae6fv2f17458446142e27@mail.gmail.com \
    --to=anothy@gmail.com \
    --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).