You are right of course, i can install hardy within 20m on a free partition
with unetbootin.
In my infinite wisdom i partitioned my hdd to take 6 different distros to play
around with and 3 slots are still free.
I will install hardy and leave it running over a few nights. If DPMS does not
break
I have 16h uptime now and DPMS stopped working a couple of hours ago, so it
takes a long time until it breaks for some unknown reason. I dont use any
audio/video programs, the only thing that i could imagine trying to access the
soundcard would be some random flash-content while surfing the
I just noticed something.
Currently the Screensaver is set to 9m and exactly after 9m of idle-time the
screen starts fading.
Before it gets completely dark though it jumps back to full brightness again
until 9m later it tries (and fails) again.
I grepped /var/log/ for the time where the
0
2
2
2
2
2
are the wrong values, it needs to be
1
1
1
1
1
1
as suggested by powertop.
Its the only way to get the desired result, a SLEEPING Cpu.
--
Powertop make wrong suggest to add usbcore.autosuspend=1
https://bugs.launchpad.net/bugs/136549
You received this bug notification because you
I have the same problem on two clean gutsy installs.
One is a Destop with nvidia cards and the other a Laptop with Intel GMA.
xset q shows the times being reset to zero after a while.
This bug is very old and apparently nobody gives a shit.
Its absurd and embarrasing that Linux is not capable to
Public bug reported:
I use fresh gutsy installs on a nvidia desktop and a intel laptop.
DPMS works on neither of them, no matter what i do with gnome-screensaver or
gnome-power-manager, the screen never turns off.
If i use xset dpms manually the values get reset after a while.
Having alot of
I have it set to 1m/2m but it doesn't turn off.
Killing screensaver or power-manager does not help either.
I would file a xorg bug about this but too many times i have seen them
reply Use cvs or else we don't care.
--
DPMS is broken
https://bugs.launchpad.net/bugs/193192
You received this bug
It did not until i rebooted.
In a couple of hours it will be broken again.
Im not even using suspend, my Laptop is just idling.
--
DPMS is broken
https://bugs.launchpad.net/bugs/193192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
*** This bug is a duplicate of bug 136549 ***
https://bugs.launchpad.net/bugs/136549
Public bug reported:
I believe that USB Autosuspend is not enabled in the default Ubuntu Kernel.
My CPU (core-duo) is stuck at C2 until i enable USB Autosuspend via powertop.
Only then is it able to go to
*** This bug is a duplicate of bug 136549 ***
https://bugs.launchpad.net/bugs/136549
I'm aware of the other Bug-report and i doubt that its powertop's fault.
Like i said is my CPU stuck at C2 until i enable USB-Autosuspend with powertop.
If you run cat
powertop (from svn) tells me that my CPU is stuck in C2 70% of the time until
- i enable usb-autosuspend with powertop
- or remove uhci_hcd myself.
after which C2 drops to zero.
At the same time cat /sys/bus/usb/devices/*/power/level reports AUTO for all
values.
No usb-devices are used except
Sorry to interrupt but does this mean that linuxwacom is supposed to
work with xorg-7.3?
From watching the linuxwacom mailing list traffic and trying myself on
my x60t i was under the impression its not ready yet.
--
Serial Wacom tablet fails to return from ACPI suspend to RAM
Public bug reported:
I tried both commenting lock_screen=true and setting it to false, in both
cases i also rebooted.
It is still asking for the password though.
Im using a pretty fresh install of Ubuntu-7.10 on a Thinkpad X60T.
I was reading the 2 other bug-reports about this but they are
There is something wrong here though.
Before i enable usb autosuspension with powertop my CPU (coreduo) is stuck in
C2 75% of the time.
Only after pressing U to enable it the CPU stays in C3 97% of the time and the
power-usage drops significantly.
--
Powertop suggest to add
101 - 114 of 114 matches
Mail list logo
