[EMAIL PROTECTED] wrote:
>
> Slowly making progress.
>
> Removed all explicit module insertions from rc.local
> On a cold reboot did:
> irdadump (in one window)
> irattach /dev/ttyS1
Did you try:
irattach /dev/ttyS1 -s
> echo 1 >> /proc/sys/net/irda/discovery
I think the -s (start discovery) is supposed to do the same as the
above, but
I don't know, and I don't have a palm :(
I'm also attaching a copy of Matt Newsome's excellent mail-howto. Dag is
saying not to use irmanager (anymore) but other than that his
documentation leaves much to be desired. Hope this helps.
Garst
>From - Mon Oct 23 12:07:24 2000
X-POP3-Rcpt: reese@kiln
Received: from server.pasta.cs.uit.no (IDENT:[EMAIL PROTECTED]
[129.242.16.119])
by kiln.isn.net (8.9.3/8.9.3) with ESMTP id LAA27177
for <[EMAIL PROTECTED]>; Mon, 23 Oct 2000 11:08:23 -0300
Received: from server.pasta.cs.uit.no (IDENT:mailman@localhost [127.0.0.1])
by server.pasta.cs.uit.no (8.9.3+3.2W/8.9.3) with ESMTP id QAA05594;
Mon, 23 Oct 2000 16:06:06 +0200 (CEST)
Received: from seville.screaming.net (m233-mp1-cvx1b.lan.ntl.com [62.252.168.233])
by server.pasta.cs.uit.no (8.9.3+3.2W/8.9.3) with ESMTP id QAA05536
for <[EMAIL PROTECTED]>; Mon, 23 Oct 2000 16:05:21 +0200 (CEST)
Received: (from matt@localhost)
by seville.screaming.net (8.9.3/8.9.3) id PAA31933;
Mon, 23 Oct 2000 15:05:13 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Mon, 23 Oct 2000 15:05:12 +0100 (BST)
From: Matt Newsome <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 6.71 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2)
Subject: [Linux-IrDA]Dell Dimension CP/Linux 2.2 <> Palm m100 HOWTO
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0beta5
Precedence: bulk
Reply-To: [EMAIL PROTECTED]
List-Id: The Pasta Projects Linux-IrDA Forum <linux-irda.pasta.cs.UiT.No>
X-Mozilla-Status: 8001
X-Mozilla-Status2: 00000000
X-UIDL: de18aaf5d59605c8999c86cc85266ee9
After *considerable* hassle, I'm glad to report I now have pilot-xfer
connecting from my Dell Dimension CP over the IR port to my Palm m100
(essentially a Palm III).
While I've been doing this it has become apparent that there is a lot
of confusing and/or contradictory information available re. how to get
such a link up. Those who have their IrDA working are running very
different versions, seemingly, to people trying to set theirs up from
scratch today, so, for the record and for the benefit of others, below
is the procedure I've used.
I hope it helps others get their connection up faster. I've been a
linux user since kernel v1.2 and have extensive access to the net, but
that has scarcely helped at all during this process; this information
doesn't seem to be available anywhere.
1) Download linux v2.2.17 sources from either www.rpmfind.net (if you
want an RPM version of the sources), or a local mirror of
ftp.kernel.org/pub/linux/kernel/v2.2/ for a tar version.
NOTE: You do not require any kernel patches to get a HotSync to your
pilot working. This was probably the hardest bit of info to find
out.
2) Build the kernel, making sure you switch on IrDA support. Here
are my settings for reference:
CONFIG_IRDA=m
CONFIG_IRLAN=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set
CONFIG_IRDA_OPTIONS=y
CONFIG_IRDA_CACHE_LAST_LSAP=y
# CONFIG_IRDA_FAST_RR is not set
CONFIG_IRDA_DEBUG=y
# CONFIG_IRDA_COMPRESSION is not set
CONFIG_IRTTY_SIR=m
CONFIG_IRPORT_SIR=m
# CONFIG_NSC_FIR is not set
# CONFIG_WINBOND_FIR is not set
# CONFIG_TOSHIBA_FIR is not set
# CONFIG_SMC_IRCC_FIR is not set
CONFIG_DONGLE=y
# CONFIG_ESI_DONGLE is not set
CONFIG_ACTISYS_DONGLE=m
# CONFIG_TEKRAM_DONGLE is not set
# CONFIG_GIRBIL_DONGLE is not set
# CONFIG_LITELINK_DONGLE is not set
# CONFIG_OLD_BELKIN_DONGLE is not set
Build the modules too, and install the modules and kernel image as
normal (newbies: see KERNEL-HOWTO or tons of stuff on the web
re. building kernel and installing new kernel modules). Don't forget
to setup lilo or make a boot disk.
3) Reboot using the new kernel.
4) Get the source for irda-utils-0.9.9 from rpmfind.net or
ftp://irda.sourceforge.net/pub/irda/irda-utils/. Expand it in a
directory, then just "make" and "make install" as root.
5) Now edit /etc/irda/drivers appropriately. In my case, my IrDA port
is on /dev/ttyS2 (check which com ports you have using dmesg |less).
On my system I edited the "start" section of the script as follows:
'start')
irattach /dev/ttyS2 # The third serial port is an
# IrDA port
# irattach /dev/ttyS0 -d esi # Attach a ESI dongle to the
# first serial port
# irattach /dev/ttyS0 -d tekram
# insmod pc87108 # If your machine as a pc87108
# FIR chipset
# modprobe uircc # Sharp UIRCC chipset
;;
6) There are probably more elegant solutions that the following steps
(e.g. with /etc/conf.modules, or rc.local), but I know this definitely
works:
modprobe irda
insmod irtty
insmod ircomm
insmod ircomm-tty
An lsmod should now show that (probably amongst others) irda, irtty,
ircomm and ircomm-tty have all been loaded.
7) Now do irmanager -d 1
8) Double check that the IR port has been found, bound and activated
by looking at /var/log/messages. Here's what I get:
Oct 23 14:27:30 ubik kernel: IrDA (tm) Protocols for Linux-2.2 (Dag
Brattli)
Oct 23 14:29:06 ubik kernel: IrCOMM protocol (Dag Brattli)
Oct 23 14:29:30 ubik irmanager: executing: 'echo 1 >
/proc/sys/net/irda/discovery'
Oct 23 14:29:31 ubik irmanager: executing: 'echo ubik >
/proc/sys/net/irda/devname'
Oct 23 14:29:31 ubik irmanager: + 1.1 Tue Nov 9 15:30:55 1999 Dag
Brattli
Oct 23 14:29:31 ubik kernel: IrDA: Registered device irda0
Oct 23 14:29:31 ubik irmanager: + 1.1 Tue Nov 9 15:30:55 1999 Dag
Brattli
Oct 23 14:29:31 ubik irattach: device=/dev/ttyS2
Oct 23 14:29:31 ubik irattach: SIR device
Oct 23 14:29:32 ubik irattach: SIR device (2)
Oct 23 14:29:32 ubik irattach: Starting device irda0
Oct 23 14:29:32 ubik irattach: executing: 'echo ubik >
/proc/sys/net/irda/devname'
9) Check the connection. Put the Palm into HotSync mode (having set
it to "IR to a PC/Handheld" mode first) and point it at the device
about a foot away with nothing between the Palm and the PC's IrDA
port(!). HotSync is activated on the Palm via IrDA by pressing
the HotSync symbol in the centre of the display. Before the HotSync
times out on the Palm, 'cat /proc/net/irda/discovery'.
You should see something like this:
IrLMP: Discovery log:
nickname: IrCOMM, hint: 0x8204, saddr: 0xaa641bb3, daddr: 0x371ab751
This shows that the device has been detected over the IR port. Now
make sure you've got a connection and see what kind of data transfer
rates you're getting. Use '/usr/sbin/irdaping 0x371ab751' (note that
this is MY daddr from above - you'll have to use the one which appears
in your discovery file).
Here's what I get:
[root@ubik matt]# /usr/sbin/irdaping 0x371ab751
IrDA ping (0x371ab751): 32 bytes
32 bytes from 0x371ab751: irda_seq=1 time=120.69 ms.
32 bytes from 0x371ab751: irda_seq=2 time=110.63 ms.
32 bytes from 0x371ab751: irda_seq=6 time=110.61 ms.
32 bytes from 0x371ab751: irda_seq=7 time=120.64 ms.
32 bytes from 0x371ab751: irda_seq=10 time=120.64 ms.
11 packets received by filter
(Note that the packet loss above is seemingly symptomatic of IR
connections; it's ok as the protocol makes allowances for this).
10) Install pilot-link if you haven't already. I used version 0.9.0,
but I gather pretty much all versions will work. You can get this
from rpmfind.net or latest source from
http://cvs.gnu-designs.com/cgi-bin/vcvs/viewcvs.cgi/?cvsroot=Open+Palm+Group.
Now set PILOTRATE and PILOTPORT, e.g.
export PILOTPORT=/dev/ircomm0
export PILOTRATE=9600
(the latter should be set much higher if you can, but use this just to
test your connection).
Finally, do:
pilot-xfer -b <directory>
or similar (see pilot-link DOCS for more info on what you can do with
pilot-xfer).
Run HotSync on the Palm, again ensuring the Palm is in HotSync mode,
having set it to "IR to a PC/Handheld" mode first and pointed it at
the device about a foot away with nothing between the Palm and the
PC's IrDA port. HotSync is activated on the Palm via IrDA by pressing
the HotSync symbol in the centre of the Palm display.
This time, however, you should hear the familiar HotSync chimes and
see the HotSync take place.
I hope that helps at least one person. Post any questions to the list
in the first instance.
I'll be playing with IrOBEX next and will post any success I have
there for the benefit of others.
--
Matt Newsome
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
