Hello,
A brief introduction followed by a question. I am new to this list but have been using Linux on and off over the last 3 years. My current system is PIII 667Mhz, 128M RAM Dual booting with Win 98SE and SuSe 7.0(Professional, an amazing boxed set).
Now my question concerns the 64M recognition limit, I have added the line mem=128M to the append line in the LILO configuration section of YAST1. When I interrogate with top or the K memory utility it tells be that I have 64M RAM. Have I done something wrong or is it one of those things where the software is wrong ?
Many thanks in advance
Andy Cartwright
P.S.
May be a bit out of date now but I have the boxed set SuSe 6.0 with manual boot disks etc. I have the new V7.0 Pro so have no need for 6.0, it is free to any good home if anyone can make any use of it.
Hi Andy
On Wed, 10 Jan 2001, Andy Cartwright wrote:
Now my question concerns the 64M recognition limit, I have added the line mem=128M to the append line in the LILO configuration section of YAST1. When I interrogate with top or the K memory utility it tells be that I have 64M RAM. Have I done something wrong or is it one of those things where the software is wrong ?
Ok a few ideas are does windows see the memory? (I guess so), and have you re-run lilo since you added the line in Yast or does Yast do this automatically? also the line you want is probably (from memory)
append="mem=128M"
as this is working on several machines here. I would try adding the line by hand (as root) and re-running lilo (also as root). If this does not fix the problem then you could try telling us which version of the kernel you are running and the make/model of your motherboard.
The chances of the software being wrong are very low indeed ;-)
Adam
Adam Bower wrote:
Ok a few ideas are does windows see the memory? (I guess so), and have you re-run lilo since you added the line in Yast or does Yast do this automatically? also the line you want is probably (from memory)
append="mem=128M"
Yes, YAST does this. I have checked /etc/lilo.conf and my append line is as follows :- append="hdc=ide-scsi hdd=ide-scsi mem=128M" and yes windows sees all 128Mb.
as this is working on several machines here. I would try adding the line by hand (as root) and re-running lilo (also as root). If this does not fix the problem then you could try telling us which version of the kernel you are running and the make/model of your motherboard.
Kernel is 2.2.16, motherboard is Packard Bell Phoenix+, chipset VIA Apollo 133A.
The chances of the software being wrong are very low indeed ;-)
I fear you are correct here!!
Many thanks so far
Andy Cartwright ivorydawn@ntlworld.com
P.S. I am not using lilo for the dual boot but am using Bootmagic, could this be the reason?
On Wed, Jan 10, 2001 at 06:59:54PM +0000, Andy Cartwright wrote:
Adam Bower wrote:
...
The chances of the software being wrong are very low indeed ;-)
I fear you are correct here!!
As a double check you can look at how much memory the kernel reports when it starts. Though this usually disappears too fast to see you can get it back by running the 'dmesg' command. the first few lines will look something like:
Linux version 2.2.18pre21 (fozzy@pelvoux) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #9 Fri Dec 29 12:26:40 GMT 2000 Detected 755301 kHz processor. ide_setup: idebus=66 Console: colour VGA+ 80x25 Calibrating delay loop... 1507.32 BogoMIPS Memory: 647560k/655360k available (668k kernel code, 416k reserved, 6676k data, 40k init)
P.S. I am not using lilo for the dual boot but am using Bootmagic, could this be the reason?
I assume from this that you have bootmagic on the MBR and have LILO installed on the boot record of the primary linux partition. If that is the case then I would expect the configuration to work correctly.
The exception would be if bootmagic had moved a LILO boot record from the MBR, where the Linux installer had put it, to the Linux partition. In that case it may be possible that the 'lilo' command would not update the boot parameters correctly.
Hi Steve,
Steven Fosdick wrote:
As a double check you can look at how much memory the kernel reports when it starts. Though this usually disappears too fast to see you can get it back by running the 'dmesg' command. the first few lines will look something like:
Dmesg gives me this:-
Linux version 2.2.16 (root@Pentium.suse.de) (gcc version 2.95.2 19991024 (releas e)) #1 Wed Aug 2 20:22:26 GMT 2000 Detected 666685 kHz processor. ide_setup: hdc=ide-scsi ide_setup: hdd=ide-scsi Console: colour VGA+ 80x25 Calibrating delay loop... 1330.38 BogoMIPS Memory: 63324k/66556k available (1448k kernel code, 412k reserved, 980k data, 68 k init, 0k bigmem)
I assume from this that you have bootmagic on the MBR and have LILO installed on the boot record of the primary linux partition. If that is the case then I would expect the configuration to work correctly.
The exception would be if bootmagic had moved a LILO boot record from the MBR, where the Linux installer had put it, to the Linux partition. In that case it may be possible that the 'lilo' command would not update the boot parameters correctly.
I will double check, when I installed I specified lilo to go on /boot and Bootmagic is on MBR. The SCSI emulation works OK so I assume that everything is being loaded from the append line of lilo.conf.
Many thanks all for the help so far
Andy Cartwright ivorydawn@ntlworld.com
On Thu, 11 Jan 2001, Andy Cartwright wrote:
I will double check, when I installed I specified lilo to go on /boot and Bootmagic is on MBR. The SCSI emulation works OK so I assume that everything is being loaded from the append line of lilo.conf.
OK if the APPEND=mem line is exactly the same in lilo.conf as what I specified earlier I would try to re-run lilo and see what happens, but be warned that this may cause a problem because of boot magic (a program that I have no experience of myself). Also could someone confirm that when you edit the lilo.conf in Yast that yast re-runs lilo for you?
Adam
Hi Adam,
Adam Bower wrote:
OK if the APPEND=mem line is exactly the same in lilo.conf as what I specified earlier I would try to re-run lilo and see what happens, but be warned that this may cause a problem because of boot magic (a program that I have no experience of myself). Also could someone confirm that when you edit the lilo.conf in Yast that yast re-runs lilo for you?
Following on from the message from steve I ran YAST and specified lilo to run from /boot. It does run lilo and when I rebooted BINGO 128Mb. Obviously I had specified incorrectly when I amended YAST to include mem=128M.
The box is somewhat faster now!!
Many thanks all for the help, it has been much appreciated
Andy Cartwright ivorydawn@ntlworld.com
-
Adam Bower -
Andy Cartwright -
Steven Fosdick