Hi,
It looks like there are a few people that have problems using IrCOMM. It's
very hard for me to debug the problems, since I would need to be there and
test it myself. All my IrCOMM devices works just fine with me, it's hard to
reproduce your problems. But I can give some recommendations on how you
should go forward. Please read it carefully!
1) Kernel version
Use Linux-2.2.15-pre6 and nothing else. The IrCOMM code in the unpatched
kernel is being phased out and is _very_ different from the pre6 code. If
you use the unpatched code, then _I_ do not care, and don't want to know
about it. Feel free to use it, but you're on your own! The new code will go
into 2.2.15, so it's much more important to debug this code!!
Make sure your IrCOMM devices in /dev looks like this:
crw-r--r-- 1 root 161, 0 Dec 22 14:15 /dev/ircomm0
crw-r--r-- 1 root 161, 1 Nov 5 08:36 /dev/ircomm1
crw-r--r-- 1 root 161, 16 Nov 5 08:36 /dev/irlpt0
Make sure your /etc/conf.modules includes these lines:
# IrDA
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty
2) PPP
If you have problems with PPP, then use "irdadump -x -s 200" to see if
Linux sends or answers any PPP stuff at all. PPP frames inside IrDA frames
looks like this:
22:39:05.414519 (0040.00 ms) i:rsp > ca=f6 pf=1 nr=4 ...
[hex output removed]
. . . . . . ~ . } # . ! } ! } ! } } 4 } " } & } } *
If you don't see such frames going out then go to 3)
3) Linux does not send any IrCOMM data
If Linux does not send out any data to the other side, then that means that
Linux is flow controlled off. This can happen if the other side flows it
off, or never flows it on. Some devices does this, and I have never found
any good way around it. To check if this is really the case by looking
at /proc/tty/driver/ircomm. If the last line sais: Hardware: stopped then
you have problems!
Another sign of this problem is if you see the message "Polling for line
settings" in dmesg. This is something Linux does to try and make the other
device flow it on. WinCE does not care about this so it doesn't help
For pppd you and specify that you don't want any hardware flow control
"pppd ... noctsrcts ..." which should fix the problem
If you the connection only works sometimes, then check if it only fails
when you are the IrCOMM client or server. You can find out if you became
the client or server by looking at /proc/tty/drivers/ircomm which should
say Role: server (or client)
4) Cannot connect with WinCE using PPP
WinCE sends you the word "CLIENT" which you must respond to by sending
"CLIENTSERVER" in order to get PPP working. Using pppd you can fix it like
this:
pppd ... connect 'chat "CLIENT" "CLIENTSERVER"'
5) PPP works with cable but not with IrCOMM
If you have problems with connecting to your ISP, then you should make sure
you are using the same pap/chap setup with IrCOMM as you are with your
cable setup? If you are sure, then you should try using the nocrtscts
option to pppd. If that doesn't help then we'll need to wait until somebody
tells me what to write here. Sorry!
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
