LG P1-Express Dual: Internal keyboard doesn't work in Ubuntu 13.10 and 14.04

[britgreek]

Internal keyboard of LG P1-Express Dual doesn't work in Ubuntu 13.10 or 14.04 32bit using the default kernel. The internal keyboard also doesn't work on any Ubuntu derivative or Ubuntu-based distribution (Mint 16, etc). Furthermore, the three special buttons to adjust volume, access direct media, or configure SRS do not work either. Number lock light is on, even though the keyboard doesn't work.

WORKAROUND: I am using an external USB Microsoft wired keyboard (400 v.1).

I installed the 3.2.0-0302000-generic-pae mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/linux-image-3.2.0-030200-generic-pae_3.2.0-030200.201201042035_i386.deb and the internal keyboard works fine. However, after installing it, other unrelated issues have occurred (sound problems, mainly static-cracking sound upon starting any audio or sound, or adjusting volume).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-15-generic 3.13.0-15.35
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic i686
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user1 1736 F.... pulseaudio
CurrentDesktop: Unity
CurrentDmesg:

Date: Wed Mar 5 22:28:34 2014
HibernationDevice: RESUME=UUID=5202ca10-629d-4d1e-9e5d-38ea9e130e64
InstallationDate: Installed on 2014-03-05 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140124)
MachineType: LG Electronics 608KSYU001402
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=62f0615b-9813-4a98-ba2e-be32b9528830 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-15-generic N/A
 linux-backports-modules-3.13.0-15-generic N/A
 linux-firmware 1.125
SourcePackage: linux
StagingDrivers: et131x
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: RKYWSF33
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:bvrRKYWSF33:bd09/19/2007:svnLGElectronics:pn608KSYU001402:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
dmi.product.name: 608KSYU001402
dmi.product.version: Not Applicable
dmi.sys.vendor: LG Electronics

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alberto Salvia Novella (es20490446e)]

It affects an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse).

[britgreek (britgreek)]

Thank you for your reply. Just one question. As I could not use the laptop, I installed ElementaryOS, which is based on Ubuntu 12.04 and everything works fine (apart from an instant crackling noise coming out of the speakers whenever any kind of audio starts). Is there anyway to follow the suggested steps, without having to reinstall Ubuntu? The laptop is used daily in a professional environment and I had to install an OS that would work, after reporting the bug.

Thanks again.

[britgreek (britgreek)]

I used 12.04 for a year, and everything worked fine. The problems started in version 13.10 onwards. I hope that helps. If you want, I can run any live cd/dvd and post any logs that are required.

The popping sound issue that i have reported has existed in all Ubuntu releases from 11.10 onwards (and ubuntu derivatives) that I have used, but following the instructions on

http://www.foxswap.com/computers-and-technology/ubuntu-12-04-clicking-sound-from-speakers/ I can fix it instantly.

Thanks once again for your interest and help. I will be waiting for your instructions.

[penalvch (penalvch)]

britgreek, the next step is to fully commit bisect from 12.04.0 to 13.10 in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[britgreek (britgreek)]

Thank you for replying. Unfortunately, I do not understand at all how to do the whole procedure. My knowledge of linux is rather limited to user level and I am not allowed to change the os currently installed, as this is a laptop used for business.

Would there be any other way to approach the issue?

[ikarias (marco-moebus)]

I can confirm the bug on a LG T1 Express Dual laptop. Had the same issue trying to install 14.04 from a Live USB stick. I got stuck due to the non-working keyboard during the install process and cannot currently install, since I am still looking for a USB keyboard asa substitute.
I can also confirm the laptop keyboard was also recognized fine with earlier versions of Ubuntu, although the latest version I had was 12.10 (so I cannot currently confirm in which kernel the bug got introduced).
Once I am back on a running 14.04 system installed, I will try and test the mainline kernel. While I am willing to experiment and also have some deeper , I must say I have not pulled kernel builds manually so far, so I might need some assistance along the way for single steps (while come back here and request, if neccessary).

[penalvch (penalvch)]

ikarias, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[britgreek (britgreek)]

No, the problem persists, even after upgrading to the latest kernel. The last version of Ubuntu and its derivatives that worked fine was 12.04.

[penalvch (penalvch)]

britgreek, in order to address this report, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[britgreek (britgreek)]

Sorry, I do not understand how to upgrade the kernel in order to test it.

Do you mean I should run

sudo apt-get update

sudo apt-get dist-upgrade ?

The page that you quoted is not very clear to me and I cannot figure out how to follow the procedure.

[Attitudeswe (ubuntu-visser)]

bug confirmed to exist on ubuntu 14.04.01 as well with 3.13.0-32-generic kernel. Will report back once kernel has been upgraded...

[penalvch (penalvch)]

Attitudeswe, thank you for your comment. Please do not mark this a duplicate of another bug (especially one that is marked Invalid), or vice versa.

Despite this, so your problem and hardware may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Attitudeswe (ubuntu-visser)]

when installing the latest 14.04.1 kernel 3.14.0-43-generic the internal keyboard of lg p1 works (didnt work before update). So it seems this bug has been resolved at least for 14.04

[jos logister (joslogister)]

Dear Christopher

What do you mean?

Do I have to report my bug to: ubuntu-bug linux, https://help.ubuntu.com/community/ReportingBugs

And via Launchpad account??

With kind regards

Jos Logister

-----Oorspronkelijk bericht-----
Van: <email address hidden> [mailto:<email address hidden>] Namens Christopher M. Penalver
Verzonden: maandag 29 december 2014 11:53
Aan: <email address hidden>
Onderwerp: [Bug 1288414] Re: LG P1-Express Dual: Internal keyboard doesn't work in Ubuntu 13.10 and 14.04

Attitudeswe, thank you for your comment. Please do not mark this a duplicate of another bug (especially one that is marked Invalid), or vice versa.

Despite this, so your problem and hardware may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** This bug is no longer a duplicate of bug 1243904
   [LG P1-J273B] Internal keyboard doesn't work in 13.10

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1288414

Title:
  LG P1-Express Dual: Internal keyboard doesn't work in Ubuntu 13.10 and
  14.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Internal keyboard of LG P1-Express Dual doesn't work in Ubuntu 13.10
  or 14.04 32bit using the default kernel. The internal keyboard also
  doesn't work on any Ubuntu derivative or Ubuntu-based distribution
  (Mint 16, etc). Furthermore, the three special buttons to adjust
  volume, access direct media, or configure SRS do not work either.
  Number lock light is on, even though the keyboard doesn't work.

  WORKAROUND: I am using an external USB Microsoft wired keyboard (400
  v.1).

  I installed the 3.2.0-0302000-generic-pae mainline kernel from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/linux-
  image-3.2.0-030200-generic-pae_3.2.0-030200.201201042035_i386.deb and
  the internal keyboard works fine. However, after installing it, other
  unrelated issues have occurred (sound problems, mainly static-cracking
  sound upon starting any audio or sound, or adjusting volume).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-15-generic 3.13.0-15.35
  ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
  Uname: Linux 3.13.0-15-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: us...

[penalvch (penalvch)]

jos logister, yes, please file a new report.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]