From: f5ibh <f5ibh@db0bm.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-prerelease, AX25 problems
Date: Mon, 1 Jan 2001 16:09:18 +0100 [thread overview]
Message-ID: <200101011509.QAA15904@db0bm.ampr.org> (raw)
Hi and Happy New Year,
I've just compiled and tested 2.4.0-prerelease. My AX25 (hamradio) system does
not work with this new release. There is a timing problem. When a fram is sent
on the air, the frame is VERY long (switched off by the watchdog of my drsi
card) and contains no data. On this point of vue, the previous test version was
right.
My system :
-----------
K6-2 500 / 128Mb
Kernel modules 2.3.24
Gnu C 2.95.2
Binutils 2.9.5.0.41
Linux C Library 2.1.3
Dynamic linker ldd: version 1.9.11
Procps 2.0.6
Mount 2.10o
Net-tools 2.05
Console-tools 0.2.3
Sh-utils 2.0
Modules Loaded ppp slhc af_packet scc ax25 parport_probe parport_pc lp
parport mousedev usb-ohci hid input autofs lockd sunrpc usbcore serial unix
Ax25 related config :
---------------------
#
# Amateur Radio support
#
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
CONFIG_AX25=m
CONFIG_AX25_DAMA_SLAVE=y
# CONFIG_NETROM is not set
# CONFIG_ROSE is not set
#
# AX.25 network device drivers
#
# CONFIG_MKISS is not set
# CONFIG_6PACK is not set
# CONFIG_BPQETHER is not set
# CONFIG_DMASCC is not set
CONFIG_SCC=m
# CONFIG_SCC_DELAY is not set
# CONFIG_SCC_TRXECHO is not set
CONFIG_BAYCOM_SER_FDX=m
# CONFIG_BAYCOM_SER_HDX is not set
# CONFIG_BAYCOM_PAR is not set
# CONFIG_BAYCOM_EPP is not set
# CONFIG_SOUNDMODEM is not set
# CONFIG_YAM is not set
-----
Regards
Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-01 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 15:09 f5ibh [this message]
2001-01-01 15:32 ` 2.4.0-prerelease, AX25 problems Hans Grobler
-- strict thread matches above, loose matches on Subject: below --
2001-01-01 22:28 f5ibh
2001-01-01 22:45 ` Hans Grobler
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=200101011509.QAA15904@db0bm.ampr.org \
--to=f5ibh@db0bm.ampr.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.