Hi,

getting this working is becoming more and more frustrating. For some
time I was able to dialout with my phone using the mainstream 2.2.14
release. At some point this mysteriously stopped working. SO I upgraded
to 2.2.15pre17. I was delighted that ircomm was working straight away.
However now I can't get it to work.


My phone: Motorola L Series+ (shows up as Timeport in discovery)
Computer: ACER Travelmate 14T

After the upgrade I could use ppp as follows. 

1. Activate IR port on phone (display reads "activating")
2. Launch PPP - pon provider
3. Display on phone would change to "activated"
4. Everything would work fine.

However now the phone never reads "activated"

I can't even irdaping the phone.

> cat /proc/net/irda/discovery

IrLMP: Discovery log:

nickname: Timeport, hint: 0xb104, saddr: 0x51ea18c8, daddr: 0xfda01a84

> irdaping 0xfda01a84
IrDA ping (0xfda01a84): 32 bytes

>irdadump

22:27:36.224922 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:27:41.224907 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:27:46.224908 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:27:51.224919 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:27:56.224908 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:28:01.224930 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:28:06.224908 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:28:11.224924 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:28:16.224908 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:28:21.224926 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
22:28:26.224912 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 
...snip
22:29:12.714911 xid:cmd ffffffff < 67024c70 S=6 s=0 (14) (phone
"activating" here)
22:29:12.794916 xid:cmd ffffffff < 67024c70 S=6 s=1 (14) 
22:29:12.884934 xid:cmd ffffffff < 67024c70 S=6 s=2 (14) 
22:29:12.974911 xid:cmd ffffffff < 67024c70 S=6 s=3 (14) 
22:29:13.064911 xid:cmd ffffffff < 67024c70 S=6 s=4 (14) 
22:29:13.144930 xid:cmd ffffffff < 67024c70 S=6 s=5 (14) 
22:29:13.244909 xid:cmd ffffffff < 67024c70 S=6 s=* Timeport hint=b104 [
PnP Modem Fax IrCOMM ] (25) 
22:29:16.224907 xid:cmd 51ea18c8 > ffffffff S=6 s=1 (14) 

> cat /proc/net/irda/*
IrLMP: Discovery log:

nickname: Timeport, hint: 0xb104, saddr: 0x51ea18c8, daddr: 0x67024c70

Instance 0:
LM-IAS Objects:
name: Device, id=0
 - Attribute name: "IrLMPSupport", value[IAS_OCT_SEQ]: octet sequence

 - Attribute name: "DeviceName", value[IAS_STRING]: "Linux"

irlap0 state: LAP_NDM
  caddr: 0x9a, saddr: 0x51ea18c8, daddr: 0x000000
  win size: 0, win: 0, line capacity: 0, bytes left: 0
  tx queue len: 0 win queue len: 0 rbusy: FALSE mbusy: FALSE
  retrans: 0 vs: 0 vr: 0 va: 0
  qos   bps     maxtt   dsize   winsize addbofs mintt   ldisc   comp
  tx    9600    0       64      1       11      0       0       0
  rx    9600    0       64      1       11      0       0       0
Unconnected LSAPs:
lsap state: LSAP_DISCONNECTED, slsap_sel: 0x0, dlsap_sel: 0xff, (IrIAS
srv)

Registred Link Layers:
lap state: LAP_STANDBY, saddr: 0x51ea18c8, daddr: 0xffffffff, refcount:
0

Connected LSAPs:

* Some other strange things I noticed. I use the Lucent winmodem driver
module. It is compiled for 2.2.12 but works fine with 2.2.14. When I
removed this module then restarted irmanager it crashed my kernel. Don't
know the significance of this.

I really need some help with this as I need to use this soon. Hate to
have to resort to Windows.

Iain.

-- 
Iain Pople
[EMAIL PROTECTED]

_______________________________________________
Linux-IrDA mailing list  -  [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda

Reply via email to