/dev/modem: device or resource busy

/dev/modem: device or resource busy

Post by the lOne gUnm » Wed, 28 May 1997 04:00:00



I attempted to use minicom, but it said, "/dev/modem: device or
resource busy."  I tried again as root, but experienced the same
error.

minicom USED to work fine -- I believe my problem is with mgetty,
which I've just installed to allow dial-in calls to my Linux box.  I
have mgetty setup to use /dev/ttyS0.  the /dev/modem file is a link to
/dev/cua0.  I know /dev/cua0 and /dev/ttyS0 are actually the same
piece of hardware, but isn't mgetty supposed to allow use of the modem
(by other programs) when mgetty itself is not using the modem?

It seems that I may have some minor setup detail askew.

BTW, mgetty works fine for answering dial-in calls.

thanks

   l   o   n   e/(___ ____ g   u  n/(___  _____m  a  n  /(____  ____
   /(_________/_    /    )___  __/_    |/     )_______/      \/    )
  /   ______    )  /    /    \/    )         /         )  /       /
 /   \      \__/ _/    /  /  /    /         /   _     /  /       /
(____        \______  /  /       /__|/___  /   /     /__/\____  /
    /_______  )    .)/__/\____  /       .)/___/___  /        .)/

 
 
 

/dev/modem: device or resource busy

Post by the lOne gUnm » Wed, 28 May 1997 04:00:00


I attempted to use minicom, but it said, "/dev/modem: device or
resource busy."  I tried again as root, but experienced the same
error.

minicom USED to work fine -- I believe my problem is with mgetty,
which I've just installed to allow dial-in calls to my Linux box.  I
have mgetty setup to use /dev/ttyS0.  the /dev/modem file is a link to
/dev/cua0.  I know /dev/cua0 and /dev/ttyS0 are actually the same
piece of hardware, but isn't mgetty supposed to allow use of the modem
(by other programs) when mgetty itself is not using the modem?

It seems that I may have some minor setup detail askew.

BTW, mgetty works fine for answering dial-in calls.

thanks

   l   o   n   e/(___ ____ g   u  n/(___  _____m  a  n  /(____  ____
   /(_________/_    /    )___  __/_    |/     )_______/      \/    )
  /   ______    )  /    /    \/    )         /         )  /       /
 /   \      \__/ _/    /  /  /    /         /   _     /  /       /
(____        \______  /  /       /__|/___  /   /     /__/\____  /
    /_______  )    .)/__/\____  /       .)/___/___  /        .)/


 
 
 

1. /dev/modem: Device or resource busy

I installed RedHat 5.1 for the first time a month ago.  At first I
couldn't get minicom to work, but the problem went away un-explicably and
I was able to use it.  Un-explicably, the problem came back.  When I start
minicom as myself I get the following error:

minicom: cannot open /dev/modem: Device or resource is busy

When I start minicom as root, it runs, but I can't dial out and it won't
give me an AT command line.  I have /dev/modem linked to /dev/cua1 (COM2)
which is root/uucp writable while /usr/bin/minicom is executable by all
with group ownership and GID bit on.  I can't find any lock files
anywhere.  I can't find any processes that are using /dev/modem or
/dev/cua1 either.

I tried Seyon, too, but of course it wouldn't work.  It responded with:
        no modem device is specified
        modem device is locked
        failure to open modem device

I tried "echo ATDT > /dev/modem", but that didn't work either.

Would someone like to explicate a solution?  TIA,

Fred

2. how to setup Impact IQ and Lavaport 16650 ISA jumpered

3. DIP tty open (/dev/modem, RW):Device or resource busy???

4. wu-ftpd compilation problem AGAIN

5. /dev/modem: Device or Resource Busy

6. The verb to Linux

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

8. DIP SLIP woes

9. /dev/md0: Device or resource busy

10. Floppy: /dev/fd0: Device or resource busy

11. mouse -> /dev/mouse "device or resource busy"

12. Sblaster Pro /dev/audio Resource or Device Busy?

13. /dev/cua0: Device or Resource busy