All of a sudden it won't initiate. I use modem lights in gnome, which just uses the ifup ppp0, ifdown ppp0 I think. At first modem lights just turned yellow like it was dialing, however the modem never initiated. Now it does nothing. If I do ifup ppp0 from command line it just sits there. Pretty much a newbie so be gentle.

Check your dev link. That is, go into your /dev directory and see that the link for /dev/modem points to the correct /dev/ttyS? (where "?" is a number, 0 for COM1, 1 for COM2,...)

Then see if you can actually dial out using the modem, open a term and run "minicom". Do a "ATDT 555-1212" and listen for the dialing.

Try it in Windows (I'm a sucker for a simple solution).

If it works in any of these tests, then it's a config problem and then we have to do some admin work.

Let us know what you find out.


It's not us, it's those pesky Moderators that are too rough.


John

okay......

I did
staterial /dev/cau1 and it returned 1 where appropriate so the modem is on ttyS1. That is strange because I know it was ttyS2 before.
/dev/modem points to ttyS1 which is where the modem is. I checked the settings of the modem, tried both ttyS1 and ttyS2 and got nothing. And minicom did dial out succesfully. So now what?

I guess I better throw in this bit of info to see if it helps. Kudzu is always telling me either it found my modem or it was removed. I always ignore it and it has never caused any problems. I tried ifup ppp0 and it says
"failed to activate ppp0 with error 5"

I tried searching on google but to no avail.

Have you tried reinitiating wvdial as root:

cp /etc/wvdial.conf /etc/wvdial.conf.bak &&
wvdialconf /etc/wvdial.conf

?
Bert

Error 5 is an input/output error and you got SIGHUP'ed (hungup on, not as in the phone, but the SIGnal).

http://www.google.com/linux?q=ppp0+%...&start=30&sa=N


According to this guy it's a failure to communicate with the serial port.

http://web.gnu.walfield.org/mail-arc...-May/0044.html


What does your /var/log/localmessages (and dmesg & messages) have to say?


And according to this guy, you don't need pppd anyways.

http://linux.umbc.edu/lug-mailing-li.../msg00393.html


Try connecting as root, and if that works, resetup your modem.


John

I was only able to dial out once with minicom, now it won't intialize the modem. Seems like this is going from bad to worse.

Okay, so it looks like it's a modem problem. Do you have a spare one that you can try out?

Before you do that, try swapping it back to the original interrupt. But I would probably start pricing a good USR unit.


John

but the modem works in windows.....

Oh, somehow I missed that detail

Did you try it on both COM1 (INT4), and COM2 (INT3) (don't forget the proper I/O ranges, 3F8 for COM1, 2F8 for COM2).

Don't forget about any board jumpers...

And did you try out bert's suggestion?


What does Windows show it as, and what is the make & model of the modem?


John

okay....I have it working in minicom now everytime. The modem is on ttyS2, IRQ 7, and it is COM3 and IRQ 7 in windows. I think I have it narrowed down to my wvdial.conf. Here are the contents if anyone sees anything screwy:

[Modem0]
Modem = /dev/ttyS2
Baud = 57600
SetVolume = 4
Dial Command = ATDT
Init1 = ATZ
FlowControl = CRTSCTS
[Dialer WsHost]
Username = yeah
Password = right
Phone = 555-1212
Stupid Mode = 1
Inherits = Modem0

If I try to reinitate wvdial.conf like Bert said, it does not communicate with the modem.
Both windows and Linux detect is as a USR 56k Voice INT PnP.
Looks like it is a USR3070, ISA card.

okay, problem fixed. It turns out that somehow the otherday when I was in the BIOS, my parrallel port was set to IRQ 7, the same as my modem. Well, I don't even use my parrallel port so I just disable dit and everything was fine. I also foind a pretty good howto on modems http://new.linuxnow.com/docs/content...dem-HOWTO.html

evem though it didn't directly solve the problem it had a lot of good info.

And thanks for all of your info.

Heh. The Bios, I didn't think of that... Sheesh...

You really should keep COM1 on INT4, and COM2 on INT3. It only matters if some poorly written software looks for the IRQ's there (for example some old sound card programs wanted the sound card to be on INT5).

But if it works, don't fix it...


John

Topic caught my eye as similar to one I am having. Special driver
got my Linmodem to work briefly with noise and all but then the
same prob as Glock Shooter on next root-login = Modem Lights
or X-netcfg "activate" seem to think they have done the connect
job but have not, and soundlessly. minicom says "OK" to AT
strings, but when ph-number added returns "NO CARRIER".
Because this a soft-Modem on ttySHSF0 the advice is that this is
not a normal port nor IRQ mixup. I would give it away at once,
of course, except for that brief hiccupless success immediately
after the install. Any clues for next test ?



Xstack