From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <05da77cc-86c2-478c-8369-4fed0401e386@r15g2000prd.googlegroups.com>
References: <05da77cc-86c2-478c-8369-4fed0401e386@r15g2000prd.googlegroups.com>
Date: Fri, 23 Jan 2009 08:25:29 -0800
Message-ID: <13426df10901230825t3dbaf0b2v86bcd9c415a61537@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] plan9 won't install on my system
Topicbox-Message-UUID: 8600b046-ead4-11e9-9d60-3106f5b1d025

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