| 1 |
On 09/13/2012 10:37 AM, Volker Armin Hemmann wrote: |
| 2 |
> Am Mittwoch, 12. September 2012, 17:18:38 schrieb Daniel Frey: |
| 3 |
>> So about a month ago I decided to update my kernel to the dreaded 3.x |
| 4 |
>> series. My old 2.6.x kernel was working fine, but of course I decided |
| 5 |
>> to try to update it anyway, knowing there were problems with suspend |
| 6 |
>> and a few other things. |
| 7 |
>> |
| 8 |
>> I've always used gentoo-sources. So I tried 3.3.8. |
| 9 |
>> |
| 10 |
>> Hrm. Suspend doesn't work. I tried 3.4.5, 3.4.9 and 3.0.35 (older |
| 11 |
>> versions are no longer available.) If I'd known it would completely |
| 12 |
>> kill my suspend and make it useless, I wouldn't have bothered. |
| 13 |
>> |
| 14 |
>> Here's the problem: |
| 15 |
>> |
| 16 |
>> I can suspend fine. It appears to work. It powers off and goes into |
| 17 |
>> its suspend state. I press the space bar. Nothing. So, then I |
| 18 |
>> discovered that as of 3.2 USB wakeup had completely changed in the |
| 19 |
>> kernel, and you need to set hubs and devices in /proc/acpi/wakeup |
| 20 |
> I don't have to do that. |
| 21 |
|
| 22 |
You're lucky then - I've googled the issue and it has hit a lot of users |
| 23 |
from all sorts of distros, it's not specific to gentoo. Usually when the |
| 24 |
keyboard won't wake up the PC you can use the power button, which didn't |
| 25 |
work on my machine either. |
| 26 |
|
| 27 |
I'm kind of suspecting the PSU now. It's getting worse, and it happens |
| 28 |
on several kernel versions (even on 3.0.x which I had for about 3 weeks |
| 29 |
before going to something > 3.2. When I powered up my machine today |
| 30 |
(after being off all night) X bombed with no screens found. I restarted |
| 31 |
xdm and it worked... I'm thinking if the PSU is off maybe it's taking a |
| 32 |
while to warm up to be reliable - my video card uses one of those 6 port |
| 33 |
extra power plugs. I'll bet after being on for a few minutes it was |
| 34 |
fine. I hate diagnosing weird & intermittent hardware problems. The PSU |
| 35 |
in here is way too much for what I've got in here anyway. Come to think |
| 36 |
of it, I think I have a spare in my closet, although I can't remember |
| 37 |
the wattage. |
| 38 |
|
| 39 |
|
| 40 |
> |
| 41 |
>> (which is normally done for you) *and* in /sys/devices. No biggie, I |
| 42 |
>> wrote a script to do just that at |
| 43 |
> neither that. In fact, I have done nothing. It just works, with fglrx. |
| 44 |
> |
| 45 |
> uname -a |
| 46 |
> Linux energy 3.4.10 #1 SMP Sun Sep 9 23:01:01 CEST 2012 x86_64 AMD Phenom(tm) |
| 47 |
> II X4 955 Processor AuthenticAMD GNU/Linux |
| 48 |
> |
| 49 |
> and 3.2 before that |
| 50 |
> |
| 51 |
> and 3.0 before that. |
| 52 |
> |
| 53 |
It worked with 3.0.x for a couple of weeks, all hell broke loose after I |
| 54 |
upgraded to 3.3.8 (I think.) I've also tried 3.4.5 and 3.4.9, nothing |
| 55 |
works. Sigh... |
| 56 |
|
| 57 |
I'd better figure out a way to rule out the PSU. It's possible the |
| 58 |
emerge world that I did at the same time I upgraded to 3.3.8 stressed |
| 59 |
the PSU. |
| 60 |
|
| 61 |
Dan |
Archives