Re: How to get infrared and/or Nokia working
Christian Jaeger <christian.jaeger@ethlife.ethz.ch> wrote:
> Hi Julien and everybody
Hi Christian,
You're not far away from a working setup; everything is working fine
on the system's side, you just have to get gnokii working (see
below). You should already be able to use your phone to establish a
plain old ppp connection (over /dev/ircomm0).
> Finally, irdadump is showing these:
>
> 19:40:11.620026 xid:cmd b9e67de2 > ffffffff S=6 s=3 (14)
> 19:40:11.710036 xid:cmd b9e67de2 > ffffffff S=6 s=4 (14)
> 19:40:11.800029 xid:cmd b9e67de2 > ffffffff S=6 s=5 (14)
> 19:40:11.880010 xid:rsp b9e67de2 < 0000dc28 S=6 s=5 Nokia 6100
> hint=b125 [ PnP Modem Fax Telephony IrCOMM IrOBEX ] (27)
> 19:40:11.890052 xid:cmd b9e67de2 > ffffffff S=6 s=* lombi hint=0400 [
> Computer ] (21)
Good !
> root@lombi root# xgnokii
> Lockfile /var/lock/LCK..ttyS1 is stale. Overriding it..
^^^^^
Use /dev/ircomm0 ;) And gnokii --identify is better for testing.
> GSM/FBUS init failed!
> Xlib: unexpected async reply (sequence 0x3897)!
> root@lombi root# strings /usr/lib/libgnokii.so.1.0|grep 6110
> 6110
> 6110|6130|6150|6190|5110|5130|5190|3210|3310|3330|3360|3410|8210|8250|8290|5100|RPM-1
> Does that mean 6100 is supported or not?
No idea there. Just try :)
> I've never seen any other packet in irdadump output than those already
> shown above (i.e. normal discovery activity).
Because you used the wrong device ;)
>>But you shouldn't use /dev/ttyS1. You should load the ircomm module
>>and use /dev/ircomm0.
>
> Only for minicom, right? (or also for gnokii? I guess that no?)
Only irattach should use /dev/ttyS1, other applications that want to
use the irda link to communicate with another device must use
/dev/ircomm0 (in this case -- there are other protocols that use other
devices, but that's the one for ircomm).
>>The irda port on the mac can be used as a SIR device (what you're
>>currently doing), I think it could be used as a FIR device too but
>>there is currently no driver for that (assuming it's possible at all,
>>which I'm not sure).
>
> Aren't you using a FIR driver, if you have
> * irda-common/firdev: smc-ircc
> in your irda-common configuration?
No. I think it's overriden by
* irda-common/selectdevice: serial
And it's only a leftover from my first attempts at getting IrDA
working, IIRC.
> Here's my new config:
> * irda-common/ttydev: /dev/ttyS1
> * irda-common/aboutdoc:
> * irda-common/enable: true
> * irda-common/changes:
> irda-common/mkirdev:
> * irda-common/discovery: true
> * irda-common/regen: true <---how to change that?
Run "dpkg-reconfigure irda-common" as root, you should be prompted
with this question (and the others too).
> * irda-common/dongle: none
> irda-common/firdev: <----there was no possiblity to choose smc-ircc
That doesn't matter.
> irda-common/firopt:
> * irda-common/selectdevice: serial
>
> Where's the smc-ircc coming from that you are using?
I can't remember. Probably a leftover or something.
> Here are the only modules shown by lsmod that were loaded by my tests:
> irtty 7072 2 (autoclean)
> irda 101572 0 (autoclean) [irtty]
That's good. The ircomm module (and ircomm_tty) will be loaded when
needed.
>>The device (ttydev) to use is the _serial_ device on which the IrDA
>>port is attached, so that would be /dev/ttyS1 and not /dev/ircomm0
>>(that you should use when you want to reach a device over the IrDA
>>link).
>
> (I know what a serial protocol looks like; I know a little bit about
> talking to serial devices on linux; now is ircomm implemented on top
> of serial or vice versa or are they both implemented on top of
> something else - i.e. what does the protocol look like that's flashing
> the lights, normal serial or not?)
I think (I'm no expert) that there is an IrDA protocol that guarantees
data integrity, and your data is on top of this.
> Non-commentedout contents of /root/.gnokiirc:
> [global]
> port = /dev/ttyS1
> model = 6110
> initlength = default
> connection = irda
> bindir = /usr/sbin/
> use_locking = yes
> serial_baudrate = 19200
> smsc_timeout = 10
> [connect_script]
> TELEPHONE = 12345678
> [disconnect_script]
Here's mine :
[global]
port = /dev/ircomm0
model = AT
initlength = 1
connection = serial
bindir = /usr/sbin/
use_locking = yes
serial_baudrate = 57600
handshake = software
[connect_script]
TELEPHONE = 12345678
[disconnect_script]
[sms]
timeout = 20
> Thanks for the endurance
You're welcome. I just know how painful it is to get all that working
:) You're not far from getting it working OK. Chances are your 6100
will work with gnokii by using model = AT, just as my 8210 does. [in
fact I'm pretty sure it'll work, as it advertises the same
capabilities as my 8210 does]
Here's the content of my /etc/irda.conf, in case you'd like to compare
with yours :
#irda.conf Version: 1.0
IRDADEV=/dev/ttyS1
#DONGLE= # specify dongle type
DISCOVERY=-s
ENABLE=yes # if you do not need to start irattach, set "no"
JB.
--
Julien BLACHE <jblache@debian.org> | Debian, because code matters more
Debian & GNU/Linux Developer | <http://www.debian.org>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
Reply to: