LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Linux - Hardware (http://www.linuxquestions.org/questions/forumdisplay.php?f=18)
-   -   Your BIOS doesn't leave a aperture memory hole (http://www.linuxquestions.org/questions/showthread.php?t=624088)

harikrishnan81 02-26-2008 09:05 PM

Your BIOS doesn't leave a aperture memory hole
 
Hi all ,
I am getting an error in one of my server m/c with Phoenix motherboard ,AMD processor with 16GB RAM.The error message is

"CPU 0: aperture @ 0 size 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 "

Is this a bios problem or an os bug?The os is Red Hat Enterprise Linux ES release 4 (Nahant)(64Bit).

Can anyone help me to solve this error?
Thanks in advance
Regards,
Hari

harikrishnan81 02-26-2008 10:25 PM

Hi All,

Can i Solve this problem by using the boot option "iommu=memapper=3"
I saw this optin in a forum but this server is an importent m/c in our enviornment and i cant experiment on this.
Please help me to solve this if any one of you faced such a problem.
Thnaks and regard,
Hari

H_TeXMeX_H 02-27-2008 11:50 AM

Have you tried doing what it says:

Quote:

Please enable the IOMMU option in the BIOS setup

SuperSparky 04-23-2008 02:48 PM

Quote:

Originally Posted by H_TeXMeX_H (Post 3071704)
Have you tried doing what it says:

And people wonder why Linux isn't more mainstream with people like this to "help" you.

I get the same error, and I don't have an AGP machine (this is a GART error). My system is a PCIExpress system with two PCIE x16 slots. There is no IOMMU setting in the BIOS, nor any "aperture" setting. This aperture is just an AGP need.

Oddly enough, when looking at DMESG, it says it can't find an AGP bridge, but despite that, it decides to act as if there is one there. The problem isn't BIOS settings. The problem appears to be a poorly written kernel module not smart enough to realize that when there is no AGP hardware it shouldn't try to allocate resources for one.

How about a competent reply this time?

Quote:

Checking aperture...
CPU 0: aperture @ eb40000000 size 32 MB
Aperture 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
Mapping aperture over 65536 KB of RAM @ c000000

Emerson 04-23-2008 08:33 PM

If you don't have it and you don't need it ... why don't you disable it in kernel configuration!?

billymayday 04-23-2008 08:55 PM

Quote:

Originally Posted by SuperSparky (Post 3130639)
And people wonder why Linux isn't more mainstream with people like this to "help" you.

...

How about a competent reply this time?

As a fairly active particiant in the forum, I'd like to say, I think you're taking this comment out of context. I see a large number of posts where an error message pretty clearly states an error and proposed solution and the poster gives no indication of whether or not (s)he has followed the advice or not.


I wouldn't take the comment posted as insulting or frivolous, merely a valid question to ask before spending more time on the problem. More an issue of style than anything.

Consider sitting down face to face with the OP showing you that message on screen. Would your first question be what was asked? A lot of people would say yes.


My 2c

sumit dash 04-23-2008 09:21 PM

hi
 
Hi friend,
Its not a OS bug you have to update ur BIOS information, serch the compatible bios information from internet and update ur BIOS u r operating system would work fine.

Thank you
sumit

H_TeXMeX_H 04-24-2008 03:21 AM

Quote:

Originally Posted by SuperSparky (Post 3130639)
And people wonder why Linux isn't more mainstream with people like this to "help" you.

How about a competent reply this time?

Normally, I would not even reply to such a post.

If you were to search a bit on google you'd see that this usually happens when you have more than 4GB of RAM.

Read about IOMMU here:
http://en.wikipedia.org/wiki/IOMMU

Here's a good post on it in a mailing list describing the problem and solution:
http://www.x86-64.org/pipermail/disc...er/006680.html

note that both of the suggestions on there have been posted in this thread, one by harikrishnan81 and one by me. If you didn't know there actually is an IOMMU option in most new BIOSes.

I assure you that the kernel devs are much smarter than you and know much more than you on this subject, so don't say things like:

Quote:

Originally Posted by SuperSparky (Post 3130639)
The problem isn't BIOS settings. The problem appears to be a poorly written kernel module not smart enough to realize that when there is no AGP hardware it shouldn't try to allocate resources for one.

unless you have proof or know what you are talking about.

harikrishnan81 04-25-2008 12:41 AM

Hi All,
Sorry for the late replay.I was on leave due to some personal problems and due to that i couldnt check the repalys.
Thanks for the help.

In BIOS settings i couldn't find any IOMMU option.
Insted i tried with RHEL4.6 and its working fine.

Regards,
Hari

harikrishnan81 04-25-2008 12:43 AM

Thakyou all for spending your valuable time to help me.

SuperSparky 04-25-2008 02:25 PM

Quote:

Originally Posted by H_TeXMeX_H (Post 3131207)
Normally, I would not even reply to such a post.

If you were to search a bit on google you'd see that this usually happens when you have more than 4GB of RAM.

Read about IOMMU here:
http://en.wikipedia.org/wiki/IOMMU

Here's a good post on it in a mailing list describing the problem and solution:
http://www.x86-64.org/pipermail/disc...er/006680.html

note that both of the suggestions on there have been posted in this thread, one by harikrishnan81 and one by me. If you didn't know there actually is an IOMMU option in most new BIOSes.

I assure you that the kernel devs are much smarter than you and know much more than you on this subject, so don't say things like:



unless you have proof or know what you are talking about.

Oddly enough, my search on Google showed this thread. Hmmm....

Since this only started happening with recent versions of the Fedora version of the Kernel, a "solution" from 2005 didn't seem to apply.

Also, had you actually read my response as you seem to be indicating I do about posts spread all over the Internet, you would have noticed that I said no such settings are possible in my BIOS, and similar posts by people on other sites on the Internet seem to say the same thing, which is the purpose for the post in the first place. Why post a message about a Kernel issue giving instructions on how to fix it, unless the indicated "solution" is not possible? Your complaint about my "nasty" post doesn't make any sense.

It seemed quite obvious to me that "Why don't you do what it says" was the uncalled-for response to an obvious indication that the "solution" or the ability to "do what it says" was not possible in the case of the post.

Instead of assuming everyone that posts a problem is an idiot or is required to "RTFM", how about assuming they have already attempted the obvious and are requesting other means? That was my complaint about the "passive-aggressive" nature of the short and useless original response.

To complain about the detailed correction of another having the same or similar issues seems to also be quite elitist.

I have an ASUS M2N32 SLI-Deluxe Vista Edition motherboard with a PCIExpress and PCI (NVidia) chipset. Yes, it does have 4 Gigs of RAM. Also, in its BIOS, there is no aperture or IOMMU setting (the manual is available for download). That was the first thing I happened to look for when I saw the error message. Having not found it and then looking on Google and only seeing responses such as "Do what it says" and no other solutions, since doing what it says was not possible, I did find that all of these various posts mentioned the AGP port as being the cause for the need of an aperture for IODMA in large memory environments outside the 32 bit memory footprint of AGP. Having no AGP port, it is natural to assume this need for an aperture is not necessary in a PCIExpress system, although my assumptions could be wrong, they were not founded on a whim.

So, to summarize:
  1. The solution given by the kernel itself is not possible on my BIOS
  2. I used Google to research the problem, and no real solutions were found, only responses saying to do what the error message says. This is sort of a catch-22 situation.
  3. Reading between the lines, I found it was related to the AGP subsystem and large RAM footprints.
  4. Still, as of yet, no indication as to WHY the error is happening on a non-AGP system without an aperture or IOMMU setting in the BIOS, and no (physically possible) solutions have been offered.
  5. Assuming the programming of a Kernel module is coded incorrectly, is not unfounded especially since the "solution" is not possible on all systems, and the subsystem involved in the error doesn't seem to relate to the type of system it is running on. If I am wrong in this assumption, then I apologize, but clearly the "solution" needs to be something possible on all types of systems.
  6. Finally, given all this, no solution in my situation has been offered. I'd be happy to try whatever is possible, but the BIOS setting approach isn't possible (at least not as given).

H_TeXMeX_H 04-25-2008 02:56 PM

Quote:

Originally Posted by SuperSparky (Post 3132908)
Since this only started happening with recent versions of the Fedora version of the Kernel, a "solution" from 2005 didn't seem to apply.

Well, there's your problem, the fedora kernel. Try compiling your own vanilla kernel, it'll probably solve it.

revof11 05-18-2008 01:21 PM

I know it's a little late, but I can successfully boot adding the iommu=noagp kernel parameter. I still get the error messages, but I can at least boot.

SuperSparky 05-18-2008 11:37 PM

Can you prove the Fedora Kernal was the problem, or was condescending Slackware evangelism clouding your judgement?


Quote:

Originally Posted by H_TeXMeX_H (Post 3132942)
Well, there's your problem, the fedora kernel. Try compiling your own vanilla kernel, it'll probably solve it.


H_TeXMeX_H 05-19-2008 05:11 AM

I can't prove it, because I don't run Fedora, but when I did, most of the problems came from the crappy kernel they use, probably because the patch the crap out of it. It could also be just a kernel bug, but typically compiling a kernel myself fixed the problem that I had, so I'm thinking it's Fedora's kernel. You can prove it, not me.


All times are GMT -5. The time now is 01:10 AM.