I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting. At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good. There is an SKB article about 8.2 oopsing when additional RAM >= 1GB is added to a working system. The solution was to add "mem=880M" to the boot line. This had no effect for me. The system BIOS sees the extra RAM just fine (it's an Asus A7V133 motherboard that fully supports up to 1.5GB of RAM), and--sorry to say--the system dual boots Windows 2000 with the 1GB RAM installed just fine. I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing. Anyone seen anything like this before? Thanks! Mark -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
On Fri, 2004-02-06 at 18:07, L. Mark Stone wrote:
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting.
At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good.
There is an SKB article about 8.2 oopsing when additional RAM >= 1GB is added to a working system. The solution was to add "mem=880M" to the boot line. This had no effect for me.
The system BIOS sees the extra RAM just fine (it's an Asus A7V133 motherboard that fully supports up to 1.5GB of RAM), and--sorry to say--the system dual boots Windows 2000 with the 1GB RAM installed just fine.
I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing.
Anyone seen anything like this before?
Thanks! Mark
What does the BIOS say ? Dee
On Fri, 2004-02-06 at 22:21, W.D.McKinney wrote:
On Fri, 2004-02-06 at 18:07, L. Mark Stone wrote:
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting.
At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good.
There is an SKB article about 8.2 oopsing when additional RAM >= 1GB is added to a working system. The solution was to add "mem=880M" to the boot line. This had no effect for me.
The system BIOS sees the extra RAM just fine (it's an Asus A7V133 motherboard that fully supports up to 1.5GB of RAM), and--sorry to say--the system dual boots Windows 2000 with the 1GB RAM installed just fine.
I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing.
Anyone seen anything like this before?
Thanks! Mark
What does the BIOS say ?
The BIOS says 1,048,576 KB, which is close enough to 1GB for me! As it turns out, Windows is now hiccupping. So, I'm going to try blowing away the RAID-1 array from which I boot, and see if things aren't better without it. After doing some testing, my sense is the issue is with the controller (or conroller/mobo combo), not the RAM. I ran the new stick alone for a whole day, under both Linux and Windows, and not a problem. The sticks are also identical P/Ns from Crucial, and the brand/markings on the chips are also identical.
Dee
-- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
IMHO, RAM is what is killing your setup... I struggled with the same problem - for 3 weeks on a new setup, before pulling in the PC builder & between us trouble-shooting part-by-part for 3 hours... It turned out to be a problem on the MOBO, directly linked to the RAM. The better quality Kingston RAM was able to run at the correct BIOS RAM settings, whereas the 'pooer quality' RAM, at identical BIOS settings displayed intermittant errors, lockups & re-sets in WinBlow$, & 'no start' in Linux. We replaced the MOBO, updated the bios, removed all RAM except 1 chip, tested 3 chips in this way, then inserted 2 chips, cycled chips , eventually up to 3 chips - wheels fell off... I then went to a large city & purchased the quality RAM I was looking for. Bingo... no more RAM problems... On Sun, 2004-02-08 at 08:53, L. Mark Stone wrote:
On Fri, 2004-02-06 at 22:21, W.D.McKinney wrote:
On Fri, 2004-02-06 at 18:07, L. Mark Stone wrote:
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting.
At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good.
There is an SKB article about 8.2 oopsing when additional RAM >= 1GB is added to a working system. The solution was to add "mem=880M" to the boot line. This had no effect for me.
The system BIOS sees the extra RAM just fine (it's an Asus A7V133 motherboard that fully supports up to 1.5GB of RAM), and--sorry to say--the system dual boots Windows 2000 with the 1GB RAM installed just fine.
I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing.
Anyone seen anything like this before?
Thanks! Mark
What does the BIOS say ?
The BIOS says 1,048,576 KB, which is close enough to 1GB for me!
As it turns out, Windows is now hiccupping. So, I'm going to try blowing away the RAID-1 array from which I boot, and see if things aren't better without it.
After doing some testing, my sense is the issue is with the controller (or conroller/mobo combo), not the RAM. I ran the new stick alone for a whole day, under both Linux and Windows, and not a problem. The sticks are also identical P/Ns from Crucial, and the brand/markings on the chips are also identical.
Dee
-- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107
Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com -- Best regards,
Des Aubery... ============================================================> adTherm Technology --> _///^\\\_ Home of Virtual --> --> _///^\\\_ Thermal Engineering... --> Contact: --> _///^\\\_ o Automotive Heat- --> www.adtherm.com --> _///^\\\_ Transfer Devices --> info@adtherm.com --> _///^\\\_ o Virtual Radiator --> Ph : +66 42 614967 --> _///^\\\_ o CFD --> Fax: +66 42 614967 --> _///^\\\_ o FEA --> Mob: +66 6 8553801 --> _///^\\\_ o Brazing & Furnace --> --> _///^\\\_ o Consultants --> Des Aubery --> _///^\\\_ o Nocolok, CuproBraze --> ============================================================>
On Friday 06 February 2004 10:07 pm, L. Mark Stone wrote:
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting.
At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good.
In case of doubt about memory, I like to run memtest, which comes with SuSE Linux. It can be an option on bootup. It's usually at /boot/memtest.bin. Paul Abrahams
On Sat, 7 Feb 2004 14:07, L. Mark Stone wrote:
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting.
At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good.
There is an SKB article about 8.2 oopsing when additional RAM >= 1GB is added to a working system. The solution was to add "mem=880M" to the boot line. This had no effect for me.
The system BIOS sees the extra RAM just fine (it's an Asus A7V133 motherboard that fully supports up to 1.5GB of RAM), and--sorry to say--the system dual boots Windows 2000 with the 1GB RAM installed just fine.
I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing.
Anyone seen anything like this before?
Thanks! Mark
Have you tried running the memory test (memtest86)? Should be on the boot menu otherwise have a look here http://www.memtest86.com/ This will really test your RAM, takes quite a long time to run. It might be a problem with mismatched RAM sticks. Linux is rather hard on RAM when compared with windows. Linux uses all RAM available to the computer, whereas Windows only uses it as needed. I bet if you load up Windows with memory heavy apps it will fall over. -- Regards, Graham Smith ---------------------------------------------------------
There is a definite problem either with the RAM quality, or your MOBO... I had this problem when I first set up my current workstation. I purchased Kingston RAM & this sorted out the problem... I had managed to tweek the bios settings with the old RAM, & only inserted 2 RAM cards, instead of 3, in order to stabilise the system. Linux does not like bad RAM & will cough right at the start, whereas WinBlows will start up, but crash & give many errors... On Sat, 2004-02-07 at 10:07, L. Mark Stone wrote:
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting.
At first I thought it might be bad RAM (even though both sticks are identical part numbers from Crucial), so I took out the known good working stick and replaced it with the new stick. System booted fine with 512MB as before. OK, so new RAM stick is good.
There is an SKB article about 8.2 oopsing when additional RAM >= 1GB is added to a working system. The solution was to add "mem=880M" to the boot line. This had no effect for me.
The system BIOS sees the extra RAM just fine (it's an Asus A7V133 motherboard that fully supports up to 1.5GB of RAM), and--sorry to say--the system dual boots Windows 2000 with the 1GB RAM installed just fine.
I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing.
Anyone seen anything like this before?
Thanks! Mark
-- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107
Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com -- Best regards,
Des Aubery... ============================================================> adTherm Technology --> _///^\\\_ Home of Virtual --> --> _///^\\\_ Thermal Engineering... --> Contact: --> _///^\\\_ o Automotive Heat- --> www.adtherm.com --> _///^\\\_ Transfer Devices --> info@adtherm.com --> _///^\\\_ o Virtual Radiator --> Ph : +66 42 614967 --> _///^\\\_ o CFD --> Fax: +66 42 614967 --> _///^\\\_ o FEA --> Mob: +66 6 8553801 --> _///^\\\_ o Brazing & Furnace --> --> _///^\\\_ o Consultants --> Des Aubery --> _///^\\\_ o Nocolok, CuproBraze --> ============================================================>
"L. Mark Stone"
I just tried adding a second 512MB stick 'o RAM to my SuSE 9.0 system, and got a kernel oops upon rebooting. ... I suspect I am simply ignorant of the proper procedure for adding RAM, but heavy Googling and reading of the Admin Guide and the How-Tos has yielded nothing.
There is no such procedure. Linux uses BIOS to detect the amount of RAM. Some very old BIOSes didn't report the amount of RAM correctly and then it was necessary to boot with the option e.g. mem=1024M. Otherwise nothing else had to be done. -- A.M.
participants (6)
-
Alexandr Malusek -
Des Aubery -
Graham Smith -
L. Mark Stone -
Paul W. Abrahams -
W.D.McKinney