9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] laptop install woes
Date: Sat, 15 Aug 2009 13:34:01 -0400	[thread overview]
Message-ID: <2270ba97b28b19fe21b17e6251ee9b4f@quanstro.net> (raw)
In-Reply-To: <575e1a150908150410q1753cc4ar2ce39b634e9c132d@mail.gmail.com>

> I also tried booting from Erik's atom iso, but don't get very far. eg:
> PBS1
> Plan 9 from Bell Labs
> ELCR: 0CA0
> pcirouting: south bridge 10de, 0260 not found
> aoepnp(<nil>)
> found 11 e820 entries
> Boot devices: fd0 fd1
> boot from:
>
> It doesn't detect IDE controller, so no local disk/CD-ROM to boot from.

sorry.

i did turn off probing legacy ports unless a recognized
pci device was found.  this was paranoia on my part.  (i hope.)
just trying to get past our sata drives with ide programming interface
problem.  i've turned blind probing back on and will put out a new iso
shortly.  i've also added jmicron ide.

> North Bridge: NVIDIA C51MV
> South Bridge: MCP51 - ignored

this is okay.

> NVIDIA GeForce Go 6100 graphics - works fine with 1024x768x16 VESA

using the native nvidia driver is proablly a better idea.

> NVIDIA MCP51 ethernet controller - not detected

there's no forcedeth support for plan 9.  sorry

> NVIDIA MCP51 PATA controller - buggy? see below...

the controller should be just fine.  i used to have an
nvidia controller and it worked just fine until it was
taken out by an electricial storm.

ati and intel chipsets tend to have the best support.

- erik



  reply	other threads:[~2009-08-15 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 11:10 Jamie Gavahan
2009-08-15 17:34 ` erik quanstrom [this message]
2009-08-15 18:46   ` Jamie Gavahan
2009-08-15 21:16     ` erik quanstrom
2009-08-16  1:12     ` matt
2009-08-16 20:46       ` Jamie Gavahan

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=2270ba97b28b19fe21b17e6251ee9b4f@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).