Hi again...

        I played again with IrComm between my two computers. Thanks to
the info from Dag, I made it much more simpler (modules are loaded
automatically) and solve all the troubles. It seems that I managed to
find in every pitfall there was to be found, so I feel a bit
unlucky...
        By the way, I use IrDA 2.2.13-irda4.

        One big lesson is that irdaping is evil. All my troubles were
in fact due to the fact that I had an instance of irdaping running in
another terminal. So, don't run irdaping when you want to connect.
        I got also bitten by the ircomm-tty versus ircomm_tty, and I
had the wrong in my /etc/modules.conf.
        As opposed to what I was saying before, the order in which you
start the server and the client doesn't matter. If you start kermit
before, it will just wait after "set line" until you bring up the
other side.

        Ok, let's go :

Common :
------
        Both computer, compile kernel with IrDA -> patch-2.2.13-irda4
        (kernel must be configured with kernel module autoloader)
        Compile & install modules
        Install irda-utils-0.9.5
        > mknod /dev/ircomm0 c 161 0
        > mknod /dev/ircomm1 c 161 1
        > chmod 666 /dev/ircomm*
        edit /etc/irda/* (not really needed here)
        edit /etc/conf.modules and add the following :
---------------------------------
# IrDA stuff...
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty         # if you want IrCOMM support
# These values are hard-coded in irattach (not instance order)
alias irda-dongle-0 tekram              # Tekram IrMate IR-210B
alias irda-dongle-1 esi                 # ESI JetEye
alias irda-dongle-2 actisys             # Actisys IR-220L
alias irda-dongle-3 actisys             # Actisys IR-220L+
alias irda-dongle-4 girbil              # Greenwich GIrBIL
alias irda-dongle-5 litelink            # Parallax LiteLink
alias irda-dongle-6 airport             # Adaptec Airport 1000 and 2000
---------------------------------
        This will get you both ircomm-tty/ircomm autoloading (when the
app touch /dev/ircomm0) and dongle autoloading (when you do irattach).

Server side :
-----------
        > irattach /dev/ttyS0 -d esi            # I have a ESI dongle
        > getty ircomm0 DT19200 vt100           # Red-Hat syntax
or :    > getty -L ircomm0 19200 vt100          # Debian syntax
        At this point, your text terminal should get reset and you
come back to a login prompt. That's normal. I don't know what happen
in X.


Client side :
-----------
        > irattach /dev/ttyS1 -s 1              # OB5500 integrated Ir port
        > kermit
        > > set line /dev/ircomm0
        > > set speed 19200
        > > connect
        Hop ! The prompt appear !
        > > > stty sane                         # Get backspace to work ok

        Ignore the following message :
        "Warning: no access to tty (Inappropriate ioctl for device).
        Thus, no job control enabled"
        And :
        "Can't open terminal /dev/tty"

Minicom :
-------
        Minicom is a bit more problematic, and I'm still fighting with
it. I still don't understand how to connect. I managed to make it work
like this :
        o start minicom
        o Configure (^A O)
        o sub-menu serial
        o set to /dev/ircomm0
        o set speed to 19200
        o exit
        o sub-menu "save as dft"
        o exit
        o Exit (^A X)
        o restart minicom

        Ciao...

        Jean

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

Reply via email to