Kermit hangs on /dev/ttyS2..

Kermit hangs on /dev/ttyS2..

Post by e.. » Wed, 18 May 1994 06:30:27



I recently switched my modem device from cua2 to ttyS2
so that I could install mgetty+sendfax. But my kermit
dial outs started  behaving a little abnormal.

After the boot up, the first time I dial out everthing
works fine.  But the next time I dial out, kermit hangs
at the command

     set line /dev/ttyS2

in  .kermrc.  Then I do a cntrl-C and it continues as
if nothing happened.

I did not have this problem with cua2 and
I am not running mgetty on this device yet..
In rc.local I do

     setserial /dev/modem irq 2 uart 16550

and /dev/modem is linked to /dev/ttyS2

Thanks in advance for any suggestions/hints to get rid
of this  bug knawing at me..  ismail.

 
 
 

1. /dev/ttyS2 (/dev/cua2) reports "device or resource busy" on kernel 2.1.95

I have just upgraded my kernel from 2.1.77 to 2.1.95

I use isapnp tools to set the IRQ and I/O address of my modem, then
setserial
to tell the driver that /dev/ttyS2 is where it is.

This worked fine on 2.1.77 kernel but now I get the message that the
"device or resource busy", when I attempt to open it (with say, dip
or kermit). Nothing else is using the port.

What has changed between these two kernel releases that would cause
this?

(also tried /dev/cua2 (which is being 'deprecated') to the same
effect...
works on 2.1.77 and is busy on 2.1.95)

(remove the '__' before the address when replying please)
--
   |\      _,,,---,,_          Michael Katzmann  ( NV3Z / VK2BEA / G4NYV
)
   /,`.-'`'    -.  ;-;;,_              -  Broadcast Sports Technology
Inc.
  |,4-  ) )-,_. ,\ (  `'-'             -  Odenton, Maryland. U.S.A.

public key)

2. system crash

3. kermit cannot open /dev/tty, /dev/cua1?

4. Problem installing modem

5. recreating /dev/ttyS2

6. NFS server

7. /dev/cua2 - ttyS2 - IRQs

8. *** POSSIBLE SECURITY HOLE ***

9. how do I get /dev/ttyS2 to offer a login: prompt

10. setserial /dev/ttyS2 IRQ11 - invalid flag?

11. Hayes ESP card as /dev/ttyS2 under Linux

12. /dev/ttyS2 is not a tty!

13. Re-creating /dev/ttyS2 ?