Sup everyone.. i recently installed slack 8.1 upgrading from 8.0 .. when trying to dial up to my isp on X using kppp .. i get the error "sorry the modem is busy" .. i do not have a winmodem ..it used to work before. anyone know how i fix this problem? what command to use..or any other help would be appreciated

Check the link /dev/modem and see if it exists. If it does then check to make sure it is valid and pointing to your modem. You chould check kppp configuration and see what it is actually looking for.

the link to /dev/modem points to /dev/ttyS1 ..everything for my modem seems to be in order and all the configuration is correct..there must be another problem somewhere.. i really need help with this..so if anyone or Excalibur can help..please it would be appreciated

Are you logged in as root?

Did you change the kernel when you upgraded? does your kernel support
PPP? did you use the same port in 8.0? is this an internal modem?

Excalibur: yes im running it as root.. my kernel supports PPP and yea my modem is internal.. im gonna try reinstalling slack .. hopefully it will work

Is your modem installed on COM2: (/dev/ttyS1)

Also, check in the /var/run directory for an old pid file. It might be called ttyS1.pid, modem.pid, ppp0.pid, kppp.pid or similar. If kppp detects that it thinks a process is using the modem port then it could report that it is busy. "pid" stands for process identification and the file should contain a valid process number using the resource. But if a process dies unexpectedly then it might leave the pid file.

yes excalibur the modem is install on COM2 .. i looked in the /var/run dir ..no files similar to kppp or ppp0 or ne thing like that.. still says modem is busy.. i dunno wuts going on but its getting me very upset.. is there ne thing else i could do ? ..i have no clue whats goin on

What happens if you do a:

echo "atdt" > /dev/modem

Since you're using Slackware, you have another option that isn't as pretty
as kppp, but usually works.

As root, in an xterm or console, do:

cp /etc/resolv.conf /etc/resolv.conf.back
(only necessary if you've setup your DNS server via some other
means, if this file is basically empty, you don't need to back it up)
pppsetup

this will take you through setting up a script that starts your PPP
connection. You'll need to know what happens when you connect (does
your IP require you to log in? do they call you back? same thing you
provided to kppp). Go through the setup, and when you're done, you
should be able to run the script in
/usr/sbin/ppp-go
to start the PPP connection
and
/usr/sbin/ppp-off
to end the PPP connection.

Let us know how this goes. . .

well moses..ive already tried the whole ppp-go thing and it just says connect script failed when i try to use it.. when i type echo "atdt" /dev/modem it brings me back to the command line.. i also tried echo "atdt" /dev/ttyS1 and it says input/output error.. have any other ideas?

It's very important that you use the redirect after the atdt:

echo atdt > /dev/ttyS1

should give you the same result as

echo atdt > /dev/modem

if /dev/modem points to /dev/ttyS1.
If this is not the case, let's try figuring out what is wrong with /dev/ttyS1
since you seem sure that's where your modem is and you are getting an
error on something that should not give an error.

post the output of:
cat /proc/devices

Ok now when i type echo atdt /dev/ttyS1 it gives me the same thing as echo atdt /dev/modem ... heres the output of cat /proc/devices

Character Devices:
1 mem
2 pty
3 ttyp
4 ttyS
5 cua
7 vcs
10 misc
14 sound
21 sg
29 fb
109 lvm
128 ptm
129 ptm
136 pts
137 pts
162 raw

Block devices:
1 ramdisk
2 fd
3 ide0
7 loop
9 md
22 ide1
43 nbd
58 lvm


thats the output of cat /proc/devices

So, just to be clear, when you

echo atdt > /dev/ttyS1

it just returns with no error?

Good. This means the device isn't necessarily all funked up.

Now, let's try this:

echo "atdt#####" > /dev/ttyS1

where ##### is the number you would usually dial to connect to your ISP.
You should hear a dialtone (if you are connected to a phone line) for a
second, then hear the modem dialing the number, and possibly an
answer from the other modem. If you aren't connected to a phone line,
you'll get nothing.

What we're doing is just making sure the device (not the modem, but the
device "file" that linux sees) is working (well, OK, we're also checking that
the modem works).

If the other modem answers and you want to hang up:

echo "ath" > /dev/ttyS1

ok i did the echo "atdt12123592000" > /dev/ttyS1 when i did it it just brought me back to the command line..im hooked up to a fone line but it didnt dial anything ..