Lirc doesn't work (Pinnacle)

dienadel · 2006-10-03 17:15:06

Hello,

I can't put to work the remote control.

I follow the instructions on the wiki.

1- Installed lirc
As i use the normal arch-kernel, i:
2- setserial /dev/ttyS0 uart none
3- modprobe lirc_serial

Perfect, no problem

I try "irrecord -d /dev/lirc0 /tmp/my_remote" without response.

I copy from /usr/share the appropiate lircd.conf y /etc, start lircd, execute irw, and nothing happens.

All the above operations are done as root.

It's like the cable were unplugged, or the remote broken, so, i installed a win, and tested it, and yes, all is ok, the port is the COM1 (ttyS0), and works ok.

When lirc was lirc-pctv the remote was fine, but a year ago changed it, and all gone bad. Now, i'm trying again to start it.

I don't know what thing can be bad, as no error messages appears.

What can i do?

Thanks!!

dienadel

mouse256 · 2006-10-04 08:14:00

hmm, I think I made a misstake in the wiki, I think you'll need to start the lirc deamon before irrecord:

/etc/rc.d/lircd start

does that help?

dienadel · 2006-10-04 10:07:47

Hello,

I'm at work, so i can't test it. But, i think, it won't solve it. The irrecord command is to create a lircd.conf, and when you start the daemon it looks for it.

I remenber, that when i used LFS, i created a lircd.conf file using the irrecord tool, and it detected it. I used the file created by me, althought the lircd.conf.pctv worked too.

I'll try it soon.

thanks

mouse256 · 2006-10-04 10:31:15

you might be right, so let's start comparing then
As you do have a working lircd.conf, you doesn't need to use irrecord, just skip that step and put the working file in /etc/lircd.conf

[12:26][tom@mouse256:~]$ lsmod | grep lirc
lirc_serial            11776  1
lirc_dev               12916  1 lirc_serial

[12:27][tom@mouse256:~]$ tail /var/log/lircd
Oct  3 19:01:47 mouse256 lircd: accepted new client on /dev/lircd
Oct  3 19:01:50 mouse256 lircd: removed client
Oct  3 23:55:01 mouse256 lircd: removed client
Oct  3 23:55:18 mouse256 lircd: caught signal
Oct  4 09:52:24 mouse256 lircd: lircd(all) ready
Oct  4 09:54:42 mouse256 lircd: accepted new client on /dev/lircd
Oct  4 11:47:08 mouse256 lircd: removed client
Oct  4 11:47:13 mouse256 lircd: caught signal
Oct  4 11:51:50 mouse256 lircd: lircd(all) ready
Oct  4 12:24:05 mouse256 lircd: accepted new client on /dev/lircd

Do you get something different here?
What is your output when you start irw?

dienadel · 2006-10-04 11:47:36

Hello again,

Here is the output:

[root@IUS2001 iban]# setserial /dev/ttyS0 uart none
[root@IUS2001 iban]# modprobe lirc_serial
[root@IUS2001 iban]# lsmod | grep lirc
lirc_serial 11776 0
lirc_dev 12916 1 lirc_serial
[root@IUS2001 iban]# /etc/rc.d/lircd start
:: Starting LIRC Daemon [DONE]
[root@IUS2001 iban]# tail /var/log/lircd
Oct 3 18:56:39 IUS2001 lircd: accepted new client on /dev/lircd
Oct 3 18:57:06 IUS2001 lircd: removed client
Oct 3 18:57:14 IUS2001 lircd: caught signal
Oct 3 19:00:54 IUS2001 lircd: lircd(all) ready
Oct 3 19:01:22 IUS2001 lircd: accepted new client on /dev/lircd
Oct 3 19:01:29 IUS2001 lircd: removed client
Oct 3 19:01:38 IUS2001 lircd: accepted new client on /dev/lircd
Oct 3 19:01:45 IUS2001 lircd: removed client
Oct 3 19:01:58 IUS2001 lircd: caught signal
Oct 4 13:38:15 IUS2001 lircd: lircd(all) ready
[root@IUS2001 iban]# irw

I push the buttons but nothing, happens. I stop it by "Ctrl+C". The log after closing irw:

[root@IUS2001 iban]# tail /var/log/lircd
Oct 3 18:57:14 IUS2001 lircd: caught signal
Oct 3 19:00:54 IUS2001 lircd: lircd(all) ready
Oct 3 19:01:22 IUS2001 lircd: accepted new client on /dev/lircd
Oct 3 19:01:29 IUS2001 lircd: removed client
Oct 3 19:01:38 IUS2001 lircd: accepted new client on /dev/lircd
Oct 3 19:01:45 IUS2001 lircd: removed client
Oct 3 19:01:58 IUS2001 lircd: caught signal
Oct 4 13:38:15 IUS2001 lircd: lircd(all) ready
Oct 4 13:38:50 IUS2001 lircd: accepted new client on /dev/lircd
Oct 4 13:39:04 IUS2001 lircd: removed client
[root@IUS2001 iban]#

the only difference is the line "lirc_serial 11776 0". You have 1 instead 0. What's that?

:-(

mouse256 · 2006-10-04 15:05:59

hmm it seems to be normal, I think your configfile is wrong for your remote.
try this as root:

/etc/lircd stop
mode2 -d /dev/lirc0

when you now press buttons on your remote, do you see raw codes? (pulses and spaces)
If so, you have a wrong configfile. If not, well, then let's think it over again

dienadel · 2006-10-04 17:21:11

nothing... :-(

There is no output, as happens with irw, and with irrecord. Nothing at all. The same as i'd no have a remote. No software errors, no signal catched. :-(

Perhaps something related to the serial port?

I've "investigated", perhaps it helps you:

- In Win, it works, COM1=ttyS0
- dmesg output related to serial ports:

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

- Tried adding this in modprobe.conf:

alias char-major-61 lirc_serial
options lirc_serial irq=3 io=0x2f8

but trying "modprobing" the module happens this:

FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-ARCH/kernel/drivers/misc/lirc_serial.ko): Device or resource busy

and in the dmesg output:

lirc_serial: port 02f8 already in use
lirc_serial: use 'setserial /dev/ttySX uart none'
lirc_serial: or compile the serial port driver as module and
lirc_serial: make sure this module is loaded first

I'm lost. At least, could you say me things to probe, or to look at?

Thanks

dienadel · 2006-10-04 17:44:11

More information... i've changed the remote to the COM1 and added to the modprobe.conf the following lines (in the previous message the values were wrong for the ttyS0):

alias char-major-61 lirc_serial
options lirc_serial irq=3 io=0x2f8

And made this:

1- Rebooted the PC (OK)
2- setserial /dev/ttyS1 uart none (OK)
3- modprobe lirc_serial (OK, and these lines appears at the botton:)

lirc_dev: IR Remote Control driver registered, at major 61
lirc_serial: auto-detected active high receiver
lirc_dev: lirc_register_plugin: sample_rate: 0

4- irrecord -d /dev/lirc0 /tmp/my_remote (NO RESPONSE)
5- mode2 -d /dev/lirc0 (NO RESPONSE)
6- /etc/rc.d/lircd start (OK)
7- irw (NO RESPONSE)

And that's all.

Why can't i have "normal errors"???? At least, with error messages!!! Arghh!!! :-( With the nvidia driver, something similar!

Greets

mouse256 · 2006-10-05 07:39:42

for your last post: you're using ttyS1 and says your remote is connected to com1, that's wrong, ttyS1 is com2 (but your previous post you already seem to know this)
For the rest, I have no idea anymore. It's a normal serial receiver? is it a homemade one (like me) or did you buy it? did you do some special configuration in winlirc?

dienadel · 2006-10-05 09:19:27

Hello!

For the last post, i fisically changed the remote connected to the COM1 to the COM2, to discart that COM1 doesn't work in linux (¿?). So i think, that the things i explain in the last post are correct, as the remote was connected to the COM2.

I didn't knew about winlirc. I'll try it, and will comment what happens.

The remote is the normal one that came with the TV card (pinnacle), and is connected to the serial port.

Humm, perhaps, as last attemp, i'd try with another linux distribution. Perhaps Ubuntu? what do you think?

Thanks

Arch Linux

#1 2006-10-03 17:15:06

Lirc doesn't work (Pinnacle)

#2 2006-10-04 08:14:00

Re: Lirc doesn't work (Pinnacle)

#3 2006-10-04 10:07:47

Re: Lirc doesn't work (Pinnacle)

#4 2006-10-04 10:31:15

Re: Lirc doesn't work (Pinnacle)

#5 2006-10-04 11:47:36

Re: Lirc doesn't work (Pinnacle)

#6 2006-10-04 15:05:59

Re: Lirc doesn't work (Pinnacle)

#7 2006-10-04 17:21:11

Re: Lirc doesn't work (Pinnacle)

#8 2006-10-04 17:44:11

Re: Lirc doesn't work (Pinnacle)

#9 2006-10-05 07:39:42

Re: Lirc doesn't work (Pinnacle)

#10 2006-10-05 09:19:27

Re: Lirc doesn't work (Pinnacle)

Board footer