Serial configuration problems.

Serial configuration problems.

[K. David Prince]

Here's what I can do:

Reset the PK-96 according to the documentation (9600, 7E1, COM1), then
type one "*" at which point the modem's cmd propt comes up.  I'm talking
to the modem using Hyperterminal under Windows 98.  In other words, the
serial port works; I can communicate with the modem.

Here's what I can't do:

Reboot to Debian (2.4.19 kernel).  Setserial so that I'm getting...

/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
	Baud_base: 9600, close_delay: 50, divisor: 0
	closing_wait: 3000
	Flags: spd_normal skip_test

I start minicom and configure the same as what I had been running with
Hyperterminal under Win98.  (9600, 7E1, COM1=/dev/ttyS0).  When I power
up the PK-96, minicom reports that I'm "online", but when I type the
asterisk "*", I get nothing back from the modem.

I've RTFM'd my eyeballs out, scanned the net for info. installed every
module that looks like it would remotely be relevant.  Installed the
latest kernel (2.4.19).  Even deleted the distribution and reinstalled
just to make sure.  No matter what I do, I can't get minicom to tickle the
PK-96 for a cmd prompt.  And, yes, I've tried setting minicom to (9600,
8N1, COM1=/dev/ttyS0)

My progression with my Debian installs goes from "stable" to "testing" to
"unstable."  None of these do anything with the PK-96.  The bottom line is
that the PK-96 works with Win98, and doesn't work with any of the Debian
distributions.  I find that to be highly...peculiar...to say the least.

Here's more specific information:

uname -a
========
Linux acs 2.4.19-586tsc #1 Sun Oct 6 18:00:21 EST 2002 i586 unknown unknown GNU/Linux

dmesg (relevant lines)
=======================
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A

setserial -a /dev/ttyS0
=======================
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
	Baud_base: 9600, close_delay: 50, divisor: 0
	closing_wait: 3000
	Flags: spd_normal skip_test

stty -a < /dev/ttyS0
====================
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

As to the cable, I'm using an "off the shelf" Belkin cable, 9-pin on one
side, 25-pin on the other.  I'll have to retrieve my ohm meter from Jim's
place before I can check the pins.  I actually have two serial cables and
neither work.

Other info: I've tried connecting to the modem using other CD-ROM bootable
linux versions.  As in Knoppix 3.1 (very nice, by the way) and lnx-bbc.
Neither worked.

I did try going light with modules.  Did a rmmod on mkiss and ax25.
Also, poked around /proc and everything there seems to be in order.
I.e., I don't see any conflicts.  And, I still have the same problem.

Just to make sure, I checked all the pins on my serial cables:

Pin	TNC		Computer
Name	(25-pin)	(9-pin)
=================================
FG	1		n/a
TXD	2		3
RXD	3		2
RTS	4		7
CTS	5		8
DSR	6		6
SG	7		5
DCD	8		1
DTR	20		4

Both serial cables work with both TNC's (PK-96 and KPC-3+) under Win98.
I've got two machines running with debian and neither of them seem to be
getting up on /dev/ttyS0 (both have PS2 ports for the mouse connections;
no conflicts there).

I was poking around looking for packages that might help me with this
serial problem.  I found one called "statserial".  I ran it on one of the
machines I'm trying to setup.  It updates the table below every second or
so:

Signal  Pin  Pin  Direction  Status  Full
Name    (25) (9)  (computer)         Name
-----   ---  ---  ---------  ------  -----
FG       1    -      -           -   Frame Ground
TxD      2    3      out         -   Transmit Data
RxD      3    2      in          -   Receive  Data
RTS      4    7      out         1   Request To Send
CTS      5    8      in          0   Clear To Send
DSR      6    6      in          0   Data Set Ready
GND      7    5      -           -   Signal Ground
DCD      8    1      in          0   Data Carrier Detect
DTR     20    4      out         1   Data Terminal Ready
RI      22    9      in          0   Ring Indicator

When I turn on the PK-96, CTS, DSR and DCD go to status=1.  However, when
I fire up minicom or kermit and send "*", asterisks, TxD and RxD simply
show no status, neither a 1 or 0.  The fact that I'm getting a status
change on the input CTS, DSR and DCD, suggests there "shouldn't" be a
conflicting IRQ or port, I think, which leads me to believe there is some
misconfigured parameter.  This is all amateurish speculation, of course.
The plot thickens....

So, is there anyone out there that might give me a suggestions as to what
I'm missing?

Thanks,
Dave
WB0RAZ

Re: Serial configuration problems.

[Jack Zielke]

Dave,
    What are you sending as a modem init string?  I use minicom to talk to my
th-d7.  Since in the past I have used minicom for other things I saved a
configuration just for the radio.  I run 'minicom ham'  I was wondering if
possibly the modem init string or the modem reset string may be confusing the
radio.  Just a stab in the dark.

Jack
KG4GJY

cat /etc/minirc.ham
# Machine-generated file - use "minicom -s" to change parameters.
pu baudrate         9600
pu bits             8
pu parity           N
pu stopbits         1
pu minit            
pu mreset  

setserial -a /dev/ttyS1
/dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test

stty -a < /dev/ttyS1
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

LINUX screen blanking

[Demetre Valaris]

Hi guys,

Sorry for the off topic message, but this has been bugging me for a long time!
How can I stop LINUX from blanking my screen?
I run SUSE 7.3 with kernel 2.4.10-GB in text mode, no X-Windoze!!!

I have looked everywhere and there is no mention on how to stop the screen 
blanking so I thought that Linux-Hams is my last resort!

Thanks in advance to anyone that will reply!!!

Regards to all.

73 de Demetre SV1UY
e-mail sv1uy@sv1uy.ampr.org
http://www.athnet.ampr.org/~sv1uy

Re: LINUX screen blanking

[Al Bolduc]

On Sun, 17 Nov 2002, Demetre Valaris wrote:

> Hi guys,
>
> Sorry for the off topic message, but this has been bugging me for a long time!
> How can I stop LINUX from blanking my screen?
> I run SUSE 7.3 with kernel 2.4.10-GB in text mode, no X-Windoze!!!
>

setterm -blank 0

Al

#  Al Bolduc - abolduc@attbi.com - ka1as@amsat.org - ka1as@arrl.net

Re: LINUX screen blanking

[Demetre Valaris]

On 17 Nov 2002 at 9:36, Al Bolduc wrote:

> On Sun, 17 Nov 2002, Demetre Valaris wrote:
> 
> > Hi guys,
> >
> > Sorry for the off topic message, but this has been bugging me for a long
> > time! How can I stop LINUX from blanking my screen? I run SUSE 7.3 with
> > kernel 2.4.10-GB in text mode, no X-Windoze!!!
> >
> 
> setterm -blank 0
> 
> Al
> 

Dear Al, 

Thanks for reply, but how can I stop the screen blanking globaly? For example 
I have JNOS starting from inittab in tty6 and I would like this one not to be  
blanked! Maybe I could put the same command in the startup script!!!
I will have to try that!

73 de Demetre SV1UY
e-mail sv1uy@sv1uy.ampr.org
http://www.athnet.ampr.org/~sv1uy

Re: LINUX screen blanking

[Al Bolduc]

On Sun, 17 Nov 2002, Demetre Valaris wrote:

> On 17 Nov 2002 at 9:36, Al Bolduc wrote:
>
> > On Sun, 17 Nov 2002, Demetre Valaris wrote:
> >
> > > Hi guys,
> > >
> > > Sorry for the off topic message, but this has been bugging me for a long
> > > time! How can I stop LINUX from blanking my screen? I run SUSE 7.3 with
> > > kernel 2.4.10-GB in text mode, no X-Windoze!!!
> > >
> >
> > setterm -blank 0
> >
> > Al
> >
>
> Dear Al,
>
> Thanks for reply, but how can I stop the screen blanking globaly? For example
> I have JNOS starting from inittab in tty6 and I would like this one not to be
> blanked! Maybe I could put the same command in the startup script!!!
> I will have to try that!

I have that command in rc.local.  That way it gets set every time I boot.

Al

#  Al Bolduc - abolduc@attbi.com - ka1as@amsat.org - ka1as@arrl.net

Re: LINUX screen blanking

[Demetre Valaris]

On 17 Nov 2002 at 10:33, Al Bolduc wrote:

> I have that command in rc.local.  That way it gets set every time I boot.
> 
> Al
> 
> #  Al Bolduc - abolduc@attbi.com - ka1as@amsat.org - ka1as@arrl.net
> 
> 

Right you are Al,

Just tried it and it works FB FB FB! Thanks a lot.
I had in my JNOS startup script and it is FB.
Will now put it in rc.local as you suggested, well /sbin/init.d/boot.local in 
my SUSE distribution.

Many thanks again. Regards to you and yours!!!

73 de Demetre SV1UY
e-mail sv1uy@sv1uy.ampr.org
http://www.athnet.ampr.org/~sv1uy

Re: LINUX screen blanking

[pa3gcu]

On Sunday 17 November 2002 14:26, Demetre Valaris wrote:
> Hi guys,
>
> Sorry for the off topic message, but this has been bugging me for a long
> time! How can I stop LINUX from blanking my screen?
> I run SUSE 7.3 with kernel 2.4.10-GB in text mode, no X-Windoze!!!

I presume SUSE uses the same method as slackware (pls corr me if i am wrong),

/bin/setterm -blank 0

I belive if the "0" is omitted it should still be valid.

>
> I have looked everywhere and there is no mention on how to stop the screen
> blanking so I thought that Linux-Hams is my last resort!
>
> Thanks in advance to anyone that will reply!!!
>
> Regards to all.
>
> 73 de Demetre SV1UY
> e-mail sv1uy@sv1uy.ampr.org
> http://www.athnet.ampr.org/~sv1uy
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/