Hi everybody...

        I managed to connect my two computers using IrComm. The latest
patch Linux-2.2.13-irda4 seems to behave better, I also admit that I
probably do things better.
        One thing that I have learned : if you start the client
(kermit) before the server (getty), the stack on the server goes into
funny mode and won't accept connections. Also, ircomm and ircomm-tty
need to be insmod by hand and are not loaded automatically. I use
kermit because minicom seems to not collaborate with getty.
        By the way, thanks Dag for your comments, but I managed it
without you anyway ;-)

        For those curious, here is what I do :

Common :
------
        Both computer, compile kernel with IrDA -> patch-2.2.13-irda4
        Compile & install modules
        Install irda-utils-0.9.5
        edit /etc/conf.modules and /etc/irda/*
        > mknod /dev/ircomm0 c 161 0
        > chmod 666 /dev/ircomm0

Server side :
-----------
        > insmod irda
        > insmod esi                            # that's the one I got
        > irattach /dev/ttyS0 -d esi
        > insmod ircomm
        > insmod ircomm-tty
        > getty ircomm0 DT19200 vt100           # Red-Hat syntax
        At this point, your text terminal should get reset and you
come back to a login prompt. I don't know what happen in X.
        For Debian, you would do :
        > getty -L ircomm0 9600 vt100           # Debian syntax

Client side :
-----------
        Don't start kermit before getty is running !
        > insmod irda
        > irattach /dev/ttyS1 -s 1              # OB5500 integrated Ir port
        > insmod ircomm
        > insmod ircomm-tty
        > kermit
        > > set line /dev/ircomm0
        > > set speed 19200
        > > connect
        Hop ! The prompt appear !


        All is not perfect though. I've got some character lost or
maybe the terminal is not properly configured.
        I also get the messages :
        "Warning: no access to tty (Inappropriate ioctl for device).
        Thus, no job control enabled"
        And :
        "Can't open terminal /dev/tty"

        One might wonder what is the practical purpose of the
exercise. As irdaping doesn't work for me, it's a nice way to verify
that the IrDA stack work and everything is in place. As you can see,
things are not really "plug and play", so being able to check onself
is essential ;-)

        Have fun...

        Jean

_______________________________________________
Linux-IrDA mailing list  -  [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda

Reply via email to