RE: [opensuse-factory] Phone does not begin charging unless I am logged in to Desktop?
-----Ursprüngliche Nachricht----- Von: Howard Guo Gesendet: Mi. 13.04.2016 08:15 An: opensuse-factory@opensuse.org Betreff: [opensuse-factory] Phone does not begin charging unless I am logged in to Desktop?
Hello fellow Tumbleweed users.
I noticed a strange phenmenon with charging my Sony phone on this Tumbleweed workstation - it does not charge in multi-user.target, or VT, or display-manager. It only charges after I have logged into desktop. Does anyone know how to alter the behaviour so that Linux will allow it to charge as long as the system is powered up?
Thanks.
Regards, Howard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----Ursprüngliche Nachricht Ende----- This is not only a problem of Tumbleweed but of all installations and does AFAIK more depend on the BIOS setting.
Two solutions come to my mind: a) you set the "usb-legacy" support to "on" in the BIOS. That should power up USB even if the desktop is not logged in. b) you use a dedicated usb plug (some of the machines have a special plug that charges even if no OS has been started up). Maybe that has also to do with PAM as the Sony will probably charge when recognized as a usb-key or token. For security reasons it is possible that the PAM setting does not allow to mount such devices (mass storage) but only after the authorized user logged in. However I do not know sufficiently about PAM to tell with certainty. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/13/2016 04:00 PM, stakanov@freenet.de wrote:
-----Ursprüngliche Nachricht----- Von: Howard Guo Gesendet: Mi. 13.04.2016 08:15 An: opensuse-factory@opensuse.org Betreff: [opensuse-factory] Phone does not begin charging unless I am logged in to Desktop?
Hello fellow Tumbleweed users.
I noticed a strange phenmenon with charging my Sony phone on this Tumbleweed workstation - it does not charge in multi-user.target, or VT, or display-manager. It only charges after I have logged into desktop. Does anyone know how to alter the behaviour so that Linux will allow it to charge as long as the system is powered up?
Thanks.
Regards, Howard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----Ursprüngliche Nachricht Ende----- This is not only a problem of Tumbleweed but of all installations and does AFAIK more depend on the BIOS setting.
Two solutions come to my mind: a) you set the "usb-legacy" support to "on" in the BIOS. That should power up USB even if the desktop is not logged in. b) you use a dedicated usb plug (some of the machines have a special plug that charges even if no OS has been started up).
Maybe that has also to do with PAM as the Sony will probably charge when recognized as a usb-key or token. For security reasons it is possible that the PAM setting does not allow to mount such devices (mass storage) but only after the authorized user logged in. However I do not know sufficiently about PAM to tell with certainty.
On the bios of my last desktop (ASUS Motherboard) I found that by enabling wake on USB I was able to charge my my phone even when the PC was off. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Wed, 2016-04-13 at 20:59 +0930, Simon Lees wrote:
On the bios of my last desktop (ASUS Motherboard) I found that by enabling wake on USB I was able to charge my my phone even when the PC was off.
Good tip, but I cannot solve an issue that arises while the host is active. Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello! Thanks for your hints. I suspected that power management is the curlpit, and it turned out that "autosuspend" is the magical parameter. By writing -1 into /sys/module/usbcore/parameters/autosuspend, the USB port remains powered non-stopping. Regards, Howard On Wed, 13 Apr 2016, Oliver Neukum wrote:
On Wed, 2016-04-13 at 20:59 +0930, Simon Lees wrote:
On the bios of my last desktop (ASUS Motherboard) I found that by enabling wake on USB I was able to charge my my phone even when the PC was off.
Good tip, but I cannot solve an issue that arises while the host is active.
Regards Oliver
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Apr 19, 2016 at 6:31 AM, Howard Guo
Hello!
Thanks for your hints. I suspected that power management is the curlpit, and it turned out that "autosuspend" is the magical parameter.
By writing -1 into /sys/module/usbcore/parameters/autosuspend, the USB port remains powered non-stopping.
So..what is the USB id of this device.. so we can figure out what is enabling autosuspend for this particular device (it isn't/wasn't enabled by default last time I checked) and udev rules to enable usb autospend by default were rejected with EKERNELPROBLEM :-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks Cristian. lsusb output is attached: Bus 002 Device 004: ID 0fce:019e Sony Ericsson Mobile Communications AB Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0fce Sony Ericsson Mobile Communications AB idProduct 0x019e bcdDevice 2.32 iManufacturer 1 Sony iProduct 2 C6906 iSerial 3 BH90122E0D bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x001c 1x 28 bytes bInterval 6 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 On Tue, 19 Apr 2016, Cristian Rodríguez wrote:
So..what is the USB id of this device.. so we can figure out what is enabling autosuspend for this particular device (it isn't/wasn't enabled by default last time I checked) and udev rules to enable usb autospend by default were rejected with EKERNELPROBLEM :-)
On Tue, 2016-04-19 at 15:34 -0300, Cristian Rodríguez wrote:
On Tue, Apr 19, 2016 at 6:31 AM, Howard Guo
wrote: Hello!
Thanks for your hints. I suspected that power management is the curlpit, and it turned out that "autosuspend" is the magical parameter.
By writing -1 into /sys/module/usbcore/parameters/autosuspend, the USB port remains powered non-stopping.
So..what is the USB id of this device.. so we can figure out what is enabling autosuspend for this particular device (it isn't/wasn't enabled by default last time I checked) and udev rules to enable usb autospend by default were rejected with EKERNELPROBLEM :-)
We would want it to be autosuspend while we are operating on battery though. Simply removing the rule wonŽt do the job. Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thank you Simon! By turning on USB wake support, the phone begins charging as soon as the system is powered on, where previously it would only charge in desktop. However, it still stops charging during the Linux boot process, and would only resume when I'm in desktop. The year of Linux desktop will come eventually.. Kind regards, Howard On Wed, 13 Apr 2016, Simon Lees wrote:
On the bios of my last desktop (ASUS Motherboard) I found that by enabling wake on USB I was able to charge my my phone even when the PC was off.
Cheers
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Cristian Rodríguez
-
Howard Guo
-
Oliver Neukum
-
Simon Lees
-
stakanov@freenet.de