[mythtv-users] LIRC in Mythbuntu 8.04.1 (now 8.10!!!!)
Harry Devine
lifter89 at comcast.net
Tue Nov 4 22:16:38 UTC 2008
steve.goodey at bt.com wrote:
> No, the X means either 0 or 1 as required. No, I don't understand that
> bit either. You have got zero 0 not O?
>
> Also is the program setserial installed?
>
> >From http://www.lirc.org/html/install.html
>
> If you want to use a home-brew receiver, an Anir Multimedia Magic, a
> Packard Bell receiver, the IRdeo or if you want to use the SIR IrDA
> driver, I suggest that you compile the Linux kernel serial port driver
> as a module (however, you can choose not to do so if you use setserial
> properly, see below). The according kernel option that should be set to
> M is Standard/generic (dumb) serial support (resp. Standard/generic
> (8250/16550 and compatible UARTs) serial support for 2.4 kernels) in the
> Character devices section of the kernel configuration dialogue. Usually
> the serial port driver grabs all ports it auto-detects as soon as it is
> loaded and the LIRC modules won't be able to use any of them.
>
> There are two solutions for this problem. Either you load the LIRC
> module before the kernel serial port driver is loaded (that's why you
> have to compile it as a module) or you call setserial /dev/ttySx uart
> none to release the according port. setserial usually is already called
> during boot-up in some init script whose location depends on the
> distribution you use. Be aware that setserial might also be the cause of
> trouble. The reason for this is a kernel bug (known to be true for
> 2.2.20, patches are on the way). If you tell setserial to configure a
> port that is already claimed by a LIRC module, the kernel serial driver
> will steal the port from the LIRC module and LIRC will stop working. So
> check your setserial configuration to only configure available ports.
> Debian users should adjust their /etc/serial.conf.
>
> You must be getting a bit fed up with this now? But it seems you're
> almost there.
>
> Steve.
>
>
>> -----Original Message-----
>> From: Harry Devine [mailto:lifter89 at comcast.net]
>> Sent: 04 November 2008 16:00
>> To: Goodey,SJ,Steve,ASAC6N R
>> Subject: Re: [mythtv-users] LIRC in Mythbuntu 8.04.1 (now 8.10!!!!)
>>
>> steve.goodey at bt.com wrote:
>>
>>> Harry,
>>>
>>> Try looking at the following:-
>>>
>>> http://en.gentoo-wiki.com/wiki/LIRC
>>>
>>> Towards the bottom under troubleshooting it mentions your
>>>
>> dmesg error
>>
>>> and talks about "Prevent the kernel module from configuring
>>>
>> the port"
>>
>>> Steve.
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Harry Devine [mailto:lifter89 at comcast.net]
>>>> Sent: 04 November 2008 15:18
>>>> To: Goodey,SJ,Steve,ASAC6N R; Discussion about mythtv
>>>> Subject: Re: [mythtv-users] LIRC in Mythbuntu 8.04.1 (now 8.10!!!!)
>>>>
>>>> steve.goodey at bt.com wrote:
>>>>
>>>>
>>>>> No, I think you are correct that com1 is 03f8.
>>>>>
>>>>> Do you remember modifying a file hardware.conf on the
>>>>>
>>>>>
>>>> previous version
>>>>
>>>>
>>>>> of Mythbuntu when you got the remote to work?
>>>>>
>>>>> Steve
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Harry Devine [mailto:lifter89 at comcast.net]
>>>>>> Sent: 04 November 2008 13:40
>>>>>> To: Goodey,SJ,Steve,ASAC6N R
>>>>>> Cc: Discussion about mythtv
>>>>>> Subject: Re: [mythtv-users] LIRC in Mythbuntu 8.04.1
>>>>>>
>> (now 8.10!!!!)
>>
>>>>>> steve.goodey at bt.com wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> I'm pretty certain that I didn't make any typos (well, I
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> did at first
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> but corrected it). Here's what I did:
>>>>>>>> 1) setup a custom remote in MCC
>>>>>>>> 2) copied my lircd.conf for my remote to /etc/lirc and
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> made it root
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> owner and root group
>>>>>>>> 3) copied my lircrc to /home/hdevine/.lirc, renamed it to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> mythtv and
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> gave it hdevine owner and hdevine group
>>>>>>>> 4) added modprobe lirc_serial to /etc/init.d/bootmisc.sh
>>>>>>>> 5) ran the dpkg-reconfigure setserial command and chose manual
>>>>>>>> 6) modified /var/lib/setserial/autoserial.conf by adding
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> "setserial
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> /dev/ttyS0 uart none"
>>>>>>>> 7) copied the autoserial.conf to /etc/serial.conf
>>>>>>>> 8) rebooted
>>>>>>>>
>>>>>>>> Just to be clear, I originally had "/dev/tty/S0 uart none" in
>>>>>>>> autoserial.conf and that didn't work. I realized that it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> needed to
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> be /dev/ttys0 instead so I tried that and got nothing.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> Then, based
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> on the /var/log/messages error, I changed it to "setserial
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> /dev/ttys0
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> uart none" as it is now.
>>>>>>>>
>>>>>>>> Hopefully someone has some idea what I'm missing. Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> again for
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> the help!
>>>>>>>> Harry
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> Harry,
>>>>>>> How about looking in dmesg, any other info/error messages there?
>>>>>>> Something about port already in use?
>>>>>>>
>>>>>>> Steve.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> dmesg shows the following:
>>>>>>
>>>>>> [ 18.409777] lirc_dev: IR Remote Control driver
>>>>>>
>>>>>>
>>>> registered, major 61
>>>>
>>>>
>>>>>> [ 18.414347] lirc_serial: port 03f8 already in use
>>>>>> [ 18.414350] lirc_serial: use 'setserial /dev/ttySX uart none'
>>>>>> [ 18.414351] lirc_serial: or compile the serial port driver
>>>>>> as module and
>>>>>> [ 18.414353] lirc_serial: make sure this module is loaded first
>>>>>>
>>>>>> I thought that 03f8 was com1, which is where it's
>>>>>>
>> plugged into. I
>>
>>>>>> never moved it when I reinstalled the OS. Should I change
>>>>>>
>>>>>>
>>>> /dev/ttyS0
>>>>
>>>>
>>>>>> to ttyS1?
>>>>>>
>>>>>> Thanks,
>>>>>> Harry
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> Nope, never had to touch that file. I see that it exists in
>>>> /etc/lirc, but based on its contents, I don't think I have
>>>>
>> to touch
>>
>>>> it. It doesn't mention anything in there about ports, etc.
>>>>
>>>> Haryr
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>> I added "/dev/ttyS0 uart none" to it, but I can't test it
>> until I get home. Should it be /dev/ttySX as it says? Also,
>> I don't understand the line in that link that says: "After
>> that you have to enable serial init-script via rc-update add
>> serial default". I have NO idea what they're talking about
>> there! Do you?
>>
>> Thanks again for all of the help!
>> Harry
>>
>>
>>
>
>
OK, here's what I get now:
/var/log/messages:
Nov 4 17:03:06 hdevine-desktop kernel: [ 17.357543] lirc_dev: IR
Remote Contr
ol driver registered, major 61
Nov 4 17:03:06 hdevine-desktop kernel: [ 17.860037] lirc_serial:
auto-detecte
d active low receiver
Nov 4 17:03:06 hdevine-desktop kernel: [ 17.860040] lirc_dev:
lirc_register_p
lugin: sample_rate: 0
dmesg:
[ 17.357543] lirc_dev: IR Remote Control driver registered, major 61
[ 17.860037] lirc_serial: auto-detected active low receiver
[ 17.860040] lirc_dev: lirc_register_plugin: sample_rate: 0
Based on those messages, one would think it's working. However, I still
get nothing. Is there somewhere else I should be looking? In looking
at my frontend log, I get the following:
2008-11-04 17:03:26.756 JoystickMenuClient Error: Joystick disabled -
Failed to
read /home/hdevine/.mythtv/joystickmenurc
mythtv: could not connect to socket
mythtv: No such file or directory
2008-11-04 17:03:26.756 lirc_init failed for mythtv, see preceding messages
I have verified that /home/hdevine/.lirc/mythtv exists and has the
proper ownership and permissions.
Any ideas?
Harry
More information about the mythtv-users
mailing list