Bug 11278
Summary: | Memory above 64MB not recognised | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Simon Oldfield <simon.oldfield> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-05-10 03:44:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Simon Oldfield
2000-05-07 12:33:07 UTC
I got linux to recognise the correct amount of memory by sepcifying the "mem=256MB" option to lilo. Is this a BIOS problem or a linux problem? Is it simply that this is a new-ish motherboard, and it will all go away at some point in the future or will I have to explicity set the memory forever more? This sounds like your bios doesn't support the extended memory detection call that the 2.2.14 kernel we ship uses. This shouldn't be a problem with the 2.4 kernel since it uses the 0e80 call to get the bios memory mapping. Until then you will need to keep passing the mem= parameter to the 2.2 kernels on your machine. Duh....that should be the e820 call in the sentences above....technical accuracy and all... |