From: WiseLYNX <wis...@fa...> - 2003-01-20 14:48:56
|
Some times ago I asked help on this list because I couldn't manage getting my irda port working. All was resolved when I found at last what was my chipset, and that I had to setserial the uart to none. Now... now the irda is up, and I can happily discover other devices (I tried with my cellular and another laptop running WinXP). But all stops here. Mhh? What the problem is? I really don't know. If I run minicom, it does not matter on which port and with which parameters, it suddenly=20 disconnect the irda device it previously saw, and minicom freezes (I=20 have to kill -11 it, and it badly crashes the terminal from which I=20 launched). This is the "fun" result, seen through irdadump eyes: 14:24:05.249541 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D0 (14) 14:24:05.339534 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D1 (14) 14:24:05.429535 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D2 (14) 14:24:05.519533 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D3 (14) 14:24:05.609538 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D4 (14) 14:24:05.686258 xid:rsp ed62e0ad < 636577ba S=3D6 s=3D4 T39 hint=3D9124 [= PnP=20 Modem IrCOMM IrOBEX ] (20) 14:24:05.699548 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D5 (14) 14:24:05.789536 xid:cmd ed62e0ad > ffffffff S=3D6 s=3D* naima hint=3Dc420= [=20 Computer LAN Access IrOBEX ] (22) /* Here I launch minicom */ 14:24:05.835528 snrm:cmd ca=3Dfe pf=3D1 ed62e0ad > 636577ba new-ca=3Da0 LAP QoS: Baud Rate=3D4000000bps Max Turn Time=3D500ms Data Size=3D2048B=20 Window Size=3D7 Add BOFS=3D0 Min Turn Time=3D1000us Link Disc=3D12s (33) 14:24:05.948567 ua:rsp ca=3Da0 pf=3D1 ed62e0ad < 636577ba LAP QoS: Baud Rate=3D1152000bps Max Turn Time=3D500ms Data Size=3D256B W= indow=20 Size=3D3 Add BOFS=3D0 Min Turn Time=3D0us Link Disc=3D12s (31) 14:24:05.948666 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) 14:24:06.189536 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) 14:24:06.689538 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) 14:24:07.189538 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) 14:24:07.689539 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) 14:24:08.189539 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) 14:24:08.689539 rr:cmd > ca=3Da0 pf=3D1 nr=3D0 (2) One more detail, after all of this happens, I have no way to have the=20 irda to discover again devices but rebooting the machine. Which is, in=20 my opinion, a very bad thing under a GNU/Linux environment. I found in a web page=20 (http://www.hpl.hp.com/personal/Jean_Tourrilhes/IrDA/IrDA.html) a notice=20 about bugs with Ericsson T39 (my phone :-). I tried to apply the=20 "patches", but I have some difficulties in applying the one in=20 /proc/sys/net/irda/max_tx_window, because I get an error saying the file=20 does not exist. Anyway, it doesn't seem to work, and it seems my irda=20 get blocked before it can reach those problems. =B0=B0=B0 Wise O LYNX |