[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This problem appears to be solved by setting
GRUB_CMDLINE_LINUX="i8042.nomux=1 i8042.reset" in /etc/default/grub (as
advised in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210748). Looks
like it's either buggy hardware or a buggy driver, then.
--
You received this bug notification
Matteo Dell'Amico, to keep this report relevant to upstream, could you
please continue to test the latest mainline kernel as it comes out (now
4.6-rc7)?
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This is just to confirm that the bug still appears in Ubuntu 16.04. I am
stuck with bisection, because I can't find the binaries for Saucy from
the link you posted -- appears to be too old. Also, when I tried to run
old kernels on this laptop nothing was working as apparently newer
distros require
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Matteo Dell'Amico, for instructions on this please see
https://wiki.ubuntu.com/Kernel/KernelBisection .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512482
Title:
Keyboard and
Unfortunately, I don't have them anymore as I had to delete them to make
space for upgrades.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512482
Title:
Keyboard and touchpad
Matteo Dell'Amico, you wouldn't have to download them as they would
still be loadable via GRUB given you upgraded from Saucy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512482
Title:
Could you please tell me where to download them from? I'm having a bit
of a hard time navigating through old-releases.ubuntu.com. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Matteo Dell'Amico, could you please advise which release prior to vivid
specifically this wasn't an issue in?
If you don't know, it would need to be confirmed to root cause. Prior
release ISOs are available via http://releases.ubuntu.com/ .
** Tags removed: kernel-bug-exists-upstream-4.3
** Tags
I remember that I didn't have this problem in 13.10 (Saucy) and I had it
in Vivid and now Wily.
What do you mean as "confirmed to root cause"? What do you expect me to
do next?
thanks!
matteo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Matteo Dell'Amico, if you boot a kernel from Saucy, is this issue still
reproducible?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512482
Title:
Keyboard and touchpad malfunctioning
Bug confirmed also on the 4.4-rc3 kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512482
Title:
Keyboard
Matteo Dell'Amico, the latest mainline kernel is 4.4-rc2 (not 4.3.x).
** Tags removed: bios-outdated-1.71
** Tags added: latest-bios-1.71
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
I just reproduced it on the mainline kernel 4.3 (4.3.0-040300-generic).
Now I've reproduced the bug with all combinations of BIOS and kernel
versions.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Couldn't reproduce it yet. At the moment, the situation is:
Kernel 4.2.0, both BIOS versions (v. 1.69 & v. 1.71): bug present
Mainline kernel 4.3, old BIOS v. 1.69: bug present
Mainline kernel 4.3, new BIOS v. 1.71: but not reproduced yet
--
You received this bug notification because you are a
I was speaking too early. The problem resurfaced. Now running 1.71 BIOS
and 4.2.0-19-generic kernel.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Matteo Dell'Amico, and how does it run on the latest mainline kernel?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Christopher and Joseph, thanks a lot!
After updating the BIOS, the problem *seems* to be gone. I'll mark this
as Invalid, and will change it to Confirmed it if it shows up again.
The output for the dmidecode commands is
GDETB1WW (1.71 )
09/14/2015
Thanks a lot!
matteo
** Changed in: linux
Matteo Dell'Amico, as per http://support.lenovo.com/us/en/products
/laptops-and-netbooks/thinkpad-twist-series-laptops/thinkpad-twist-
s230u/3347/4hu an update to your computer's buggy and outdated BIOS is
available (1.71). If you update to this following
After a reboot, the same problem is now happening with the upstream
(4.3) kernel.
Again, I'm not really sure this is a kernel problem and the devices are
not appearing on xinput --list.
Please let me know how I can help further.
** Tags removed: kernel-fixed-upstream needs-reverse-bisect
--
Matteo Dell'Amico, the next step is to fully reverse commit bisect from
kernel 4.2 to 4.3 in order to identify the last bad commit, followed
immediately by the first good one. Once this commit has been identified,
then it may be reviewed as a candidate for backporting into your
release. Could you
If I remember correctly, I started having the issue with the upgrade
from 14.10 to 15.04, I believe. Stupid me, I didn't file the bug because
I didn't know which package to file it for.
Right now I'm running the 4.3 mainline kernel, and everything seems to
run fine.
** Tags added:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3
24 matches
Mail list logo
