From: <cil...@co...> - 2005-10-27 05:32:13
|
(Not sure whether this is a problem with pilot-link or irda ...) Trying to sync a PDA (Palm m100) to a laptop (Dell i8000) using irda. It almost works -- irda appears to work most of the time, but I can't connect. I'm running SuSE 9.0 with the default 2.4.21 kernel. After: modprobe irtty irattach -s the result of irddadump is: 23:34:26.453160 xid:rsp 8b5e3836 < 0828053f S=6 s=5 Palm III hint=8220 [ PDA/Palmtop IrOBEX ] (25) 23:34:26.463181 xid:cmd 8b5e3836 > ffffffff S=6 s=* Octini hint=0400 [ Computer ] (22) and if I also do modprobe ircomm-tty I get 15:00:51.775990 xid:cmd ffffffff < 170ed749 S=6 s=* IrCOMM hint=8204 [ PDA/Palmtop IrCOMM ] (23) However, all efforts to use e.g. pilot-xfer -l fail silently. Trying to sync while running irdadump yields: 15:00:51.825996 snrm:cmd ca=fe pf=1 f6445ca0 < 170ed749 new-ca=92 (32) 15:00:51.826028 ua:rsp ca=92 pf=1 f6445ca0 > 170ed749 (31) 15:00:52.406054 rr:cmd < ca=92 pf=1 nr=0 (2) 15:00:52.406075 rr:rsp > ca=92 pf=1 nr=0 (2) 15:00:52.426052 i:cmd < ca=92 pf=1 nr=0 ns=0 LM slsap=01 dlsap=00 CONN_CMD (6) 15:00:52.426084 i:rsp > ca=92 pf=1 nr=1 ns=0 LM slsap=00 dlsap=01 CONN_RSP (6) 15:00:52.446058 i:cmd < ca=92 pf=1 nr=1 ns=1 LM slsap=01 dlsap=00 GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "IrDA:TinyTP:LsapSel" (37) 15:00:52.446076 i:rsp > ca=92 pf=1 nr=2 ns=1 LM slsap=00 dlsap=01 GET_VALUE_BY_CLASS: No such class (11) 15:00:52.466056 disc:cmd < ca=0x92 pf=1 (2) 15:00:52.466064 ua:rsp ca=92 pf=1 f6445ca0 > 170ed749 (10) 15:00:52.466114 ua:rsp ca=92 pf=1 f6445ca0 > 170ed749 (0) So far as I can tell, none of this is affected by playing with the settings in /proc/sys/net/irda. After getting this far, I realized that my BIOS was set to "Fast IR", so I changed it to "Slow IR" and rebooted. Much worse -- irdadump now runs very slowly, and fails to detect the PDA. Worse yet, when I reset it to "Fast IR" and rebooted, the latter behavior persisted, and I can no longer detect the PDA at all... I am running an old BIOS (A10), which I have been reluctant to tinker with. I'm also using the SuSE 9.0 default RPMs, which are irda-0.9.13 and pilot-link-0.11.8. My logs yield: ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A ttyS03 at port 0x02e8 (irq = 3) is a 16550A with the last one being the (unused) modem on my PCMCIA network card. Only thing I can think of other than trying more recent software is that I'm missing a parameter setting somewhere. Should I be concerned about the irqs? Most of what I've found online addresses problems getting irda to discover my PDA, which seems to be working (or at least it used to work), so I'm not sure what to try next. Thanks for any suggestions. |