RE: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

RE: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Donald Maner]

The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?

-----Original Message-----
From: Raul Miller [mailto:moth@magenta.com] 
Sent: Wednesday, December 10, 2003 10:52 PM
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB
ram.


[1.] Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Nick Piggin]

Donald Maner wrote:

>The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?
>
>-----Original Message-----
>From: Raul Miller [mailto:moth@magenta.com] 
>Sent: Wednesday, December 10, 2003 10:52 PM
>To: linux-kernel@vger.kernel.org
>Subject: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB
>ram.
>
>
>[1.] Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.
>

Raul Miller wrote:

>
>[7.2.] /proc/cpuinfo says:
>
>processor       : 0
>vendor_id       : AuthenticAMD
>cpu family      : 15
>model           : 5
>model name      : AMD Opteron(tm) Processor 240
>

Or ARCH=x86_64 ?

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Ed Sweetman]

I thought highmem wasn't necesarily needed for memory <=2GB? Highmem 
incurs some performance hits doesn't it and so the urge to move to it 
with only 2GB is not very attractive.  Anyways i'm just interested in if 
that's the case or not since 2GB is easy to get to these days and i had 
heard that highmem could be avoided passed the 1GB barrier.



Nick Piggin wrote:
> 
> 
> Donald Maner wrote:
> 
>> The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?
>>
>> -----Original Message-----
>> From: Raul Miller [mailto:moth@magenta.com] Sent: Wednesday, December 
>> 10, 2003 10:52 PM
>> To: linux-kernel@vger.kernel.org
>> Subject: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB
>> ram.
>>
>>
>> [1.] Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.
>>
> 
> Raul Miller wrote:
> 
>>
>> [7.2.] /proc/cpuinfo says:
>>
>> processor       : 0
>> vendor_id       : AuthenticAMD
>> cpu family      : 15
>> model           : 5
>> model name      : AMD Opteron(tm) Processor 240
>>
> 
> Or ARCH=x86_64 ?
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[William Lee Irwin III]

On Thu, Dec 11, 2003 at 12:33:39AM -0500, Ed Sweetman wrote:
> I thought highmem wasn't necesarily needed for memory <=2GB? Highmem 
> incurs some performance hits doesn't it and so the urge to move to it 
> with only 2GB is not very attractive.  Anyways i'm just interested in if 
> that's the case or not since 2GB is easy to get to these days and i had 
> heard that highmem could be avoided passed the 1GB barrier.

You're probably thinking of 2:2 split patches.

2:2 splits are at least technically ABI violations, which is probably
why this isn't merged etc. Applications sensitive to it are uncommon.

Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
top of the process address space.


-- wli

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Roland Dreier]

    William> 2:2 splits are at least technically ABI violations, which
    William> is probably why this isn't merged etc. Applications
    William> sensitive to it are uncommon.

    William> Yes, the SVR4 i386 ELF/ABI spec literally mandates
    William> 0xC0000000 as the top of the process address space.

What about the 4G/4G split stuff for x86 (which is in 2.6 as well as
the RH EL 3 kernel)?  It seems that would be just as big a violation
of the ABI...

 - Roland

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[William Lee Irwin III]

William> 2:2 splits are at least technically ABI violations, which
William> is probably why this isn't merged etc. Applications
William> sensitive to it are uncommon.
William> Yes, the SVR4 i386 ELF/ABI spec literally mandates
William> 0xC0000000 as the top of the process address space.

On Wed, Dec 10, 2003 at 09:48:11PM -0800, Roland Dreier wrote:
> What about the 4G/4G split stuff for x86 (which is in 2.6 as well as
> the RH EL 3 kernel)?  It seems that would be just as big a violation
> of the ABI...

I oversimplified it. It only requires it to be at or above 0xC0000000,
so the 4/4 patches are compliant.


-- wli

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Nick Piggin]

William Lee Irwin III wrote:

>On Thu, Dec 11, 2003 at 12:33:39AM -0500, Ed Sweetman wrote:
>
>>I thought highmem wasn't necesarily needed for memory <=2GB? Highmem 
>>incurs some performance hits doesn't it and so the urge to move to it 
>>with only 2GB is not very attractive.  Anyways i'm just interested in if 
>>that's the case or not since 2GB is easy to get to these days and i had 
>>heard that highmem could be avoided passed the 1GB barrier.
>>
>
>You're probably thinking of 2:2 split patches.
>
>2:2 splits are at least technically ABI violations, which is probably
>why this isn't merged etc. Applications sensitive to it are uncommon.
>
>Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
>top of the process address space.
>

At any rate, Raul, highmem shouldn't hurt your performance significantly
with the 2.6 kernel. If it does then send a note to the list.

Your other options are a different user/kernel split, or a 64-bit kernel,
both of which should have less overhead than highmem.

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Raul Miller]

On Wed, Dec 10, 2003 at 11:06:46PM -0600, Donald Maner wrote:
> The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?

No.


On Thu, Dec 11, 2003 at 04:13:25PM +1100, Nick Piggin wrote:
> Or ARCH=x86_64 ?

Yes.  Well, no... I don't see that option in my .config.  I
did specify the amd64 bit archictecture, but I don't know
what that means in .config terms.  Here's what's set under
"# Processor type and features":

CONFIG_X86_PC=y
CONFIG_MK8=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y

On Thu, Dec 11, 2003 at 04:48:51PM +1100, Nick Piggin wrote:
> At any rate, Raul, highmem shouldn't hurt your performance significantly
> with the 2.6 kernel. If it does then send a note to the list.

Ok, I guess I'll try that (tomorrow, unless I hear any better suggestions
before then).

[I thought highmem was something completely different -- that it declared
a watermark and memory above that watermark was treated differently.
However, I guess I understand that this might have the side effect of
bumping things around such that I get access to the memory.]

Thanks,

-- 
Raul Miller
moth@magenta.com

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Nick Piggin]

Raul Miller wrote:

>On Wed, Dec 10, 2003 at 11:06:46PM -0600, Donald Maner wrote:
>
>>The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?
>>
>
>No.
>
>
>On Thu, Dec 11, 2003 at 04:13:25PM +1100, Nick Piggin wrote:
>
>>Or ARCH=x86_64 ?
>>
>
>Yes.  Well, no... I don't see that option in my .config.  I
>did specify the amd64 bit archictecture, but I don't know
>what that means in .config terms.  Here's what's set under
>"# Processor type and features":
>

This optimises the kernel for your chip when its in 32-bit mode.
make 'ARCH=x64_64' to make a 64-bit kernel, however you would
need a cross compiler.

>
>On Thu, Dec 11, 2003 at 04:48:51PM +1100, Nick Piggin wrote:
>
>>At any rate, Raul, highmem shouldn't hurt your performance significantly
>>with the 2.6 kernel. If it does then send a note to the list.
>>
>
>Ok, I guess I'll try that (tomorrow, unless I hear any better suggestions
>before then).
>
>[I thought highmem was something completely different -- that it declared
>a watermark and memory above that watermark was treated differently.
>However, I guess I understand that this might have the side effect of
>bumping things around such that I get access to the memory.]
>

No you're right, but the kernel tries not to use highmem for data it
accesses a lot. cache and anonymous memory for example.

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[David Lang]

Ed,
highmem isn't nessasary for mem<1G (actually 960M) on x86.

you are useing the opteron CPU, but was your kernel compiled for it
(x86064) or are you running an x86 kernel? (both will run, but the x86-64
kernel will give you better performance (including removing the need for
highmem)

David Lang

On Wed, 10 Dec 2003, William Lee Irwin III wrote:

> Date: Wed, 10 Dec 2003 21:41:11 -0800
> From: William Lee Irwin III <wli@holomorphy.com>
> To: Ed Sweetman <ed.sweetman@wmich.edu>
> Cc: Nick Piggin <piggin@cyberone.com.au>, Donald Maner <donjr@maner.org>,
>      Raul Miller <moth@magenta.com>, linux-kernel@vger.kernel.org
> Subject: Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB
>     ram.
>
> On Thu, Dec 11, 2003 at 12:33:39AM -0500, Ed Sweetman wrote:
> > I thought highmem wasn't necesarily needed for memory <=2GB? Highmem
> > incurs some performance hits doesn't it and so the urge to move to it
> > with only 2GB is not very attractive.  Anyways i'm just interested in if
> > that's the case or not since 2GB is easy to get to these days and i had
> > heard that highmem could be avoided passed the 1GB barrier.
>
> You're probably thinking of 2:2 split patches.
>
> 2:2 splits are at least technically ABI violations, which is probably
> why this isn't merged etc. Applications sensitive to it are uncommon.
>
> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
> top of the process address space.
>
>
> -- wli
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Martin J. Bligh]

--William Lee Irwin III <wli@holomorphy.com> wrote (on Wednesday, December 10, 2003 21:41:11 -0800):

> On Thu, Dec 11, 2003 at 12:33:39AM -0500, Ed Sweetman wrote:
>> I thought highmem wasn't necesarily needed for memory <=2GB? Highmem 
>> incurs some performance hits doesn't it and so the urge to move to it 
>> with only 2GB is not very attractive.  Anyways i'm just interested in if 
>> that's the case or not since 2GB is easy to get to these days and i had 
>> heard that highmem could be avoided passed the 1GB barrier.
> 
> You're probably thinking of 2:2 split patches.
> 
> 2:2 splits are at least technically ABI violations, which is probably
> why this isn't merged etc. Applications sensitive to it are uncommon.
> 
> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
> top of the process address space.

You mean like we place the stack in the "ABI compliant place"? 
Yeah, right ;-)

M.

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[William Lee Irwin III]

William Lee Irwin III <wli@holomorphy.com> wrote:
>> You're probably thinking of 2:2 split patches.
>> 2:2 splits are at least technically ABI violations, which is probably
>> why this isn't merged etc. Applications sensitive to it are uncommon.
>> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
>> top of the process address space.

On Wed, Dec 10, 2003 at 11:08:38PM -0800, Martin J. Bligh wrote:
> You mean like we place the stack in the "ABI compliant place"? 
> Yeah, right ;-)

No specific address is ever cited as a requirement for stack placement;
stack immediately below text is merely given as a "typical arrangement".
i.e. "Although applications may control their memory assignments, the
typical arrangement appears below: [diagram and other bits]" It then
goes on to say, "Processes, therefore, shount _not_ depend on finding
their stack at a particular virtual address."

The process address space boundary is, however, stated as a requirement:
"the reserved area shall not consume more than 1GB of the address space."


-- wli

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Martin J. Bligh]

>>> You're probably thinking of 2:2 split patches.
>>> 2:2 splits are at least technically ABI violations, which is probably
>>> why this isn't merged etc. Applications sensitive to it are uncommon.
>>> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
>>> top of the process address space.
> 
> On Wed, Dec 10, 2003 at 11:08:38PM -0800, Martin J. Bligh wrote:
>> You mean like we place the stack in the "ABI compliant place"? 
>> Yeah, right ;-)
> 
> No specific address is ever cited as a requirement for stack placement;
> stack immediately below text is merely given as a "typical arrangement".
> i.e. "Although applications may control their memory assignments, the
> typical arrangement appears below: [diagram and other bits]" It then
> goes on to say, "Processes, therefore, shount _not_ depend on finding
> their stack at a particular virtual address."
> 
> The process address space boundary is, however, stated as a requirement:
> "the reserved area shall not consume more than 1GB of the address space."

;-)

OK, fair enough ... it doesn't actually break anything though ;-)

m.

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[William Lee Irwin III]

William Lee Irwin III <wli@holomorphy.com> wrote:
>> You're probably thinking of 2:2 split patches.
>> 2:2 splits are at least technically ABI violations, which is probably
>> why this isn't merged etc. Applications sensitive to it are uncommon.
>> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
>> top of the process address space.

On Wed, Dec 10, 2003 at 11:08:38PM -0800, Martin J. Bligh wrote:
> You mean like we place the stack in the "ABI compliant place"? 
> Yeah, right ;-)
> M.

Something odd is happening here; this is the second time I've gotten this
message. I suspect something is wrong with smtp-out2.blueyonder.co.uk

In fact, other messages in this thread are getting resent, too.


-- wli

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Raul Miller]

> On Thu, Dec 11, 2003 at 12:33:39AM -0500, Ed Sweetman wrote:
> > I thought highmem wasn't necesarily needed for memory <=2GB? Highmem 
> > incurs some performance hits doesn't it and so the urge to move to it 
> > with only 2GB is not very attractive.  Anyways i'm just interested in if 
> > that's the case or not since 2GB is easy to get to these days and i had 
> > heard that highmem could be avoided passed the 1GB barrier.

On Wed, Dec 10, 2003 at 09:41:11PM -0800, William Lee Irwin III wrote:
> You're probably thinking of 2:2 split patches.
> 
> 2:2 splits are at least technically ABI violations, which is probably
> why this isn't merged etc. Applications sensitive to it are uncommon.
> 
> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
> top of the process address space.

Apologies if I'm asking about the obvious, but... 

[1] isn't 0xC0000000 at 3GB?  
[2] Even if ELF did restrict a user process to 1GB (which I'm pretty
sure it doesn't), wouldn't the kernel still be able to manage 2GB of
user memory?

Probably my real question is: "what's this about 2:2 split patches"?

Basically, I thought "linux supports 2GB ram" had been been the case
since the dark ages.  It's hard for me to comprehend how highmem, or 64
bit cpus, could have much to do with a 1GB limit.

[In my fantasies, I was thinking that the system came up with only 1GB of
the memory easily usable, and that the lack of support for my hardware
meant that it couldn't be properly reconfigured.  But I recognize that
I haven't spent the time researching this to see if in fact this is
the case.]

I am in the process of bringing up an cross compilation environment for
amd64 -- I need to do that anyways -- and I'll try building a real 64
bit kernel to see if that helps any.  If that doesn't, I guess I'll try
a couple 4G highmem kernels (one 64 bit, one 32 bit).  If nothing else,
that will eat up some time...

Thanks,

-- 
Raul Miller
moth@magenta.com

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Raul Miller]

On Thu, Dec 11, 2003 at 09:41:48AM -0500, I wrote:
> since the dark ages.  It's hard for me to comprehend how highmem, or 64
> bit cpus, could have much to do with a 1GB limit.

[Well, unless my motherboard really has a problem caching memory above
1GB.  But that seems unlikely, since it's the CPU which is acting as
the memory controller.  In any event, if this is actually the issue,
shouldn't the kernel issue a warning message, about why it's ignoring
the rest of the memory?]

Thanks again,

-- 
Raul Miller
moth@magenta.com

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[William Lee Irwin III]

On Wed, Dec 10, 2003 at 09:41:11PM -0800, William Lee Irwin III wrote:
>> You're probably thinking of 2:2 split patches.
>> 2:2 splits are at least technically ABI violations, which is probably
>> why this isn't merged etc. Applications sensitive to it are uncommon.
>> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
>> top of the process address space.

On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> Apologies if I'm asking about the obvious, but... 
> [1] isn't 0xC0000000 at 3GB?  

It is.


On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> [2] Even if ELF did restrict a user process to 1GB (which I'm pretty
> sure it doesn't), wouldn't the kernel still be able to manage 2GB of
> user memory?

You have it backward. The SVR4/i386 ELF ABI specification is requiring
userspace to be granted at least 3GB of address space.

This does not necessarily present a restriction for the kernel;
consider task gates (mingo did it by hand).


On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> Probably my real question is: "what's this about 2:2 split patches"?
> Basically, I thought "linux supports 2GB ram" had been been the case
> since the dark ages.  It's hard for me to comprehend how highmem, or 64
> bit cpus, could have much to do with a 1GB limit.

You should probably ignore this thread. It's probably not relevant to
you.


On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> [In my fantasies, I was thinking that the system came up with only 1GB of
> the memory easily usable, and that the lack of support for my hardware
> meant that it couldn't be properly reconfigured.  But I recognize that
> I haven't spent the time researching this to see if in fact this is
> the case.]

Highmem support gets you this on ia32. Other architectures can support it
with less overhead.


On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> I am in the process of bringing up an cross compilation environment for
> amd64 -- I need to do that anyways -- and I'll try building a real 64
> bit kernel to see if that helps any.  If that doesn't, I guess I'll try
> a couple 4G highmem kernels (one 64 bit, one 32 bit).  If nothing else,
> that will eat up some time...

If you have such a cpu why are you bothering with highmem (or wondering
if > 2GB is supported)?


-- wli

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[moth]

On Thu, Dec 11, 2003 at 07:00:11AM -0800, William Lee Irwin III wrote:
> You should probably ignore this thread. It's probably not relevant to
> you.

Ok, thanks.  My mistake.

> > [In my fantasies, I was thinking that the system came up with only 1GB of
> > the memory easily usable, and that the lack of support for my hardware
> > meant that it couldn't be properly reconfigured.  But I recognize that
> > I haven't spent the time researching this to see if in fact this is
> > the case.]
> 
> Highmem support gets you this on ia32. Other architectures can support it
> with less overhead.

Are there docs on this?

> > I am in the process of bringing up an cross compilation environment for
> > amd64 -- I need to do that anyways -- and I'll try building a real 64
> > bit kernel to see if that helps any.  If that doesn't, I guess I'll try
> > a couple 4G highmem kernels (one 64 bit, one 32 bit).  If nothing else,
> > that will eat up some time...
> 
> If you have such a cpu why are you bothering with highmem (or wondering
> if > 2GB is supported)?

I'm not wondering if > 2GB is supported.  I'm trying to get 2GB
to work (and I'm having a problem -- perhaps because I believe
Documentation/memory.txt doesn't cover the issues I'm facing).

I've not yet bothered with highmem, but I will if building a 64 bit
kernel doesn't get me access to 2GB.

Does that answer your question?

Thanks,

-- 
Raul

Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[William Lee Irwin III]

On Thu, Dec 11, 2003 at 11:17:41AM -0500, moth@magenta.com wrote:
> I'm not wondering if > 2GB is supported.  I'm trying to get 2GB
> to work (and I'm having a problem -- perhaps because I believe
> Documentation/memory.txt doesn't cover the issues I'm facing).
> I've not yet bothered with highmem, but I will if building a 64 bit
> kernel doesn't get me access to 2GB.
> Does that answer your question?

You should be fine with a 64-bit kernel.


-- wli

Where did the ELF spec go? (SCO website?)

[Rob Landley]

On Thursday 11 December 2003 09:00, William Lee Irwin III wrote:
> On Wed, Dec 10, 2003 at 09:41:11PM -0800, William Lee Irwin III wrote:
> >> You're probably thinking of 2:2 split patches.
> >> 2:2 splits are at least technically ABI violations, which is probably
> >> why this isn't merged etc. Applications sensitive to it are uncommon.
> >> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
> >> top of the process address space.
>
> On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> > Apologies if I'm asking about the obvious, but...
> > [1] isn't 0xC0000000 at 3GB?
>
> It is.
>
> On Thu, Dec 11, 2003 at 09:41:48AM -0500, Raul Miller wrote:
> > [2] Even if ELF did restrict a user process to 1GB (which I'm pretty
> > sure it doesn't), wouldn't the kernel still be able to manage 2GB of
> > user memory?
>
> You have it backward. The SVR4/i386 ELF ABI specification is requiring
> userspace to be granted at least 3GB of address space.

Where does one get a copy of the SVR4 spec these days?  The link I could track 
down went to http://www.sco.com/developer/devspecs/ which just ain't there no 
more.

And no, not because of a "DDOS".  There isn't one.  SCO's website IP moved 
from 216.250.128.13 to 216.250.128.20, and it's up at the new IP right now.  
They didn't get the new DNS record propogated on time.  Rookie mistake...

But looking at http.://216.250.128.20/developer/devspecs redirects you to the 
/developer page.  The devspecs page went away...

Is this mirrored somewhere?

Rob

Re: Where did the ELF spec go? (SCO website?)

[William Lee Irwin III]

On Thursday 11 December 2003 09:00, William Lee Irwin III wrote:
>> You have it backward. The SVR4/i386 ELF ABI specification is requiring
>> userspace to be granted at least 3GB of address space.

On Thu, Dec 11, 2003 at 01:26:32PM -0600, Rob Landley wrote:
> Where does one get a copy of the SVR4 spec these days?  The link I
> could track down went to http://www.sco.com/developer/devspecs/ which
> just ain't there no more.
> And no, not because of a "DDOS".  There isn't one.  SCO's website IP moved 
> from 216.250.128.13 to 216.250.128.20, and it's up at the new IP right now.  
> They didn't get the new DNS record propogated on time.  Rookie mistake...
> But looking at http.://216.250.128.20/developer/devspecs redirects
> you to the /developer page.  The devspecs page went away...
> Is this mirrored somewhere?

I'm looking at a dead tree copy. I have no idea if it's online or not.

Also, it's largely an ELF ABI spec; I'm not sure how/why SVR4 got into
the picture, but its name is on there.


-- wli

Re: Where did the ELF spec go? (SCO website?)

[Richard B. Johnson]

On Thu, 11 Dec 2003, William Lee Irwin III wrote:

> On Thursday 11 December 2003 09:00, William Lee Irwin III wrote:
> >> You have it backward. The SVR4/i386 ELF ABI specification is requiring
> >> userspace to be granted at least 3GB of address space.
>
> On Thu, Dec 11, 2003 at 01:26:32PM -0600, Rob Landley wrote:
> > Where does one get a copy of the SVR4 spec these days?  The link I
> > could track down went to http://www.sco.com/developer/devspecs/ which
> > just ain't there no more.
> > And no, not because of a "DDOS".  There isn't one.  SCO's website IP moved
> > from 216.250.128.13 to 216.250.128.20, and it's up at the new IP right now.
> > They didn't get the new DNS record propogated on time.  Rookie mistake...
> > But looking at http.://216.250.128.20/developer/devspecs redirects
> > you to the /developer page.  The devspecs page went away...
> > Is this mirrored somewhere?
>
> I'm looking at a dead tree copy. I have no idea if it's online or not.
>
> Also, it's largely an ELF ABI spec; I'm not sure how/why SVR4 got into
> the picture, but its name is on there.


http://developers.sun.com/solaris/articles/elf.html


Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.

Re: Where did the ELF spec go? (SCO website?)

[Johannes Stezenbach]

Richard B. Johnson wrote:
> On Thu, 11 Dec 2003, William Lee Irwin III wrote:
> 
> > On Thursday 11 December 2003 09:00, William Lee Irwin III wrote:
> > >> You have it backward. The SVR4/i386 ELF ABI specification is requiring
> > >> userspace to be granted at least 3GB of address space.
> >
> > On Thu, Dec 11, 2003 at 01:26:32PM -0600, Rob Landley wrote:
> > > Where does one get a copy of the SVR4 spec these days?  The link I
> > > could track down went to http://www.sco.com/developer/devspecs/ which
> > > just ain't there no more.

http://www.caldera.com/developers/devspecs/

-js

PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[Raul Miller]

[1.] Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.

[2.] Full description of problem:

While I have 2G ram installed, I only get the benefit of 1G.  The bios,
and grub, both report 2G.  However, even passing mem=2048m as a boot
parameter doesn't get me access to the other half of my memory.  I see
no warning messages about why this memory isn't available.

I understand that there's a distinct possibility that this won't be
corrected in 2.6 (after all, my machine isn't crashing), but I'm hoping
at least for a few tips on how to patch things up in some ad-hoc fashion.

[3.] Keywords: memory, motherboard

[4.] Kernel version: Linux version 2.6.0-test11 (root@localhost) (gcc version 3.3.2 (Debian)) #3 SMP Fri Dec 5 22:37:08 EST 2003

[5.] Oops: n/a, however here's cat /proc/meminfo, just in case there's
anything relevant here which doesn't show up in /proc/iomem:
MemTotal:       904612 kB
MemFree:        749108 kB
Buffers:         11680 kB
Cached:          71008 kB
SwapCached:          0 kB
Active:          85892 kB
Inactive:        51068 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       904612 kB
LowFree:        749108 kB
SwapTotal:     4000208 kB
SwapFree:      4000208 kB
Dirty:               4 kB
Writeback:           0 kB
Mapped:          81988 kB
Slab:            10716 kB
Committed_AS:   139044 kB
PageTables:        812 kB
VmallocTotal:   122808 kB
VmallocUsed:      2756 kB
VmallocChunk:   119744 kB

[6.] Demo program: (n/a)

[7.1.] ver_linux says:

Linux localhost 2.6.0-test11 #3 SMP Fri Dec 5 22:37:08 EST 2003 i686 GNU/Linux
 
Gnu C                  3.3.2
Gnu make               3.80
util-linux             2.12
mount                  2.12
module-init-tools      0.9.15-pre3
e2fsprogs              1.35-WIP
Linux C Library        2.3.2
Dynamic linker (ldd)   2.3.2
Procps                 3.1.14
Net-tools              1.60
Console-tools          0.2.3
Sh-utils               5.0
Modules Loaded         fglrx hid ppp_async ppp_generic slhc uhci_hcd parport_pc lp parport 3c59x usbmouse usbkbd usbcore

It's probably worth noting that I'm using a radeon 9800 xt as one of
my graphics cards.  And, no, the kernel doesn't recognize that card,
either.  Amusingly, the ATI driver doesn't properly recognize it either
(fglrx-flc22, version 3.2.8 reports that I've got a non-ati card).
However, since this happens well after memory is detected, I'm presuming
that it's unrelated to my problem.

[7.2.] /proc/cpuinfo says:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 5
model name      : AMD Opteron(tm) Processor 240
stepping        : 1
cpu MHz         : 1403.869
cache size      : 1024 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall mmxext lm 3dnowext 3dnow
bogomips        : 2752.51

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 5
model name      : AMD Opteron(tm) Processor 240
stepping        : 1
cpu MHz         : 1403.869
cache size      : 1024 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall mmxext lm 3dnowext 3dnow
bogomips        : 2801.66


[7.3.] /proc/modules says:
fglrx 207268 0 - Live 0xf8aca000
hid 33280 0 - Live 0xf8a6f000
ppp_async 12288 0 - Live 0xf8a5d000
ppp_generic 30352 1 ppp_async, Live 0xf8a79000
slhc 7040 1 ppp_generic, Live 0xf8a5a000
uhci_hcd 34064 0 - Live 0xf8a65000
parport_pc 34048 1 - Live 0xf8a1a000
lp 9824 0 - Live 0xf8a10000
parport 30240 2 parport_pc,lp, Live 0xf8a24000
3c59x 39656 0 - Live 0xf8a4f000
usbmouse 5632 0 - Live 0xf8a17000
usbkbd 7296 0 - Live 0xf8a14000
usbcore 114012 6 hid,uhci_hcd,usbmouse,usbkbd, Live 0xf8a32000

[7.4.a] /proc/ioports says:

0000-001f : dma1
0020-0021 : pic1
0040-005f : timer
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0376-0376 : ide1
0378-037a : parport0
03c0-03df : vga+
03f6-03f6 : ide0
0cf8-0cff : PCI conf1
a000-afff : PCI Bus #01
  a000-a0ff : 0000:01:00.0
b000-b07f : 0000:00:06.0
  b000-b07f : 0000:00:06.0
b400-b407 : 0000:00:0f.0
b800-b803 : 0000:00:0f.0
bc00-bc07 : 0000:00:0f.0
c000-c003 : 0000:00:0f.0
c400-c40f : 0000:00:0f.0
c800-c8ff : 0000:00:0f.0
cc00-cc0f : 0000:00:0f.1
  cc00-cc07 : ide0
  cc08-cc0f : ide1
d000-d01f : 0000:00:10.0
  d000-d01f : uhci_hcd
d400-d41f : 0000:00:10.1
  d400-d41f : uhci_hcd
d800-d81f : 0000:00:10.2
  d800-d81f : uhci_hcd
e000-e0ff : 0000:00:11.5

[7.4.b] /proc/iomem says:

00000000-0009d7ff : System RAM
0009d800-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-7feeffff : System RAM
  00100000-003260d8 : Kernel code
  003260d9-003f50bf : Kernel data
7fef0000-7fef2fff : ACPI Non-volatile Storage
7fef3000-7fefffff : ACPI Tables
d0000000-dfffffff : 0000:00:00.0
e0000000-efffffff : PCI Bus #01
  e0000000-e7ffffff : 0000:01:00.0
  e8000000-efffffff : 0000:01:00.1
f0000000-f1ffffff : PCI Bus #01
  f1000000-f100ffff : 0000:01:00.0
  f1010000-f101ffff : 0000:01:00.1
f2000000-f2003fff : 0000:00:05.0
f3000000-f37fffff : 0000:00:05.0
f5000000-f500ffff : 0000:00:0b.0
f5010000-f501007f : 0000:00:06.0
f5011000-f50110ff : 0000:00:10.4
fec00000-ffffffff : reserved

[7.5.] lspci -vvvx says:

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3188 (rev 01)
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 8
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Capabilities: [80] AGP version 3.0
		Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
	Capabilities: [c0] #08 [0060]
	Capabilities: [68] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] #08 [8001]
00: 06 11 88 31 06 00 30 22 01 00 00 06 00 08 00 00
10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b188 (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000a000-0000afff
	Memory behind bridge: f0000000-f1ffffff
	Prefetchable memory behind bridge: e0000000-efffffff
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 88 b1 07 01 30 02 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 a0 a0 20 22
20: 00 f0 f0 f1 00 e0 f0 ef 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 08 00

00:05.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W [Millennium] (rev 01) (prog-if 00 [VGA])
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f2000000 (32-bit, non-prefetchable) [disabled] [size=16K]
	Region 1: Memory at f3000000 (32-bit, prefetchable) [disabled] [size=8M]
	Expansion ROM at <unassigned> [disabled] [size=64K]
00: 2b 10 19 05 80 00 80 02 01 00 00 03 00 00 00 00
10: 00 00 00 f2 08 00 00 f3 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 00

00:06.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64)
	Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 17
	Region 0: I/O ports at b000 [size=128]
	Region 1: Memory at f5010000 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: b7 10 55 90 07 00 10 02 64 00 00 02 08 20 00 00
10: 01 b0 00 00 00 00 01 f5 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 55 90
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 0a 0a

00:0b.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03)
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (16000ns min), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f5000000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable+ DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
	Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
		Address: fffffffdfffffbe4  Data: ffff
00: e4 14 53 16 06 00 b0 02 03 00 00 02 08 20 00 00
10: 04 00 00 f5 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 07 00 00 00 62 14 00 13
30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 01 40 00

00:0f.0 RAID bus controller: VIA Technologies, Inc.: Unknown device 3149 (rev 80)
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Interrupt: pin B routed to IRQ 20
	Region 0: I/O ports at b400 [size=8]
	Region 1: I/O ports at b800 [size=4]
	Region 2: I/O ports at bc00 [size=8]
	Region 3: I/O ports at c000 [size=4]
	Region 4: I/O ports at c400 [size=16]
	Region 5: I/O ports at c800 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 49 31 07 00 90 02 80 00 04 01 00 20 80 00
10: 01 b4 00 00 01 b8 00 00 01 bc 00 00 01 c0 00 00
20: 01 c4 00 00 01 c8 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 c0 00 00 00 00 00 00 00 0b 02 00 00

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Interrupt: pin A routed to IRQ 20
	Region 4: I/O ports at cc00 [size=16]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 cc 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 01 00 00

00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 21
	Region 4: I/O ports at d000 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d0 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 01 00 00

00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 21
	Region 4: I/O ports at d400 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d4 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 01 00 00

00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin B routed to IRQ 21
	Region 4: I/O ports at d800 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d8 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 02 00 00

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
	Subsystem: VIA Technologies, Inc. USB 2.0
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin C routed to IRQ 21
	Region 0: Memory at f5011000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 04 31 07 00 10 02 86 20 03 0c 08 20 80 00
10: 00 10 01 f5 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 04 31
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 03 00 00

00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3227
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 27 32 87 00 10 02 00 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 60)
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin C routed to IRQ 22
	Region 0: I/O ports at e000 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 06 11 59 30 01 00 10 02 60 00 01 04 00 00 00 00
10: 01 e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 c0 00 00 00 00 00 00 00 05 03 00 00

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Capabilities: [80] #08 [2101]
	Capabilities: [a0] #08 [2101]
	Capabilities: [c0] #08 [2101]
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 03 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Capabilities: [80] #08 [2101]
	Capabilities: [a0] #08 [2101]
	Capabilities: [c0] #08 [2101]
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00

00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 03 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4e4a (prog-if 00 [VGA])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1300
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 255 (2000ns min), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at a000 [size=256]
	Region 2: Memory at f1000000 (32-bit, non-prefetchable) [size=64K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [58] AGP version 3.0
		Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 02 10 4a 4e 87 00 b0 02 00 00 00 03 08 ff 80 00
10: 08 00 00 e0 01 a0 00 00 00 00 00 f1 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 13
30: 00 00 00 00 58 00 00 00 00 00 00 00 0a 01 08 00

01:00.1 Display controller: ATI Technologies Inc: Unknown device 4e6a
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 1301
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Region 0: Memory at e8000000 (32-bit, prefetchable) [disabled] [size=128M]
	Region 1: Memory at f1010000 (32-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 02 10 6a 4e 80 00 b0 02 00 00 80 03 08 20 00 00
10: 08 00 00 e8 00 00 01 f1 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 01 13
30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 08 00


[7.6.] I've not turned on scsi yet


[Etc.] 

Motherboard is a K8T Master2 FAR -- chipset is VIA K8T 800 and VIA VT8237.
I think I'll be happy to run tests for people, as long as they're
reasonably specific.

I did have to futz around a bit to get the system up and working, but to
my knowledge I've not done anything which could shed more light on why my
memory map isn't to my taste.  Which shows what little I know, I suppose.

I hope this isn't too much of a distraction from the GPL flames...

Thanks in advance,

-- 
Raul Miller
moth@magenta.com