Dear All,
I'm terribly sorry that I just found I've mistakenly configured the dram MA Map Type, and now memtest showed no errors. But I still have to reduce the mem size when reporting to system through ram_resource or filo couldn't be started. I have disabled the integrated graphics card and the agp, so I don't think the top memory should be reserved for frame buffer.
aaron lwe wrote:
Dear All,
I'm terribly sorry that I just found I've mistakenly configured the dram MA Map Type, and now memtest showed no errors. But I still have to reduce the mem size when reporting to system through ram_resource or filo couldn't be started. I have disabled the integrated graphics card and the agp, so I don't think the top memory should be reserved for frame buffer.
And now you're where I am. For some reason there's a reserved memory range _somewhere_ at the tolm, of some unknown size. I've found that reserving an extra 1MB doesn't work, but 32MB does. I've found nothing in the documentation I have to explain this. BTW, have you had to make any code changes other than the MA Map, and board-specific fixes? I'm wondering how generic that code really is.
-Corey
Quoting Corey Osgood corey.osgood@gmail.com:
aaron lwe wrote:
Dear All,
I'm terribly sorry that I just found I've mistakenly configured the dram MA Map Type, and now memtest showed no errors. But I still have to reduce the mem size when reporting to system through ram_resource or filo couldn't be started. I have disabled the integrated graphics card and the agp, so I don't think the top memory should be reserved for frame buffer.
And now you're where I am. For some reason there's a reserved memory range _somewhere_ at the tolm, of some unknown size. I've found that reserving an extra 1MB doesn't work, but 32MB does. I've found nothing in the documentation I have to explain this. BTW, have you had to make any code changes other than the MA Map, and board-specific fixes? I'm wondering how generic that code really is.
-Corey
Hmm. I think this also is true with some Intel chipsets. Even without graphics enabled there has to be some kind of reserved memory space just below tolm (the smallest I was sucessfull with was 1MB) or filo chokes. Doesn't LB allocate a bounce buffer just before the payload starts? Is this bounce buffer just below tolm??
Thanks - Joe
On Dec 21, 2007 1:40 PM, Corey Osgood corey.osgood@gmail.com wrote:
aaron lwe wrote:
Dear All,
I'm terribly sorry that I just found I've mistakenly configured the dram MA Map Type, and now memtest showed no errors. But I still have to reduce the mem size when reporting to system through ram_resource or filo couldn't be started. I have disabled the integrated graphics card and the agp, so I don't think the top memory should be reserved for frame buffer.
And now you're where I am. For some reason there's a reserved memory range _somewhere_ at the tolm, of some unknown size. I've found that reserving an extra 1MB doesn't work, but 32MB does. I've found nothing in the documentation I have to explain this. BTW, have you had to make any code changes other than the MA Map, and board-specific fixes? I'm wondering how generic that code really is.
-Corey
From what you have said, I guess it might be AGP aperture memory
that caused this problem. I saw you allocated 32MB for agp aperture memory in agp.c, so reserving 32MB works for you, and I changed this to 128MB for agp aperture memory so 128MB works for me. The problem is why this agp aperture memory is at physical memory range (tolm - agp_aperture_size to tolm) while we have set this agp aperture memory base at some very large address(e.g 0xe0000000). should this memory range be assigned a mtrr?
The changes I made to your code are : 1) some registers in host bus, as their values are different from the factory BIOS ones; 2) dram size releated registers 3) dram timing is ok. and I found couldn't change dram operating frequency ;-(
On Dec 21, 2007 1:40 PM, Corey Osgood corey.osgood@gmail.com wrote:
aaron lwe wrote:
Dear All,
I'm terribly sorry that I just found I've mistakenly configured the dram MA Map Type, and now memtest showed no errors. But I still have to reduce the mem size when reporting to system through ram_resource or filo couldn't be started. I have disabled the integrated graphics card and the agp, so I don't think the top memory should be reserved for frame buffer.
And now you're where I am. For some reason there's a reserved memory range _somewhere_ at the tolm, of some unknown size. I've found that reserving an extra 1MB doesn't work, but 32MB does. I've found nothing in the documentation I have to explain this. BTW, have you had to make any code changes other than the MA Map, and board-specific fixes? I'm wondering how generic that code really is.
-Corey
It seems that the last message I sent is wrong...
From what you have said, I guess it might be AGP aperture memory
that caused this problem. I saw you allocated 32MB for agp aperture memory in agp.c, so reserving 32MB works for you, and I changed this to 128MB for agp aperture memory so 128MB works for me. The problem is why this agp aperture memory is at physical memory range (tolm - agp_aperture_size to tolm) while we have set this agp aperture memory base at some very large address(e.g 0xe0000000). should this memory range be assigned a mtrr?
The changes I made to your code are : 1) some registers in host bus, as their values are different from the factory BIOS ones; 2) dram size releated registers 3) dram timing is ok. and I found couldn't change dram operating frequency ;-(
On Dec 21, 2007 1:40 PM, Corey Osgood corey.osgood@gmail.com wrote:
And now you're where I am. For some reason there's a reserved memory range _somewhere_ at the tolm, of some unknown size. I've found that reserving an extra 1MB doesn't work, but 32MB does. I've found nothing in the documentation I have to explain this. BTW, have you had to make any code changes other than the MA Map, and board-specific fixes? I'm wondering how generic that code really is.
-Corey
Corey, I think I've found the cause of this problem, it's agp aperture memory that caused this memory unusable. When I set agp aperture memory size to 128MB, I found I could only use the tolm - 128 * 1024 memory, and you set agp aperture memory size to 32MB, so reserving 32MB worked for you. The smallest size I can set for agp apertur memory size is 4MB and after setting that, memtest now reports 508MB(512MB - 4MB) is working fine ;-) Only I don't know why agp aperture memory would interfere with physical memory.
aaron lwe wrote:
On Dec 21, 2007 1:40 PM, Corey Osgood corey.osgood@gmail.com wrote:
And now you're where I am. For some reason there's a reserved memory range _somewhere_ at the tolm, of some unknown size. I've found that reserving an extra 1MB doesn't work, but 32MB does. I've found nothing in the documentation I have to explain this. BTW, have you had to make any code changes other than the MA Map, and board-specific fixes? I'm wondering how generic that code really is.
-Corey
Corey, I think I've found the cause of this problem, it's agp aperture memory that caused this memory unusable. When I set agp aperture memory size to 128MB, I found I could only use the tolm - 128 * 1024 memory, and you set agp aperture memory size to 32MB, so reserving 32MB worked for you. The smallest size I can set for agp apertur memory size is 4MB and after setting that, memtest now reports 508MB(512MB - 4MB) is working fine ;-) Only I don't know why agp aperture memory would interfere with physical memory.
Are you configuring the system for AGP 2.0 or 3.0, ie are you configuring dev 0.0 or 1.0? The way I had it set up, I thought, was 32MB for video, 32MB for agp, and the rest for the system, using AGP 3.0. I could very well have messed something up somewhere, though.
-Corey
Are you configuring the system for AGP 2.0 or 3.0, ie are you configuring dev 0.0 or 1.0? The way I had it set up, I thought, was 32MB for video, 32MB for agp, and the rest for the system, using AGP 3.0. I could very well have messed something up somewhere, though.
-Corey
I'm configuring the system for AGP 3.0. AFAIK, frame buffer uses physical memory but agp aperture memory do not use physical memory. We could set agp aperture memory size to be 128MB even we only have 64MB physical memory. and I've disabled the integrated graphics card, reserving no memory for it.
-
aaron lwe -
Corey Osgood -
joe＠smittys.pointclark.net