15c2:0038 Unable to boot from S5 with Soundgraph iMon IR module

[Olli Niemikorpi]

After complete Ubuntu shut down, the system does not wake up with Soundgraph Imon IR. Since complete remote boot is possible after Windows shutdown, this seems to be a Linux Kernel bug and related to the way Linux handles the shut down process. Some users have reported that remote boot was possible with Kernels prior to 2.6.32 version.

There are several topics around the issue I have, but I was unable to find any bug reports of the issue. Please refer:
http://ubuntuforums.org/showthread.php?t=2014242
http://www.soundgraph.com/forums/showthread.php?p=37616
http://forum.kodi.tv/showthread.php?tid=194870
http://ubuntuforums.org/showthread.php?t=2219778

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-37-generic 3.13.0-37.64
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: niemikorpi 1861 F.... pulseaudio
 /dev/snd/controlC0: niemikorpi 1861 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Nov 2 18:01:57 2014
HibernationDevice: RESUME=UUID=deab300a-6f47-44e7-834e-94ac0954061a
InstallationDate: Installed on 2014-10-15 (17 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=78e2c4b6-1ff6-4e09-ae97-92a0f97acbb5 ro nomodeset quiet splash nomodeset video=uvesafb:mode_option=800x600-24,mtrr=3,scroll=ywrap vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-37-generic N/A
 linux-backports-modules-3.13.0-37-generic N/A
 linux-firmware 1.127.7
RfKill:

SourcePackage: linux
StagingDrivers: lirc_imon
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1206
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1206:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Olli Niemikorpi, thank you for reporting this and helping make Ubuntu better. 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.18-rc1

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.

[penalvch (penalvch)]

Olli Niemikorpi, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Tocinillo (evanelion-infinite)]

I can confirm the same bug with iMON 0036. I tried everything but nothing works. The bug is not fixed in the latest RC Kernel :(

Regards.

[penalvch (penalvch)]

Tocinillo, 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 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

[Tocinillo (evanelion-infinite)]

Wooooa! Finally after one week of work and investigate finally I can poweron my HTPC (OrigenM10 with 15c2:0036 VFD+Remote). This annyioing bug is very easy to fix. Edit your /etc/init.d/lirc file and change the line:

DISABLE_KERNEL_SUPPORT=true

to

DISABLE_KERNEL_SUPPORT=false

Everything is working perfect now! :)

I think maybe that Soundgraph IR need the kernel support or something like this ;)

[Olli Niemikorpi (mr-oole)]

Thank you, Tocinillo! Works like a charm even without lirc (which seems to break the remote wake up facility)...

[penalvch (penalvch)]

Oli Niemikorpi, this would not be Status Opinion as defined by https://wiki.ubuntu.com/Bugs/Status . The root cause package may be of a difference of opinion, but a developer may work on this issue now to investigate and fix.

[Alec Leamas (leamas-alec)]

In any case, this bug should be re-assigned to the kernel, obvious from earlier discussion

[penalvch (penalvch)]

Alec Leamas, at the top of this report, it has been marked Triaged for linux (Ubuntu) since December 22, 2014.

[Alec Leamas (leamas-alec)]

OK, thanks for feedback. I'm a Debian rookie trying to maintain lirc... Is there any legend explaining what these statuses means in general.. And, here what does "Triaged for linux" mean here?

[penalvch (penalvch)]

Alec Leamas, thanks for your Debian efforts with lirc! Status is defined via https://wiki.ubuntu.com/Bugs/Status . Please feel free to ping me anytime if it would be helpful to you.