On Friday 01 June 2001 00:27, Leonardo T. de Carvalho wrote:
memtest-x86.bin in /images on the CD
You can always boot the CD and hit F1 at the splash screen and enter rescue
mode to run it.
Civileme
> Ric Tibbetts wrote:
> > Thank you!
>
> Always here!
> =o)
>
> > And correct. I
Benjamin Sher wrote:
>
Just had my friend Bill, the computer expert, install my new PNY
memory
> modules. The two new modules (128 meg each) together with the 128 module
> already on my system (there are three sockets on my Soyo SY-5EMA + Super
> 7 Mainboard version 2.0 motherboard) add up to 38
Ric Tibbetts wrote:
>
>
> Thank you!
Always here!
=o)
> And correct. If the memory is there, and not properly configured, things
> can get "goofy". I had a machine do this to me. Spent most of a week
> trying to figure out what was wrong.
It's a UGLY situation...
>
>
Dan Swartzendruber wrote:
>
.
>
> hmmm, news to me. usually segvs are bad RAM. if linux isn't even
> recognizing the RAM, how can it touch it to fault?
The board says that recognizes the RAM, but when trying to
access, -->> BOOM <<--.
Something about the memory maps, I think.
Leonardo T. de Carvalho wrote:
> Dan Swartzendruber wrote:
>
>
>>none of this explains why he is freezing though.
>>
>
> Yup, when the memory is not properly recognized , the system
> hangs at random times...
> I've seen this, mainly on SiS mboards..
> =o(
>
>
Thank you!
On Thu, 31 May 2001, Leonardo T. de Carvalho wrote:
> Dan Swartzendruber wrote:
> >
>
> >
> > none of this explains why he is freezing though.
>
> Yup, when the memory is not properly recognized , the system
> hangs at random times...
> I've seen this, mainly on SiS mboards..
hmmm, n
At 03:01 PM 05/31/01, Dan Swartzendruber wrote:
>On Thu, 31 May 2001, Ric Tibbetts wrote:
>
> > When you boot it, from the LILO prompt, try:
> >
> > linux mem=384
> >
> > Also, try going back to Windows, and check to see if it is recognizing
> > ALL of that memory.
>
>none of this explains why he
Dan Swartzendruber wrote:
>
>
> none of this explains why he is freezing though.
Yup, when the memory is not properly recognized , the system
hangs at random times...
I've seen this, mainly on SiS mboards..
=o(
--
Leonardo T. de Carvalho
Ibiz Tecnologia
Frase
On Thu, 31 May 2001, Ric Tibbetts wrote:
> When you boot it, from the LILO prompt, try:
>
> linux mem=384
>
> Also, try going back to Windows, and check to see if it is recognizing
> ALL of that memory.
none of this explains why he is freezing though.
When you boot it, from the LILO prompt, try:
linux mem=384
Also, try going back to Windows, and check to see if it is recognizing
ALL of that memory.
Ric
Benjamin Sher wrote:
> Dear friends:
>
> Using LM 8.0 on my AMD k6-2 400 CPU with KDE 2.1.1.
>
> Just had my friend Bill, the computer
Benjamin Sher wrote:
>
> Dear friends:
>
> Using LM 8.0 on my AMD k6-2 400 CPU with KDE 2.1.1.
<...>
> already on my system (there are three sockets on my Soyo SY-5EMA +
> was already in KDE but KDE froze when it reached the "desktop" part of
> the KDE launch).
>
> Second time, Linux froze d
On Thu, 31 May 2001, Benjamin Sher wrote:
> Dear friends:
>
> Using LM 8.0 on my AMD k6-2 400 CPU with KDE 2.1.1.
>
> Just had my friend Bill, the computer expert, install my new PNY memory
> modules. The two new modules (128 meg each) together with the 128 module
> already on my system (there ar
Dear friends:
Using LM 8.0 on my AMD k6-2 400 CPU with KDE 2.1.1.
Just had my friend Bill, the computer expert, install my new PNY memory
modules. The two new modules (128 meg each) together with the 128 module
already on my system (there are three sockets on my Soyo SY-5EMA + Super
7 Mainboard
13 matches
Mail list logo
