I think I roughly understand this requirement. So basically I'm supposed to go back the mainline kernel list where I used the top link in the previous email and starting with the original trusty kernel go midway up the list and test that kernel (as above) and keep using this search algorithm in addition to testing until the kernel where the bug got fixed is pinpointed. However when I downloaded the [v3.14-trusty/ 25-Feb-2015 09:38] kernel and installed it using [sudo dpkg -i *.deb] and then booted into it the keyboard worked fine. Maybe because I already edited the /etc/default/grub file on this same machine as described above.
On Wed, Feb 25, 2015 at 2:56 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Bashar, the next step is to fully reverse commit bisect from kernel 3.13 > to 4.0-rc1 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 please do this following > > https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F > ? > > Please note, finding adjacent kernel versions is not fully commit > bisecting. > > Thank you for your understanding. > > Helpful bug reporting tips: > https://wiki.ubuntu.com/ReportingBugs > > ** Tags removed: kernel-fixed-upstream-4.0.0-040000rc1 > ** Tags added: apport-bug compiz-0.9 i386 kernel-fixed-upstream-4.0-rc1 > needs-reverse-bisect trusty ubuntu > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1338555 > > Title: > Keyboard completely unresponsive > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338555/+subscriptions > -- Bashar Maree -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338555 Title: Keyboard completely unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
