i have redhat 9 running on a dell inspiron 8200, and i've been searching linux questions as well as googling but still no results.

i installed RH9 and got modem drivers from linuxantDOTcom got the correct drivers and had dial up to my ISP working for some time. using up2date i upgraded the kernel to 2.4.20-20.9, i removed the old modem drivers (rpm) and installed the new drivers (hsfmodem-6.03.00lnxt03030800free_k2.4.20_20.9-1rh.i686.rpm) from the same place (linuxantDOTcom) for the new kernel version. now i can not dial up to my ISP.

after installing the new drivers i ran "hsfconfig"

here is the log when i try to connect to my ISP:

************start capture********************
Sep 10 22:27:32 firefly xinetd[3030]: removing time
Sep 10 22:27:32 firefly xinetd[3030]: removing time
Sep 10 22:27:33 firefly xinetd[3030]: xinetd Version 2.3.11 started with libwrap loadavg options compiled in.
Sep 10 22:27:33 firefly xinetd[3030]: Started working: 1 available service
Sep 10 22:27:38 firefly modprobe: modprobe: Can't locate module char-major-188
Sep 10 22:27:39 firefly last message repeated 15 times
Sep 10 22:27:40 firefly rhnsd[3186]: Red Hat Network Services Daemon starting up.
Sep 10 22:27:43 firefly modprobe: modprobe: Can't locate module char-major-226
Sep 10 22:27:43 firefly last message repeated 3 times
Sep 10 22:28:08 firefly modprobe: modprobe: Can't locate module sound-service-0-0
Sep 10 22:30:03 firefly ifup-ppp: pppd started for ppp0 on /dev/modem at 460800
Sep 10 22:30:03 firefly pppd[3489]: pppd 2.4.1 started by root, uid 0
Sep 10 22:30:05 firefly insmod: /usr/lib/hsfmodem/modules/binaries/i686/rh/linux-2.4.20-20.9/hsfpcibasic2.o: init_module: No such device
Sep 10 22:30:05 firefly insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Sep 10 22:30:05 firefly insmod: /usr/lib/hsfmodem/modules/binaries/i686/rh/linux-2.4.20-20.9/hsfmc97via.o: init_module: No such device
Sep 10 22:30:05 firefly insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Sep 10 22:30:05 firefly insmod: /usr/lib/hsfmodem/modules/binaries/i686/rh/linux-2.4.20-20.9/hsfmc97ali.o: init_module: No such device
Sep 10 22:30:05 firefly insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Sep 10 22:30:06 firefly wvdial[3509]: WvDial: Internet dialer version 1.53
Sep 10 22:30:06 firefly wvdial[3509]: Initializing modem.
Sep 10 22:30:06 firefly wvdial[3509]: Sending: ATZ
Sep 10 22:30:06 firefly wvdial[3509]: ATZ
Sep 10 22:30:06 firefly wvdial[3509]: OK
Sep 10 22:30:06 firefly wvdial[3509]: Sending: ATM2
Sep 10 22:30:06 firefly wvdial[3509]: ATM2
Sep 10 22:30:06 firefly wvdial[3509]: OK
Sep 10 22:30:06 firefly wvdial[3509]: Modem initialized.
Sep 10 22:30:06 firefly wvdial[3509]: Sending: ATDT7140020
Sep 10 22:30:06 firefly wvdial[3509]: Waiting for carrier.
Sep 10 22:30:07 firefly wvdial[3509]: ATDT7140020
Sep 10 22:31:06 firefly wvdial[3509]: NO CARRIER
Sep 10 22:31:06 firefly wvdial[3509]: No Carrier! Trying again.
Sep 10 22:31:06 firefly wvdial[3509]: Sending: ATDT7140020
Sep 10 22:31:06 firefly wvdial[3509]: Waiting for carrier.
Sep 10 22:31:07 firefly wvdial[3509]: ATDT7140020
Sep 10 22:31:42 firefly wvdial[3509]: CONNECT 38400
Sep 10 22:31:42 firefly wvdial[3509]: Carrier detected. Chatmode finished.
Sep 10 22:31:42 firefly pppd[3489]: Serial connection established.
Sep 10 22:31:42 firefly pppd[3489]: Using interface ppp0
Sep 10 22:31:42 firefly pppd[3489]: Connect: ppp0 <--> /dev/modem
Sep 10 22:32:13 firefly pppd[3489]: LCP: timeout sending Config-Requests
Sep 10 22:32:13 firefly pppd[3489]: Connection terminated.
Sep 10 22:32:13 firefly pppd[3489]: Hangup (SIGHUP)
Sep 10 22:32:13 firefly pppd[3489]: Exit.

****************end capture**********************

i've been searching the net for info on "LCP: timeout sending Config-Requests" and i found that i'm not alone but no answers on solving the issue. i've also noticed that every time i start to dial up the first attempt fails with NO CARRIER error, then the next attempt goes until the LCP: timeout. after that all attempts fail with the timeout issue.

any help would be great.