At last! Thanks to Mitch DSouza, Garst R. Reese, the HOWTO of Matt Newsome, http://www4.pasta.cs.uit.no/pipermail/linux-irda/2000-October/001857.html and the Thinkpad Linux howto of Zit Seng, http://www.cir.nus.edu.sg/~lzs/linux_t20.html, I now have IRDA and syncing to palm working on my Thinkpad T20, RedHat 7.0, kernel 2.2.16-22. For others' benefit a brief summary of the breakthrough. The crucial point is, quoting Seng: " The stock Linux Mandrake kernel has the IrDA configuration part figured out right, but you need serial support compiled as a module. The reason is that you need to load the IrDA module before the serial module in order for the IrDA module to manage the IrDA device. If serial is compiled into the kernel, then the kernel will grab control of the IrDA device and the real IrDA module (nsc-ircc) will fail to load." This is true also with RedHat 7.0. It means you need to recompile the kernel (unless someone out there knows an easier work around). In short SERIAL MUST BE HANDLED AS A MODULE and unloaded before IRDA modules are loaded. Then you can in your rc.d/rc.local /sbin/rmmod serial /sbin/modprobe ircomm-tty /usr/sbin/irattach /dev/ttyS1 ** irmanager is not needed. ** you don't have to explicitly start discovery except for testing. This is sufficient to set up modules correctly. Part of my problem was the lack of documentation of irdadump etc. I could get some packets before I fixed this problem. They looked like 00:55:06.398827 xid:cmd ff227c55 > ffffffff S=6 s=1 (14) 00:55:11.398827 xid:cmd ff227c55 > ffffffff S=6 s=1 (14) 00:55:16.398829 xid:cmd ff227c55 > ffffffff S=6 s=1 (14) One line repeating every few seconds after starting discovery with echo 1 /proc/sys/net/irda/discovery and like 00:55:24.048835 xid:cmd ffffffff < f25c525b S=6 s=0 (14) 00:55:24.138831 xid:cmd ffffffff < f25c525b S=6 s=1 (14) 00:55:24.228832 xid:cmd ffffffff < f25c525b S=6 s=2 (14) 00:55:24.318831 xid:cmd ffffffff < f25c525b S=6 s=3 (14) 00:55:24.408833 xid:cmd ffffffff < f25c525b S=6 s=4 (14) 00:55:24.498831 xid:cmd ffffffff < f25c525b S=6 s=5 (14) 00:55:24.598832 xid:cmd ffffffff < f25c525b S=6 s=* IrCOMM hint=8204 [ PDA/Palmtop IrCOMM ] (23) when I hit the sync button on Palm. These seem to show that the interface is working but actually it is NOT. Discovery by the laptop ought to look like 01:06:17.006298 xid:cmd f8cf64a9 > ffffffff S=6 s=3 (14) 01:06:17.096286 xid:cmd f8cf64a9 > ffffffff S=6 s=4 (14) 01:06:17.186288 xid:cmd f8cf64a9 > ffffffff S=6 s=5 (14) 01:06:17.276285 xid:cmd f8cf64a9 > ffffffff S=6 s=* localhost hint=0400 [ Computer ] (25) 01:06:19.736303 xid:cmd f8cf64a9 > ffffffff S=6 s=0 (14) 01:06:19.826292 xid:cmd f8cf64a9 > ffffffff S=6 s=1 (14) 01:06:19.916286 xid:cmd f8cf64a9 > ffffffff S=6 s=2 (14) 01:06:19.996282 xid:rsp f8cf64a9 < 7b7c343d S=6 s=2 hutch hint=8220 [ PDA/Palmtop IrOBEX ] (22) 01:06:20.006299 xid:cmd f8cf64a9 > ffffffff S=6 s=3 (14) 01:06:20.096288 xid:cmd f8cf64a9 > ffffffff S=6 s=4 (14) 01:06:20.186289 xid:cmd f8cf64a9 > ffffffff S=6 s=5 (14) 01:06:20.276286 xid:cmd f8cf64a9 > ffffffff S=6 s=* localhost hint=0400 [ Computer ] (25) 01:06:22.736299 xid:cmd f8cf64a9 > ffffffff S=6 s=0 (14) etc ... Even before hitting anything on the Palm. If it does not then you are not really able to send out packets it seems. Then the command pilot-xfer /dev/ircomm0 -l will list the modules in your pilot if it is working. By the way, of course you need the utils and pilot link software. I am using irda-utils-0.9.9 pilot-link-0.9.3. Boy, do we need a decent HOWTO! But I'm not the one to write it, seeing how little I know. Thanks for all the fish! Ian Hutchinson, Plasma Science and Fusion Center, MIT. http://psfc.mit.edu/~hutch/home.html _______________________________________________ Linux-IrDA mailing list - [EMAIL PROTECTED] http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
