[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
> I must agree completely about power supplies. They are my least
> favorite component to troubleshoot. Sometimes they go swiftly and
> other times it's an incredibly intermittent problem that causes a
> myriad of misleading symptoms. Blah.. ;)
>
> J. D.
>
> On 10/23/05, *James P. Kinney III* <jkinney at localnetsolutions.com
> <<a rel="nofollow" href="mailto:jkinney">mailto:jkinney</a> at localnetsolutions.com>> wrote:
>
> Ah ,hardware. If I recall, the hard drive choked on that syustem that
> was running 7.1. I suspect that a reinstall of 7.1 will still not
> allow
> compilations. A board level voltage spike caused by a dying power
> supply
> can damage RAM in subtle ways while cooking other parts like hard
> drives.
>
> It's VERY frustrating to realize that the one component that can kill
> everything in the system is being produced to lower and lower
> lifetime
> expectancy standards. Some of my older equipment is running just fine
> after 7-8 years of daily use while some of the newer stuff is good for
> 1-2 years tops. Most of the system failures I have seen in the past 3
> years have been caused by an intermittent power supply issue. Poor
> quality analog components like capacitors and choke coils are to blame
> for the vast majority of the crappy power supplies that have broken my
> and my clients stuff.
>
> It doesn't help that everyone wants to "save money" so the power
> supply
> installed is the smallest capable of just running the box as
> shipped. So
> add a DVD burner to that old system and play Russian Roulette with
> your
> hard drive. Power supply makers rate their device to the absolute
> maximum it could possible put out assuming all the components are
> fully
> up to spec and the bean counters didn't by a bargain that "fell of
> the
> truck". The sad reality is power supplies don't put out what their
> label
> says except for a very brief test time.
>
> So I size up my power supply to provide full power for every device
> running at maximum and still have at least a 30% overhead before the
> labeled rating is hit. I would much prefer a 50% overhead but newer
> systems are already such power hogs I can't get a 2kw internal power
> supply!
>
>
> </rant>
>
> On Sun, 2005-10-23 at 16:42 -0400, Bob Kruger wrote:
> > James;
> >
> > I have pretty much decided that the problem is hardware induced. I
> > just pulled the HD with the Slack 10.2 distro in it, put it in
> another
> > machine, and I can compile to my heart's content. The old
> motherboard
> > had no problems with Slack 7.1 - it peacefully ran for four years.
> > But, it will not peacefully coexist with Slack 10.2. Its time has
> > come and gone.
> >
> > Thanks all who wrote back.
> >
> > V/r
> >
> > Bob
> >
> > James P. Kinney III wrote:
> > > On Sun, 2005-10-23 at 15:32 -0400, Bob Kruger wrote:
> > >
> > > > Christopher;
> > > >
> > > > Fair enough. The three shown here are "segmentation
> faults" Here are
> > > > some snippets. Firstly, compiling samba 3.0.22b:
> > > >
> > >
> > > I'm not running slack 10.2. Nor have I had compilation issues
> with the
> > > slack machines I do have.
> > >
> > > However, I have seen seg faults during compiles. 2 were memory
> faults
> > > (RAM was bad in ways that only a compiler would find or
> memtest86) and 2
> > > were bad applications configures. On one of the bad app
> configs, I had
> > > to do a lot more than just ./configure; make; make install.
> There were a
> > > bunch of settings I had to tweak.
> > >
> > > Samba, MySQL and PHP are monster applications that usually
> need much
> > > more than the vanilla ./configure to make correctly.
> > >
> > >
> > >
> > >
> ____________________________________________________________________
> > >
> > > _______________________________________________
> > > Ale mailing list
> > > Ale at ale.org <<a rel="nofollow" href="mailto:Ale">mailto:Ale</a> at ale.org>
> > > <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org <<a rel="nofollow" href="mailto:Ale">mailto:Ale</a> at ale.org>
> > <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
> --
> James P. Kinney III \Changing the mobile computing world/
> CEO & Director of Engineering \ one Linux user /
> Local Net Solutions,LLC \ at a time. /
> 770-493-8244 \.___________________________./
> <a rel="nofollow" href="http://www.localnetsolutions.com">http://www.localnetsolutions.com</a>
>
> GPG ID: 829C6CA7 James P. Kinney III (M.S . Physics)
> <jkinney at localnetsolutions.com <<a rel="nofollow" href="mailto:jkinney">mailto:jkinney</a> at localnetsolutions.com>>
> Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQBDXAJYYZCtw4KcbKcRArc7AJ9R30acpPJvZzOHi5MQYWUc9YzAAACgtutL
> Y6awP/ESO0fCXMABAQiWbqk=
> =ZVsd
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org <<a rel="nofollow" href="mailto:Ale">mailto:Ale</a> at ale.org>
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
><a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
>
Probably made in China by some 5 yr old kid.................................
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00458" href="msg00458.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00446" href="msg00446.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00447" href="msg00447.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> n4zm at mindspring.com (zeb)</li></ul></li>
<li><strong><a name="00448" href="msg00448.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00449" href="msg00449.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> ale at accipiter.org (Christopher R. Curzio)</li></ul></li>
<li><strong><a name="00450" href="msg00450.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00451" href="msg00451.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
<li><strong><a name="00452" href="msg00452.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00453" href="msg00453.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
<li><strong><a name="00454" href="msg00454.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> jdonline at gmail.com (J. D.)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00456.html">[ale] Connecting with SUSE 10.0</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00458.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00454.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00458.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00457"><strong>Date</strong></a></li>
<li><a href="threads.html#00457"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>