Red Hat Linux 2.4.20-8, modem problem

[avimit]

HI All,
I am getting problems in getting linux hooked up with internet.
I have external as well as internal modems on my PC(which is a dual boot) with Red-Hat linux. 2.4.20-8 kernal.
I have managed to dial ISP access number, and got the typical noise, which usually is observed when a dial up connection is made.
I am using 'wvdial'.
Everything seems fine, but just after that typical noise, I see error messsage:
'NO CARRIER'
I tried to install a new driver for modem. But the web site ftp://ftp.smlink.com/linux/unsupported gave me C source codes for the drivers which I was not able to compile in my red-hat linux.
Any body to help me out?
I know Guvenc Gulce had the exact problem, and he managed to run his internet after all, hey Gulce, can you help me? how did you managed to compile the source code of the drivers.

Kr,
Aviral Mittal.

[Steven E. Protter]

An itrc search or look at http://tldp.org will probably yeild you instructions on how to compile the drivers.

A simpler answer in the world of $15 modems is to buy one on the compatability list and use that.

Based on time benefit analyis thats what I'd do. I'm driving by the computer store and may post a certified modem or two with the price.

SEP

[Bruce Copeland]

Aviral,

If you're using a US Robotics external modem (mentioned in another thread) and you can get the modem to dial and attempt handshaking (audio noise), I really doubt you have a driver problem. It's more likely that there is something wrong with your logon configuration for your ISP.

The time-honored way to test modem hardware under Linux is with the minicom communications program. It's a command line interface, but you shouldn't have much trouble setting it up to dial your ISP. You can then logon manually. If your logon is successful, you then know that you don't have a hardware/driver problem. At that point, we can then move on to helping you set up your wvdial PAP/CHAP configuration correctly.

Try it.

Bruce

[Vernon Brown_4]

Your U.S. Robotics modem will probably be supported with drivers for Linux. If you can't compile C source you could search for .rpm packaged drivers.

To compile C source you need to have installed the gcc development options in your Linux install. If you have that installed you just get the source out of its tarball:

tar xf the-tar-file-you-downloaded

or

tar xfz the-.gz-tarball

A README file will usually be in the package and explain how you compile it. Usually it is simply:

make
make install

Vern

[avimit]

Hi, All,
thanks for your help. I was able to get .rpm file, and I installed the driver successfully. My earlier problem has gone, but new ones have come. This time I am usning Internal Modem. and I dwonloaded the driver from http://www.linuxant.com...
Here is the message I get
----------------------------------
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT0845 6042086
--> Waiting for carrier.
ATDT0845 6042086
CONNECT 115200
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sun May 23 22:28:32 2004
--> pid of pppd: 3577
--> Disconnecting at Sun May 23 22:28:36 2004
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconnect will be attempted in 5 seconds

-----------------------------------------------

[Vernon Brown_4]

There are scripts in /etc/ppp that control the auto-connect. You probably need to tweak the config scripts. If I remember; it seems that you might need to look at pppoe.conf and pap-secrets. Some comments in pppoe.conf can help.

In my case, the GUI setup for pap-secrets didn't work. I had to edit the file and enter the login name and password. There were several entries appended by the GUI that I had to remove to make it work.

Vern

[avimit]

HI All,
Thanks very much for all your help, I am able to connect to internet using linux, and I am writing this message with linux connected net :)
Kr,
Avi

[Pashmina]

Hi,
I am also facing the same problem of :
"The PPP daemon has died (exit code = 16)".
Can you pls tell me how you solved that problem?
Thanks.

[avimit]

I can help you with it, but you will have to let me know what modem are you using and what driver are you using and also what linux are you using.
Are you familiar with wvdial etc.?

[Pashmina]

Hi,
The Linux version is Red Hat 8.1 AS.
As for the modem and its driver, am not sure whether the problem is because of that. Actually a number of controller devices are connected to the modem. And am able to connect via wvdial to some of the controllers and for some, its giving me this problem.
As for wvdial, I have a fair idea of it.

Thanks.

[Pashmina]

Hi
Am gettin the problem of 'PPP daemon has died! (exit code = 16)'.
With the same modem am able to connect to another devices.Also this device can be accessed using windows OS and the IE explorer.

The Os am using is Red Hat 8.1 AS
WvDial: Internet dialer version 1.41
Modem and Driver info
Name : dgdm Relocations: (not relocateable)
Version :1.1 Vendor: Digi International
Release : 1
Group : Applications/Communications Source RPM: dgdm-1.1-1.src.rpm
Size :4336344 License: GPL
Packager:Scott Kilau
URL : http://www.digi.com/
Summary : The Dense Modem Drivers and System Software
Description :
This packages contains the device drivers and the supporting management
applications for the following Digi International adapter families:
Digi DataFire RAS
Digi DataFire DSP cPCI
Digi AccelePort RAS
Digi AccelePort Xp

modinfo /lib/modules/2.4.9-e.3smp/misc/dgdm.o
filename:/lib/modules/2.4.9e.3smp/misc/dgdm.o
description: "Driver for dxb2 based product line"
author: "Digi International, http://www.digi.com"
license: "GPL"
parm: indevice string
parm: outdevice string
parm: printdevice string
parm: specdevice string
parm: ramdevice string
parm: dspramdevice string
parm: flashdevice string
parm: vpdalldevice string
parm: iodevice string
parm: regdevice string
parm: gdbdevice string
parm: dmabufdevice string
parm: rawdxbdevice string
parm: major int, description "Default major number"
parm: tty int, description "Run as tty (Serial and Callout) driver"
parm: print int, description "Enable Transparent Print"
parm: control int, description "Register Control devices"
parm: isdn int, description "Run as an ISDN driver"
parm: debug int, description "Driver debugging level"
parm: rawreadok int, description "Bypass flip buffers on input"
parm: cook_size int, description "Size of each channels LD cook buffer"
parm: loopback int, description "All tty channels are loopbacks"
parm: intr_period int, description "Period for interrupts"
parm: polling int, description "Poll boards instead of using interrupts"
parm: download int, description "If not set, we do not download the FEP"
parm: gdb int, description "If set, we are trying to GDB very early"
parm: dxb_align int, description "If set, force alignment of DXB struct"
parm: print_waits int, description "If set, FEP will wait when print buf full"
parm: erase_nvm int, description "If set, FEP will erase NV parms at start"
parm: rxbufsize int, description "Drv rx dxb (not flip) buf size. Power of 2."
parm: trcbuf_size int, description "Debugging trace buffer size. 1M default."
parm: latency int, description "Set the LD low latency flag,"
parm: alt_fail_open int, description "Enable alternate failed open behavior"
parm: fillmem long, description "Fill memory with value before loading FEP"
parm: dxbttyname string, description "Name of DXB serial device"
parm: usrlibdir string, description "Directory where firmware is located"
What can be done to solve this?

[Pashmina]

hey one correction am using Red Hat Linux Advanced Server release 2.1AS/i686 (Pensacola)