Getting the lirc_nct677 module to work on ION330 with (ubuntu) kernel 2.6.32-23+

Due to a change in the lirc_dev module the LIRC driver module provided by ASRock will no longer compile / install (depending on your approach) on ubuntu kernels 2.6.32.23 that came with a recent update for ubuntu 10.40.

Compiling the module via dkms might give errors like:

error: ‘struct irctl’ has no member named ‘lock’ in lirc_wb677_main.c

Loading a previous version of the module might give errors like:

lirc_wb677: disagrees about version of symbol lirc_register_driver
lirc_wb677: Unknown symbol lirc_register_driver

To solve this problem I created an updated source-deb of the wb677 driver that does compile on 2.6.32-23 and newer kernels.
You can download it here .

How to use (as root or use sudo):

  1. remove and uninstalled all old modules and (source) packages for the lirc_wb677 module.
  2. download the updated driver dkms-source file
  3. apt-get install dkms
  4. apt-get install lirc-modules-source
  5. dpkg -i  ./lirc-nct677x-src-dkms_1.0.4-ubuntu10.04_all.deb[1]
  6. dkms add -m lirc-nct677x-src -v 1.0.4-ubuntu10.04
  7. dkms build -m lirc-nct677x-src -v 1.0.4-ubuntu10.04
  8. dkms install -m lirc-nct677x-src -v 1.0.4-ubuntu10.04

Make sure you use the default lirc_dev module that comes with the 2.6.32-23 kernel! Delete /lib/modules/2.6.32-23-generic/updates/dkms/lirc_dev.ko folder if it exists and run depmod -a.

To see if the new module loads run modprobe lirc_wb677 and check dmesg for errors.

Configure the lirc modules as outlined in the PDF provided by ASRock.

Update:

A compiled .ko module for the 2.6.32-24 kernel can be found here. Remove everything after the .ko and put the file here: /lib/modules/2.6.32-24-generic/updates/dkms/lirc_wb677.ko

Footnotes:

[Back to post] 1) You can safely ignore the warning generated by dpkg listed below. It must be due to do with my inferior packaging skills. Dpkg just needs to install the source code at the right location (/usr/src) and that bit works just fine.

Warning:
This package appears to be a binaries-only package
you will not be able to build against kernel 2.6.32-23-generic
since the package source was not provided

Posted on July 3, 2010 at 16:12 by alex · Permalink
In: linux · Tagged with: , ,

60 Responses

Subscribe to comments via RSS

  1. Written by biermeester
    on 2010/07/13 at 12:46
    Permalink

    Was really happy to find this blog, but I still keep getting the same errors:

    lirc_wb677: disagrees about version of symbol lirc_register_driver
    lirc_wb677: Unknown symbol lirc_register_driver

    The add/build/install happens without any errors. Might it still not work since I’m using a x86_64 kernel?

    2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

  2. Written by Olov
    on 2010/07/14 at 11:59
    Permalink

    Hi,

    I get an error using your .deb file, any ideas?

    Unpacking replacement lirc-nct677x-src-dkms …
    Setting up lirc-nct677x-src-dkms (1.0.4-ubuntu10.04) …
    Loading new lirc-nct677x-src-1.0.4 DKMS files…
    First Installation: checking all kernels…
    Building only for 2.6.32-23-generic
    Building for architecture i686
    This package appears to be a binaries-only package
    you will not be able to build against kernel 2.6.32-23-generic
    since the package source was not provided

  3. Written by admin
    on 2010/07/15 at 10:11
    Permalink

    Hi Biermeester,

    I’m sorry it did not work for you. It should work on 64bit kernels as well, but it looks like it’s still using the old driver. Please remove all versions of the lirc_wb677.ko on your systems (at least for the 2.6.32-23 kernel) and reinstall. The new driver should be located in the /lib/modules/$kernelversion/updates. Also, make sure you actually booted with the kernel you want to compile the module for.

    While dkms should do it automatically, you might want to run a manual depmod -a to make sure modprobe even considers the new module.

    if it still fails please send me the output of a modinfo lirc_wb677.

    Alex.

    PS: as I don’t have access to box right now, this is all form memory. I will double check tonight.

  4. Written by admin
    on 2010/07/15 at 11:11
    Permalink

    Hi Olov,

    Did you remove the old modules / .deb packages? Are you 100% sure you’re using my package?
    The package I uploaded is explicitly source-only. There are no binaries in that package at all, so it makes no sense dkms / dpkg would say it’s binaries-only.

    Alex.

  5. Written by biermeester
    on 2010/07/15 at 16:03
    Permalink

    Hi,

    Thanks for your reply!

    I get the same ‘binaries only” message as Olov, but the source code gets installed just fine.

    I purged Lirc, lirc-modules-source and anything lirc related and removed the lirc_wb677.ko.

    After that I installed everything again, and tried to build and install your package. But sadly, the problem remains.

    [code]
    root@mediagleuf:/usr/src# modinfo lirc_wb677
    filename: /lib/modules/2.6.32-23-generic/updates/dkms/lirc_wb677.ko
    license: GPL
    author: Nuvoton PS Team
    description: LIRC driver for Nuvoton W83667HG-A & W83677HG CIR
    srcversion: 32C731B485442D1598FF613
    alias: acpi*:NTN0530:*
    alias: pnp:dNTN0530*
    alias: acpi*:WEC0530:*
    alias: pnp:dWEC0530*
    depends: lirc_dev
    vermagic: 2.6.32-23-generic SMP mod_unload modversions
    parm: DRVNAME:Device file name in /dev/ and /sys/class/. (charp)
    parm: CIR_BASE:Base IO port address of 667/677 CIR device. (ushort)
    parm: CIR_IRQ_NUM:IRQ number for 667/677 CIR device. (ushort)
    parm: CIR_WAKE_BASE:Base IO port address of 667/677 CIR WAKE device. (ushort)
    parm: CIR_WAKE_IRQ_NUM:IRQ number for 667/677 CIR WAKE device. (ushort)
    parm: nopnp:Scan for device instead of relying on PNP. (default 0) (uint)
    [/code]

  6. Written by admin
    on 2010/07/15 at 19:36
    Permalink

    update: You can ignore this warning from dpkg. Just follow the rest of the steps. Please let me know if this works for you. (tnx biermeester)

  7. Written by admin
    on 2010/07/15 at 20:11
    Permalink

    Hi,

    You’re right about the binaries only warning, I’ve updated the post.

    The output from your modinfo looks fine to me. I just purged the src and module and reinstalled using this guide and it still worked for me, so possibly it has indeed something to do with the 64bit kernel. ASrock does not provide a separate source for x86_64 systems however.

    Just to be sure: The only other lirc* module that should be loaded is lirc_dev and that should be the version that comes with the 2.6.32-23 kernel (no self-compiled or ‘updated’ or ‘dkms’ version):

    modinfo lirc_dev
    filename: /lib/modules/2.6.32-23-generic/kernel/ubuntu/lirc/lirc_dev/lirc_dev.ko

    alex.

  8. Written by biermeester
    on 2010/07/16 at 00:35
    Permalink

    Thanks again! You’ve put me on the right track: /lib/modules/2.6.32-23-generic/updates/dkms/lirc_dev.ko got inserted instead of the /lib/modules/2.6.32-23-generic/kernel/ubuntu/lirc/lirc_dev/lirc_dev.ko one!

    Not sure where the dkms lirc_dev cam from, and since I’m too much of a noob, I cheated and copied the ‘kernel’ one over the dkms module. That made it lirc start without a problem.

    But still, the remote did not fully work, until I finally came upon the answer: remove the batteries from the remote and put them back. This resets something and now it works!

  9. Written by admin
    on 2010/07/16 at 15:36
    Permalink

    Great! I’ve added the stuff about lirc_dev to the post.

    Thanks for your feedback.

  10. Written by greg johnson
    on 2010/09/20 at 02:55
    Permalink

    hi,

    i’m trying to get linuxmce running on a ION330, which should be a very popular platform for linuxmce.

    linuxmce uses kubuntu intrepid 8.10 with kernel 2.6.27-17.

    any hints as to how to go about getting a lirc_nct677 version to work in that environment?

    many thanks,
    regards,
    greg johnson

  11. Written by Olov
    on 2010/09/23 at 16:49
    Permalink

    Has anyone successfully built it for 2.6.32-24?

    When I run: dkms build -m lirc-nct677x-src -v 1.0.4-ubuntu10.04

    I get:

    Kernel preparation unnecessary for this kernel. Skipping…

    Building module:
    cleaning build area….
    make KERNELRELEASE=2.6.32-24-generic -C lirc_wb677 KSRC=/lib/modules/2.6.32-24-generic/build KVER=2.6.32-24-generic modules….(bad exit status: 2)

    Error! Bad return status for module build on kernel: 2.6.32-24-generic (i686)
    Consult the make.log in the build directory
    /var/lib/dkms/lirc-nct677x-src/1.0.4-ubuntu10.04/build/ for more information.
    0
    0

  12. Written by admin
    on 2010/09/23 at 20:29
    Permalink

    Hi Greg,

    Isn’t there an old version of the asrock (ubuntu) driver available somewhere?
    doesn’t this one: http://europe.asrock.com/downloadsite/drivers/Nettop/Ubuntu/IR(9.10).zip work?

    I’m sorry but I don’t have the time to look in to this.

  13. Written by admin
    on 2010/09/23 at 20:42
    Permalink

    Hi Olov,

    By adding the the driver to the dkms system (with dkms add …) kernel updates should automagically rebuild the driver during the update process. And much to my suprise that actually worked for the -23 to -24 upgrade back in august and subsequent updates to the -24 kernel worked just fine as well.

    But apparently not for you 🙁 Did you try if it ‘just worked’ after the upgrade? Or did you get errors during the kernel update?

    What does the make.log say? Alternatively I could just post my binary .ko file here and be done with it 🙂

  14. Written by Olov
    on 2010/09/25 at 10:25
    Permalink

    Well it was me that was really stupid, after checking the log file i figured out i sometime must have removed lirc-modules-source, after installing it everything builds and installs just fine but the remote isn’t showing up in the reciever list when i’m doing an “dpkg-reconfigure lirc”

    any ideas?

    modinfo looks ok, i think… 🙂

    modinfo lirc_wb677
    filename: /lib/modules/2.6.32-24-generic/updates/dkms/lirc_wb677.ko
    license: GPL
    author: Nuvoton PS Team
    description: LIRC driver for Nuvoton W83667HG-A & W83677HG CIR
    srcversion: 32C731B485442D1598FF613
    alias: acpi*:NTN0530:*
    alias: pnp:dNTN0530*
    alias: acpi*:WEC0530:*
    alias: pnp:dWEC0530*
    depends: lirc_dev
    vermagic: 2.6.32-24-generic SMP mod_unload modversions 586
    parm: DRVNAME:Device file name in /dev/ and /sys/class/. (charp)
    parm: CIR_BASE:Base IO port address of 667/677 CIR device. (ushort)
    parm: CIR_IRQ_NUM:IRQ number for 667/677 CIR device. (ushort)
    parm: CIR_WAKE_BASE:Base IO port address of 667/677 CIR WAKE device. (ushort)
    parm: CIR_WAKE_IRQ_NUM:IRQ number for 667/677 CIR WAKE device. (ushort)
    parm: nopnp:Scan for device instead of relying on PNP. (default 0) (uint)

  15. Written by Johan
    on 2010/09/26 at 16:26
    Permalink

    I’m having the same problem as Olov on kernel 2.6.32-24. Your pkg builds and installs fine but modprobe lirc_wb677 gives me:

    lirc_wb677: disagrees about version of symbol lirc_register_driver
    lirc_wb677: Unknown symbol lirc_register_driver

    Modinfo looks fine though.
    modinfo lirc_wb677
    filename: /lib/modules/2.6.32-24-generic/updates/dkms/lirc_wb677.ko
    license: GPL
    author: Nuvoton PS Team
    description: LIRC driver for Nuvoton W83667HG-A & W83677HG CIR
    srcversion: 32C731B485442D1598FF613
    alias: acpi*:NTN0530:*
    alias: pnp:dNTN0530*
    alias: acpi*:WEC0530:*
    alias: pnp:dWEC0530*
    depends: lirc_dev
    vermagic: 2.6.32-24-generic SMP mod_unload modversions
    parm: DRVNAME:Device file name in /dev/ and /sys/class/. (charp)
    parm: CIR_BASE:Base IO port address of 667/677 CIR device. (ushort)
    parm: CIR_IRQ_NUM:IRQ number for 667/677 CIR device. (ushort)
    parm: CIR_WAKE_BASE:Base IO port address of 667/677 CIR WAKE device. (ushort)
    parm: CIR_WAKE_IRQ_NUM:IRQ number for 667/677 CIR WAKE device. (ushort)
    parm: nopnp:Scan for device instead of relying on PNP. (default 0) (uint)

    When I install lirc it fails to start irexec, maybe that has something to do with it? My remote worked fine before… damn I never should have upgraded my kernel…

  16. Written by Johan
    on 2010/09/27 at 07:42
    Permalink

    Let’s see if I got this right…

    You can disregard my last post, the error to load irexec was fixed by purging and reinstalling lirc AND liblircclient.

    I am now running kernel 2.6.32-23 instead.

    I have followed your instructions and then I downloaded and installed the asrock driver for kernel 23. My remote works as expected but what exactly does your deb do? Will I now be able to upgrade to kernel 24 and my remote will still work? That’s what I was hoping but now as it finally works again I’m not too keen on trying the upgrade just to find out I broke my working setup again… 🙂

  17. Written by admin
    on 2010/09/27 at 09:06
    Permalink

    Yes that shoud work.

    It’s not my .deb.that does that, (the .deb is just the source code for the driver) but the dmks add -m lirc-nct677x-src -v 1.0.4-ubuntu10.04 commando does. When upgrading the kernel (via apt) you can see the upgrade process recompiles all the dkms modules. And in my case that just worked fine. You must keep the source code and it’s dependencies (lirc-modules-source) on your system.

    So, an apt upgrade to a new kernel should leave you with a working remote. Do not re-run the lirc reconfigure process, it’s not necessary.

  18. Written by Johan
    on 2010/09/27 at 09:15
    Permalink

    Unfortunatly I tried the upgrade while waiting on your reply and my remote does no longer work. I tried going back to kernel 23 but now I can’t get that working either.

    sudo service lirc start
    * Loading LIRC modules
    …done.
    * Unable to load LIRC kernel modules. Verify your
    * selected kernel modules in /etc/lirc/hardware.conf
    * Starting execution daemon: irexec
    …fail!

    I don’t get why it won’t load.

  19. Written by admin
    on 2010/09/27 at 09:22
    Permalink

    It might have to do with your lirc.hwdb file. I’ts located in: /usr/share/lirc/lirc.hwdb

    The install process patches that file to add the Nuvotron driver. Perhaps something went wrong there. Have a look at /usr/src/lirc-nct677x-src-1.0.4-ubuntu10.04/lirc_wb677/lirc-nct677x-lirc0.8.6.patch to see what needs te be added.

  20. Written by Johan
    on 2010/09/27 at 09:35
    Permalink

    After some tinkering and rebooting my remote now works again and irexec loads on kernel 23. I will stick with this for now as I have run a purge on my 24 kernel (I assume this prevents a “normal” apt upgrade).

  21. Written by admin
    on 2010/09/27 at 15:44
    Permalink

    Johan,

    In case you might want to try things out with the -24 kernel, I’ve included a link to the compiled module for that kernel at the bottom the main post. Each kernel has it’s own module directory so you should be able to switch between kernels and update a kernel without breaking the other one.

    Once you have a working lirc_wb677 module, you don’t have to (re)configure the lirc-settings between kernels. They all use the same config files.

    So if you’ve got -23 working, upgrade the kernel and, if necessary, copy the compiled module in place and your remote should just be working.

  22. Written by Johan
    on 2010/09/27 at 18:31
    Permalink

    The link to your precompiled module is broken atm.

    I have previously purged kernel 24 which means I can’t do an upgrade. I had to do an apt-get install to get kernel 24 and the remote does not work.

    I can’t do the modprobe as I get the disagree error. I hope your file works better than mine.

  23. Written by admin
    on 2010/09/27 at 19:52
    Permalink

    Sorry, fixed the link. apt-get install is basically the same as an upgrade so it should/could still work. I’m not sure why it doesn’t work for you.

  24. Written by admin
    on 2010/09/27 at 20:06
    Permalink

    And for even more fun, there is yet another kernel update for ububtu 10.04, 2.6.32-25 this time. And again, it automatically compiled the dkms lirc_677 driver. For referene, here’s what an kernel-upgrade looks like on my ion330:

    (note the “run-parts: executing /etc/kernel/header_postinst.d/dkms ..” near the end, that’s where the modules are recompiled. This takes quite some time).

    20:55:02@XBMC# apt-get install linux-generic linux-headers-generic linux-image-generic linux-libc-dev
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    The following extra packages will be installed:
    linux-headers-2.6.32-25 linux-headers-2.6.32-25-generic linux-image-2.6.32-25-generic
    Suggested packages:
    fdutils linux-doc-2.6.32 linux-source-2.6.32 linux-tools
    The following NEW packages will be installed:
    linux-headers-2.6.32-25 linux-headers-2.6.32-25-generic linux-image-2.6.32-25-generic
    The following held packages will be changed:
    linux-image-generic
    The following packages will be upgraded:
    linux-generic linux-headers-generic linux-image-generic linux-libc-dev
    4 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
    Need to get 43.0MB of archives.
    After this operation, 185MB of additional disk space will be used.
    Do you want to continue [Y/n]?
    Get:1 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-image-2.6.32-25-generic 2.6.32-25.44 [31.5MB]
    Get:2 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-generic 2.6.32.25.27 [4,112B]
    Get:3 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-image-generic 2.6.32.25.27 [4,120B]
    Get:4 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-headers-2.6.32-25 2.6.32-25.44 [9,893kB]
    Get:5 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-headers-2.6.32-25-generic 2.6.32-25.44 [752kB]
    Get:6 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-headers-generic 2.6.32.25.27 [4,110B]
    Get:7 http://archive.ubuntu.com/ubuntu/ lucid-updates/main linux-libc-dev 2.6.32-25.44 [794kB]
    Fetched 43.0MB in 9s (4,716kB/s)
    Selecting previously deselected package linux-image-2.6.32-25-generic.
    (Reading database … 118761 files and directories currently installed.)
    Unpacking linux-image-2.6.32-25-generic (from …/linux-image-2.6.32-25-generic_2.6.32-25.44_i386.deb) …
    Done.
    Preparing to replace linux-generic 2.6.32.24.25 (using …/linux-generic_2.6.32.25.27_i386.deb) …
    Unpacking replacement linux-generic …
    Preparing to replace linux-image-generic 2.6.32.24.25 (using …/linux-image-generic_2.6.32.25.27_i386.deb) …
    Unpacking replacement linux-image-generic …
    Selecting previously deselected package linux-headers-2.6.32-25.
    Unpacking linux-headers-2.6.32-25 (from …/linux-headers-2.6.32-25_2.6.32-25.44_all.deb) …
    Selecting previously deselected package linux-headers-2.6.32-25-generic.
    Unpacking linux-headers-2.6.32-25-generic (from …/linux-headers-2.6.32-25-generic_2.6.32-25.44_i386.deb) …
    Preparing to replace linux-headers-generic 2.6.32.24.25 (using …/linux-headers-generic_2.6.32.25.27_i386.deb) …
    Unpacking replacement linux-headers-generic …
    Preparing to replace linux-libc-dev 2.6.32-24.43 (using …/linux-libc-dev_2.6.32-25.44_i386.deb) …
    Unpacking replacement linux-libc-dev …
    Setting up linux-image-2.6.32-25-generic (2.6.32-25.44) …
    Running depmod.
    update-initramfs: Generating /boot/initrd.img-2.6.32-25-generic
    Running postinst hook script /sbin/update-grub.
    Searching for GRUB installation directory … found: /boot/grub
    Searching for default file … found: /boot/grub/default
    Testing for an existing GRUB menu.lst file … found: /boot/grub/menu.lst
    Searching for splash image … none found, skipping …
    Found kernel: /boot/vmlinuz-2.6.32-25-generic
    Found kernel: /boot/vmlinuz-2.6.32-24-generic
    Found kernel: /boot/vmlinuz-2.6.32-23-generic
    Found kernel: /boot/vmlinuz-2.6.32-22-generic
    Replacing config file /var/run/grub/menu.lst with new version
    Updating /boot/grub/menu.lst … done

    Examining /etc/kernel/postinst.d.
    run-parts: executing /etc/kernel/postinst.d/dkms 2.6.32-25-generic /boot/vmlinuz-2.6.32-25-generic
    run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-25-generic /boot/vmlinuz-2.6.32-25-generic

    Setting up linux-image-generic (2.6.32.25.27) …
    Setting up linux-generic (2.6.32.25.27) …
    Setting up linux-headers-2.6.32-25 (2.6.32-25.44) …
    Setting up linux-headers-2.6.32-25-generic (2.6.32-25.44) …
    Examining /etc/kernel/header_postinst.d.
    run-parts: executing /etc/kernel/header_postinst.d/dkms 2.6.32-25-generic /boot/vmlinuz-2.6.32-25-generic

    Setting up linux-headers-generic (2.6.32.25.27) …
    Setting up linux-libc-dev (2.6.32-25.44) …

    /root
    20:57:18@XBMC# ls -lsa /lib/modules/2.6.32-25-generic/updates/dkms/
    total 10604
    4 drwxr-xr-x 2 root root 4096 2010-09-27 20:57 .
    4 drwxr-xr-x 3 root root 4096 2010-09-27 20:56 ..
    36 -rw-r–r– 1 root root 34928 2010-09-27 20:56 lirc_wb677.ko
    10560 -rw-r–r– 1 root root 10810500 2010-09-27 20:57 nvidia-current.ko

    /root
    20:57:57@XBMC#

  25. Written by Johan
    on 2010/09/27 at 20:34
    Permalink

    Your compile gives me the same error as my own unfortunately.

    sudo modprobe lirc_wb677
    FATAL: Error inserting lirc_wb677 (/lib/modules/2.6.32-24-generic/updates/dkms/lirc_wb677.ko): Invalid module format

    Not sure where to go from here.

  26. Written by Johan
    on 2010/09/27 at 21:25
    Permalink

    Tried kernel 25, same issue. Your source doesn’t like my system.

    What kind of setup do you run? I have a minimal ubuntu install (like used in this guide http://wiki.xbmc.org/?title=XBMCbuntu) Perhaps I’m missing some stuff that lirc or dkms needs to compile/use your source/package?

    It would me really cool to be able to use your solution instead of waiting forever for asrock to update the drivers…

  27. Written by admin
    on 2010/09/27 at 22:36
    Permalink

    Hmm if it compiles then it should work. Do you use the ‘standard’ liec_dev module that comes with the kernel? See this bit form my original post:

    Make sure you use the default lirc_dev module that comes with the 2.6.32-23 kernel! Delete /lib/modules/2.6.32-23-generic/updates/dkms/lirc_dev.ko file if it exists and run depmod -a.

    where 2.6.32-23 can obviously be -24 or -25 as well, depending on your kernel.

  28. Written by Johan
    on 2010/09/27 at 23:13
    Permalink

    Yup, that’s what I have done (for every kernel).

    sudo modinfo lirc_dev
    filename: /lib/modules/2.6.32-23-generic/kernel/ubuntu/lirc/lirc_dev/lirc_dev.ko
    alias: char-major-61-*
    license: GPL
    author: Artur Lipowski
    description: LIRC base driver module
    srcversion: 8651E703EAEED391AFE67E8
    depends:
    vermagic: 2.6.32-23-generic SMP mod_unload modversions
    parm: debug:Enable debugging messages (bool)

  29. Written by Johan
    on 2010/09/28 at 00:12
    Permalink

    After some more tinkering I have build your source for kernel 25 and modprobe lirc_wb677 does not give me any errors. Seems to me it’s working but I can’t launch lirc:

    sudo service lirc start
    * Starting execution daemon: irexec
    …fail!

    I see no errors in syslog.

    After adding/building/installing your source, exactly what should I do? dpkg-reconfigure lirc? Install the official asrock stuff? I feel like I’m missing something… When do I select the novuton receiver as I would when installing the official driver?

  30. Written by Johan
    on 2010/09/28 at 00:26
    Permalink

    Finally I got it working with kernel 25. I installed the official asrock kernel 23 driver on top of everything and now it works.

    Does this mean I will survive the next kernel upgrade without all this hassle? I guess it’s a few months away but I’m already curious 🙂

  31. Written by admin
    on 2010/09/28 at 19:36
    Permalink

    Now you’ve got it all working, I’ve got good hopes that the next kernel upgrade will go smoothly. Unless, of course, they change something in the kernel that brakes compatibility with the source code 🙁

  32. Written by Donovan Baarda
    on 2010/10/23 at 15:12
    Permalink

    These instructions worked for me with Ubuntu 10.04 with the one exception that I had to also install the ASRock provided kernel module deb even though It was for an older kernel and didn’t get used just so that it would update the lirc configs needed to select the nuvoton remote.

    For the record, this seems to be broken again for Ubuntu 10.10. The lirc-module-source now puts stuff in /usr/src/lirc-0.8.7~pre3, and I get an error message that seems to indicate your lirc-nct677x-src-dkms source is trying to include headers from /usr/src/lirc-8.6.

    So far the best instructions I’ve found for making it work for Ubuntu 10.10 is http://ubuntuforums.org/showthread.php?t=1596052, but it requires patching/compiling a whole kernel, which seems wrong to me in the age of modules… I should be able to just compile a module.

  33. Written by generator
    on 2010/11/26 at 09:44
    Permalink

    I’ve accidentally installed kernel 2.6.32-26, and now I broke my ir remote again. I was looking for a way to make the drivers kernel independent, so I came across this site.

    Is there any way I can make this work on 2.6.32-26? Should this just work when I follow the steps above?

  34. Written by admin
    on 2010/11/26 at 10:56
    Permalink

    Hi generator,

    I just upgraded to -26 myself and it works just fine for me. So you should be able to get lirc working again.

  35. Written by generator
    on 2010/11/26 at 19:24
    Permalink

    Thx, but when following this guide I get the following error:

    FATAL: Error inserting lirc_wb677 (/lib/modules/2.6.32-26-generic/updates/dkms/lirc_wb677.ko): Unknown symbol in module, or unknown parameter (see dmesg)

    When running dmesg I see this:
    [67778.542612] lirc_wb677: Unknown symbol lirc_register_driver
    [67902.787633] lirc_wb677: disagrees about version of symbol lirc_register_drive

  36. Written by generator
    on 2010/11/26 at 19:43
    Permalink

    Ok I completely missed the lirc_dev.ko file, but it was there and I deleted it.

    The error’s are gone, but when starting lirc I get “Starting execution daemon: irexec [Fail]” just like before…

  37. Written by Johan Samuelsson
    on 2010/11/26 at 20:10
    Permalink

    Today I gambled and updated to kernel 26 and the remote broke again.

    Please describe exactly what you are doing when “Configure the lirc modules as outlined in the PDF provided by ASRock.”.

    I’m probably missing some very easy part of this process as I still can’t get this right. I have followed your instructions to the point. No errors in dmesg after “modprobe lirc_wb677”, what is my next step? Please explain like I was 9 years old because this is really bugging me 🙂

  38. Written by Johan Samuelsson
    on 2010/11/26 at 20:13
    Permalink

    I also think you should be more precise and write the exact command to perform step 1 just to make this install as painless as possible. I know people (except me) are still stuggling to get it running.

  39. Written by generator
    on 2010/11/27 at 11:10
    Permalink

    Yeah I’m not really sure about those steps either. I did a search for 677 in Synaptics and purged the two lirc drivers that came up.

    And for the last step I run dpkg-reconfigure lirc but Nuvoton doesn’t show up in the two list that are presented to me. (When I use the .deb installer from Asrock I get two screens with two choices, so I guess I’m missing two screens).

  40. Written by generator
    on 2010/11/27 at 11:11
    Permalink

    Does this mean you figured it out?

  41. Written by Johan Samuelsson
    on 2010/11/29 at 21:00
    Permalink

    No, I still haven’t got it working on kernel 26. Waiting for detailed instructions to pop up here.

  42. Written by generator
    on 2010/12/01 at 20:26
    Permalink

    Ok, I’ve got it working now. But I honestly can’t say how I got it working. I even went as far as re-installing and booting into the 23 kernel. Then I completely purged lirc, lirc-modules-source and dkms. After following the above steps, I just run the regular 23 kernel .deb file from Asrock.

    Just when I was about to give up, it worked. If you’ve got any specific questions, just ask. Maybe I can help you a little bit.

  43. Written by Johan Samuelsson
    on 2010/12/02 at 11:39
    Permalink

    So you are in fact running on kernel 23 now? I guess I could go back to kernel 25 but that isn’t really solving the problem, just a working around it.

  44. Written by generator
    on 2010/12/02 at 11:54
    Permalink

    No, I’m gunning kernel 26. When you reinstall kernel 26 it should recompile the drivers For that version (if everything went well)

  45. Written by Johan Samuelsson
    on 2010/12/02 at 12:59
    Permalink

    And you did not at all use the updated source-deb from this page? Now I’m just confused.

  46. Written by alex
    on 2010/12/02 at 13:12
    Permalink

    Hi Johan,

    I must confess that I’m not really sure how to install/configure the ‘userland’ part of the driver. My guess is that it’s best to install and configure the original ASRock module, so all settings are correct. Then remove any compiled modules and compile and install ‘mine’ as stated above. Can you install the asrock driver on kernel 26? or doesn’t that work at all? Alternatively I’ll try to post my settings here tonight.

  47. Written by generator
    on 2010/12/02 at 14:02
    Permalink

    I did use the file on this page. But after everything was finished I installed the regular driver over it.

  48. Written by Johan Samuelsson
    on 2010/12/02 at 16:13
    Permalink

    I have it working now on kernel 23. Purged all later kernels, lirc lirc-modules-source and dkms. Followed the guide to the point and then installed the asus deb pkg for kernel 23 on top and rebooted.

    I should now be able to update my kernel without breaking the remote, right? I’m not sure I want to try this update again… 🙂

  49. Written by generator
    on 2010/12/02 at 20:37
    Permalink

    It did work for me.

  50. Written by generator
    on 2010/12/02 at 20:39
    Permalink

    And maybe you have to remove the lirc_dev.ko file and run depmod -a if it doesn’t work right away.

Subscribe to comments via RSS

Leave a Reply