Re: [newbie] Testing for bad RAM-solved and update
On Monday 26 February 2001 16:01, you wrote: > > I took the suspect ram sticks back to the shop where I bought them and the > tech put it in a windows box and booted it up. It booted right up, so they > said the memory was tested ok. They gave me an exchange anyway, but I > thought it interesting that their test was to boot it and let the bios test > tell them if it was ok. That's fine i'm back to 256M and it was instantly > recognized in LM7.2 on boot. Dennis M. First off I'm glad you have your memory problem solved and I'll bet it was an incompatibility, however if any of the Tech's that work for me ever used the method you just described to troubleshoot a memory problem they would be in the unemployment line... In my shop we have an SP3000 for testing Simms and Dimms and as a standard practice if they test good we exchange the memory with another brand and always make sure we are matching the same speed.. My advice find a better shop with professional Tech's. Scott Faulkner > This is the funny thing about my situation, no crashes, no weird things > going on, I just can't get linux to recognize my ram. The system doesn't > even seem to run any slower, transfers of web pages and searches are as > fast as ever. I am thinking motherboard, so I will try suggested test of > putting the ram in another box and see if it causes problems there. Two of > the sticks are only a couple of months old and I should be able to > exhchange them if I can determine good or bad. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Johnson > Sent: Wednesday, February 21, 2001 8:58 AM > To: '[EMAIL PROTECTED]' > Subject: RE: [newbie] Testing for bad RAM > > > Naa, I can't believe this, I have a 256 stick that crashed three computers > continuously and it counted up in the bios just fine in all three. This > 128 stick isn't quite so ruthless on me but linux apps keep crashing on me > left and right and weird things like the logout won't work sometimes in > X... > > -Original Message- > From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 20, 2001 2:20 PM > To: '[EMAIL PROTECTED]' > Subject: RE: [newbie] Testing for bad RAM > > > > I've been told by local computer techs that if your bios sees the ram at > bootup ,( in other words detects it and counts it off on the first screen > that shows your primary and secondary IDE devices and you can hit del to > get to bios) then the ram memory is good and should be functional. I am not > a technician so I am relying on their advice. > > BM__MailData-Original Message- > From: [EMAIL PROTECTED] [ > mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> ] On Behalf Of Mark Johnson > Sent: Tuesday, February 20, 2001 1:31 PM > To: LinuxNewbie (E-mail) > Subject:[newbie] Testing for bad RAM > > I am suspicious that my RAM is bad. Is there anyway in linux that I can > confirm this? Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: 7bit Content-Description:
Re: [newbie] Testing for bad RAM
On Tuesday 20 February 2001 14:19, you wrote: Hi Dennis, > > I've been told by local computer techs that if your bios sees the ram at > bootup ,( in other words detects it and counts it off on the first screen > that shows your primary and secondary IDE devices and you can hit del to > get to bios) then the ram memory is good and should be functional. I am not > a technician so I am relying on their advice. Find some new Techs... :) this is totally false, being a Tech myself with over 18 years experience I know for a fact that you can indeed have a system with either bad ram or incompatiable ram and the system will still post.. BIO's does not check or test each and every register on a stick of ram this can only be accomplished by either using a dedecated ram tester ( most repair shops have one ) or the less reliable method is PC-Check or one of it's many clones.. One of the other gotcha's with newer systems is ram module incompatibilitys two different manufactures modules installed and one being either of a different speed or just plain incompatiable and these problems 99% of the time do not show up until an OS is loaded and the ram is fully utilized... Regards, Scott > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson > Sent: Tuesday, February 20, 2001 1:31 PM > To: LinuxNewbie (E-mail) > Subject: [newbie] Testing for bad RAM > > I am suspicious that my RAM is bad. Is there anyway in linux that I can > confirm this? Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: quoted-printable Content-Description:
Re: [newbie] Ran KDE 2.1 twice; now X is dead
On Wednesday 21 February 2001 01:18, you wrote: > Hi all, Hi Miark, My reply is inline.. > I updated from KDE 2.0 to 2.0.1. It just didn't work, so I > figured I may as well try 2.1. So I did, and it worked > great. But after running 2.1 twice, X is dead (which may > very well be a coincidence). I can't run KDE, Gnome, or > anything else. This is what the tail end of the log says: > > --- > > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Error:Can't find file "pc" for symbols include > > Exiting > > Abandoning symbols file "default" > > Errors from xkbcomp are not fatal to the X server > Couldn't load XKB keymap, falling back to pre-XKB keymap > Could not init font path element unix/:-1, removing from > list! > > Fatal server error: could not open default font 'fixed' I had this exact same problem and found that if I went into BIO's and disabled asign irq for vga that the problem went away also double check all of your irq's that PNP ( Plug in Pray ) are asigning, quite a few times I've seen linux installs go south because of a resource conflict. Regards, Scott
[newbie] HP 7200 CDRW
I have Mandrake 7.2 installed and have an HP 7200 cdrw everything works perfectly and I understand that in order for the cdrw to work correctly linux has to emulate the cdrw as a scsi device, but the problem is when ever I use an app like package managment I see dual entrys same applies for reading directoys from the cdrw how can this be corrected?? TIA. Scott Faulkner
