From: Roman Dobosz <gryf73@op.pl>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Kernel 4.x and (probably) event issues
Date: Sat, 12 Mar 2016 17:16:36 +0100 [thread overview]
Message-ID: <20160312171636.09ad23cf4053e3fe1a2b57c7@op.pl> (raw)
In-Reply-To: <CAC=wYCFDSJ-fd-dOurZrjKgTuymEF8QkMLRDMiwVrgndL3NvhA@mail.gmail.com>
On Mon, 7 Mar 2016 11:00:26 +1100
Adam Carter <adamcarter3@gmail.com> wrote:
> > 1. After successful boot, I've noticed, that buttons above the
> > touchpad[1] stopped working. Tried to debug the thing, but they do
> > nothing even under xev or in showkey - seems like they dead. Didn't find
> > anything interesting by searching the net.
> Longshot (since i've had one instance in the last few years where i need to
> rebuild xorg after a kernel update) have you tried rebuilding the
> xf86-input-* packages against the new kernel?
Yep, that was the first thing, right after rebuilding 3rd party
modules, I've done.
I've done a little test with Live USB with some popular desktop
distribution, and it turns out, those buttons doesn't work there
either. Not sure if it's a kernel bug, or something else.
> > 2. This one is more annoying. After boot to the new shiny 4.x kernel,
> > devices connected via the usb seems to have aggressive power safe mode.
> > For example - if I typing for a while everything is fine, if I stop for
> > a couple of seconds, and then start to type, for approximately 2 seconds
> > there is no response from the device, and after that i can type again.
> > Note, that during those 2s no buffering is done, so whatever I'm typing
> > in this short period, is lost. Same goes to the mouse movement and
> > buttons.
> I haven't had much luck with USB power saving working in a useful way and
> leave it off. Strange its been enabled by default for you.
>
> cat /sys/bus/usb/devices/*/power/control will show you what the current
> settings are.
>
> The options are on/auto.
>
> "on" means that the device should be resumed and autosuspend is not allowed.
>
> so that's what you want. It can blanket set with;
>
> echo on | tee /sys/bus/usb/devices/*/power/control
>
> Or you could work out which devices are actually a problem and just "on"
> those particular ones.
Actually, this was very useful. Thank you for the hint. I've created
simple script which gives me a device and power status next to it.
I've compared values from the distro I've mentioned above with the
values I get from the Gentoo system. It turns out that indeed all
devices are set to "auto". I've noticed either, that I have running
laptop mode (app-laptop/laptop-mode-tools), which was the one
responsible for setting all devices to "auto". Will investigate it a
bit further, if laptop-mode was the only one who change those values.
Thanks.
--
-^- _ something is grinding the emptiness:
_ /O)_\// Tristesse de La Lune - Coriolis
(_(|__(_(_) grf. https://tormentedradio.com
next prev parent reply other threads:[~2016-03-12 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 15:15 [gentoo-user] Kernel 4.x and (probably) event issues Roman Dobosz
2016-03-07 0:00 ` Adam Carter
2016-03-12 16:16 ` Roman Dobosz [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-05 8:37 Roman Dobosz
2016-03-07 16:46 ` [gentoo-user] " James
2016-03-12 16:19 ` Roman Dobosz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160312171636.09ad23cf4053e3fe1a2b57c7@op.pl \
--to=gryf73@op.pl \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox