Re: lirc_serial / mode2 reports nothing.

[MattSpam B. <spa...@gm...>]

Ah, I figured it out. The IguanaWorks transceiver works perfectly, it was
the internal cable from the serial port headers to the back of my PC that
was fubar'd. All is well now.

Matt


On 1/8/06, MattSpam Bockol <spa...@gm...> wrote:
>
> Hi Folks,
>
> I bought the serial IR transciever pre-assembled from iguanaworks (pretty
> cool) but I haven't been able to make it work yet. If anyone can make hea=
ds
> or tails of what I'm doing wrong I'd appreciate a hand. Here's what I've =
got
> so far:
>
> I'm running a self-compiled 2.6.15 kernel under debian sarge (3.1)
>
> Serial drivers are built as modules:
>
>         from the .config:
>         CONFIG_SERIO_SERPORT=3Dm
>         CONFIG_SERIO_RAW=3Dm
>         CONFIG_SERIAL_8250=3Dm
>         CONFIG_SERIAL_CORE=3Dm
>
> My PC has two serial ports with the following io/irqs
>         serial 1 io=3D0x3f8 irq=3D4
>         serial 2 io=3D0x2f8 irq=3D3
>
> I built lirc-0.8.0pre3 (0.7.2 has issues with the 2.6.15) with the
> following:
>
> ./configure     --prefix=3D/usr/local/
>                 --with-driver=3Dserial
>                 --with-kerneldir=3D/usr/src/linux-2.6.15
>                 --with-transmitter
>                 --with-port=3D0x3f8
>                 --with-irq=3D4
>                 --with-x
>
> I removed /dev/lirc* so that the make install can create them itself.
>
> make / make install proceed without incident.
>
> I restart the system.
>
> lsmod shows no modules installed.
>
> I load the lirc_serial module with
>
>         modprobe lirc_serial type=3D0 irq=3D4 io=3D0x3f8
>         (I've tried adding sense=3D1 / sense=3D0 / debug too)
>
> dmesg reports:
>
>         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
>
> Running lirc/bin/mode2 and hitting it with several remotes (an inch away
> from the detector) reports nothing.
>
> Rebooting, then loading the modules on the other serial port:
>
>         modprobe lirc_serial type=3D0 irq=3D3 io=3D0x2f8
>
> dmesg reports:
>
>         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
>
> Running lirc/bin/mode2 again reports nothing.
>
>
>
> I've tried adding the serial modules first (didn't think I should need
> them at all, but ... ), and used
> setseral to set the uart to none, then loading lirc_serial:
>
>         modprobe  8250
>         setserial /dev/ttyS0 uart none
>         setserial /dev/ttyS1 uart none
>         lirc_serial type=3D0 irq=3D4 io=3D0x3f8
>
>         dmesg reports:
>         Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
> disabled
>         serial8250: ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A
>         serial8250: ttyS1 at I/O 0x2f8 (irq =3D 3) is a 16550A
>         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
>
>         mode2 reports nothing
>
>         tried the same steps, but with lirc_serial on irq=3D3 io=3D0x2f8,
> still nothing.
>
>
> Last ditch effort, I dug out my old external serial modem (US Robotics
> 28.8) and plugged it into the box.
> Minicom worked (Hayes command set still burned into my brain from calling
> BBSes in the 80s) and I confirmed
> which serial port was ttyS0 (0x3f8 irq4) and which was ttyS1 (0x2f8 irq3)=
.
>
> See any obvious misteps? I tried it with Winlirc as well (thought a littl=
e
> less rigorously) and still didn't
> get any response (but the app seemed kinda flakey).
>
> I've been fairly careful handling the adapter, grounding myself, only
> holding it by the edges, not touching any of the mounted components
> except for the dsub9. Any ideas?
>
> I apprecaite any help you can provide.
>
> Thanks,
> Matt
>
>