I have an intermittent problem with the serial ports ser1 and ser2 at boot
time. For testing this, I have a 3 wire null-modem cable going from COM1 to
COM2 on the PC. I start qtalk on each port from sysinit and four out of five
times (approx), everything works fine and I can send and receive to each
port, however, when it fails it seems like one character gets through and
the communications hang.
If I boot without starting the qtalk sessions from sysinit and then login, I
can start the qtalk sessions and that always seems to work. I’ve run out of
things to try. Anyone have a suggestion? Thanks.
My stripped down sysinit file looks like this:
###################################
export TZ=EST5DST4,M4.1.0/2,M10.5.0/2
rtc hw
Dev -n 100 &
Dev.con -n 4 &
Dev.ser -F &
nameloc &
Net &
Net.ether82557 &
#Fsys.floppy &
#Dosfsys a=/dev/fd0
emu87 &
netmap -f
#mount /dev/fd0 /qnx/fd0 &
on -t /dev/con1 qtalk -m /dev/ser1 -b 9600,o,7,1
sleep 2
on -t /dev/con2 qtalk -m /dev/ser2 -b 9600,o,7,1
sleep 2
tinit -T /dev/con3 /dev/con4 -t /dev/con3 /dev/con4 &
#######################################
Almost forgot:
If I slay Dev32.ser and restart it, things work again.
“Dan Eberth” <daniel.eberth@kodak.com> wrote in message
news:9ulh53$1up$1@news.kodak.com…
I have an intermittent problem with the serial ports ser1
Does stty </dev/ser1 and stty </dev/ser2 show anything “*paged”,
for example ospaged? If you see one of those, that would explain why
they don’t talk. You could force the paged condition(s)
off or try starting the driver with a -w option which helps with
some chips.
Dan Eberth wrote:
Almost forgot:
If I slay Dev32.ser and restart it, things work again.
“Dan Eberth” <> daniel.eberth@kodak.com> > wrote in message
news:9ulh53$1up$> 1@news.kodak.com> …
I have an intermittent problem with the serial ports ser1
Those are good suggestions. Unfortunately, the system is unavailable today.
I’ll try these things tomorrow and let you know what I find.
Thanks,
Dan
“Richard R. Kramer” <rrkramer@kramer-smilko.com> wrote in message
news:3C0E8ED7.28AB19CC@kramer-smilko.com…
Does stty </dev/ser1 and stty </dev/ser2 show anything “*paged”,
for example ospaged? If you see one of those, that would explain why
they don’t talk. You could force the paged condition(s)
off or try starting the driver with a -w option which helps with
some chips.
Dan Eberth wrote:
Almost forgot:
If I slay Dev32.ser and restart it, things work again.
“Dan Eberth” <> daniel.eberth@kodak.com> > wrote in message
news:9ulh53$1up$> 1@news.kodak.com> …
I have an intermittent problem with the serial ports ser1