Page 1 of 4 123 ... LastLast
Results 1 to 10 of 38

Thread: lirc does not seem to be loading in hardy (upgrade from gutsy)

  1. #1
    Join Date
    Dec 2005
    Beans
    113

    lirc does not seem to be loading in hardy (upgrade from gutsy)

    I just upgraded from Gutsy to Hardy.

    Lirc doesn't seem to want to load/run.

    Code:
    [   46.412902] lirc_dev: disagrees about version of symbol struct_module
    [   46.413591] lirc_i2c: disagrees about version of symbol struct_module
    [  150.498761] lirc_dev: disagrees about version of symbol struct_module
    [  150.505809] lirc_dev: disagrees about version of symbol struct_module
    [  150.508594] lirc_i2c: disagrees about version of symbol struct_module

    It sounds like the following error occurs when the headers do not match the kernel? It that correct?
    Could this be a problem with the repositories?

    I don't know what to do from here. Any suggestions?

    Thanks.

  2. #2
    Join Date
    Dec 2006
    Location
    Jacksonville, FL
    Beans
    36

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    I am experiencing the same problem. Did you happen to find a solution?

    dmesg | grep -i lirc
    [ 47.438608] lirc_dev: disagrees about version of symbol struct_module
    [ 47.466036] lirc_i2c: disagrees about version of symbol struct_module
    [ 465.284937] lirc_dev: disagrees about version of symbol struct_module
    [ 465.291459] lirc_dev: disagrees about version of symbol struct_module
    [ 465.292111] lirc_i2c: disagrees about version of symbol struct_module

  3. #3
    Join Date
    Oct 2005
    Location
    Milano, Italy
    Beans
    871
    Distro
    Ubuntu Jaunty Jackalope (testing)

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    You must add lirc_dev under MODULES in /etc/lirc/hardware.conf
    Code:
    MODULES="lirc_i2c"
    became
    Code:
    MODULES="lirc_dev lirc_i2c"
    In my case (upgraded from Gutsy to Hardy) was necessary to remove this package too:
    Code:
    sudo apt-get --purge remove dkms
    ------------------------------------------------
    yep ”short and long URL„
    http://yep.it/
    ------------------------------------------------

  4. #4
    Join Date
    Dec 2005
    Beans
    113

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    Thanks! This seems to help.

    I no longer get the 'disagrees about version of symbol struct_module' errors after uninstalling dkms and rebooting.

    However, the remote still does not work.

    $ sudo lircd
    lircd: WARNING: config file contains no valid remote control definition

    BUT

    # /etc/lirc/hardware.conf
    #
    #Chosen Remote Control
    REMOTE="Hauppauge TV card"
    REMOTE_MODULES="lirc_dev lirc_i2c"
    REMOTE_DRIVER=""
    REMOTE_DEVICE="/dev/lirc0"
    REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
    :
    :

    # /etc/lirc/lircd.conf
    # Configuration for the Hauppauge TV card remote:
    include /usr/share/lirc/remotes/hauppauge/lircd.conf.hauppauge

    # /usr/share/lirc/remotes/hauppauge/lircd.conf.hauppauge
    #
    # this config file was automatically generated
    # using lirc-0.5.5pre8 on Sun Apr 18 11:43:45 1999
    #
    # contributed by Jens Leuschner <leuschner@gmx.net>
    #
    # brand: Hauppauge
    # model:
    # supported devices: WinTV primo; WinTV pci; WinTV radio
    #
    # This config file will work with both homebrew receivers and
    # original Hauppauge TV cards !!!
    #
    <remote code definitions>
    :
    :

    Any ideas?

  5. #5
    Join Date
    Oct 2005
    Location
    Milano, Italy
    Beans
    871
    Distro
    Ubuntu Jaunty Jackalope (testing)

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    Hi,
    your hardware.conf seems incomplete; did you re-run:
    Code:
    sudo dpkg-reconfigure lirc
    Anyway this is my hardware.conf (Hauppauge too):
    Code:
    # /etc/lirc/hardware.conf
    #
    # Arguments which will be used when launching lircd
    LIRCD_ARGS=""
    
    #Don't start lircmd even if there seems to be a good config file
    START_LIRCMD=false
    
    #Try to load appropriate kernel modules
    LOAD_MODULES=true
    
    # Run "lircd --driver=help" for a list of supported drivers.
    DRIVER=""
    # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
    # automatically used instead
    DEVICE="/dev/lirc"
    MODULES="lirc_dev lirc_i2c"
    
    # Default configuration files for your hardware if any
    LIRCD_CONF=""
    LIRCMD_CONF=""
    REMOTE="Hauppauge TV card"
    REMOTE_MODULES="lirc_dev lirc_i2c"
    REMOTE_DRIVER=""
    REMOTE_DEVICE="/dev/lirc/0"
    REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
    REMOTE_LIRCD_ARGS=""
    TRANSMITTER="Command IR : Direct TV Receiver"
    TRANSMITTER_MODULES="lirc_dev lirc_cmdir"
    TRANSMITTER_DRIVER=""
    TRANSMITTER_DEVICE="/dev/lirc/1"
    TRANSMITTER_LIRCD_CONF="directtv/general.conf"
    TRANSMITTER_LIRCD_ARGS=""
    START_LIRCD="true"
    FORCE_NONINTERACTIVE_RECONFIGURATION="false"
    As you can see (at least in my case) the REMOTE_DEVICE and the TRANSMITTER_DEVICE changed the dev position

    More strange: lirc is working, but during the bootup give me "fail" as daemon, but in KDE I create an Autostart entry for "irexec"
    Code:
    sudo ln -s /usr/bin/irexec ~/.kde/Autostart/irexec
    and it works! Despite the error in the bootup process.

    In any case the lirc is there on my box:
    Code:
    dmesg |grep lirc
    Code:
    [   48.889995] lirc_dev: IR Remote Control driver registered, at major 61
    [   49.021645] lirc_i2c: chip 0x10005 found @ 0x18 (Hauppauge IR)
    [   49.021672] lirc_dev: lirc_register_plugin: sample_rate: 10
    [   49.163904] lirc_dev: lirc_register_plugin: sample_rate: 20
    [   49.165676] lirc_cmdir: freq set to 38000Hz
    Last edited by dentaku65; April 27th, 2008 at 12:33 PM.
    ------------------------------------------------
    yep ”short and long URL„
    http://yep.it/
    ------------------------------------------------

  6. #6
    Join Date
    Dec 2005
    Beans
    113

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    Thanks. I tried to run the command you suggest:

    Code:
    $ sudo dpkg-reconfigure lirc
     * Stopping remote control mouse daemon: LIRCMD                          [fail]
     * Stopping remote control daemon(s): LIRC       .conf                   [fail]
     * Reloading kernel event manager...                                     [ OK ]
     * Loading LIRC modules                                                  [ OK ]
     * Unable to load LIRC kernel modules. Verify your
     * selected kernel modules in /etc/lirc/hardware.conf
    Checking /etc/lirc/hardware.conf:

    Code:
    # /etc/lirc/hardware.conf
    #
    #Chosen Remote Control
    REMOTE="Hauppauge TV card"
    REMOTE_MODULES="lirc_dev lirc_i2c"
    REMOTE_DRIVER=""
    REMOTE_DEVICE="/dev/lirc0"
    REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
    REMOTE_LIRCD_ARGS=""
    
    #Chosen IR Transmitter
    TRANSMITTER="None"
    TRANSMITTER_MODULES=""
    TRANSMITTER_DRIVER=""
    TRANSMITTER_DEVICE=""
    TRANSMITTER_LIRCD_CONF=""
    TRANSMITTER_LIRCD_ARGS=""
    
    #Enable lircd
    START_LIRCD="true"
    
    #Don't start lircmd even if there seems to be a good config file
    #START_LIRCMD="false"
    
    #Try to load appropriate kernel modules
    LOAD_MODULES="true"
    
    # Default configuration files for your hardware if any
    LIRCMD_CONF=""
    
    #Forcing noninteractive reconfiguration
    #If lirc is to be reconfigured by an external application
    #that doesn't have a debconf frontend available, the noninteractive
    #frontend can be invoked and set to parse REMOTE and TRANSMITTER
    #It will then populate all other variables without any user input
    #If you would like to configure lirc via standard methods, be sure
    #to leave this set to "false"
    FORCE_NONINTERACTIVE_RECONFIGURATION="false"
    START_LIRCMD=""
    And it doesn't looks like lirc is running at all.
    Code:
    dmesg | grep lirc
    gives nothing.

    Everything seems like it's in order?
    Last edited by kacheng; April 27th, 2008 at 12:48 PM.

  7. #7
    Join Date
    Oct 2005
    Location
    Milano, Italy
    Beans
    871
    Distro
    Ubuntu Jaunty Jackalope (testing)

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    What is the output of:
    Code:
    ls -al /dev/lirc*
    ------------------------------------------------
    yep ”short and long URL„
    http://yep.it/
    ------------------------------------------------

  8. #8
    Join Date
    Dec 2005
    Beans
    113

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    I get:

    Code:
    $ ls -al /dev/lirc*
    srw-rw-rw- 1 root root 0 2008-04-27 04:50 /dev/lircd

  9. #9
    Join Date
    Oct 2005
    Location
    Milano, Italy
    Beans
    871
    Distro
    Ubuntu Jaunty Jackalope (testing)

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    So, as I wrote above the REMOTE_DEVICE is changed; replace the entry in hardware.conf:
    Code:
    REMOTE_DEVICE="/dev/lirc0"
    into
    Code:
    REMOTE_DEVICE="/dev/lirc/0"
    Then reload lirc
    Code:
    sudo /etc/init.d/lirc restart
    Is the output ok?
    ------------------------------------------------
    yep ”short and long URL„
    http://yep.it/
    ------------------------------------------------

  10. #10
    Join Date
    Dec 2005
    Beans
    113

    Re: lirc does not seem to be loading in hardy (upgrade from gutsy)

    Hmm,

    I made the change, and tried:

    REMOTE_DEVICE="/dev/lirc/0"
    REMOTE_DEVICE="/dev/lirc0"
    REMOTE_DEVICE="/dev/lircd"
    REMOTE_DEVICE="/dev/lircd/0"

    but there is no change in output of
    Code:
    $sudo /etc/init.d/lirc restart
     * Stopping remote control mouse daemon: LIRCMD                          [fail]
     * Stopping remote control daemon(s): LIRC                               [fail]
     * Loading LIRC modules                                                  [ OK ]
     * Unable to load LIRC kernel modules. Verify your
     * selected kernel modules in /etc/lirc/hardware.conf
    $ dmesg | grep lirc
    <no output>
    Anything else I should check?

Page 1 of 4 123 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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