Re: Memory - 512 SIMMS - Status
Oh, I did very briefly... not much was available... Cliff Wells wrote: You might just try googling for it, you might find other people who have run into the same problem with that model of mobo. I'd do it for you but I'm off to a Python SIG =) -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Tue, 2003-01-14 at 08:03, Cliff Wells wrote: > On Mon, 2003-01-13 at 22:57, Joshua Schmidlkofer wrote: > > Nice message numnuts. It's blank. Tease me w/ a subject, then give me > > the blank screen. dick. > > I'd like to apologise to everyone on the list. My friend is paralyzed > from the neck up and doesn't realize he replied to the list instead of > me. > > -- > Cliff Wells, Software Engineer > Logiplex Corporation (www.logiplex.net) > (503) 978-6726 x308 (800) 735-0555 x308 Actually, I owe everyone an apology, it's true, I am paralyzed from the neck up. The only defense I can offer is a three week old son, he is not sleeping that much yet, and I am a wee-bit over tired. In any case, my mail filters order is fixed now. js -- VB programmers ask why no one takes them seriously, it's somewhat akin to a McDonalds manager asking employees why they don't take their 'career' seriously. signature.asc Description: This is a digitally signed message part
Re: Memory - 512 SIMMS - Status
On Tue, 2003-01-14 at 17:00, John B. Moore wrote: > I agree, so far I have found nothing about the voltage requirements for > the SIMMs on the FIC website. I posted a tech support question about > this yesterday, no reply, also posted a queston on their "forums" so > far, no reply.. > >Maybe I need to go motherboard shopping... You might just try googling for it, you might find other people who have run into the same problem with that model of mobo. I'd do it for you but I'm off to a Python SIG =) -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
I agree, so far I have found nothing about the voltage requirements for the SIMMs on the FIC website. I posted a tech support question about this yesterday, no reply, also posted a queston on their "forums" so far, no reply.. Maybe I need to go motherboard shopping... John... Cliff Wells wrote: On Tue, 2003-01-14 at 14:05, John B. Moore wrote: Thanks, that makes sense.. trouble is the Manual I have does not indicate the voltage for either the DIMM or the SIMMs.. I'll check the FIC website and see if there is more info on this.. That's what I love about manuals that come with most modern PC's. A dearth of technical info, but lots of stuff about how to sit up straight in your chair and take a break every 15 minutes. Come to think of it, the breaks are inevitable if you're running Windows: they could just tell you to take a break on every reboot -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
On Tue, 2003-01-14 at 14:05, John B. Moore wrote: > Thanks, that makes sense.. trouble is the Manual I have does not > indicate the voltage for either the DIMM or the SIMMs.. I'll check the > FIC website and see if there is more info on this.. That's what I love about manuals that come with most modern PC's. A dearth of technical info, but lots of stuff about how to sit up straight in your chair and take a break every 15 minutes. Come to think of it, the breaks are inevitable if you're running Windows: they could just tell you to take a break on every reboot -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
Nate, Thanks, that makes sense.. trouble is the Manual I have does not indicate the voltage for either the DIMM or the SIMMs.. I'll check the FIC website and see if there is more info on this.. I'll try the 511 suggestion tomorrow.. (got to earn some money first..) John.. nate wrote: John B. Moore said: Correct... mem=512M ... (fingers getting behind brain...) some system setups have a tendancy to eat up to 1MB of extra memory, on such systems the solution is to use mem=XXXM where XXX is 1MB less then what you have, so in your case mem=511M . I have encountered this with certain bios setups too(I forget which bios option(s) do this but have seen the behavior change back to "normal" after tweaking the bios) also I reccomend checking your MB manual again to be sure your memory is the right voltage. Some boards use 5V simms with 3.3V dimm sockets which is why they reccomend against mixing SIMMS & DIMMS because the 5V simm voltage channel can(eventually/potentially) damage the lower voltage DIMMS (thats at least how one of my board manuals explains it, I think it's a AOpen AP5T-3 running a P200MMX). If I remember your original email right you mentioned using 3.3V simms .. just a thought or 2 .. nate -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
John B. Moore said: > Correct... mem=512M ... (fingers getting behind brain...) some system setups have a tendancy to eat up to 1MB of extra memory, on such systems the solution is to use mem=XXXM where XXX is 1MB less then what you have, so in your case mem=511M . I have encountered this with certain bios setups too(I forget which bios option(s) do this but have seen the behavior change back to "normal" after tweaking the bios) also I reccomend checking your MB manual again to be sure your memory is the right voltage. Some boards use 5V simms with 3.3V dimm sockets which is why they reccomend against mixing SIMMS & DIMMS because the 5V simm voltage channel can(eventually/potentially) damage the lower voltage DIMMS (thats at least how one of my board manuals explains it, I think it's a AOpen AP5T-3 running a P200MMX). If I remember your original email right you mentioned using 3.3V simms .. just a thought or 2 .. nate -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
Correct... mem=512M ... (fingers getting behind brain...) Cliff Wells wrote: On Tue, 2003-01-14 at 09:18, John B. Moore wrote: [snip] Using mem=512 still sometimes causes a kernal panic during the INIT. I [snip] entering mem=512 and pressing enter I get Error 28: Selected item can not fit into memory [snip] I then removed half of the memory and tested with and without the MEM=256 Just to be certain, since you repeated the same typo three times: it's MEM=512M, not MEM=512. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14 Jan 2003 07:59:06 -0800, Cliff Wells wrote: > On Mon, 2003-01-13 at 16:48, Edward Dekkers wrote: > > > [Once again, reposting - I wonder if this is due to GPG sig > > > attachement?] > > > > I don't know what it is with your mails Cliff, but they nearly > > always show up on my screen as attachments instead of plain vanilla > > e-mail, like everybody else's. > > > > Mind you, I'm using LookOut here at work so the problem could be at > > this end. > > This is a known problem with Outlook. It doesn't properly parse > S/MIME messages. > > Usually when I post to public forums I do it without GPG signing as a > courtesy to the Outlook users, but since this is a Linux forum I > hadn't followed that rule. I suppose I'll stop signing messages here > as well. > > Oh well. It looks like something else. The message in question is multipart, but truncated. No S/MIME PGP detached signature at all. The second part is missing. This is how the message source looks below the mail headers: https://listman.redhat.com/pipermail/redhat-list/2003-January/164312.html - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+JGoV0iMVcrivHFQRAjOmAJ9m0LCSILcsh/Ceg9XoTAdyj5dv3gCghoH4 lorTooEOsdpJwVQ4RA/4SoI= =gVEe -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
On Tue, 2003-01-14 at 09:18, John B. Moore wrote: [snip] > Using mem=512 still sometimes causes a kernal panic during the INIT. I [snip] > entering mem=512 and pressing enter I get > > Error 28: Selected item can not fit into memory [snip] > I then removed half of the memory and tested with and without the MEM=256 Just to be certain, since you repeated the same typo three times: it's MEM=512M, not MEM=512. -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Tue, 2003-01-14 at 11:44, Kent Perrier wrote: > On Tue, 2003-01-14 at 09:59, Cliff Wells wrote: > > This is a known problem with Outlook. It doesn't properly parse S/MIME > > messages. > > > > Usually when I post to public forums I do it without GPG signing as a > > courtesy to the Outlook users, but since this is a Linux forum I hadn't > > followed that rule. I suppose I'll stop signing messages here as well. > > > > Oh well. Sorry, should have been clearer. The problem with my postings showing up as blank is a mystery. What I was referring to with Outlook is Edward's comment that often my posts come as attachments when he reads them with Outlook. This is a known issue (and if you use Evolution, it's good to be aware of it if you are communicating with people who use Outlook as S/MIME is the way Evo 1.2 does it now). > As an FYI, I use Evolution 1.2.1 and I got a blank screen as well... -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Tue, 2003-01-14 at 09:59, Cliff Wells wrote: > This is a known problem with Outlook. It doesn't properly parse S/MIME > messages. > > Usually when I post to public forums I do it without GPG signing as a > courtesy to the Outlook users, but since this is a Linux forum I hadn't > followed that rule. I suppose I'll stop signing messages here as well. > > Oh well. As an FYI, I use Evolution 1.2.1 and I got a blank screen as well... Kent -- Kent Perrier <[EMAIL PROTECTED]> -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS - Status
Folks, Ok, here is where I'm at and it does not look to good.. On the Memory front I ran DocMemory over night (15+ hours) and it has passed 13 iterations of the test sequence. I had also run memtest86 and it did show some problems. I had called Cruial and they had recommended DocMemory.. I'll call them again and see if they have any further ideas.. Booting Linux Using mem=512 still sometimes causes a kernal panic during the INIT. I get different errors each time I try it. Sometimes it just hangs right before the INIT with the output at: Freeing unused kernel memory 160k freed.. Other times it gets started on the INIT sequence and spits out some error relating to either not finding a "file" or memory allocation . Interestingly now I'm getting a different error.. immediately after entering mem=512 and pressing enter I get Error 28: Selected item can not fit into memory ??? I then removed half of the memory and tested with and without the MEM=256 with: I got the above error twice and then on the third time it made it to the INIT.. then froze without: Always froze at "Freeing unused kernel" which is right before the INIT. There appears to be no settings in CMOS that might affect this.. so I think I'm SOL.. Any further WAGs...??? John... Daily, Shane, CTR wrote: Put a space before MEM=512M -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Mon, 2003-01-13 at 22:57, Joshua Schmidlkofer wrote: > Nice message numnuts. It's blank. Tease me w/ a subject, then give me > the blank screen. dick. I'd like to apologise to everyone on the list. My friend is paralyzed from the neck up and doesn't realize he replied to the list instead of me. -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Mon, 2003-01-13 at 16:48, Edward Dekkers wrote: > > [Once again, reposting - I wonder if this is due to GPG sig > > attachement?] > > I don't know what it is with your mails Cliff, but they nearly always show > up on my screen as attachments instead of plain vanilla e-mail, like > everybody else's. > > Mind you, I'm using LookOut here at work so the problem could be at this > end. This is a known problem with Outlook. It doesn't properly parse S/MIME messages. Usually when I post to public forums I do it without GPG signing as a courtesy to the Outlook users, but since this is a Linux forum I hadn't followed that rule. I suppose I'll stop signing messages here as well. Oh well. Regards, -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
Nice message numnuts. It's blank. Tease me w/ a subject, then give me the blank screen. dick. -- VB programmers ask why no one takes them seriously, it's somewhat akin to a McDonalds manager asking employees why they don't take their 'career' seriously. signature.asc Description: This is a digitally signed message part
Re: Memory - 512 SIMMS
Fred, Thanks for the thoughts... I'll investigate.. I have run memtest and MemoryDoc (or is it DocMemory??) the memtest86 did appear to report a problem in the test #6, I then called Crucial and they ask me to run the DocMemory tester.. The quick test passed, I'm running the "BurnIn" all night tonight.. I'll beat on this some more in the morning... John... fred smith wrote: I've got a pair of VA503+ boards here, which also allow both SIMMS and DIMMS. Only once have I attempted to use 72 pin SIMMS in either board, and that attempt did not meet with success. It MAY be that I needed to enter the SETUP util and change the RAM timings to be something suitable for that form of RAM, but somehow I had the idea that the board would take care of that for me. After a little bit of time fooling with it I put the PC100 DIMM back in it and gave up. One question, of course, is how similar is a 503+ to a 502. Does anything else boot on it? have you tried DOS/Windoze? How about MEMTEST86 ? (free from www.memtest86.com) Checked the FIC web site for a FAQ or troubleshooting info? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Mon, Jan 13, 2003 at 01:14:15PM -0800, John B. Moore wrote: > Cliff Wells wrote: > >I take it you mean 64MB DIMMS . > Of course, my bad... > >Why not use 2 256MB DIMMS? Cheaper, faster and easier to find. > According to my motherboard doc, 64 is the largest DIMM allowed. > >I've had a couple of mobos that supported both SIMMS and DIMMS. The > >DIMMS always worked better. However, you might check your BIOS settings > >to make sure that the memory is configured properly. Many BIOS' will > >let you set timing and other things associated with RAM. Sometimes > >tweaking these can make a difference. > > > According to my motherboard docs there is no "switch" settings, it auto > configures.. > >You might also try passing mem=512M on the boot line. >Yes, I've tried that and I get a kernal panic.. (see response to > other messages) I've got a pair of VA503+ boards here, which also allow both SIMMS and DIMMS. Only once have I attempted to use 72 pin SIMMS in either board, and that attempt did not meet with success. It MAY be that I needed to enter the SETUP util and change the RAM timings to be something suitable for that form of RAM, but somehow I had the idea that the board would take care of that for me. After a little bit of time fooling with it I put the PC100 DIMM back in it and gave up. One question, of course, is how similar is a 503+ to a 502. Does anything else boot on it? have you tried DOS/Windoze? How about MEMTEST86 ? (free from www.memtest86.com) Checked the FIC web site for a FAQ or troubleshooting info? -- Fred Smith -- [EMAIL PROTECTED] - But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. --- Romans 5:8 (niv) -- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
> [Once again, reposting - I wonder if this is due to GPG sig > attachement?] I don't know what it is with your mails Cliff, but they nearly always show up on my screen as attachments instead of plain vanilla e-mail, like everybody else's. Mind you, I'm using LookOut here at work so the problem could be at this end. --- Edward Dekkers (Director) Triple D Computer Services P/L -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
Kevin, Thanks for that info.. I'll followup on this ideas as soon as I finish the memory tests... John... Kevin MacNeil wrote: What chipset does this mainboard have? My wife has a VA-503+ (also with dimm and simm slots) with 1mb onboard cache and an mvp3 chipset, and it can't cache more than 256mb ram. Having more ram than the system can cache can cause performance and stability problems. You may want to post your question on alt.comp.periphs.mainboard.fic. Some folks hang out there who are knowledgeable about older boards. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Mon, Jan 13, 2003 at 10:27:15AM -0800, John B. Moore wrote: > Greetings, > >I need to run this by you folks and see if there are any > alternatives/issues that might get this to work. (using the very latest > kernal) > > I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. What chipset does this mainboard have? My wife has a VA-503+ (also with dimm and simm slots) with 1mb onboard cache and an mvp3 chipset, and it can't cache more than 256mb ram. Having more ram than the system can cache can cause performance and stability problems. You may want to post your question on alt.comp.periphs.mainboard.fic. Some folks hang out there who are knowledgeable about older boards. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
Shane, Ahhh Ok, I'll test that as soon as the memory test finishes.. So far it is at test #4 (of 8) and everything is passing. John... Daily, Shane, CTR wrote: Put a space before MEM=512M -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 2:30 PM To: [EMAIL PROTECTED] Subject: Re: Memory - 512 SIMMS Shane, Thanks,, Unfortunately I must be doing something wrong I'm using GRUB I believe and what I got in response during the boot was mkrootdev: label: /MEM=512M not found ...and then a kernal panic... I'm runing a memory test right now using memtest-86 v3.0 so I'll confirm that the memory is good.. I would like to understand why the above command did not work..??? John... Daily, Shane, CTR wrote: If using LILO Lilo Boot: linux MEM=512M If using GRUB select image (probably default) hit "a" key and append MEM=512M so that it reads something like this grub append> ro root=LABEL=/ MEM=512M I think that's correct ? Shane -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 12:37 PM To: [EMAIL PROTECTED] Subject: Re: Memory - 512 SIMMS Shane, No.. Frankly I'm not that familiar with how to do this.. Where can do this..?? Thanks... John... Daily, Shane, CTR wrote: Have you tried appending MEM=512M to the boot loader? -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 11:27 AM To: [EMAIL PROTECTED] Subject: Memory - 512 SIMMS Greetings, I need to run this by you folks and see if there are any alternatives/issues that might get this to work. (using the very latest kernal) I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. It is currently runing on the DIMM with two 64k DIMMS. Everything works fine. I wanted to up the memory and the motherboard Manual indicates that I can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from Crucial.com) This will get me to 512 RAM. The motherboard seems to accept the memory just fine and I get the boot up all the way to the "INIT: 2.84 Booting" and then it locks.. Am I SOL or is there something I can try to help Linux work with this memory..?? Thanks much John.. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: Memory - 512 SIMMS
Put a space before MEM=512M -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 2:30 PM To: [EMAIL PROTECTED] Subject: Re: Memory - 512 SIMMS Shane, Thanks,, Unfortunately I must be doing something wrong I'm using GRUB I believe and what I got in response during the boot was mkrootdev: label: /MEM=512M not found ...and then a kernal panic... I'm runing a memory test right now using memtest-86 v3.0 so I'll confirm that the memory is good.. I would like to understand why the above command did not work..??? John... Daily, Shane, CTR wrote: >If using LILO > >Lilo Boot: linux MEM=512M > >If using GRUB >select image (probably default) >hit "a" key >and append MEM=512M so that it reads something like this > >grub append> ro root=LABEL=/ MEM=512M > > >I think that's correct ? > > >Shane > >-Original Message- >From: John B. Moore [mailto:[EMAIL PROTECTED]] >Sent: Monday, January 13, 2003 12:37 PM >To: [EMAIL PROTECTED] >Subject: Re: Memory - 512 SIMMS > > >Shane, > >No.. Frankly I'm not that familiar with how to do this.. Where can >do this..?? > >Thanks... > >John... > >Daily, Shane, CTR wrote: > > > >>Have you tried appending MEM=512M to the boot loader? >> >>-Original Message- >>From: John B. Moore [mailto:[EMAIL PROTECTED]] >>Sent: Monday, January 13, 2003 11:27 AM >>To: [EMAIL PROTECTED] >>Subject: Memory - 512 SIMMS >> >> >>Greetings, >> >> I need to run this by you folks and see if there are any >>alternatives/issues that might get this to work. (using the very latest >>kernal) >> >>I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. >> >>It is currently runing on the DIMM with two 64k DIMMS. Everything works >>fine. >> >>I wanted to up the memory and the motherboard Manual indicates that I >>can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) >>as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from >>Crucial.com) This will get me to 512 RAM. >> >>The motherboard seems to accept the memory just fine and I get the boot >>up all the way to the "INIT: 2.84 Booting" and then it locks.. >> >>Am I SOL or is there something I can try to help Linux work with this >>memory..?? >> >> Thanks much >> >>John.. >> >> >> >> >> >> >> > > > > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
Shane, Thanks,, Unfortunately I must be doing something wrong I'm using GRUB I believe and what I got in response during the boot was mkrootdev: label: /MEM=512M not found ...and then a kernal panic... I'm runing a memory test right now using memtest-86 v3.0 so I'll confirm that the memory is good.. I would like to understand why the above command did not work..??? John... Daily, Shane, CTR wrote: If using LILO Lilo Boot: linux MEM=512M If using GRUB select image (probably default) hit "a" key and append MEM=512M so that it reads something like this grub append> ro root=LABEL=/ MEM=512M I think that's correct ? Shane -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 12:37 PM To: [EMAIL PROTECTED] Subject: Re: Memory - 512 SIMMS Shane, No.. Frankly I'm not that familiar with how to do this.. Where can do this..?? Thanks... John... Daily, Shane, CTR wrote: Have you tried appending MEM=512M to the boot loader? -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 11:27 AM To: [EMAIL PROTECTED] Subject: Memory - 512 SIMMS Greetings, I need to run this by you folks and see if there are any alternatives/issues that might get this to work. (using the very latest kernal) I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. It is currently runing on the DIMM with two 64k DIMMS. Everything works fine. I wanted to up the memory and the motherboard Manual indicates that I can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from Crucial.com) This will get me to 512 RAM. The motherboard seems to accept the memory just fine and I get the boot up all the way to the "INIT: 2.84 Booting" and then it locks.. Am I SOL or is there something I can try to help Linux work with this memory..?? Thanks much John.. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
Cliff Wells wrote: I take it you mean 64MB DIMMS . Of course, my bad... Why not use 2 256MB DIMMS? Cheaper, faster and easier to find. According to my motherboard doc, 64 is the largest DIMM allowed. I've had a couple of mobos that supported both SIMMS and DIMMS. The DIMMS always worked better. However, you might check your BIOS settings to make sure that the memory is configured properly. Many BIOS' will let you set timing and other things associated with RAM. Sometimes tweaking these can make a difference. According to my motherboard docs there is no "switch" settings, it auto configures.. You might also try passing mem=512M on the boot line. Yes, I've tried that and I get a kernal panic.. (see response to other messages) -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
[Once again, reposting - I wonder if this is due to GPG sig attachement?] On Mon, 2003-01-13 at 10:27, John B. Moore wrote: > Greetings, > >I need to run this by you folks and see if there are any > alternatives/issues that might get this to work. (using the very latest > kernal) > > I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. > > It is currently runing on the DIMM with two 64k DIMMS. Everything works > fine. I take it you mean 64MB DIMMS . > I wanted to up the memory and the motherboard Manual indicates that I > can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) > as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from > Crucial.com) This will get me to 512 RAM. Why not use 2 256MB DIMMS? Cheaper, faster and easier to find. > The motherboard seems to accept the memory just fine and I get the boot > up all the way to the "INIT: 2.84 Booting" and then it locks.. > > Am I SOL or is there something I can try to help Linux work with this > memory..?? I've had a couple of mobos that supported both SIMMS and DIMMS. The DIMMS always worked better. However, you might check your BIOS settings to make sure that the memory is configured properly. Many BIOS' will let you set timing and other things associated with RAM. Sometimes tweaking these can make a difference. You might also try passing mem=512M on the boot line. -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 x308 (800) 735-0555 x308 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Mon, 2003-01-13 at 12:27, John B. Moore wrote: > Greetings, > >I need to run this by you folks and see if there are any > alternatives/issues that might get this to work. (using the very latest > kernal) > > I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. > > It is currently runing on the DIMM with two 64k DIMMS. Everything works > fine. > > I wanted to up the memory and the motherboard Manual indicates that I > can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) > as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from > Crucial.com) This will get me to 512 RAM. > > The motherboard seems to accept the memory just fine and I get the boot > up all the way to the "INIT: 2.84 Booting" and then it locks.. > > Am I SOL or is there something I can try to help Linux work with this > memory..?? Have your ran the Memory testing program from memtest86.com? This will exercise you memory to see if there is a problem with it. It sounds like you have some incompatibility with the memory/mobo combination. Have called Crucial for some support? Kent -- Kent Perrier <[EMAIL PROTECTED]> -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
On Mon, 2003-01-13 at 10:27, John B. Moore wrote: > Greetings, > >I need to run this by you folks and see if there are any > alternatives/issues that might get this to work. (using the very latest > kernal) > > I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: Memory - 512 SIMMS
If using LILO Lilo Boot: linux MEM=512M If using GRUB select image (probably default) hit "a" key and append MEM=512M so that it reads something like this grub append> ro root=LABEL=/ MEM=512M I think that's correct ? Shane -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 12:37 PM To: [EMAIL PROTECTED] Subject: Re: Memory - 512 SIMMS Shane, No.. Frankly I'm not that familiar with how to do this.. Where can do this..?? Thanks... John... Daily, Shane, CTR wrote: >Have you tried appending MEM=512M to the boot loader? > >-Original Message- >From: John B. Moore [mailto:[EMAIL PROTECTED]] >Sent: Monday, January 13, 2003 11:27 AM >To: [EMAIL PROTECTED] >Subject: Memory - 512 SIMMS > > >Greetings, > > I need to run this by you folks and see if there are any >alternatives/issues that might get this to work. (using the very latest >kernal) > >I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. > >It is currently runing on the DIMM with two 64k DIMMS. Everything works >fine. > >I wanted to up the memory and the motherboard Manual indicates that I >can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) >as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from >Crucial.com) This will get me to 512 RAM. > >The motherboard seems to accept the memory just fine and I get the boot >up all the way to the "INIT: 2.84 Booting" and then it locks.. > >Am I SOL or is there something I can try to help Linux work with this >memory..?? > > Thanks much > >John.. > > > > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Memory - 512 SIMMS
Shane, No.. Frankly I'm not that familiar with how to do this.. Where can do this..?? Thanks... John... Daily, Shane, CTR wrote: Have you tried appending MEM=512M to the boot loader? -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 11:27 AM To: [EMAIL PROTECTED] Subject: Memory - 512 SIMMS Greetings, I need to run this by you folks and see if there are any alternatives/issues that might get this to work. (using the very latest kernal) I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. It is currently runing on the DIMM with two 64k DIMMS. Everything works fine. I wanted to up the memory and the motherboard Manual indicates that I can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from Crucial.com) This will get me to 512 RAM. The motherboard seems to accept the memory just fine and I get the boot up all the way to the "INIT: 2.84 Booting" and then it locks.. Am I SOL or is there something I can try to help Linux work with this memory..?? Thanks much John.. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: Memory - 512 SIMMS
Have you tried appending MEM=512M to the boot loader? -Original Message- From: John B. Moore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 11:27 AM To: [EMAIL PROTECTED] Subject: Memory - 512 SIMMS Greetings, I need to run this by you folks and see if there are any alternatives/issues that might get this to work. (using the very latest kernal) I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. It is currently runing on the DIMM with two 64k DIMMS. Everything works fine. I wanted to up the memory and the motherboard Manual indicates that I can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from Crucial.com) This will get me to 512 RAM. The motherboard seems to accept the memory just fine and I get the boot up all the way to the "INIT: 2.84 Booting" and then it locks.. Am I SOL or is there something I can try to help Linux work with this memory..?? Thanks much John.. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Memory - 512 SIMMS
Greetings, I need to run this by you folks and see if there are any alternatives/issues that might get this to work. (using the very latest kernal) I have a VA-502 revA1 motherboard that has both DIMM slots and SIMM slots. It is currently runing on the DIMM with two 64k DIMMS. Everything works fine. I wanted to up the memory and the motherboard Manual indicates that I can put 4 128 SIMMS into the 4 SIMM slots (also must remove the DIMMS) as per the Manual (128MB 72pin SIMM EDO (3.3v) 60ns bought memory from Crucial.com) This will get me to 512 RAM. The motherboard seems to accept the memory just fine and I get the boot up all the way to the "INIT: 2.84 Booting" and then it locks.. Am I SOL or is there something I can try to help Linux work with this memory..?? Thanks much John.. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
