On 13 Nov 2001, Cameron B. Prince wrote: > If anyone has further suggestions, please don't hesitate to voice > them...
I have no idea whether this has something to do with your problem, but just a few days ago I've got a problem report from somebody who failed to get a connection between a T39m and the VLSI driver. As it turned out the problem was the T39m comes with MIR 1.152Mbps support which got negotiated but the VLSI driver failed to use it due to a typo bug. Since MIR mode seems to be far from widespread usage I wouldn't be too much surprized if other drivers would have problems too. Not that I'd have any further indication to point in that direction, but have you tried to set max_baud_rate (located at /proc/sys/net/irda/) to 115200 or lower, so MIR would never be negotiated? Btw., with either max_baud_rate limited to 115200 or the VLSI fix applied this user's T39m seems to be happy with vanilla 2.4.13 - at least I've seen a proper /proc/net/irda/irlap output indicating a correct 1.152Mbps MIR connection and apparently he has now minicom (and probably pppd) working. Martin _______________________________________________ Linux-IrDA mailing list - [EMAIL PROTECTED] http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
