From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 won't install on my system
Date: Fri, 23 Jan 2009 08:25:29 -0800 [thread overview]
Message-ID: <13426df10901230825t3dbaf0b2v86bcd9c415a61537@mail.gmail.com> (raw)
In-Reply-To: <05da77cc-86c2-478c-8369-4fed0401e386@r15g2000prd.googlegroups.com>
On Fri, Jan 23, 2009 at 1:49 AM, elot <samtholi40@gmail.com> wrote:
> hey,i have an intel core 2 duo CPU E7300 with an ASUS motherboard and
> an nvidia 8500GT/PCI/SSE2 graphic card.i tried to install plan9 but it
> stops at a part that says irq 3 routing and wont even bring up the
> boot options.i looked at the list of supported hardware and i've been
> on the freenodes but no luck.what could be wrong?
It would be useful to see your full output. This could be a bad IRQ
routing table, coupled with the BIOS messing up IRQ setup in a way
that Windows or Linux might fix but Plan 9 can not.
At this point, on SMP machines, there are three tables that could be
used to provide routing for IRQs:
- $PIR (frequently wrong, not usually used if _MP_ is found)
- _MP_ mostly right but ...
- ACPI usually right (but not always!)
Plan 9 does not parse acpi yet. This is going to hurt us more and more
because in many case, motherboard manufacturers do a very poor job of
setting up the other two tables. We've seen cases where the $PIR table
was just copied from one board to a totally different board with no
changes.
If somebody wants a project ACPI is out there waiting. Warning: ACPI
will make your eyes bleed; it's that bad unless you think FOUR CHAR
NAME _ARE GOOD _FOR ALL_ USES (well that's the least worst part of
it).
Can you get some serial output for us to see?
ron
next prev parent reply other threads:[~2009-01-23 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 9:49 elot
2009-01-23 14:24 ` erik quanstrom
2009-01-23 16:25 ` ron minnich [this message]
2009-01-23 16:33 ` erik quanstrom
2009-01-26 10:31 ` elot
2009-01-26 13:26 ` 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=13426df10901230825t3dbaf0b2v86bcd9c415a61537@mail.gmail.com \
--to=rminnich@gmail.com \
--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).