touch-packages team mailing list archive

[Launchpad Bug Tracker <322954@xxxxxxxxxxxxxxxxxx>]

[Expired for ubuntu-meta (Ubuntu) because there has been no activity for
60 days.]

** Changed in: ubuntu-meta (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/322954

Title:
  Need to be able to controll some devices from GUI - power management
  and device recovery

Status in ubuntu-meta package in Ubuntu:
  Expired

Bug description:
  * Case 1:
  Problem description: Some wifi drivers/chipsets get confused after a while and will fall off the network and then fail to get on again with the normal network manager probings. A root shell and modprobe -rv ipw2200; modprobe ipw2200

  References: Windows provides a "repair device" choice in the tray
  network icon which appears to remove and reinstall the driver

  Suggested fix: A "repair network device" choice should be available
  through network manager

  * Case 2:
  Problem description: RFKILL switch kills wifi driver permanently.

  Suggested fix: See above for workaround. A setting somewhere to
  automatically reinstall the wifi driver after unkill occurs would be
  nice.

  * Case 3:
  Problem description: USB devices keeps Laptops from reaching low power states for any significant time.  My current laptop has a builtin 3G device and a builtin bluetooth device.  Both are on a USB bus.  According to powertop these rank among the top wake-up-causers on the system.

  Suggested fix 1: powertop suggests "suspending usb".  Not quite sure
  what this entails but unloading the USB stack seems one likely
  solution.  A desktop device manager to do this would be nice.

  Suggested fix 2: Powertop further suggests unloading the bluetooth and
  3G device USB drivers. This normally requires root access and
  knowledge of the driver names. This is a less drastic way to realize
  almost the same goal as in fix1. A desktop widget is needed.

  * Case 4:
  ... Once the desktop bus interface to manipulate the usb stack and wifi drivers is realized it's not all that strange to supply a "rfkill" software switch in the network manager applet that lets us do rfkill on the wifi and bluetooth but keep the 3G device going for example.

  Regards,
    Nicolai

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/322954/+subscriptions