public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Buckingham <peter@pantasys.com>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: linux-kernel@vger.kernel.org, kevin.mullins@asusts.com,
	JASON_RILEY@asusts.com, karim@opersys.com,
	Andreas Koch <koch@esa.informatik.tu-darmstadt.de>,
	Linus Torvalds <torvalds@osdl.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	dave.jones@redhat.com
Subject: Re: ASUS K8N-DL Beta BIOS AKA PROBLEM: Devices behind	PCI	Express-to-PCI bridge not mapped
Date: Wed, 29 Jun 2005 10:17:05 -0700	[thread overview]
Message-ID: <42C2D791.9020204@pantasys.com> (raw)
In-Reply-To: <1120064967.3511.4.camel@oscar.metro1.com>

Hi Sean,

Sean Bruno wrote:
>>>Aperture from northbridge cpu 0 too small (32 MB)
>>>No AGP bridge found
>>>Your BIOS doesn't leave a aperture memory hole
>>>Please enable the IOMMU option in the BIOS setup
>>>This costs you 64 MB of RAM
>>
>>this isn't a big deal, but linux expects an apperture of >= 64MB, you 
>>may want to change this setting in your bios.
>>
> 
> If the system doesn't have an AGP slot, would it even need to leave an
> aperture(this mobo has a 16x PCI-E slot for the video)?

The IOMMU is still used for some devices that are only 32bit in a 64bit 
OS. Linux actually will allocate the 64MB anyway, so it doesn't hurt to 
have the bios and linux in sync ;-)

> Would this require ASUS to modify their board/bios?

yep, good luck!

>>>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
>>>    ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace, AE_NOT_FOUND
>>>search_node ffff810142857180 start_node ffff810142857180 return_node 0000000000000000
>>>    ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0._PRT] (Node ffff810142857140), AE_NOT_FOUND
>>
>>same as above, the acpi tables are missing information.
> 
> So, this is something that ASUS "needs" to fix or is it something that
> needs to change in the ACPI part of the kernel?

Yeah, this is again something that ASUS would need to fix in their bios. 
I'm not sure how important it is though...

peter

      reply	other threads:[~2005-06-29 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 22:05 ASUS K8N-DL Beta BIOS Sean Bruno
2005-06-29  1:46 ` Karim Yaghmour
2005-06-29  4:22   ` ASUS K8N-DL Beta BIOS AKA PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped Sean Bruno
2005-06-29  4:35     ` Sean Bruno
2005-06-29 17:01     ` Peter Buckingham
2005-06-29 17:09       ` Sean Bruno
2005-06-29 17:17         ` Peter Buckingham [this message]

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=42C2D791.9020204@pantasys.com \
    --to=peter@pantasys.com \
    --cc=JASON_RILEY@asusts.com \
    --cc=dave.jones@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=karim@opersys.com \
    --cc=kevin.mullins@asusts.com \
    --cc=koch@esa.informatik.tu-darmstadt.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.bruno@dsl-only.net \
    --cc=torvalds@osdl.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