So I was looking at some of the USB settings as to why the bluetooth and webcam were always powered up.
1) USB 1-8: Webcam
"powertop -d" shows the webcam as 100% active regardless of kernel module being present or not, so I went to look at the usb power values (as we all know, powertop makes some incorrect recommendations)
/sys/bus/usb/devices/1-8/power/level = on
/sys/bus/usb/devices/1-8/power/autosuspend = 2 (same as rest of USB devices by default)
- (as root) "echo auto > /sys/bus/usb/devices/1-8/power/level"
- Now, the USB hub can go into autosuspend mode. Using powertop reveals that it is now 0% active without having to remove the kernel module.
- You can start up cheese or something else and the webcam will powerup as normal.
2) USB 3-2: Bluetooth
"powertop -d" shows the bluetooth as 100% active, regardless of whether or not the bluetooth module is present or not.
/sys/bus/usb/devices/3-2/power/level = on
/sys/bus/usb/devices/3-2/power/autosuspend = 2 (same as rest of USB devices by default)
- (as root) "echo auto > /sys/bus/usb/devices/3-2/power/level"
-"powetop -d" shows the bluetooth as 100% active still (well, I sort of expected that since as a radio, it would still doing it's radio-like things for discovery and such
- "powertop -d" now shows the bluetooth usb device as 0% active
- re-add the bluetooth module and bluetooth starts up again
So, the nc10-scripts are working well. But there is a bug with the USB power level of the webcam and bluetooth. Does anyone know who (and by who, I mean what piece of software) controls those default settings?
3) nc10-scripts and blueman
I'm now getting the same results with enabling and disabling. If I disable the blueooth, the icon is disappearing now (with the new 11-12 version of the scripts). This wasn't the case with the earlier version. However, if you have bluetooth radio disabled in blueman and then disable-enable the module, blueman will not start up again (not sure why) which is unfortunate. If it would start up again and just still be disabled, that would be great.
blueman "disable bluetooth" does essentially issue a "hciconfig hci0 down" command, but does not remove the bluetooth module.
4) possible new nc10-scripts command - would it be possible to get a command "nc10 status" that just basically runs through each of the commands to show the current status of each device? I'm lazy.
5) Something is odd with the synaptics driver OR the touchpad. On another laptop that has an Alps touchpad, when I watch gnome-power-statistics, there isn't a large increase in the processor wake-ups when using the pad. When using a USB mouse on a real desktop or in a VM, the same thing happens. But when I use the trackpad on the NC10, there are anywhere from 300-7000+ wake-ups per second from using the trackpad. This seems really odd, and since it is different from every other device, seems to say "bug" to me. Is anyone else having this same thing happen to them?
6) and then of course there is the hyperthreading issue (and the fact that is seems to have ridiculous amount of wakeups for ACPI and interrupt scheduling). oh well.