package: kernel-patch-badram
version: 2.6.5.2-2
original kernel-image-2.6.8-2-386 (shows now the same symptoms)
2nd, costumised kernel-source-2.6.8
I installed BadRam recently an my Debian Sarge system to block some
badram. Now I deinstalled it, cleaned the /boot/grub/menu.lst file, and
checked if /etc/badram.conf is present. Seems alright. However I do not
get rid of it, here is the dmesg output:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000d0000 - 00000000000d8000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003def0000 (usable)
BIOS-e820: 000000003def0000 - 000000003deff000 (ACPI data)
BIOS-e820: 000000003deff000 - 000000003df00000 (ACPI NVS)
BIOS-e820: 000000003df00000 - 000000003e000000 (usable)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
I also compiled a customised kernel, and this one does this too. I guess
it is somewhere now incorporated, where I cannot see it. Do you have an
idea where I could look for that? I figured out that the problem is not
related to the memory, as another computer uses the RAM without
problems. It is rather the processor, or the motherboard. Besides that,
the badram seems not to be consistent, that is I get different output
when running it another day.
BTW, during installation of the new kernel (make menuconfig), I cannot
see an option for using badram configuration.
Thanks you for any hints!
original kernel-image-2.6.8-2-386 (shows now the same symptoms)
2nd, costumised kernel-source-2.6.8
Best wishes,
Torsten
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
