No, I never succeed in "discovering" my PALM when it is around.
If I start up irdadump it initially gives nothing.
Then I irattach /dev/ttyS1 still nothing.
Then echo 1 /proc/sys/net/irda/discovery
and the irdadump starts registering packets as below, although the code
after cmd is different for different tries. The S=6 s=0 or 1 is always the
same. By the way this is different from the other irdadump examples I have
seen in people's email. I never get past s=1. Also the Palm usually shows
"waiting for sender" message. But I then can't get any further.
I don't have irmanager running, since I heard one should not. My kernel is
2.2.16-22 as I mentioned.
Ian Hutchinson, Plasma Science and Fusion Center, MIT.
http://psfc.mit.edu/~hutch/home.html
On Mon, 20 Nov 2000, Mitch DSouza wrote:
> Ok, that a bit better, at least your IrDA port is transmitting.
>
> irdadump should also start reporting the presence of the
> palm if it in proximity. I assuming you say it's not?
>
> Do you gave irmanager running ? That does the discovery in
> kernels less that 2.4.0-test11-pre5/6...
>
> Also try irobex_palm3 a file to your palm now. The lib and utils
> are here
>
> http://sourceforge.net/project/showfiles.php?group_id=8960&release_id=10205
>
> Cheers
> Mitch
> -------- Original Message --------
> Subject: Re: [Fwd: Re: Fwd: [Linux-IrDA]Linux IBM T20 -- Palm, IRDA nearly
>working.Not quite!]
> Date: Sun, 19 Nov 2000 21:04:53 -0500 (EST)
> From: [EMAIL PROTECTED]
> To: Mitch DSouza <[EMAIL PROTECTED]>
>
> OK, to be sure, I got the newest utils version 0.9.12 and make, make
> install.
>
> Then I get the following when running irattach /dev/ttyS1 -s after
> [/root]# irdadump
> 01:52:43.811081 xid:cmd 126cc967 > ffffffff S=6 s=0 (14)
> 01:52:51.871063 xid:cmd 126cc967 > ffffffff S=6 s=1 (14)
> 01:52:56.871064 xid:cmd 126cc967 > ffffffff S=6 s=1 (14)
> 01:53:01.871063 xid:cmd 126cc967 > ffffffff S=6 s=1 (14)
> 01:53:06.871064 xid:cmd 126cc967 > ffffffff S=6 s=1 (14)
> 01:53:11.871063 xid:cmd 126cc967 > ffffffff S=6 s=1 (14)
>
> 6 packets received by filter
>
> What does that show? It seems as if the new utilities don't now cause my
> PALM to say waiting for sender. But /proc/net/irda/discovery never
> discovers it. Should it not do so?
>
> Ian Hutchinson, Plasma Science and Fusion Center, MIT.
> http://psfc.mit.edu/~hutch/home.html
>
> On Sun, 19 Nov 2000, Mitch DSouza wrote:
>
> > Ok you must have a old version then.. Check mine out
> >
> >
> > core ~% pilot-xfer --help
> > Usage: pilot-xfer [-p port] command(s)
> >
> > Where a command is one or more of: -b(ackup) backupdir
> > -u(pdate) backupdir
> > -s(ync) backupdir
> > -r(estore) backupdir
> > -i(nstall) filename(s)
> > -m(erge) filename(s)
> > -f(etch) dbname(s)
> > -d(elete) dbname(s)
> > -e(xclude) filename
> > -P(urge)
> > -l(ist)
> > -L(istall)
> > -v(ersion)
> > -h(elp)
> > ....
> >
> >
> > Anyway setting the variables is the best answer.
> >
> > irnine is link to ircomm so it should be fine. My device is.
> >
> > Please update your tools because irdadump should show transmit packets even
> > if there is no reciever (palm) for example..
> >
> > core ~% su
> > Password:
> > core /home/mitch# irdadump
> > 18:22:41.640317 xid:cmd f7db1cd1 > ffffffff S=6 s=0 (14)
> > 18:22:41.730287 xid:cmd f7db1cd1 > ffffffff S=6 s=1 (14)
> > 18:22:41.820288 xid:cmd f7db1cd1 > ffffffff S=6 s=2 (14)
> > 18:22:41.910287 xid:cmd f7db1cd1 > ffffffff S=6 s=3 (14)
> > 18:22:42.000299 xid:cmd f7db1cd1 > ffffffff S=6 s=4 (14)
> > 18:22:42.090300 xid:cmd f7db1cd1 > ffffffff S=6 s=5 (14)
> > 18:22:42.180296 xid:cmd f7db1cd1 > ffffffff S=6 s=* core hint=0400 [ Computer ]
>(20)
> > 18:22:44.640314 xid:cmd f7db1cd1 > ffffffff S=6 s=0 (14)
> > 18:22:44.730288 xid:cmd f7db1cd1 > ffffffff S=6 s=1 (14)
> > 18:22:44.820292 xid:cmd f7db1cd1 > ffffffff S=6 s=2 (14)
> > 18:22:44.910298 xid:cmd f7db1cd1 > ffffffff S=6 s=3 (14)
> > 18:22:45.000295 xid:cmd f7db1cd1 > ffffffff S=6 s=4 (14)
> > 18:22:45.090286 xid:cmd f7db1cd1 > ffffffff S=6 s=5 (14)
> > 18:22:45.180294 xid:cmd f7db1cd1 > ffffffff S=6 s=* core hint=0400 [ Computer ]
>(20)
> >
> > 14 packets received by filter
> >
> > (This is with no revieving device in proximity).
> >
> > See irdautils just recently mentioned in http://appwatch.com
> >
> >
> > Cheers
> > Mitch
> >
> > -------- Original Message --------
> > Subject: Re: Fwd: [Linux-IrDA]Linux IBM T20 -- Palm, IRDA nearly working.Not quite!
> > Date: Sun, 19 Nov 2000 13:05:12 -0500 (EST)
> > From: [EMAIL PROTECTED]
> > To: Mitch DSouza <[EMAIL PROTECTED]>
> >
> > irdadump says
> >
> > 0 packets received by filter.
> > I don't have any /dev/irnine. But yes I put PILOTRATE=115200
> >
> > The man page says:
> >
> > SYNOPSIS
> > pilot-xfer [serial-device] [--exclude file] --backup |
> > --update | --sync directory
> >
> > or
> >
> > pilot-xfer [serial-device] [ --restore directory | --list
> > | --purge | --fetch dbname ... | --delete dbname ... |
> > --install file ... | --merge file ... ] ...
> >
> > --list and -l are the same.
> >
> > Ian Hutchinson, Plasma Science and Fusion Center, MIT.
> > http://psfc.mit.edu/~hutch/home.html
> >
> > On Sun, 19 Nov 2000, Mitch DSouza wrote:
> >
> > > What does irdadump show ?
> > >
> > > And the syntax is
> > >
> > > pilot-xfer /dev/ircomm0 -l
> > >
> > >
> > > is wrong.
> > >
> > > I'd suggest you set PILOTPORT=/dev/irnine and PILOTRATE=115200
> > >
> > > -------- Original Message --------
> > > Subject: [Linux-IrDA]Linux IBM T20 -- Palm, IRDA nearly working. Not quite!
> > > Date: Sat, 18 Nov 2000 18:56:57 -0500 (EST)
> > > From: [EMAIL PROTECTED]
> > > Reply-To: [EMAIL PROTECTED]
> > > To: [EMAIL PROTECTED]
> > >
> > > So near, but I just can't quite seem to get an IR connection between
> > > my T20 (44u) and my Palm. I don't have any other IR devices to
> > > test. But it seems probably a linux IRDA problem. I've read everything I
> > > can find on the web but would appreciate any advice as to what to try
> > > next to figure out where the problem is.
> > >
> > > Summary:
> > > I get as far as making the palm respond waiting for sender with irattach but
> > > can't get any more response. Nothing logged in discovery.
> > >
> > > Details:
> > > irda-utils=0.9.9
> > > pilot-link.0.9.3
> > >
> > > modules.conf:
> > > alias tty-ldisc-11 irtty
> > > alias char-major-161 ircomm_tty
> > > options nsc-ircc dongle_id=0x09
> > > alias irda0 nsc-ircc
> > > [Although the last two made no difference]
> > >
> > > lsmod:
> > > ircomm-tty 17128 0
> > > ircomm 5924 0 [ircomm-tty]
> > > irtty 4900 0
> > > irda 74657 0 [ircomm-tty ircomm irtty]
> > >
> > > The command
> > > irattach /dev/ttyS1 -s 1
> > > responds
> > > 1.1 Tue Nov 9 15:30:55 1999 Dag Brattli
> > > and exits leaving irattach running as indicated by ps -ax.
> > >
> > > /var/log/messages says:
> > > Nov 18 17:23:38 localhost irattach: device=/dev/ttyS1
> > > Nov 18 17:23:38 localhost irattach: SIR device
> > > Nov 18 17:23:38 localhost kernel: IrDA: Registered device irda0
> > > Nov 18 17:23:39 localhost irattach: executing: 'echo 1 >
>/proc/sys/net/irda/discovery'
> > > Nov 18 17:23:39 localhost irattach: SIR device (2)
> > > Nov 18 17:23:39 localhost irattach: Starting device irda0
> > > Nov 18 17:23:39 localhost irattach: executing: 'echo localhost >
>/proc/sys/net/irda/devname'
> > >
> > > and brings up on my Palm "waiting for sender"
> > >
> > > But there is never a log in discovery that indicates finding the palm
> > > it is just blank
> > > cat /proc/net/irda/discovery:
> > > IrLMP: Discovery log:
> > >
> > > And the command
> > > pilot-xfer /dev/ircomm0 -l
> > > gives
> > > Waiting for connection on /dev/ircomm0 (press the HotSync button now)...
> > >
> > > but just hangs. The Palm is running Palm-OS 3.3 (upgraded Palm IIIx)
> > > and hotsync is set to direct serial, IR to a PC/Handheld. Pressing the
> > > hot-sync button just times out.
> > >
> > > For what it is worth, I seem to be able to bring up the irda0 interface
> > > with ifconfig irda0 up so that ifconfig gives
> > > irda0 Link encap:IrLAP HWaddr 42:a2:b1:c6
> > > UP RUNNING NOARP MTU:2048 Metric:1
> > > RX packets:75 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:8
> > >
> > > # setserial /dev/ttyS1
> > > /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
> > >
> > > [/root]# ls /dev/ttyS? -l
> > > crw-rw---- 1 root tty 4, 64 Nov 18 18:34 /dev/ttyS0
> > > crw-rw-rw- 1 root tty 4, 65 Nov 18 18:34 /dev/ttyS1
> > > crw-rw---- 1 root uucp 4, 66 Aug 24 05:00 /dev/ttyS2
> > > c
> > >
> > > Tried doing setserial /dev/ttyS1 uart none but then irattach did not succeed
> > > it terminates immediately with /var/log/messages:
> > > Nov 18 18:39:42 localhost irattach: device=/dev/ttyS1
> > > Nov 18 18:39:42 localhost irattach: SIR device
> > > Nov 18 18:39:42 localhost irattach: tcsetattr: Input/output error
> > >
> > > Tried recompiling the kernel (2.2.16-22) with serial support as a module,
> > > since I read somewhere that was needed. No difference.
> > >
> > > As you can see, my wheels seem to be spinning. Thanks in advance for
> > > any help that anyone can offer.
> > >
> > > Ian Hutchinson.
> > >
> >
>
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
