[hsflinux] Success and then failure

[Travis Fisher]

I'm trying to get the HSF linmodem driver working on my laptop, a compaq
presario 2100.  I've had quite a trip of it.  On my first try, everything
worked.  I'd just built my first self-compiled kernel (2.4.18 in a debian
woody base installation) and followed the from-source installation
instructions for the linmodem (hsflinmodem-5.03.27lnxtbeta03042700).
All went well, I set up a wvdial script, and connected to my ISP.  
...
Several hours later, after downloading some software and playing with a
lot of system settings, the modem disconnected.  And wouldn't
reconnect.  Trying to redial would throw a kernel oops.  Rebooting didn't
help.  So I tried recompiling the modem drivers, recompiling the
kernel.  No luck -- it oopses consistently.  

So then I rebooted to windows xp (I'm set up with a dual boot), and when I
tried to dial from windows I got a BSOD and immediate reset.  This has
never happened to me before.  Does this make sense -- is there state saved
in the modem that can be corrupted and survive a reboot?  ("hard" reboot
in the sense of power off for about 1 second).  

Anyway, I'm back in windows now, played around disabling and re-enabling
the modem and its working again here.  I'll try again tomorrow to get
things up on linux.  Any suggestions would be greatly appreciated.  If it
is of use for debugging, I can provide more details about how the drivers
crash in linux.

--Travis Fisher
p.s. windows calls the modem "Conexant 56K ACLink" and gives hardware ID
PCI\VEN_1059&DEV_5457&SUBSYS_002A103C&REV_00; I think the VEN and DEV are
the numbers that lspci returns though I don't have it written down...