"Per Wallner (QRA)" <[EMAIL PROTECTED]> writes:
> Hi all,
> I'm still busy trying to connect a MC218 (epoc) device
> IP-wise to a network via a linux box.
>
> As is, I do get a connection, it does work, but the line drops
> after 10 secs-3 min. Getting the device to connect takes 1-5 tries.
> Sometimes the entire linux box freezes, nothing to do but pull the cable.
> (So far I haven't been able to capture that in a log)
>
> Setup: Linux 2.2.14-irda1, esi dongle
>
> Feb 3 16:57:47 gal kernel: IrLAP, no activity on link!
> Feb 3 16:58:22 gal kernel: IrLAP, no activity on link!
>
> I'm totally lost here, I can't even figure out at what level it fails ;(
> A far more detailed log with similar behaviour is attached.
>
> Does this make sense to anyone out there? All ideas immensly appreciated.
The IrLAP link goes down because Linux (acting as the seconday device)
stops receiving frames from the MC218. To me, this looks like a problem
with the MC218. But I would really like to see an "irdadump -d" of such a
session. I'm wondering if the MC218 cannot handle the size of the frames
sent by Linux? Linux tries to send out max frames as often as possible. But
it could be something else. So please send me:
irdadump -d
cat /proc/net/irda/irlap # when a session is running!
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
