LinHES Forums :: View topic - IR-Blaster .... Solved !

ledxmit_dev: IR Remote Control driver registered, at major 72
ledxmit_serial: auto-detected active high receiver
ledxmit_dev: ledxmit_register_plugin:sample_rate: 0

line 308 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
line 309 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
.
.
.
line 370 ttyS1: LSR safety check engaged!
line 371 ttyS1: LSR safety check engaged!
.
.
.
line 378 ledxmit_dev: IR Remote Control driver registered, at major 72
line 379 ledxmit_serial: port 02f8 already in use
line 380 ledxmit_serial: use 'setserial /dev/ttySX uart none'
line 381 ledxmit_serial: or compile the serial port driver as module and
line 382 ledxmit_serial: make sure this module is loaded first.
.
.
.
line 389 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

line 309 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
line 379 ledxmit_serial: port 02f8 already in use

ttyS1: LSR safety check engaged!
ledxmit_dev: IR Remote Control driver registered, at major 72
BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/3376
caller is init_port+0xaf/0x2a0 [ledxmit_serial]
[<c02a6d4c>] debug_smp_processor_id+0x8c/0xa0
[<e232ea3f>] init_port+0xaf/0x2a0 [ledxmit_serial]
[<e232f3a6>] init_module+0x46/0xb0 [ledxmit_serial]
[<c0136de4>] sys_init_module+0x154/0x210
[<c0102e29>] syscall_call+0x7/0xb
ledxmit_serial: auto-detected active low receiver
ledxmit_dev: ledxmit_register_plugin: sample_rate: 0
lirc_dev: IR Remote Control driver registered, at major 61
cx2388x v4l2 driver version 0.0.5 loaded
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
.
.
.
ivtv0: i2c attach to card #0 ok [client=Hauppauge IR, addr=18]
lirc_dev: lirc_register_plugin: sample_rate: 10
input: PC Speaker
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

I/O configuration device:
Serial Port A Enabled
Base I/O Address 3F8
Interrupt IRQ4

CPU Type AMD Athlon XP 3200+
CPU Speed 220 MHz/400 MHz
Cache RAM 512 kB

# start up custom LIRC to handle IR LED transmission
#
/bin/setserial /dev/ttyS1 uart none # use this for COM2
# /bin/setserial /dev/ttyS0 uart none # use this for COM1
/sbin/modprobe ledxmit_serial
if [ -x /usr/local/lirc-ledxmit/sbin/ledxmit-ledxmitd ]
then
/usr/local/lirc-ledxmit/sbin/ledxmit-ledxmitd
fi
#

Author:	gsal [ Sun Mar 12, 2006 6:45 am ]
Post subject:	IR-Blaster .... Solved !
Hello everyone: I know, I know, the IR-blaster topic has appeared a few times and I did search and found the very good instructions at http://losdos.dyndns.org:8080/public/mythtv-info/MythTV_DISH_IR_LED_TX_via_Modified_LIRC.html But after following such instructions, unfortunately, ledxmit does not seem to be loading. In the instructions, right before starting the section for STAGE 3, there are three lines that should appear in dmesg, they look like this: Code: ledxmit_dev: IR Remote Control driver registered, at major 72 ledxmit_serial: auto-detected active high receiver ledxmit_dev: ledxmit_register_plugin:sample_rate: 0 in my case, I am getting the following relevant lines out of dmesg: Code: line 308 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled line 309 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A . . . line 370 ttyS1: LSR safety check engaged! line 371 ttyS1: LSR safety check engaged! . . . line 378 ledxmit_dev: IR Remote Control driver registered, at major 72 line 379 ledxmit_serial: port 02f8 already in use line 380 ledxmit_serial: use 'setserial /dev/ttySX uart none' line 381 ledxmit_serial: or compile the serial port driver as module and line 382 ledxmit_serial: make sure this module is loaded first. . . . line 389 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A These are my conditions: AMD Athlon Working KnoppMyth R5V30 Hauppage 250 with remote control and working fine to control MythTV. On following the instructions the first time around, I couldn't pass either the disabling of the serial driver or the installation of the new one. So, instead of using LIRC 0.7.2, I went ahead and downloaded the latest one (LIRC 0.8)...got pass that. By the way, since my machine only has one COM port on the back, I am trying to use COM1 (ttyS0). Then again, in dmesg output there are a couple of lines about ttyS1...what is that about?. Does anybody have any idea what might be happening? Do the various lines from dmesg tell anything? Any help will be greatly appreciated...I am SOOO close!!!! Germán

Author:	mac [ Sun Mar 12, 2006 9:29 am ]
Post subject:
Code: line 309 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A line 379 ledxmit_serial: port 02f8 already in use kinda strange that kernel finds S0 at 03f8 and ledxmit_serial finds S0 at 02f8. try configuring it for S1.. how is the serial port configured in the bios?

Author:	gsal [ Sun Mar 12, 2006 10:34 am ]
Post subject:
First of all, thanks for the quick reply. I will try what you suggest...I just don't know what to do first...maybe what's easier? I guess I should try configuring for S1, first. Trying to see the bios is going to be a little difficult from the point (of ignorance) that I stand. Presently I have TV-out only, no monitor at the computer and work remotely via an x-server/client (cygwin on my laptop). O.k., maybe is not difficult, all I need to do is take the TV-out out of the whatever file is in and bring a monitor in...unless there is a trick to see the bios after booting? You know, from an xterm? I will post again with results.

Author:	afrosheen [ Sun Mar 12, 2006 12:34 pm ]
Post subject:
I think I found your problem. Quote: line 379 ledxmit_serial: port 02f8 already in use line 380 ledxmit_serial: use 'setserial /dev/ttySX uart none' line 381 ledxmit_serial: or compile the serial port driver as module and line 382 ledxmit_serial: make sure this module is loaded first. So...try putting the setserial /dev/ttyS0 uart none command where it belongs. You may have missed a step from that wiki page.

Author:	gsal [ Sun Mar 12, 2006 3:58 pm ]
Post subject:
Well, not working yet. Here is what I have done. First, I found an entry in /etc/X11/XF86Config-4 that has something to do with a serial mouse, so I commented that out, just in case. Made no difference. Then, I went ahead and configured the IR-blaster to use COM2. Configuration passed the tests indicated in the instructions and the lines from dmesg turned out like this: Code: ttyS1: LSR safety check engaged! ledxmit_dev: IR Remote Control driver registered, at major 72 BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/3376 caller is init_port+0xaf/0x2a0 [ledxmit_serial] [<c02a6d4c>] debug_smp_processor_id+0x8c/0xa0 [<e232ea3f>] init_port+0xaf/0x2a0 [ledxmit_serial] [<e232f3a6>] init_module+0x46/0xb0 [ledxmit_serial] [<c0136de4>] sys_init_module+0x154/0x210 [<c0102e29>] syscall_call+0x7/0xb ledxmit_serial: auto-detected active low receiver ledxmit_dev: ledxmit_register_plugin: sample_rate: 0 lirc_dev: IR Remote Control driver registered, at major 61 cx2388x v4l2 driver version 0.0.5 loaded lirc_i2c: chip found @ 0x18 (Hauppauge IR) . . . ivtv0: i2c attach to card #0 ok [client=Hauppauge IR, addr=18] lirc_dev: lirc_register_plugin: sample_rate: 10 input: PC Speaker ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Yet, nothing works, anyway. Then, I realized that at boot time, the resolution on my TV is pretty decent and I don't need to bring a monitor to the PC, I can just use the TV itself...so, I went ahead and took a look at the BIOS, I found this: Code: I/O configuration device: Serial Port A Enabled Base I/O Address 3F8 Interrupt IRQ4 CPU Type AMD Athlon XP 3200+ CPU Speed 220 MHz/400 MHz Cache RAM 512 kB So, in effect, the one serial port in my machine is in 3F8, yet, as you can see, the lines from the original dmesg indicate that ledxmit is trying to get com1 at 2f8! And just answer to afrosheen, let me say that I have added Code: # start up custom LIRC to handle IR LED transmission # /bin/setserial /dev/ttyS1 uart none # use this for COM2 # /bin/setserial /dev/ttyS0 uart none # use this for COM1 /sbin/modprobe ledxmit_serial if [ -x /usr/local/lirc-ledxmit/sbin/ledxmit-ledxmitd ] then /usr/local/lirc-ledxmit/sbin/ledxmit-ledxmitd fi # at the bottom of /etc/init.d/bootmisc.sh, as indicated in the instructions. One thing just ocurred to me...I am going to go back and modify the original myth-ledxmit.sh and specify com1 right there...maybe that thing about configuring com2 as default and later on actually requesting com1 is not cutting it for me. Other than that, anymore ideas? Germán

LinHES Forums http://forum.linhes.org/

IR-Blaster .... Solved ! http://forum.linhes.org/viewtopic.php?f=2&t=8935	Page 1 of 1

Author:	gsal [ Sun Mar 12, 2006 10:07 pm ]
Post subject:	IR-Blaster...Solved
O.k....it's working. Like I said, I went back to the instructions at http://losdos.dyndns.org:8080/public/my ... _LIRC.html but instead of using the the script myth-ledxmit.sh "as-is", I modified it to use COM1 right from the start. What happened is that the instructions lead me to believe that using the script myth-ledxmit.sh "as-is" is o.k., even though it sets up COM2 as the default port for the IR-blaster; and that later on, one can choose COM1 by explicitely requesting in bootmisc.sh...Well, that did not quite work for me. There you have it and thanks everybody for their pointers. Germán

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/