[hcflinux] Modem will not Initialize - Modprobe: Can't locatemodule hcfpcihw

[Norbert Hoeller]

----- Original Message ----- 
From: "Linuxant support" <support at linuxant.com>
To: "Norbert Hoeller" <nhoeller at primus.ca>; <hcflinux at lists.linuxant.com>
Sent: Wednesday, December 03, 2003 9:46 AM
Subject: Re: [hcflinux] Modem will not Initialize - Modprobe: Can't
locatemodule hcfpcihw


> Hi,
>
> please verify if the modules are listed when you run the following
commands.
>
> modprobe --list
> depmod --verbose
>
> You can append " | grep hcf" to the commands to see only the lines with
> "hcf" in them.
>
> Also, please send us the output from "ls -la
/lib/modules/`uname -r`/misc".
>
> Regards,
>
> Jean-Simon Durand
> Technical specialist / Linuxant
> www.linuxant.com
> support at linuxant.com
>
>
> ----- Original Message ----- 
> From: "Norbert Hoeller" <nhoeller at primus.ca>
> To: <hcflinux at lists.linuxant.com>
> Sent: Wednesday, December 03, 2003 8:14 AM
> Subject: [hcflinux] Modem will not Initialize - Modprobe: Can't
locatemodule
> hcfpcihw
>
>
> I have been using a GVC/Rockwell 127A/1023 PCI modem in an IBM 300PL with
> Windows for some time.  I installed RedHat Linux
(linux-i686(i686)-2.4.20-8
> RedHat-9) and purchased a full version of the HCF modem driver
> (1.00lnxt03112100full).  I was able to dial to my local ISP without any
> special configuration of the modem (i.e. initialization strings) - in
fact,
> connect speed improved from 48Kbps to 57.6Kbps.
>
> I lose outbound IP connectivity periodically.  I usually end up rebooting
> Linux in an attempt to recover.  At this point, I frequently cannot get
the
> modem to dial out (using demand/auto dial).  'lsmod' does not show any HCF
> modules loaded.  'modprobe hcfpcihw' fails with the error "Can't locate
> module hcfpcihw".  Running 'hcfpciconfig' returns the error 'hcfpci driver
> not active'.
>
> I have been able to get things working again by uninstalling and
> re-installing the driver.  The problemappeared on Monday - Linux reboots
as
> well as shutdown/power off/power on/ reboot did not make any difference.
I
> went back to Windows, and noticed on Tuesday when I switched to Linux for
> more problem determination that the problem had cleared up by itself.
> However, it reappeared within about two hours of usage.
>
> Any ideas on what I should do next to diagnose the problem?  I have
attached
> a --dumpdiag after a failure.  I will get a similar --dumpdiag while modem
> is working and compare the two.  I don't see anything obvious in
> /var/log/messages, other than the modprobe error (and a few problems
loading
> some 'char-major-xxx' modules).
>     Thanks, Norbert
>
>