[Lenovo IdeaPad S10-3c] keyboard problem

[Aaron Davis]

I am not sure if this issue is fixed.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/677633

I went through the steps in post #114 and #136. I am not sure what is the problem. I don't really know anything about compiling scripts like in post #111. I'm an english and math teacher, but only somewhat proficient with computers.

Just to affirm, I did copy the driver file s10-3c-keybdrv-x86-64 to the /bin directory, I did execute chmod +x /bin/s10-3c-keybdrv-x86-64 as root, and I did edit /etc/rc.local as root to add the string /bin/s10-3c-keybdrv-x86-64. I copied s10-3c-keybdrv.c to the sbin directory. I rebooted.

Is there any step I am missing?

Thank you for your help! I would love to use ubuntu on my computer. I don't want to go back to microsoft :(

should I update my bios?

should I run the script in the link on the 101st post and replace Oxad with Ox64? (not the xing profile link, but the other one).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aaron 1502 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Aug 2 00:26:58 2014
HibernationDevice: RESUME=UUID=903a0b43-e4dc-44e6-9bf3-eda6e9670706
InstallationDate: Installed on 2014-07-31 (1 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: LENOVO 4392
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog: Aug 2 00:20:10 aaron-Lenovo-S10-3c NetworkManager[706]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
dmi.bios.date: 09/15/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 3CCN13WW
dmi.board.vendor: LENOVO
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnLENOVO:bvr3CCN13WW:bd09/15/2010:svnLENOVO:pn4392:pvrLenovo-S10-3c:rvnLENOVO:rn:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: 4392
dmi.product.version: Lenovo-S10-3c
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Aaron Davis (aaron-davis8)]

Hi Chris,

Sorry for the late reply. I went through several steps to flash my bios and
for some reason freedos and several others were just not running
executables, even with unetbootin and rufus.

So, I finally just repartitioned and am dual booting windows and linux and
I flashed the bios. Here is my response to
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

aaron@aaron-Lenovo-S10-3c:~$ sudo dmidecode -s bios-version && sudo
dmidecode -s bios-release-date
[sudo] password for aaron:
3CCN16WW
01/28/2011

However, the keyboard still does not work. Is there some extra step I am
missing? I have upgraded and updated.

Thank you bunches for the help, Chris.

-Aaron

On Sat, Aug 2, 2014 at 7:36 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Aaron Davis, thank you for reporting this and helping make Ubuntu better.
> As per http://download.lenovo.com/express/ddfm.html an update to your
> BIOS is available (3CCN16WW). If you update to this following
> https://help.ubuntu.com/community/BiosUpdate does it change anything? If
> it doesn't, could you please both specify what happened, and provide the
> output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report. As well, you don't have to create a new
> bug report.
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Once the BIOS is updated, then please mark this report Status Confirmed.
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-3ccn16ww
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Summary changed:
>
> - Lenovo ideapad s10-3c keyboard problem
> + [Lenovo IdeaPad S10-3c] keyboard problem
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1351390
>
> Title:
> [Lenovo IdeaPad S10-3c] keyboard problem
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
>
> I am not sure if this issue is fixed.
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/677633
>
> I went through the steps in post #114 and #136. I am not sure what is
> the problem. I don't really know anything about compiling scripts like
> in post #111. I'm an english and math teacher, but only somewhat
> proficient with computers.
>
> Just to affirm, I did copy the driver file s10-3c-keybdrv-x86-64 to
> the /bin directory, I did execute chmod +x /bin/s10-3c-keybdrv-x86-64
> as root, and I did edit /etc/rc.local as root to add the string
> /bin/s10-3c-keybdrv-x86-64. I copied s10-3c-keybdrv.c to the sbin
> directory. I rebooted.
>
> Is there any step I am missing?
>
> Thank you for your help! I would love to use ubuntu on my computer. I
> don't want to go back to microsoft :(
>
> should I update my bios?
>
> should I run ...

[penalvch (penalvch)]

Aaron Davis, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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.17-rc2

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.

[Launchpad Janitor (janitor)]

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

[Aaron Davis (aaron-davis8)]

Ugh, I'm an idiot. I didn't compile it in C and I was stupidly trying to make the 64 bit architecture run on the 32 bit. With the Lenovo s10-3c, I can't really run the 64 (not too much ram there).

If anyone wants the file I have used to make the keyboard work, I've attached it here.

[penalvch (penalvch)]

Aaron Davis, just to advise, there would be no dependency on lack of RAM to using a 32-bit or 64-bit operating system. It's dependent on the CPU type one has.

Despite this, if you test http://cdimage.ubuntu.com/daily-live/current/ (32-bit is fine) is this still reproducible?