Howard,
Likely we can get you on line.
Though your ModemData.txt output:
Modem: PCTel Inc HSP56 MicroModem "
CLASS=0703
PCIDEV=134d:2189
SUBSYS=134d:1002
IRQ=21
SOFT=134d:2189.MC97
NEW=134d:1002
IDENT=slmodemd
Driver=snd-intel8x0m
is NOT fully correct.
When I fake your system with:
$ ./scanModem fake 134d:2189
the output includes:
PCIDEV=134d:2189
SUBSYS=some:thing
IRQ=fake
IDENT=slamr
and indeed, the slamr driver is needed for your modem. There is no
more "native" Pctel driver from the 134d:2189
chipset.
Please run:
$ bash -x ./scanModem 2>&1 | tee howard.txt
Then send me the howard.txt, enabling me to debug scanModem.
These results from your System:
======================
/device/modem symbolic link: lrwxrwxrwx 1 root root 6
2009-12-05 20:32 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10
2009-12-05 20:32 /dev/ttySL0 -> /dev/pts/0
/etc/modprobe.d/sl-modem-daemon.conf:install slamr modprobe
--ignore-install ungrab-winmodem ; modprobe --ignore-install slamr;
test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0
2>/dev/null && chgrp dialout /dev/slamr0)
==============
Show that the drivers installation was OK, and the the bootup
/etc/init.d/sl-modem-daemon scripts are working properly.
The install process may have already written a file /etc/wvdial.conf
If so edit in your personal infor and remove the symbols < > ; , using
$ sudo gedit /etc/wvdial.conf
There should be a line therein
Carrier Check = no
If /etc/wvdial.conf is not present, you can produce it with:
$ sudo wvdialconf
and due the edit as just described
After the edit, try a dialout with:
$ sudo wvdial
Note that between successive dialouts, it is necessary to restart the
driver with:
$ sudo /etc/init.d/sl-modem-daemon restart.
We do not have a success report under 2.6.31 kernels yet.
Rather there is a 2.6.30 success and 2.6.31 kernel failure report from
Antonio's SLackware Linux system
Thus we are interested in your case.
Don't both with gnome-ppp or orther network managers for know, as they
will obscure information better provided through wvdial.
MarvS
scanModem maintainer
On Sat, Dec 5, 2009 at 8:18 AM, Antonio Olivares
<olivares14031@xxxxxxxxx> wrote:
> Howard,
>
> In order to better diagnoze the situation, please send us
> ModemData.txt to list. If you have scanMidem and have run
> $ gunzip scanModem.gz
> $ chmod +x scanModem
> $ sudo ./scanModem
>
> and attach via email ModemData.txt.
>
> After this we can try to recommend some things to get it going or at
> least try to.
>
> Regards,
>
> Antonio
>
> On 12/4/09, Howard Mobley <hmobley@xxxxxxxxxxxxxxx> wrote:
>> Hello,
>>
>> I would like some help installing a Pctel HSP56 MicroModem on Ubuntu 9.10. I
>> followed the instructions on the Ubuntu website for "Identifying your
>> modem," and "Connecting with a modem." I downloaded the scanModem program.
>> But when I tried to download the gnome-network-admin package from there, it
>> wouldn't connect to anything. So I got it from somewhere else. Its version
>> gnome-network-admin_2.28_Oubuntu_i386.deb. I think this may be part of the
>> problem. When I go to System-Administration-Network, and follow the
>> numbered instructions, there's a problem when I get to #6 Choose Serial
>> Modem from the Connection Type drop down. There's nothing there. Nothing in
>> the box.
>>
>> Also at step #12 Select the DNS tab, there IS no DNS tab. Doesn't exist.
>>
>> Now on the scanModem report, it said I needed the wvdial package, so I
>> downloaded a whole bunch of files, and got that working. (I think.) I also
>> tried the Gnome PPP thing. I've tried all kinds of things and gotten pretty
>> close to getting it to work, but something is missing, and it's making me
>> very frustrated. I need some help.
>>
>> Also this is a home built computer, with a 2.4 ghz Pentium 4, Intel
>> motherboard, 512 ram, 80 gig HD which is partitioned in half with Ubuntu on
>> one and Windows XP with the modem working, on the other half. I also have a
>> 20 gig HD installed that I use to swap files between them with.
>>
>> The Scanmodem report has changed somewhat as I've gone along, but I saved
>> all of them I think. I've done everything it said to do as much as I can
>> understand it. Installed the Smartlink slamr.ko driver. Then it said
>> "slmodemd missing." So I installed that seperately. I had it recognizing the
>> thing, but kept running into various obstacles. Anyway, I need some help
>> here. I'm ready to give up on this and Linux in general.
>>
>> Thanks,
>>
>> Howard Mobley
>>
>>
>
