Daniel Roloff | 1 Sep 23:20 2002
Picon

RE: no data from user-mode soundmodem

> From: Tomi Manninen [mailto:tpm <at> prkele.tky.hut.fi]
> Sent: Thursday, August 29, 2002 03:01
>
> On Wed, 28 Aug 2002, Daniel Roloff wrote:
>
> > So I would think there must be some problem with the soundcard in the
> > desktop system, though it seems to work properly in other uses.
>
> I seem to remember you mentioned using mic input on the troublesome
> computer. Am I right? If so, are you sure you don't overload the mic
> amplifier on the soundcard. The mixer on the card is usually after the
> preamplifiers so it is completely possible to overdrive them without the
> level seeming excessive in the application.
>

Actually, it's the other way around. The two working computers are laptops
and only have mic input. The troublesome computer is a desktop with both mic
and line inputs. I've tried both on that system with no sucess. Thanks for
the info about the possibility of overload though.

Dan

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Riley Williams | 3 Sep 00:30 2002

Re: no data from user-mode soundmodem

Hi Daniel.

>>>> I have successfully gotten the user-mode soundmodem working on
>>>> two Linux systems, but a third one has me stumped. The systems
are
>>>> all very similar. For two of them, I had to install the alsa
sound
>>>> drivers to get the i810 audio to work, but after doing that, one
>>>> of the systems seems to be working fine.  (So far, I have only
tried
>>>> receiving packet data.) The other system brings up the sm0 device
>>>> (as reported by ifconfig), but never receives any packets. But
>>>> using soundmodemconfig shows audio getting to the modem and
>>>> DCD being detected. Also, using soundmodem -v255 shows DCD
>>>> being set appropriately. Neither soundmodem or soundmodemconfig
>>>> fully decode any packets though, (i.e.. nothing is printed to
stdout, or
>>>> to the diagnostic modem text window).
>>>>
>>>> In kisspkt.c, pktput is called, as is hdlc_receive, but that's as
>>>> far as I got with my debug attempt.

>>> I was able to get a little farther with debugging this and it
seems
>>> that the received packets are not passing the check_crc_ccitt
>>> call. I commented this call out and data is being received, but it
>>> is about half garbage.

>> The purpose of the check_crc_ccitt call is to detect and reject
>> packets that have been mangled, and that is apparently what is
(Continue reading)

Ian McLaughlin | 3 Sep 01:01 2002
Picon

KPC 9612+ and kissattach

Hello All,
  I have searched the archives, but cannot find a solution to my problem.

2 machines trying to talk to each other.  One seems to work, one doesn't.

Software config the same on each one - RedHat 7.3 with the ax25 libs and
utils installed.  Kernel recompiled to support ax25 and kiss devices.

The machine that works is using a Kenwood D7A radio at 9600 baud in kiss
mode.  kissattach seems to work, and if I ping the other end of the radio
link, I get the radio going in to transmit mode in sync with the ping
packets.

The other end, however is a different story.  It's a Kantronics KPC 9612+,
with no radio on the first port, and a 9600 baud radio on the second port.
Minicom works fine, and I can connect to the tnc and send and receive data
on the TNC.  My problem appears to be with mkiss.  Am I correct in assuming
that I need to run mkiss because the KPC 9612 is a dual-port TNC?  I am
running the foillowing commands:

mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1
kissattach /dev/ttyq1 RADIO 172.16.0.2

The commands are accepted, and a network device is create, but if I ping, I
get no radio traffic at all.

I am suspecting that I need to do something fancy before I go in to kiss
mode on the TNC.  At the moment, I'm just doing a mycall followed by intface
kiss.  Should I do something else?

(Continue reading)

M Taylor | 3 Sep 04:29 2002
Picon

Re: KPC 9612+ and kissattach

On Mon, Sep 02, 2002 at 04:01:58PM -0700, Ian McLaughlin wrote:
> Hello All,
>   I have searched the archives, but cannot find a solution to my problem.
> 
> 2 machines trying to talk to each other.  One seems to work, one doesn't.
> 
> Software config the same on each one - RedHat 7.3 with the ax25 libs and
> utils installed.  Kernel recompiled to support ax25 and kiss devices.
> 
> The machine that works is using a Kenwood D7A radio at 9600 baud in kiss
> mode.  kissattach seems to work, and if I ping the other end of the radio
> link, I get the radio going in to transmit mode in sync with the ping
> packets.
> 
> The other end, however is a different story.  It's a Kantronics KPC 9612+,
> with no radio on the first port, and a 9600 baud radio on the second port.
> Minicom works fine, and I can connect to the tnc and send and receive data
> on the TNC.  My problem appears to be with mkiss.  Am I correct in assuming
> that I need to run mkiss because the KPC 9612 is a dual-port TNC?  I am
> running the foillowing commands:
> 
> mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1
> kissattach /dev/ttyq1 RADIO 172.16.0.2
> 
> The commands are accepted, and a network device is create, but if I ping, I
> get no radio traffic at all.

Check the AX25-HOWTO section 6.1.1.1 ("Configuring for Dual Port TNC's")
<http://www.tldp.org/HOWTO/AX25-HOWTO/x495.html>

(Continue reading)

Ian McLaughlin | 3 Sep 05:05 2002
Picon

Re: KPC 9612+ and kissattach

Thanks for the quick response.  I did consult the HOWTO, and my commands are
based on the ones you listed.  I'm only using the 9600 baud port, so I only
have a kissattach line for the second port.  This is not working, however.
What I wanted to confirm is that I'm correctly putting the 9612+ into kiss
mode.  I'm using a factory default config, with MYCALL set, and then INTFACE
KISS.  Is this correct?  All of my configs work just fine connecting to the
TNC in a Kenwood D7A handheld, but not the KPC9612.

Thanks.

----- Original Message -----
From: "M Taylor" <mctylr <at> privacy.nb.ca>
To: "Ian McLaughlin" <ian <at> platinum.net>
Cc: <linux-hams <at> vger.kernel.org>
Sent: Monday, September 02, 2002 7:29 PM
Subject: Re: KPC 9612+ and kissattach

> On Mon, Sep 02, 2002 at 04:01:58PM -0700, Ian McLaughlin wrote:
> > Hello All,
> >   I have searched the archives, but cannot find a solution to my
problem.
> >
> > 2 machines trying to talk to each other.  One seems to work, one
doesn't.
> >
> > Software config the same on each one - RedHat 7.3 with the ax25 libs and
> > utils installed.  Kernel recompiled to support ax25 and kiss devices.
> >
> > The machine that works is using a Kenwood D7A radio at 9600 baud in kiss
> > mode.  kissattach seems to work, and if I ping the other end of the
(Continue reading)

Vivi Kusumo | 3 Sep 06:00 2002
Picon

MiniLinux

Dear All,

I need MiniLinux and searched using the search engine,
than I got the source: ftp.torun.ampr.pl and
ftp.ampr.poznan.pl
But I can not access these URL. <no connection>
Do anybody have that stuff? If anybody can give me
that stuff, it is really appreciate.

Many thanks.
Vivi

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

M Taylor | 3 Sep 06:15 2002
Picon

Re: MiniLinux

On Mon, Sep 02, 2002 at 09:00:25PM -0700, Vivi Kusumo wrote:
> Dear All,
> 
> I need MiniLinux and searched using the search engine,
> than I got the source: ftp.torun.ampr.pl and
> ftp.ampr.poznan.pl
> But I can not access these URL. <no connection>
> Do anybody have that stuff? If anybody can give me
> that stuff, it is really appreciate.

ftp.torun.ampr.pl   /pub/linux/minilinux/

Use a FTP client, some web browsers (IE) may have a problem accessing 
the site.

-ve1mct
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Wilson G. Hein | 3 Sep 07:33 2002
Picon
Picon

RE: KPC 9612+ and kissattach

Try configuring both ports and see if it makes any difference.

Regards,
Wilson, WJ3G

> -----Original Message-----
> From: linux-hams-owner <at> vger.kernel.org
> [mailto:linux-hams-owner <at> vger.kernel.org]On Behalf Of Ian McLaughlin
> Sent: Monday, September 02, 2002 11:05 PM
> To: M Taylor
> Cc: linux-hams <at> vger.kernel.org
> Subject: Re: KPC 9612+ and kissattach
>
>
> Thanks for the quick response.  I did consult the HOWTO, and my
> commands are
> based on the ones you listed.  I'm only using the 9600 baud port,
> so I only
> have a kissattach line for the second port.  This is not working, however.
> What I wanted to confirm is that I'm correctly putting the 9612+ into kiss
> mode.  I'm using a factory default config, with MYCALL set, and
> then INTFACE
> KISS.  Is this correct?  All of my configs work just fine
> connecting to the
> TNC in a Kenwood D7A handheld, but not the KPC9612.
>
> Thanks.
>
> ----- Original Message -----
> From: "M Taylor" <mctylr <at> privacy.nb.ca>
(Continue reading)

Stewart Wilkinson | 3 Sep 08:07 2002
Picon

Re: KPC 9612+ and kissattach


On Mon, 2 Sep 2002, Ian McLaughlin wrote:

> Thanks for the quick response.  I did consult the HOWTO, and my commands are
> based on the ones you listed.  I'm only using the 9600 baud port, so I only
> have a kissattach line for the second port.  This is not working, however.
> What I wanted to confirm is that I'm correctly putting the 9612+ into kiss
> mode.  I'm using a factory default config, with MYCALL set, and then INTFACE
> KISS.  Is this correct?  All of my configs work just fine connecting to the
> TNC in a Kenwood D7A handheld, but not the KPC9612.

I seem to recall that I had to set 'ABAUD 9600' to force the TNC to use 
9600 Baud for the serial port instead of it's default auto-detect method. 

Are you sure 'INTFACE KISS' was accepted ? (The TNC may not let you go
from NEWUSER mode to KISS directly, you might have to do 'INTFACE 
TERMINAL' first).

--

-- 
Stewart (G0LGS)
g0lgs <at> gb7lgs.co.uk

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Vivi Kusumo | 3 Sep 09:34 2002
Picon

ftp - Re: MiniLinux

--- M Taylor <mctylr <at> privacy.nb.ca> wrote:
> On Mon, Sep 02, 2002 at 09:00:25PM -0700, Vivi
> Kusumo wrote:
> > Dear All,
> > 
> > I need MiniLinux and searched using the search
> engine,
> > than I got the source: ftp.torun.ampr.pl and
> > ftp.ampr.poznan.pl
> > But I can not access these URL. <no connection>
> > Do anybody have that stuff? If anybody can give me
> > that stuff, it is really appreciate.
> 
> ftp.torun.ampr.pl   /pub/linux/minilinux/
> 
> Use a FTP client, some web browsers (IE) may have a
> problem accessing 
> the site.
> 
> -ve1mct

$ftp ftp.torun.ampr.pl
ftp: connect: Network is unreachable

$ftp ftp.torun.ampr.pl /pub/hamradio/linux/minilinux
ftp.torun.ampr.pl: bad port number--
/pub/hamradio/linux/minilinux usage: ftp host-name
[port]

I don't know the port number.
(Continue reading)


Gmane