From: <jtrostel-mn4gwa5WIIQysxA8WJXlww@public.gmane.org>
To: mochel-3NddpPZAyC0@public.gmane.org
Cc: John M Trostel
<john.trostel-+vhbC7un7QRBDgjK7y7TUQ@public.gmane.org>,
ACPI-list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: Can't Find PCI: primary perr bus 01 with ACPI on
Date: Fri, 6 Sep 2002 20:26:14 -0400 [thread overview]
Message-ID: <E17nTRe-0002pN-00@hall.mail.mindspring.net> (raw)
I'm using 2.4.19... with patches from Sergio Basto at http://codecs.home.sapo.pt/acpi/
>
>
> On Fri, 6 Sep 2002, John M Trostel wrote:
>
> > I'm stymied (again). Perhaps it is the crappy ACPI that's in my BIOS.
> > If I turn off acpi (acpi=off on boot prompt), then my PCI bus 01 is
> > detected (and consequently my promise chips, and my hard drives).
> >
> > ... I get:
> > PCI: Discovered primary perr bus 01 [IRQ]
> >
> > in the boot messages
> >
> > If I turn on acpi, then I never see the 'PCI: Discovered...' message
> > shown above.
> >
> > Is there someway to _force_ that bus to be detected (regardless of
> > ACPI)? Is there somewhere in the DSDT I can poke around to make the bus
> > reappear?
>
> What kernel are you using?
>
> -pat
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
next reply other threads:[~2002-09-07 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 0:26 jtrostel-mn4gwa5WIIQysxA8WJXlww [this message]
[not found] ` <E17nTRe-0002pN-00-d6NqQtMd5t6HWO7mcI6GbnHfL+gkQO6L@public.gmane.org>
2002-09-07 20:30 ` Re: Can't Find PCI: primary perr bus 01 with ACPI on Patrick Mochel
[not found] ` <Pine.LNX.4.44.0209071328300.1021-100000-yZQdDDOm3n9ZQn2sFP3R7eTW4wlIGRCZ@public.gmane.org>
2002-09-09 16:58 ` John M Trostel
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=E17nTRe-0002pN-00@hall.mail.mindspring.net \
--to=jtrostel-mn4gwa5wiiqysxa8wjxlww@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=john.trostel-+vhbC7un7QRBDgjK7y7TUQ@public.gmane.org \
--cc=mochel-3NddpPZAyC0@public.gmane.org \
/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