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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338555 Title: Keyboard completely unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Trying the USB live session of 14.04 i-386 on my laptop but the keyboard isn't responding. I'm filing this bug against xorg as stated in the 'DebuggingKeyboardDetection' wiki page. I plugged in a USB keyboard in order to be able to file this report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CasperVersion: 1.340 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 7 12:03:56 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] [1002:71c5] (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. Device [1854:0068] LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: LG Electronics S1-M401E1 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF0B dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: S1-M401E1 dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jul 7 14:49:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp