[NBLUG/talk] hsf softmodem trouble

Dave Sisley dsisley at arczip.com
Fri Sep 12 20:41:01 PDT 2003


Hi, everybody.  In an effort to escape the vortex, it was suggested that I 
upgrade to RH9.  I balked, but decided to make the plunge afterall (actually, 
I went for a total, fresh install).  My X is looking great.

...But it broke my modem.

My desktop box is a dell with an HSF softmodem (according to windows, its a
Conexant SmartHSFi V92 56k DF PCI Modem).  RH9 runs on the 2.4.20-6 kernel, 
and I installed the kernel-source.

I have been to Linuxant for the appropriate driver.  It turns out they don't 
make one for this particular kernel.  In this case they recommend that you
install a generic RPM or tarball version and then run 'hsfconfig' so that it
can read the kernel-source and you should be up and running.  

FWIW, Linuxant has decided to 'license' the drivers.  This means that you must 
pay $15 for a full version, which is supposed to run at 56k.  The free trial 
version (that they recommend trying out first to check for compatibility) runs 
at 14k; I don't know if that's relevant. The driver install completes without 
any error messages (that I can see).

To cut to the chase: I can't get a dial tone on this thing.  Below are 
excerpts from /var/log/messages, dmesg, and 'modprobe /dev/modem'.  I think 
the important part is in /var/log/messages and modprobe, where it says something 
like:

"localhost insmod: /lib/modules/2.4.20-6/misc/someFile.o: init_module: No such device"

Does this mean there is a problem with the way hsfconfig is reading the 
kernel-source?  I'd be grateful for any input.

-dave.

/var/log/messages: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sep 12 19:04:35 localhost pppd[3665]: pppd 2.4.1 started by root, uid 0
Sep 12 19:04:35 localhost kernel: PCI: Found IRQ 3 for device 01:06.0
Sep 12 19:04:36 localhost kernel: ttySHSF0 at I/O 0xc400 (irq = 3) is a Conexant HSF softmodem
Sep 12 19:04:36 localhost insmod: /lib/modules/2.4.20-6/misc/hsfmc97ich.o: init_module: No such device
Sep 12 19:04:36 localhost 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 12 19:04:36 localhost insmod: /lib/modules/2.4.20-6/misc/hsfmc97via.o: init_module: No such device
Sep 12 19:04:36 localhost 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 12 19:04:36 localhost insmod: /lib/modules/2.4.20-6/misc/hsfmc97ali.o: init_module: No such device
Sep 12 19:04:36 localhost 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 12 19:04:37 localhost wvdial[3685]: WvDial: Internet dialer version 1.53 
Sep 12 19:04:37 localhost wvdial[3685]: Initializing modem. 
Sep 12 19:04:38 localhost wvdial[3685]: Sending: ATZ 
Sep 12 19:04:38 localhost wvdial[3685]: ATZ 
Sep 12 19:04:38 localhost wvdial[3685]: OK 
Sep 12 19:04:38 localhost wvdial[3685]: Modem initialized. 
Sep 12 19:04:38 localhost wvdial[3685]: Sending: ATDT5081185 
Sep 12 19:04:38 localhost wvdial[3685]: Waiting for carrier. 
Sep 12 19:04:38 localhost wvdial[3685]: ATDT5081185 
Sep 12 19:05:31 localhost wvdial[3685]: NO CARRIER 
Sep 12 19:05:31 localhost wvdial[3685]: No Carrier!  Trying again. 
Sep 12 19:05:31 localhost wvdial[3685]: Sending: ATDT5081185 
Sep 12 19:05:31 localhost wvdial[3685]: Waiting for carrier. 
Sep 12 19:05:32 localhost wvdial[3685]: ATDT5081185 
Sep 12 19:06:25 localhost wvdial[3685]: NO CARRIER 
Sep 12 19:06:25 localhost wvdial[3685]: No Carrier!  Trying again. 
Sep 12 19:06:25 localhost wvdial[3685]: Sending: ATDT5081185 
Sep 12 19:06:25 localhost wvdial[3685]: Waiting for carrier. 
Sep 12 19:06:25 localhost wvdial[3685]: ATDT5081185 
Sep 12 19:07:19 localhost wvdial[3685]: NO CARRIER 
Sep 12 19:07:19 localhost wvdial[3685]: No Carrier!  Trying again. 
Sep 12 19:07:19 localhost wvdial[3685]: Sending: ATDT5081185 
Sep 12 19:07:19 localhost wvdial[3685]: Waiting for carrier. 
Sep 12 19:07:19 localhost wvdial[3685]: ATDT5081185 

Excerpt from dmesg: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

cdrom: This disc doesn't have any tracks I recognize!
Intel 810 + AC97 Audio, version 0.24, 10:11:52 Feb 27 2003
PCI: Found IRQ 11 for device 00:1f.5
PCI: Sharing IRQ 11 with 00:1f.3
PCI: Sharing IRQ 11 with 01:05.0
PCI: Sharing IRQ 11 with 01:09.0
PCI: Setting latency timer of device 00:1f.5 to 64
i810: Intel ICH4 found at IO 0xe400 and 0xe000, MEM 0xee081000 and 0xee082000, IRQ 11
i810: Intel ICH4 mmio at 0xd0ed9000 and 0xd0edb000
i810_audio: Primary codec has ID 0
i810_audio: Audio Controller supports 6 channels.
i810_audio: Defaulting to base 2 channel mode.
i810_audio: Resetting connection 0
i810_audio: Connection 0 with codec id 0
ac97_codec: AC97 Audio codec, id: ADS116 (Unknown)
i810_audio: AC'97 codec 0 supports AMAP, total channels = 2
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
PCI: Found IRQ 3 for device 01:06.0
ttySHSF0 at I/O 0xc400 (irq = 3) is a Conexant HSF softmodem

/sbin/modprobe /dev/modem: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/lib/modules/2.4.20-6/misc/hsfmc97ich.o: init_module: No such device
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
/lib/modules/2.4.20-6/misc/hsfmc97ich.o: insmod /lib/modules/2.4.20-6/misc/hsfmc97ich.o failed
/lib/modules/2.4.20-6/misc/hsfmc97via.o: init_module: No such device
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
/lib/modules/2.4.20-6/misc/hsfmc97via.o: insmod /lib/modules/2.4.20-6/misc/hsfmc97via.o failed



More information about the talk mailing list