[hcflinux] Modem not responding after a program crash
Franki
frankieh at vianet.net.au
Sat Apr 27 16:33:47 EDT 2002
I had a wierd problem with wvdial, where I could not access the modem until
I restared X, (if it was running.)
thats a pain, but much easier then restarting the OS altogether..
I figured it had something to do with either wvdial X or devfs
try just restarting X and see what that does.. it only used to happen to me
if I killed wvdial while it was trying to dial..
and that was with a 56k serial external.
rgds
Frank
-----Original Message-----
From: hcflinux-admin at lists.mbsi.ca
[mailto:hcflinux-admin at lists.mbsi.ca]On Behalf Of Kara Alexandr
Sent: Friday, 26 April 2002 6:16 PM
To: hcflinux at lists.mbsi.ca
Subject: [hcflinux] Modem not responding after a program crash
Hi,
I have a SmartDDA modem (14F1:1056) and tried to connect.
The installation went OK, but when I first dialed using
wvdial, there were some errors (I don't remember exactly),
so I killed wvdial. After that, the modem didn't respond
to anything, even if nobody used /dev/modem (I checked
this using fuser -v ) and I wasn't able to remove the
module (saying that it is busy). However the driver wasn't
dead as it showed information in /proc/.../lastcallstatus.
After restarting the computer, it worked OK.
Should I try to reproduce the problem (and log everything) ?
Otherwise, thanks for the driver.
Alexandr Kara
_______________________________________________
hcflinux mailing list
hcflinux at lists.mbsi.ca
http://www.mbsi.ca/mailman/listinfo/hcflinux
More information about the hcflinux
mailing list