Re: Help! Memory gone missing...
On Sun, Mar 26, 2000 at 01:06:28PM +0100, Jonathan Heaney wrote: > This is new. When I upgraded 128 -> 192, the full 192 meg was seen > correctly (no need for append line in lilo.conf) Hi, I have never been able to figure out why some folks need the append line and some folks don't, but it sounds to me like you just joined the group that does require it. Maybe I am just too accepting, but I would add the append line, and if that fixed it I would quit wondering about it, and move on to bigger and better things . . . -- Thank you, Joe Bouchard Powered by Debian GNU/Linux
Re: [Help] Memory
[EMAIL PROTECTED] (Nguyen Hai Ha) writes: | On Mon, 24 May 1999, Mr. (Ms.) Gary L. Hennigan wrote: | | > It's probably something strange going on with the BIOS function used | > by linux to detect the amount of memory in your computer. I have two | > suggestions you can try: | > | > 1) Manually edit /etc/lilo.conf and add a line like: | > | > append="mem=160M" | > | > or, if you already have an "append" line add it to the line like: | > | > append="floppy=thinkpad,mem=160M" | > | > 2) Alternatively, upgrade to kernel 2.0.36 or higher. Starting with | > 2.0.36 the memory detection uses an extended BIOS call to get the | > amount of memory and this could solve your problem. If Windows can | > properly find the amount of RAM then a Linux kernel >= 2.0.36 will | > also, since they use the same BIOS call. | > | > Gary | > | | Thanks alot for your helpfull advice. I have installed the 2.0.36 | kernel and it seems to work well with the memory but the system | itself is unstable. Sometimes, expecially when I run big programs, | the system comes down with the message like "Segmentation fault". | But when I set the memory to 32M, 64M, or 128M, the system works well. | What does this mean? Could this be a kernel's bug? Hmm. That sounds a lot like a bad memory chip. I had a very similiar situation over the weekend when one of mine went bad. I'd get unexplained kernel crashes, segmentation faults, and my machine would occasionally lock up hard. After pulling my hair out I decided to set my machine's BIOS to do a full memory test and sure enough it failed. The BIOS test isn't always successful at detecting this, but in my case it was. You can try a much more thorough memory test program available in the hwtools Debian package. Install hwtools and read /usr/doc/hwtools/README.debian, looking specifically at memtest86. You boot into it directly from a floppy. See if it shows anything. One last suggestion would be to tell Linux to use 1MB less than you actually have using: append="mem=159MB" in your /etc/lilo.conf file. I've seen reports that this often helps with memory problems like you're describing. Gary
Re: [Help] Memory
On Mon, 24 May 1999, Mr. (Ms.) Gary L. Hennigan wrote: > It's probably something strange going on with the BIOS function used > by linux to detect the amount of memory in your computer. I have two > suggestions you can try: > > 1) Manually edit /etc/lilo.conf and add a line like: > > append="mem=160M" > > or, if you already have an "append" line add it to the line like: > > append="floppy=thinkpad,mem=160M" > > 2) Alternatively, upgrade to kernel 2.0.36 or higher. Starting with > 2.0.36 the memory detection uses an extended BIOS call to get the > amount of memory and this could solve your problem. If Windows can > properly find the amount of RAM then a Linux kernel >= 2.0.36 will > also, since they use the same BIOS call. > > Gary > Thanks alot for your helpfull advice. I have installed the 2.0.36 kernel and it seems to work well with the memory but the system itself is unstable. Sometimes, expecially when I run big programs, the system comes down with the message like "Segmentation fault". But when I set the memory to 32M, 64M, or 128M, the system works well. What does this mean? Could this be a kernel's bug? P.S. To Khalid EZZARAOUI <[EMAIL PROTECTED]>, Thanks for your help. -- Nguyen Hai Ha, <[EMAIL PROTECTED]> Graduate School of Informatics, Kyoto University, Japan
Re: [Help] Memory
[EMAIL PROTECTED] (Nguyen Hai Ha) writes: | Hi folks, | | I've just installed the debian 2.0.34 on my machine. | Everything seems to work well excepts the memory. | The real memory consists of 2 DIMM 128M+32M. But it | seems to me that the kernel doesn't think so. | | % cat /proc/meminfo | | total:used:free: shared: buffers: cached: | Mem: 15171584 13418496 1753088 7012352 593920 6090752 | Swap: 119697408 5156864 114540544 | MemTotal: 14816 kB | MemFree: 1712 kB | MemShared: 6848 kB | Buffers:580 kB | Cached:5948 kB | SwapTotal: 116892 kB | SwapFree:111856 kB | | I think this is the problem of the kernel's configuration. | Please tell me something. Thanks in advance. It's probably something strange going on with the BIOS function used by linux to detect the amount of memory in your computer. I have two suggestions you can try: 1) Manually edit /etc/lilo.conf and add a line like: append="mem=160M" or, if you already have an "append" line add it to the line like: append="floppy=thinkpad,mem=160M" 2) Alternatively, upgrade to kernel 2.0.36 or higher. Starting with 2.0.36 the memory detection uses an extended BIOS call to get the amount of memory and this could solve your problem. If Windows can properly find the amount of RAM then a Linux kernel >= 2.0.36 will also, since they use the same BIOS call. Gary
