Linux-Hams archive - June 1998: Re: Baycom problem

Re: Baycom problem

Rene Brand (kcrebnip.kmkf@mx.dy.fi)
Wed, 03 Jun 1998 22:24:52 +0000


Hello all, i'll react to all emails at once.

Thomas Sailer wrote:
>
> Can you find out if interrupts are coming through?
> (cat /proc/interrupts repeatedly)

I tried looking at /proc/interrupts, the number does
not change when the modem is receiving data (only when
i run my script to start baycom i get a view extra
interrupts).

> What does sethdlc -i bc0 -d say?
> dmesg?

sethdlc -i bc0 -d says
----------------------

-- rx: 0 tx: 0 rxerr: 0 txerr: 0 dbg1: 0 dbg2: 1 dbg3: 0
-- rx: 0 tx: 0 rxerr: 0 txerr: 0 dbg1: 0 dbg2: 1 dbg3: 0
-- rx: 0 tx: 0 rxerr: 0 txerr: 0 dbg1: 0 dbg2: 1 dbg3: 0

---

Ed Lawson wrote: > > Are you setting TXDelay, PPersit, etc?

I did not set TXDelay etc., i tried it this evening but it didn't make a difference. I think the default values should at least do something.

> What do you see when you run ifconfig? > This mighthelp poin it down a bit more.

ifconfig didn't say anything, but the bc0 interface was active afterwards.

---

I think the problem is the 16550A UART like Gerd said. i'll try to find out more about this. I there anybody who's got a serial baycom modem working with a 16550A UART?

Rene Brand, PE1RXS