On Saturday 15 September 2012 17:28:26 Daniel Frey wrote:
> I guess it was not really a coincidence that the failure happened
> after a major update. This isn't the first time an `emerge -pvuDN
> world` killed my computer. :-)
A real-life example of software breaking hardware, which was drummed
Daniel Frey wrote:
> On 09/15/2012 03:29 PM, Dale wrote:
>> Daniel Frey wrote:
>>> Well, it turns out it was my PSU. The voltage drop on the 5V line was
>>> 4.08, but it would slowly warm up to 4.95V, then the PC would behave
>>> normally. I opened the PSU and there was a ruptured cap.
>>>
>>> I've
On 09/15/2012 03:29 PM, Dale wrote:
> Daniel Frey wrote:
>> Well, it turns out it was my PSU. The voltage drop on the 5V line was
>> 4.08, but it would slowly warm up to 4.95V, then the PC would behave
>> normally. I opened the PSU and there was a ruptured cap.
>>
>> I've replaced it and the proble
On 09/15/2012 03:26 PM, Mick wrote:
> I was also replacing capacitors last weekend. It is a good idea to upgrade
> them if there are alternatives of a higher maximum temperature as they will
> probably last longer. A belts & braces approach is to add another/larger
> case
> fan to keep the i
Daniel Frey wrote:
> Well, it turns out it was my PSU. The voltage drop on the 5V line was
> 4.08, but it would slowly warm up to 4.95V, then the PC would behave
> normally. I opened the PSU and there was a ruptured cap.
>
> I've replaced it and the problems are all gone.
>
> I guess it was not rea
On Saturday 15 Sep 2012 17:28:26 Daniel Frey wrote:
> Well, it turns out it was my PSU. The voltage drop on the 5V line was
> 4.08, but it would slowly warm up to 4.95V, then the PC would behave
> normally. I opened the PSU and there was a ruptured cap.
>
> I've replaced it and the problems are al
Well, it turns out it was my PSU. The voltage drop on the 5V line was
4.08, but it would slowly warm up to 4.95V, then the PC would behave
normally. I opened the PSU and there was a ruptured cap.
I've replaced it and the problems are all gone.
I guess it was not really a coincidence that the fail
On 09/12/2012 09:49 PM, Chris Stankevitz wrote:
> On Wed, Sep 12, 2012 at 5:18 PM, Daniel Frey wrote:
>> So about a month ago I decided to update my kernel to the dreaded 3.x
>> series. My old 2.6.x kernel ...
> FYI Linus Torvalds says there was no change between 2.6 and 3.0. A quote:
>
> So what
On 09/12/2012 05:59 PM, Canek Peláez Valdés wrote:
> I switched to 3.0 more than a year ago (I use vanilla-sources). Never
> had a problem with suspend and/or hibernate; I'm now running kernel
> 3.5.3. You didn't specify how do you suspend. pm-utils? dbus-send to
> upower? echo mem > /sys/power/sta
On 09/13/2012 10:37 AM, Volker Armin Hemmann wrote:
> Am Mittwoch, 12. September 2012, 17:18:38 schrieb Daniel Frey:
>> So about a month ago I decided to update my kernel to the dreaded 3.x
>> series. My old 2.6.x kernel was working fine, but of course I decided
>> to try to update it anyway, knowi
Am Mittwoch, 12. September 2012, 17:18:38 schrieb Daniel Frey:
> So about a month ago I decided to update my kernel to the dreaded 3.x
> series. My old 2.6.x kernel was working fine, but of course I decided
> to try to update it anyway, knowing there were problems with suspend
> and a few other thi
On Wed, Sep 12, 2012 at 5:18 PM, Daniel Frey wrote:
> So about a month ago I decided to update my kernel to the dreaded 3.x
> series. My old 2.6.x kernel ...
FYI Linus Torvalds says there was no change between 2.6 and 3.0. A quote:
So what are the big changes? NOTHING. Absolutely nothing. Sure
On Wed, Sep 12, 2012 at 7:18 PM, Daniel Frey wrote:
> So about a month ago I decided to update my kernel to the dreaded 3.x
> series. My old 2.6.x kernel was working fine, but of course I decided
> to try to update it anyway, knowing there were problems with suspend
> and a few other things.
>
> I
13 matches
Mail list logo
