David Baron <d_ba...@012.net.il> wrote: > Here 'tis: > [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable) > [ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) > [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > [ 0.000000] BIOS-e820: 0000000000100000 - 0000000000f00000 (usable) > [ 0.000000] BIOS-e820: 0000000000f00000 - 0000000001000000 (reserved) > [ 0.000000] BIOS-e820: 0000000001000000 - 00000000cfedf800 (usable) > [ 0.000000] BIOS-e820: 00000000cfedf800 - 00000000cfee0000 (reserved) > [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS) > [ 0.000000] BIOS-e820: 00000000cfee3000 - 00000000cfef0000 (ACPI data) > [ 0.000000] BIOS-e820: 00000000cfef0000 - 00000000cff00000 (reserved) > [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) > [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Well, the memory map stops at the 4GiB border. If the BIOS of the board is not able to remap the memory hidden by the PCI address region then there is little the kernel can do about this. This can be either the fault of the BIOS, being programmed to not provide such a remapping feature (by being too old or by design of the mainboard vendor) or the fault of the chipset of the board not being able to address more than 4GiB of RAM. In the first case, you may be able to aquire a newer BIOS version if the problem is the BIOS just being too old, in the latter two cases you are out of luck, I am afraid. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l9eec5280...@mids.svenhartge.de
