LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware kernel memmap (https://www.linuxquestions.org/questions/slackware-14/slackware-kernel-memmap-4175484940/)

Stragonian 11-17-2013 06:18 PM

Slackware kernel memmap
 
After running memtest86+ on an old Toshiba A65 Satellite, I discovered the built in onboard RAM has two bad spots, the first is at an address of 780M's and the second is at an address of 844M's , as a generic quick and dirty fix I did an append="mem=760M" in Slackware lilo.conf, but I've been attempting to find some good examples using memmap arguments to pass to the kernel to make a better memory map around the bad memory cells.

Up to 779M <- Good
From 781M to 843M <- Good
From 845M to 991M <- Good

How would I append the above parameters to lilo?
Code:

append = "memmap=?????"

bartgymnast 11-18-2013 10:54 AM

hi Stragonian

it is very tricky, but you could use the following:

Code:

append = " memmap=75M$775M"
This will ignore the memory between 775M and 850M
I have no idea if you can use the good parts in between.

Stragonian 11-20-2013 03:41 AM

Thank You bartgymnast your subjection has been helpful. I did do more digging and discovered that if a Linux Kernel is compiled with[*] Memtest option I can then append="memtest=<# of passes>" to the system and it will run memtest and map the bad ram locations for me automatically, much like the old badram patch in older linux kernels. Because memtest takes 27 passes to detect both bad ram areas on the old laptop, it boots to a blank screen for a few minutes ( which seems like forever ) before continuing and loading the kernel, but when finished the OS seems to be stable.

Here's is what I put for the lilo entry after ensuring Memtest was compiled into my kernel
Code:

image = /boot/vmliuz-3.6.8-x32
  initrd = /boot/initrd-3.6.8-x32.gz
  root = /dev/sda2
  label = 3.6.8-x32
  vga = 773
  append = "memtest=30"
  read-only

This seems to stable the system although booting the computer does take a few minutes.

lyle_s 03-02-2014 06:51 PM

Hi, Stragonian, when you say it boots to a blank screen, do you mean the screen is literally blank?

Does the screen wait at "Booting the kernel." with the cursor blinking at the beginning of the next line?

Lyle.


All times are GMT -5. The time now is 06:57 PM.