Shannon, Put in the PCtel modem , and run scanModem again. It will advise on the software to test with. These modems are supported by Pctel software PCI ID (x) Name Chip(set) HAL ~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~ 134d:7890 PCtel HSP MicroModem 56 PCT789T-C1 pct789 134d:7891 PCtel HSP MicroModem 56 PCT 789T pct789 134d:7892 PCtel HSP MicroModem 56 PCT 789T-A pct789 134d:7893 PCtel HSP MicroModem 56 S911 K017 pct789 134d:7894 PCtel HSP MicroModem 56 FT13 pct789 134d:7895 PCtel HSP MicroModem 56 PCT789T-C1 pct789 134d:7896 PCtel HSP MicroModem 56 PCT789T-C1 pct789 134d:7897 PCtel HSP MicroModem 56 PCT789T pct789 13f6:0211 C-Media CM8738 CM8738 cm8738 while the HSP56 MicroModem 688T have support through the Smartlink software, slamr.ko driver plus slmodemd helper. MarvS 2009/4/12 Antonio Olivares <olivares14031@xxxxxxxxx>: > Shannon, > > I see more or less what is happening, and there is not much I guess > that we can do? > > Apr 12 14:15:19 ubuntu-barb kernel: [ 117.559208] slamr: SmartLink AMRMO modem. > Apr 12 14:15:19 ubuntu-barb kernel: [ 117.559355] slamr: probe > 10b9:545a ALI545A card... > Apr 12 14:15:19 ubuntu-barb kernel: [ 117.559396] slamr 0000:00:0e.0: > PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10 > Apr 12 14:15:19 ubuntu-barb kernel: [ 117.559805] slamr: slamr0 is > ALI545A card. > Apr 12 14:17:31 ubuntu-barb kernel: [ 249.691273] slmodemd[3254]: > segfault at 0 ip 0806653c sp bfd88300 error 6 in > slmodemd[8048000+ef000] > > The bottom line: > tells it all: > Apr 12 14:17:31 ubuntu-barb kernel: [ 249.691273] slmodemd[3254]: > segfault at 0 ip 0806653c sp bfd88300 error 6 in > slmodemd[8048000+ef000] > > Something like this is hard to fix? Don't know what to advice. If > you reboot and do the same steps, does this happen every time, or only > once? > > Regards, > > Antonio > > 2009/4/12 Shannon VanWagner <shannon.vanwagner@xxxxxxxxx>: >> So I tried the extra Init2 strings that were mentioned earlier and I'm >> not having any luck getting connected. >> >> The modem clicks, dials, and opens up some type of transmission (as >> heard when picking up a phone), but then it just disconnects before >> ever creating a pppd. >> >> Something I noticed is that the only way I can trigger the creation of >> the /dev/ttySL0 is to execute these commands: >> sudo /etc/init.d/sl-modem-daemon stop >> sudo modprobe ungrab-winmodem >> sudo modprobe slamr >> sudo rm -rf /dev/slamr0 >> sudo mknod -m 600 /dev/slamr0 c 242 0 >> sudo slmodemd -c USA /dev/slamr0 & >> >> >> I also thought that maybe there was a problem using guest as user and >> password as password (these are the required values from >> nocharge.com), so I made the changes outlined at: >> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03815.html >> Still no luck. >> >> >> I also tried running an strace to see what sort of output would come >> of that - not sure if I did it right (see attached file: >> wvdial_test.txt) >> >> I've also attached some other output from the /var/log/messages and >> dmesg and what showed on the terminal when I tried the wvdial. >> >> Something I also notice is that the modem holds the line and never >> hangs up unless I reboot the machine. >> >> I'm beginning to wonder if there's something wrong with this modem. >> >> >> Are there any other suggestions for me to try? I was going to try the >> /etc/modprobe.d/modprobe.conf trick that was mentioned but I wasn't >> sure of the exact syntax and the file doesn't exist (perhaps you could >> put the appropriate contents in a file and send it to me?). >> >> I also have two other PCI modems here that I can try again (I did >> before and they didn't seem any easier to setup): >> PCTEL >> AGERE >> >> I have internet access via a USB wireless (named prism as you'll see >> in the attached files), but I'm trying to make the modem work and be >> setup so I can give this computer to a neighbor and new-Linux-convert. >> >> The service I'm trying to connect with is called nocharge.com and it's >> in Seattle WA. >> >> Any help is appreciated! >> >> Thanks very much!! >> >> >> Shannon VanWagner >> humans enabled >> >> On Sun, Apr 12, 2009 at 7:16 AM, Marvin Stodolsky >> <marvin.stodolsky@xxxxxxxxx> wrote: >>> Ahmed, >>> >>> RE: suggested that each of slamr/slusb code could be split into two >>> further modules (one that is GPL >>> --------- >>> Some history here is worth reporting. >>> >>> The Smartlink driver once was unitary. After someone with Mandrake >>> several years ago (forgot his name) suggested a split into the slamr >>> driver and non-driver slmodemd, maintainer Sasha Khapyorsky >>> enthusiastically adopted it. This also contributed to the current >>> service of slmodemd for non-Smartlink hardware, through >>> complementation of ALSA modem drivers. >>> >>> In the support of Lucent/Agere/LSI winmodems with a digital signal >>> processing "DSP" chip, Alexei Chentsov did a similar split, with >>> consequence that upon loading of the driver, a /dev/pts/N is created , >>> with complementation by a non-driver martian_modem helper. I'm not >>> significantly competent in COMM or C code, but perhaps the martian >>> code at http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ >>> would provide some guide in further shiifting the port creation >>> capability from slamr into an Open Source component. >>> >>> Among the winmodems various only the SmartLink code is to the best of >>> my knowledge capable of supporting multiple winmodems on the same host >>> PC, though I cannot recall whether this also extends to the >>> non-Smartlink harder supported by ALSA drivers plus slmodemd. >>> >>> Some years ago there was some experimentation with the DSP chip >>> modems, to asses if multiple modems could be managed on one host PC. >>> This ultimate failed, because the CPU did not separate the data >>> streams for the different modems. Also Agere staff informed us that >>> such sophistication had never been intended for the "consumer" ltmodem >>> code, and recommended hardware/controller chipset modems for such >>> multimodem services. >>> >>> MarvS >>> >>> On Sun, Apr 12, 2009 at 1:45 AM, أحمد المحمودي >>> <aelmahmoudy@xxxxxxxxxxxxxxxxxxxxx> wrote: >>>> On Sat, Apr 11, 2009 at 11:45:52PM -0500, Antonio Olivares wrote: >>>>> The code exists, although I am not sure whether it is appropriate or >>>>> not within GPL. The device node gets created if the following is >>>>> placed in /etc/modprobe.d/modprobe.conf >>>>> >>>>> Within /etc/modprobe.conf files: >>>>> /etc/modprobe.d/modprobe.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 uucp /dev/slamr0) >>>>> >>>>> That will create the device nodes and appropriate permissions to dialout. >>>> ---end quoted text--- >>>> >>>> That used to exist in the slmodem Debian package indeed, yet Ubuntu >>>> developers removed it. >>>> >>>> Yet this line only creates one device (which I think will be for just >>>> 1 modem), let's suppose that a machine got 2 modems, this >>>> modprobe.conf line won't create the device for the 2nd modem. I think >>>> there is a way that would create the appropriate device if a correct >>>> udev rule (and probably some supporting code in the module) is made. >>>> >>>> Yet maybe that won't work if the MODULE_LICENSE isn't GPL. >>>> >>>> Which made me make some experiment a couple of weeks ago: I changed >>>> the MODULE_LICENSE to GPL (Not Dual BSD/GPL), but GPL, and compiled >>>> slmodem, and used the slamr device, I noticed that I got extra output >>>> from udevadm when I did this, but the kernel freezed after that, so I >>>> didn't bother to try again, since that won't be legal to distribute >>>> anyways. >>>> >>>> -- >>>> أحمد المحمودي (Ahmed El-Mahmoudy) >>>> Digital design engineer >>>> GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net) >>>> GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C 156E D325 C3C8 9DCA 0B27 >>>> >>> >> >
