From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Stef Daniels VK5HSX <vk5hsx@wia.org.au>
Cc: Debian Hams List <debian-hams@lists.debian.org>,
linux-hams@vger.kernel.org
Subject: Re: multiple kiss ports
Date: Wed, 14 Feb 2007 20:14:00 +0000 [thread overview]
Message-ID: <20070214201400.GA2366@linux-mips.org> (raw)
In-Reply-To: <1171459986.3039.12.camel@localhost.localdomain>
On Thu, Feb 15, 2007 at 12:03:06AM +1030, Stef Daniels VK5HSX wrote:
> P4 1.2Ghz Celeron
> MSI Motherboard
> 512MB RAM
> 40GB ATA Drive
> ttyS0 -> 9600bd -MFJ 1270b (1200bd TNC) axport '2'
> ttyS1 -> 4800bd - AEA PK232 (4800bd TNC) axport '3'
> Debian GNU\linux 3.1 (2.4.27 kernel)
> using: libax25-0.0.11, ax25-apps-0.0.6, aax25-tools-0.0.8, node-0.3.2,
> fbb7.04j
>
> The problem is after we run our ax25 script to call up modules, tnc into
> kiss and kissattach devices (which all work fine), upon connect using
> port '2' the tnc "sta" LED comes on and tnc hangs.
>
> We have tried the following:
>
> Different- Computers, Cables, TNC's, O\S's, kernel's, hardrive, P\Supply
> and Serial ports (PCI Serial Cards), to NO avail.
>
> Any ideas, help, comments greatfully and most appreciatedly received!!
Did you try a 2.6 kernel also? The 2.4 mkiss driver usually works just
fine but it's a fairly suspect piece of code anyway, so I've turned the
KISS driver upside down for Linux 2.6.
A no-no at the current state of the code are SMP or preemptible kernels.
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
Packet: DL5RB@DB0FHN.#BAY.DEU.EU
next prev parent reply other threads:[~2007-02-14 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 13:33 multiple kiss ports Stef Daniels VK5HSX
2007-02-14 20:14 ` Ralf Baechle DL5RB [this message]
2007-02-14 20:18 ` Ray Wells
2007-02-15 10:29 ` Bernard Pidoux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070214201400.GA2366@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=debian-hams@lists.debian.org \
--cc=linux-hams@vger.kernel.org \
--cc=vk5hsx@wia.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox