Results 1 to 10 of 30

Thread: Lirc vs Maverick Meerkat 10.04

Hybrid View

  1. #1
    Join Date
    Nov 2006

    Lirc vs Maverick Meerkat 10.04

    It does this at each update . I upgrade to 10.10 and lirc is not working anymore. In 10.04, i was able to get lirc working using lirc_zilog. zilog is not loaded anymore. If i try to compile, i got error.

    My question:
    Am i the only one with problem with lirc and Maverick Lucid?
    Must i continue to use lirc_zilog?
    Does a new lirc_zilog.diff exist for lirc 0.8.7?



  2. #2
    Join Date
    Nov 2006

    Re: Lirc vs Maverick Meerkat 10.04

    Looks like lirc_zilog is the solution again. Where i can find the new .diff? is the question.
    So certain Hauppauge WinTV PVR-150 cards that have a Zilog z8 IR chip on them used to work with lirc_i2c stopped working, as the lirc_i2c driver doesn’t claim to support an i2c device id of ir_rx_z8f0811_haup. However, the lirc_zilog driver *does* claim to support ir_rx_z8f0811_haup. So the answer to this problem is for people to use lirc_zilog instead (after acquiring the requisite “firmware” blob that it needs — google knows where to find it, its also covered somewhere on this site in a blog posting on the hdpvr’s IR part). Note that lirc_i2c is likely to disappear entirely in the relatively near future, supplanted entirely by ir-kbd-i2c, which is now ported to ir-core, and its input layer event device can be snarfed for keypress data. It even works with ir_rx_z8f0811_haup devices (lirc_i2c *could* be made to support them as well, but I see no point in it, when its going away anyway).

  3. #3
    Join Date
    Nov 2006

    Re: Lirc vs Maverick Meerkat 10.04

    No answer. Does it means i'm the only one with a pvr150 and hdpvr not working on maverick 10.10?

    I tried a lot of things without success. The only thing i don't know how to do is to make lirc_zilog work with the new kernel and the version 0.8.7 of lirc. Sooo sad!


  4. #4
    Join Date
    Nov 2006

    Re: Lirc vs Maverick Meerkat 10.04

    I try the old patch that work on 10.04. Anybody knows what is auto.conf or autoconf.h. These files seem to be missing

    Command line:

    sudo apt-get install lirc-modules-source
    cd /usr/src/lirc-0.8.7
    sudo patch -p0 < ~/zilog.diff
    patching file lirc-modules-source.conf
    patching file dkms.conf
    patching file Makefile
    patching file drivers/lirc_zilog/.deps/lirc_zilog.Po
    patching file drivers/lirc_zilog/Makefile
    patching file drivers/lirc_zilog/lirc_zilog.c
    patching file drivers/Makefile
    Hunk #1 succeeded at 246 (offset 110 lines).
    sudo dpkg-reconfigure lirc-modules-source
    Removing all DKMS Modules
    Loading new lirc-0.8.7~pre3 DKMS files...
    Building only for 2.6.35-22-generic
    Building for architecture i686
    Building initial module for 2.6.35-22-generic

    Error! Bad return status for module build on kernel: 2.6.35-22-generic (i686)
    Consult the make.log in the build directory
    /var/lib/dkms/lirc/0.8.7~pre3/build/ for more information.
    Excerpt of /var/lib/dkms/lirc/0.8.7~pre3/build/make.log
    make -C drivers SUBDIRS="lirc_zilog"
    make[1]: entrant dans le répertoire « /var/lib/dkms/lirc/0.8.7~pre3/build/drivers »
    Making all in lirc_zilog
    make[2]: entrant dans le répertoire « /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog »
    cp ./../lirc_dev/Module*.symvers .
    mv Makefile Makefile.automake
    cp ./../Makefile.kernel Makefile
    make -C /lib/modules/2.6.35-22-generic/build SUBDIRS=/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog modules \
    make[3]: entrant dans le répertoire « /usr/src/linux-headers-2.6.35-22-generic »
    test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
    echo; \
    echo " ERROR: Kernel configuration is invalid."; \
    echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
    echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
    echo; \
    mkdir -p /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/.tmp_versions ; rm -f /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/.tmp_versions/*
    make -f scripts/ obj=/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog
    gcc -Wp,-MD,/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/.lirc_zilog.o.d -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/4.4.5/include -I/usr/src/linux-headers-2.6.35-22-generic/arch/x86/include -Iinclude -include include/generated/autoconf.h -Iubuntu/include -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -maccumulate-outgoing-args -Wa,-mtune=generic32 -ffreestanding -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=1024 -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DIRCTL_DEV_MAJOR=61 -DEXPORT_SYMTAB -DHAVE_CONFIG_H -I. -I. -I../.. -I/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/. -I/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/ -I/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/../.. -I/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/../.. -I/lib/modules/2.6.35-22-generic/build/include/ -I/lib/modules/2.6.35-22-generic/build/drivers/media/video/ -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(lirc_zilog)" -D"KBUILD_MODNAME=KBUILD_STR(lirc_zilog)" -c -o /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/.tmp_lirc_zilog.o /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/lirc_zilog.c
    /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/lirc_zilog.c:41: fatal error: linux/autoconf.h: Aucun fichier ou dossier de ce type
    compilation terminated.
    make[4]: *** [/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog/lirc_zilog.o] Erreur 1
    make[3]: *** [_module_/var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog] Erreur 2
    make[3]: quittant le répertoire « /usr/src/linux-headers-2.6.35-22-generic »
    make[2]: *** [lirc_zilog.o] Erreur 2
    make[2]: quittant le répertoire « /var/lib/dkms/lirc/0.8.7~pre3/build/drivers/lirc_zilog »
    make[1]: *** [all-recursive] Erreur 1
    make[1]: quittant le répertoire « /var/lib/dkms/lirc/0.8.7~pre3/build/drivers »
    make: *** [zilog] Erreur 2
    Last edited by Kheops_74; October 21st, 2010 at 02:04 AM.

  5. #5
    Join Date
    Nov 2006

    Re: Lirc vs Maverick Meerkat 10.04

    I install linux-source-2.6.35 package and change #include <linux/autoconf.h> to #include </usr/src/linux-headers-2.6.35-22-generic/include/generated/autoconf.h> in the /drivers/lirc_zilog/lirc_zilog.c file.

    The command "sudo dpkg-reconfigure lirc-modules-source" works and /dev/lirc0, /dev/lirc1 appear. The remote work.

    My last problem is the irsend command. I receive an error

    irsend --device=/dev/lircd SEND_ONCE blaster 1
    irsend: command failed: SEND_ONCE blaster 1
    irsend: hardware does not support sending
    I already had this one in the past but i don't remember what it was.

  6. #6
    Join Date
    Nov 2006

    Re: Lirc vs Maverick Meerkat 10.04

    I get lirc_zilog.c source code from this site;hb=HEAD and replace mine.

    I did sudo dpkg-reconfigure lirc-modules-source again and
    sudo rmmod lirc_i2c
    sudo rmmod lirc_zilog
    sudo rmmod lirc_dev
    sudo modprobe lirc_i2c
    sudo modprobe lirc_zilog

    I modify the hardware.conf and lircd.conf.

    The blaster work


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts