Frank Steinmetzger wrote:
> On Sat, Aug 22, 2015 at 06:28:45PM -0500, Dale wrote:
>
>> Alan Grimes wrote:
>>> The PSU is an Antec EarthWatts 750.
>>>
>>> Biggest hoggs outside the motherboard are the, um, er, well [nvidia 980
>>> gpu] and an aging Western Digital Velociraptor boot drive. There is a
On Sat, Aug 22, 2015 at 06:28:45PM -0500, Dale wrote:
> Alan Grimes wrote:
> > The PSU is an Antec EarthWatts 750.
> >
> > Biggest hoggs outside the motherboard are the, um, er, well [nvidia 980
> > gpu] and an aging Western Digital Velociraptor boot drive. There is also
> > a 3TB drive for all my
Alan Grimes wrote:
> The PSU is an Antec EarthWatts 750.
>
> Biggest hoggs outside the motherboard are the, um, er, well [nvidia 980
> gpu] and an aging Western Digital Velociraptor boot drive. There is also
> a 3TB drive for all my p***, er kerbals ( Kerbal Space Program ) .
> There is one optic
On 22/08/2015 18:40, Alan Grimes wrote:
> The PSU is an Antec EarthWatts 750.
>
> Biggest hoggs outside the motherboard are the, um, er, well [nvidia 980
> gpu] and an aging Western Digital Velociraptor boot drive. There is also
> a 3TB drive for all my p***, er kerbals ( Kerbal Space Program )
The PSU is an Antec EarthWatts 750.
Biggest hoggs outside the motherboard are the, um, er, well [nvidia 980
gpu] and an aging Western Digital Velociraptor boot drive. There is also
a 3TB drive for all my p***, er kerbals ( Kerbal Space Program ) .
There is one optical drive and four chassis fans
On Saturday 22 Aug 2015 12:47:52 Alan McKinnon wrote:
> On 22/08/2015 13:25, Mick wrote:
> > Then try a replacement PSU if you have a spare one, or take your
> > multimeter and measure the output, checking for lower voltage values and
> > fluctuations. If you get bad measurements, then take your s
On 22/08/2015 13:25, Mick wrote:
> On Saturday 22 Aug 2015 09:18:05 Dale wrote:
>> Fernando Rodriguez wrote:
>>> On Saturday, August 22, 2015 1:52:00 AM Alan Grimes wrote:
That said, I spent the day doing diagnostics:
Findings:
1. There were a hell of a lot more memory
On Saturday 22 Aug 2015 09:18:05 Dale wrote:
> Fernando Rodriguez wrote:
> > On Saturday, August 22, 2015 1:52:00 AM Alan Grimes wrote:
> >> That said, I spent the day doing diagnostics:
> >>
> >>
> >> Findings:
> >>
> >> 1. There were a hell of a lot more memory errors than I had seen before.
>
Fernando Rodriguez wrote:
> On Saturday, August 22, 2015 1:52:00 AM Alan Grimes wrote:
>
>> That said, I spent the day doing diagnostics:
>>
>>
>> Findings:
>>
>> 1. There were a hell of a lot more memory errors than I had seen before.
>> 2. There was a smudge on one of the dimm's contacts and some
On Saturday, August 22, 2015 1:52:00 AM Alan Grimes wrote:
> J. Roeleveld wrote:
> > Please don't bother this list with more of your complaining until you grow
up
> > and learn how to use computers properly.
>
> I built my first machine nearly a quarter century ago. =|
Shame!
> That said, I sp
J. Roeleveld wrote:
> Please don't bother this list with more of your complaining until you grow up
> and learn how to use computers properly.
I built my first machine nearly a quarter century ago. =|
That said, I spent the day doing diagnostics:
Findings:
1. There were a hell of a lot more m
On Friday, August 21, 2015 11:00:16 AM Alan Grimes wrote:
> Grant Edwards wrote:
> > On 2015-08-21, Alan McKinnon wrote:
> >
> >> Earlier I saw segfaults in gcc, and another poster pointed it out.
> >>
> >> When gcc segfaults, it is always suspicious mostly because the compiler
> >> is an app wher
Alan Grimes wrote:
> Grant Edwards wrote:
>> On 2015-08-21, Alan McKinnon wrote:
>>
>>> Earlier I saw segfaults in gcc, and another poster pointed it out.
>>>
>>> When gcc segfaults, it is always suspicious mostly because the compiler
>>> is an app where we know the devs take extraordinary measure
On Friday, August 21, 2015 11:00:16 AM Alan Grimes wrote:
> Grant Edwards wrote:
> Yeah, I know there's a single bit error out at the end of RAM that will
> appear on the third or fourth pass...
Replace it
> I have already RMA'd half of the ram in this machine because it was
> giving a whole fist
On 2015-08-21, Alan Grimes wrote:
> Grant Edwards wrote:
>> On 2015-08-21, Alan McKinnon wrote:
>>
>>> Earlier I saw segfaults in gcc, and another poster pointed it out.
>>>
>>> When gcc segfaults, it is always suspicious mostly because the compiler
>>> is an app where we know the devs take extra
Grant Edwards wrote:
> On 2015-08-21, Alan McKinnon wrote:
>
>> Earlier I saw segfaults in gcc, and another poster pointed it out.
>>
>> When gcc segfaults, it is always suspicious mostly because the compiler
>> is an app where we know the devs take extraordinary measures to prevent it.
>>
>> The
On 2015-08-21, Alan McKinnon wrote:
> Earlier I saw segfaults in gcc, and another poster pointed it out.
>
> When gcc segfaults, it is always suspicious mostly because the compiler
> is an app where we know the devs take extraordinary measures to prevent it.
>
> The most common cause is faulty ha
Alan Grimes verizon.net> writes:
> 8, got to the end of the list about two and a half days later (which is
> par for my machine.)
Hello Alan Grimes,
You seem to imply you are running hardware less that some version
of the latest 4/8 processor monster?
Perhaps something lighter then the kde5
On 2015-08-20, Alan McKinnon wrote:
> Let me describe what I see.
>
> This can't be a clusterfuck, as it is affecting only you. No-one else to
> my knowledge is reporting problems caused by ncurses.
>
> So, it is then highly likely that you have a setup that the devs did not
> consider, and it is
19 matches
Mail list logo
