'dillo wrote (Fri, 20 Oct 2000 06:56:09 -0700):
> It would help if you could tell us what kind of laptop you have.
It's a Dell Latitude CP, but I also have an ActiSys 220L on order.
Kernel info:
Linux ubik 2.2.5-22 #1 Wed Jun 2 09:02:27 EDT 1999 i586 unknown
Linux version 2.2.5-22 ([EMAIL PROTECTED]) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Wed Jun 2
09:02:27 EDT 1999
COM ports:
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ
enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 16550A
> Which port are you telling minicom to use?
> If it's /dev/ttyS0, that's your problem right there. You need to use the
> pseudo device /dev/ircomm0. That way minicom will register itself properly
> as an IrCOMM service for the Palm to connect to.
> By setting your PILOTPORT to /dev/ircomm0 you should be able to HotSync as
> well. I've been doing it like this for over a year now.
Well, this is strange. My devices are as follows:
[matt@ubik matt]$ ls -al /dev/ir*
crw-rw---- 1 root matt 161, 0 Oct 17 00:36 /dev/ircomm0
crw-rw-rw- 1 root root 161, 1 Oct 17 00:36 /dev/ircomm1
crw-rw-rw- 1 root root 161, 0 Oct 17 00:08 /dev/irnine
irnine came from other mails I've seen in the group. If I do this:
[root@ubik /root]$ irmanager -d 1
IrDA device irda0 registered.
[root@ubik /root]$ cat /var/log/messages
...
Oct 22 16:12:44 ubik irmanager: executing: '/sbin/modprobe irda'
Oct 22 16:12:44 ubik irmanager: executing: 'echo 1 >
/proc/sys/net/irda/discovery'
Oct 22 16:12:44 ubik kernel: Linux-2.2 Support for the IrDA (tm)
Protocols (Dag Brattli)
Oct 22 16:12:44 ubik irmanager: executing: 'echo ubik
> /proc/sys/net/irda/devname'
Oct 22 16:12:45 ubik irmanager: executing: './drivers start 0'
Oct 22 16:12:45 ubik irmanager: + 0.1 Fri Jul 25 11:45:26 1997 Dag
Brattli
Oct 22 16:12:45 ubik irmanager: + 0.1 Fri Jul 25 11:45:26 1997 Dag
Brattli
Oct 22 16:12:45 ubik irattach: Serial connection established.
Oct 22 16:12:45 ubik kernel: IrDA device irda0 registered.
(NB. formatting changes are mine) and put the Palm m100 (== Palm III)
in front of the IrDA port, I get "Waiting for sender" on the Palm and
the following:
[root@ubik /root]# cat /proc/net/irda/discovery
IrLMP: Discovery log:
Link saddr=0x00012bbe
name: MattNewsome, hint: PDA/Palmtop IrOBEX , daddr: 0x19590e05
I can now ping the device, too:
[root@ubik /root]# /usr/sbin/irdaping 0x19590e05
IrDA ping (0x19590e05): 32 bytes
32 bytes from 0x19590e05: irda_seq=0 time=100.00 ms.
32 bytes from 0x19590e05: irda_seq=2 time=100.05 ms.
32 bytes from 0x19590e05: irda_seq=3 time=100.05 ms.
32 bytes from 0x19590e05: irda_seq=5 time=100.05 ms.
32 bytes from 0x19590e05: irda_seq=6 time=100.05 ms.
32 bytes from 0x19590e05: irda_seq=8 time=100.05 ms.
9 packets received by filter
I now put the device into HotSync mode and note the following in
/var/log/messages:
Oct 22 16:24:47 ubik irmanager: executing: '/sbin/modprobe
ircomm_tty'
Oct 22 16:24:47 ubik kernel: IrCOMM_common, $Revision: 1.13 $ $Date:
1998/10/13 12:59:05 $ (Takahide Higuchi)
Oct 22 16:24:47 ubik kernel: IrVTD, $Revision: 1.2 $ $Date:
1998/09/27 08:37:04 $ (Takahide Higuchi)
Oct 22 16:24:51 ubik irmanager: executing: '/sbin/modprobe
ircomm_tty'
Oct 22 16:25:22 ubik last message repeated 11 times
Oct 22 16:26:24 ubik last message repeated 13 times
Oct 22 16:27:33 ubik last message repeated 20 times
(Think the last few comments are re. the next bit). Now I set the
Pilot to HotSync over IR using IrComm:
(proc/net/irda/discovery):
IrLMP: Discovery log:
Link saddr=0x00012bbe
name: IrCOMM, hint: PDA/Palmtop IrCOMM , daddr: 0x19590e05
(/var/log/messages):
IrCOMM_common, $Revision: 1.13 $ $Date: 1998/10/13 12:59:05 $
(Takahide Higuchi)
IrVTD, $Revision: 1.2 $ $Date: 1998/09/27 08:37:04 $ (Takahide
Higuchi)
a double check with a ping checks out:
IrDA ping (0x19590e05): 32 bytes
32 bytes from 0x19590e05: irda_seq=1 time=110.05 ms.
32 bytes from 0x19590e05: irda_seq=2 time=110.03 ms.
32 bytes from 0x19590e05: irda_seq=3 time=110.05 ms.
6 packets received by filter
tell pilot-xfer where to point:
export PILOTPORT=/dev/ircomm0
export PILOTRATE=9600
and finally set it in motion:
pilot-xfer -b temp/
and now I get:
Unable to bind to port '/dev/ircomm0'.
(Please see 'man pilot-xfer' or 'pilot-xfer --help' for information
on setting the port).
Same problem with cu:
[root@ubik /root]# cu -s 9600 -l ircomm0
cu: open (/dev/ircomm0): Permission denied
cu: ircomm0: Line in use
Is the problem here obvious to someone?
Thanks,
--
Matt Newsome
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
