[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ltsp-developer
Subject:    Re: [Ltsp-developer] Workstation halts when loading the NIC module
From:       Bryce C <Plug () BryceCo ! Net>
Date:       2004-12-26 17:40:12
Message-ID: 1104082812.6670.21.camel () school3 ! CoBryce ! Com
[Download RAW message or body]

Just to test the RAM theory (which does still hold ground and I've come
across the very same before), try switching the RAM between another
computer. If the other computer fails and this one works, you've
probably found the problem.

-- 
Bryce C <Plug@BryceCo.Net>
CoBryce Communications


On Sun, 2004-26-12 at 05:48 -0500, Dr. Sichendra Bista wrote:
> Thank you, Andy/
> 
> But none of the stuffs you spedified is valid as the motherboard has
> built in 8MB RAM and I added two 8MB RAMs piece by piece after
> testing. So no problem with the RAM.
> 
> Second, I don't see any reason to replace the box as the two other
> workstations are functioning fine with similar configurations (even
> slower ones 100Mhz and 133Mhz and samd NIC Cards except 32 MB of RAM.
> Indeed, Jim helped me to configure one of them in the beginning) The
> current one is PI 166Mhz.
> 
> So, the point that RAM is invalid or the machine needs to be changed
> does not hold ground, methin.
> 
> Thank you again and Season's Greetings to you and your family
> 
> Sichendra
> 
> 
> On Sun, 26 Dec 2004 11:11:22 +0200, Andy Rabagliati <andyr@wizzy.com> wrote:
> > On Sun, 26 Dec 2004, Dr. Sichendra Bista wrote:
> > 
> > > If the RAM is bad, it won't show when the machine is booted (BIOS
> > > count) in the beginning. I do not see your reasoning why you suspected
> > > it is RAM? Could you explain?
> > 
> > Ram is hard to test.
> > 
> > Sticking patterns in and reading them back is a basic go/nogo test, but
> > far from complete.
> > 
> > Refresh ? If I store something there, will it be there 10 seconds later ?
> > 
> > Patterns ? A one in a sea of zeroes ? vice-versa ?
> > 
> > Often access timing can be different if the CPU is /executing/ code out
> > of that block as opposed to read/write. Data read/write implies there is
> > another fetch stream (the instruction stream) also being fetched - maybe
> > that is enough to give the data portion a 'rest' between accesses ?
> > 
> > memtest86 is a small program you can run off a boot floppy - but is
> > invariably incomplete. Some people swear that a good ramtest is a gcc
> > kernel compile.
> > 
> > You have 24 M RAM. Try taking 8M out ? Can you do that ?
> > 
> > Swap RAM from another box ? Shuffle the RAM in the slots ?
> > 
> > Try an older LTSP client package - maybe it will fail in a diferent place ?
> > 
> > Or (shock horror) get another client box ? My time is worth more that 3
> > hours futzing around with old clients. I live in South Africa.
> > 
> > Cheers,      Andy!
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://productguide.itmanagersjournal.com/
> > _____________________________________________________________________
> > Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
> >       https://lists.sourceforge.net/lists/listinfo/ltsp-developer
> > For additional LTSP help,   try #ltsp channel on irc.freenode.net
> > 
> 
> 


["signature.asc" (application/pgp-signature)]
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net

[prev in list] [next in list] [prev in thread] [next in thread]