On Sun, 14 Nov 1999, you wrote:
> On Sun, Nov 14, 1999 at 09:21:46PM -0700, Thomas Heide Clausen wrote:
> > On Sun, 14 Nov 1999, you wrote:
> > > Thomas Heide Clausen <[EMAIL PROTECTED]> writes:

<SNIP>
 
> Check that irda0 is configured:
>       ifconfig
> 
> if not, either get the latest irda-utils or:
>       ifconfig irda0 up
> 

Thanks, Dave. Upon realizing the really embarrasing mistake of not having IrDA
support compiled with ifconfig, I can now get:

irda0     Link encap:IrLAP  HWaddr af:c2:4e:9a  
          UP RUNNING NOARP  MTU:2048  Metric:1
          RX packets:8648 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:8 

I can even fire up minicom on /dev/ircomm0 and talk with the modem. Most nice
indeed, thanks to those who's help brought me this far (Dave, Dag + the rest of
the IrDA team & those who replied to my emails). However.....

Now the funny thing starts when I have this little chat with the modem:

atz
OK
atdt<phonenumber>
[The mobile lites up and types "dialling <phonenumber>, then a second later the
light goes off]
NO CARRIER

I can dial the phonenumber from the keypad of the phone with no problems. So I
am lead to believe that i either still have IrDA problems or that I need some
spooky init-string. Most docs I've come across said "AT&F", which I have tried
with no much luck. Likewise, I have had no luck with "ATZE0" - which I have
also seen mentioned (but which afaik does nothing but disable echo'ing of what
I send to the modem).

Anyone with a clue who can help me out? Thanks in advance.

--thomas

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

Reply via email to