This is immediately following a kernel update this weekend.
]]>#!/bin/bash
if [ $EUID != 0 ]; then
sudo "$0" "$@"
sudo tee "/sys/bus/pci/devices/0000:00:19.0/power/control" <<< on
exit $?
fi
$ sudo -i
and try again.
]]>What do I do if this happens:
sudo echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control
bash: /sys/bus/pci/devices/0000:00:19.0/power/control: Permission denied
ls -al /sys/bus/pci/devices/0000\:00\:19.0/power
total 0
drwxr-xr-x 2 root root 0 17. Apr 20:30 .
drwxr-xr-x 5 root root 0 17. Apr 20:29 ..
-rw-r--r-- 1 root root 4096 17. Apr 20:30 async
-rw-r--r-- 1 root root 4096 17. Apr 20:30 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 17. Apr 20:32 control
-r--r--r-- 1 root root 4096 17. Apr 20:30 runtime_active_kids
-r--r--r-- 1 root root 4096 17. Apr 20:30 runtime_active_time
-r--r--r-- 1 root root 4096 17. Apr 20:30 runtime_enabled
-r--r--r-- 1 root root 4096 17. Apr 20:30 runtime_status
-r--r--r-- 1 root root 4096 17. Apr 20:30 runtime_suspended_time
-r--r--r-- 1 root root 4096 17. Apr 20:30 runtime_usage
-rw-r--r-- 1 root root 4096 17. Apr 20:30 wakeup
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_abort_count
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_active
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_active_count
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_count
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_expire_count
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_last_time_ms
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_max_time_ms
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_prevent_sleep_time_ms
-r--r--r-- 1 root root 4096 17. Apr 20:30 wakeup_total_time_ms
uname -a
Linux chaos 3.8.7-1-ARCH #1 SMP PREEMPT Sat Apr 13 09:01:47 CEST 2013 x86_64 GNU/Linux
On a Thinkpad T430
Thanks for any help, might as well just me being dumb…
]]>Please consider :
https://bugs.launchpad.net/ubuntu/+sour … ug/1112652
The issue is solved in 3.9rc3 with :
https://bugs.launchpad.net/ubuntu/+sour … omments/24
We need this backport in 3.8 kernel...
++
]]>The workaround works but its a little annoying to do it after every suspend/reboot.
]]>drdnl wrote:Previous kernel didn't work at all, now it works occasionally?
Yes indeed: sometimes I have to do the workaround after booting, sometimes I don't.
Oddly, didn't work for me this morning either. Intentionally booted without cable inserted, will have to narrow it down somehow.
]]>Previous kernel didn't work at all, now it works occasionally?
Yes indeed: sometimes I have to do the workaround after booting, sometimes I don't.
]]>drdnl wrote:Fixed for me in 3.8.5.1
Not for me. It works sometimes but I just did a boot and network stayed off.
Previous kernel didn't work at all, now it works occasionally?
]]>BTW: is anybody else bothered by this https://bugzilla.kernel.org/show_bug.cgi?id=47091 ?
It seems that this driver sucks for laptop users...
]]>Fixed for me in 3.8.5.1
Not for me. It works sometimes but I just did a boot and network stayed off.
]]>Just did a fresh boot, checked whether "auto" was on and (un)plugged the cable a couple times. Then did the same for suspend.
]]>