Re: irda package
Wolfgang Fuschlberger wrote:
On Sun, 21 Oct 2001, Tom Allison wrote:
This is where I get confused, because some of the information I've found
on the web have specific instructions for 'mknod /dev/irda0 c 160 0'...
this device doesn't exist here
I guess the first thing I should get an answer to are these two questions:
Can I actually run with with ttyS0 as a regular serial port and ttyS1 as
a IR port?
IMO ttyS1 can never be a IR port because you always need the modules irda,
irtty ircomm ircomm-tty which are providing the device /dev/ircomm0
If I'm trying to communicate with a PalmPilot Vx, should I load ircomm,
irda, irtty, or some combination thereof?
if you do an 'irda start' and have defined the correct aliases in
/etc/modules.conf the modules should be loaded automatically
### update-modules: start processing /etc/modutils/irda
alias tty-ldisc-11 irtty
# The following is for new kernel.
alias char-major-161 ircomm-tty
# ll /dev/ir*
crw-rw---- 1 root dialout 161, 0 22. Okt 08:39 /dev/ircomm0
crw-rw---- 1 root dialout 161, 1 25. Jul 12:41 /dev/ircomm1
crw-rw---- 1 root dialout 161, 16 25. Jul 12:42 /dev/irlpt0
crw-rw---- 1 root dialout 161, 17 25. Jul 12:42 /dev/irlpt1
This all makes sense.
It seems that I am having troubles the most when nsc-ircc is loaded from
the 2.4.9 tree. Everything seems to load and function OK, up to this
point. After a modprobe nsc-ircc, things go horribly wrong! My PCMCIA
card freaks out - it throws a NETDEV WATCHDOG timeout error and
reinitializes as eth0 (it's supposed to be eth1) and then the route
tables are incorrect (I have a built in eth0 that I use differently) and
it keeps doing this Watchdog timeout error.
At this point I have no ethernet.
It may be a more subtle problem with the serial ports than anything else.