/dev/modem: Device or Resource Busy

/dev/modem: Device or Resource Busy

Post by John D. Sundbe » Thu, 10 Mar 1994 14:13:14



I am having problems with my modem - not sure if it has always
been the case or not.  (I do not think it has always been the case.)
When using kermit (after reboot I get):

/dev/modem: Device or resource busy

If I (as root) do:
kill (the getty on /dev/ttyS1) ; dir > /dev/modem
all will be fine from this point on. If I dont write to /dev/modem
the modem still will be busy - getty respawns too fast and I cant use it.
Or if someone were to dial in before I attempt to use the modem
after a reboot - things will also be fine.  

I program my internal modem (Practical Peripherals 14400FX):

at&F1&Q9M0&D3S0=2E0Q2&W

which if I do at&V I get:

ACTIVE PROFILE:            DTE:38400      DCE:14400     PARITY:NONE
B16 B1 E0 L2 M0 N1 P Q2 V1 W0 X4 Y0 &A0 &B1 &C1 &D3 &G0 &J0 &K3 &L0 &Q9 &R0 &S0
&T4 &U0 &X0 &Y0
S00:002 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:050 S08:002 S09:006
S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S30:000 S36:007 S37:000 S38:020
S43:000 S46:002 S48:007 S49:064 S50:220 S63:000 S82:128 S86:000 S95:000 S97:030
S108:001 S109:062 S110:002
STORED PROFILE 0:
B16 B1 E0 L2 M0 N1 P Q2 V1 W0 X4 Y0 &A0 &C1 &D3 &G0 &J0 &K3 &L0 &Q9 &R0 &S0 &T4
S00:002 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000
S25:005 S26:001 S30:000 S36:007 S37:000 S38:020 S46:002 S48:007 S63:000 S82:128
S95:000 S97:030 S108:1 S109:062 S110:2
STORED PROFILE 1:
B16 B1 E1 L2 M1 N1 P Q0 V1 W0 X4 Y0 &A0 &C1 &D2 &G0 &J0 &K3 &L0 &Q5 &R0 &S0 &T4
S00:000 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000
S25:005 S26:001 S30:000 S36:007 S37:000 S38:020 S46:002 S48:007 S63:000 S82:128
S95:000 S97:030 S108:1 S109:062 S110:2
TELEPHONE NUMBERS:
&Z0=                                    &Z1=
&Z2=                                    &Z3=

OK

I have pl14 and no other boards using that IRQ (5) and my recompiled kernel
has been working fine for quite awhile (at least a month).

An strace of the kermit pid shows a failure to open the device
which tells me there are no locks on the modem.

Of course - it is very possible I dont know what I am doing and the
answer is obvious.  The Serial Howto mentions this problem - it says to
check DCD - make sure its only on when a connection is made which according
to my modem docs &C1 is the settings that I should have.
It also mentions other possibilities - which have not panned out.

Any help would be greatly appreciated and paid back with a virtual beer.
(Or at least a nice jpeg of a neat beer label.)
-John
--
_________________________________________________________________

Eagan, MN USA                                      (612) 683-1130

 
 
 

/dev/modem: Device or Resource Busy

Post by Peter Casc » Sat, 12 Mar 1994 16:15:15



: I am having problems with my modem - not sure if it has always
: been the case or not.  (I do not think it has always been the case.)
: When using kermit (after reboot I get):

: /dev/modem: Device or resource busy

: If I (as root) do:
: kill (the getty on /dev/ttyS1) ; dir > /dev/modem
: all will be fine from this point on. If I dont write to /dev/modem
: the modem still will be busy - getty respawns too fast and I cant use it.
: Or if someone were to dial in before I attempt to use the modem
: after a reboot - things will also be fine.  

: I have pl14 and no other boards using that IRQ (5) and my recompiled kernel
: has been working fine for quite awhile (at least a month).

: An strace of the kermit pid shows a failure to open the device
: which tells me there are no locks on the modem.

: Of course - it is very possible I dont know what I am doing and the
: answer is obvious.  The Serial Howto mentions this problem - it says to
: check DCD - make sure its only on when a connection is made which according
: to my modem docs &C1 is the settings that I should have.
: It also mentions other possibilities - which have not panned out.

I don't know if this is the same problem, since you're running pl14.  I had
the same symptom with pl15j.  I applied the getty_ps 2.0.7b -> 2.0.7c patch
(in sunsite.unc.edu:/pub/Linux/system/Serial).  The message in the patch said
that getty_ps 2.0.7b was broken by pl15.  So, good luck!
--
Pete Cascio -- Black Forest, Colorado -- "May the forest be with you!"



 
 
 

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. AMD and LINUX

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

4. Help needed installing Debian 2.2R2 on PowerMac G4

5. /dev/modem: device or resource busy

6. Major Login Problem

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

8. Nt error message

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