Roland, Try changing in /etc/wvdial.conf to: Init2 = ATQ0 V1 E1 L3 M1 S0=0 &C1 &D2 +MS=34 # Stupid Mode = yes Should this compensation for poor line quality work, next try Init2 = ATQ0 V1 E1 L3 M1 S0=0 &C1 &D2 +MS=90 for higher speed. The default is +MS=92 , but is known to be faulty as implemented at some IPs Also you should read in detail Jacques PostIntall Howto, accessed off http://linmodems.technion.ac.il/ The emerging usages of /dev/pts/N ports was I recall, advocated my Linus Torvalds, addressing general issues of device ports. Eventually it is expected that kernel experts will promote the /dev/pts/N ports to Sound Competence But until then, there is no option but to add Carrier Check = no for any modem using a /dev/pts/N port. This includes the Mars/Apollo chipset modems from Lucent using the martian_dev driver the Smartlink chipset modems, and the many modems using slmodemd + one of the ALSA modem drivers (snd-intel8x0m, snd-atiipx-modem, snd-via82xx-modem or snd-hda-intel) This is NOT a modem issue per se, it is a kernel development issue. Many members of this List are happily thus using Carrier Check = no This includes Trevor, who reporting success usage of Smartlink chipset modem on Karmic Incidentally, there was no support of your Motorola chipset modem at all, until Zello experimented. He tried adding init recognition for your 1057:3052 chipset to the slamr code. Possible there are changes under the 2.6.31 Karmic code which will fault the support enjoyed under past kernels for the Motorola 1057:3052 chipset. But alternatively, a solution to the problem may be found. If the guidance above doesn't help, there are a few other things to try. For example, we have had cases where a change to a non Ubuntu kernel solves the problem, But try simpler things first. Lastly, after each dialout try, you should kill slmodemd. Unload slamr and ungrab-winmodem Then per the script, reload the drivers and slmodemd setup. This is necessary because there was a KERNEL code change some versions back, which bars successive dialouts through the slamr driver You might also get some details on the failure on your System by generating a log file with: $ sudo slmodemd -c USA --debug=2 --log /dev/slamr0 MarvS On Fri, Oct 9, 2009 at 10:32 AM, Roland Hughes <roland@xxxxxxxxxxxxxxxxxxxx> wrote: > Marv, > > As I said. > > roland@logikaldesktop:~$ sudo wvdial > [sudo] password for roland: > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 L3 M1 S0=0 &C1 &D2 +FCLASS=0 > ATQ0 V1 E1 L3 M1 S0=0 &C1 &D2 +FCLASS=0 > OK > --> Modem initialized. > --> Sending: ATDT16302051593 > --> Waiting for carrier. > ATDT16302051593 > NO CARRIER > ERROR > --> No Carrier! Trying again. > --> Sending: ATDT16302051593 > --> Waiting for carrier. > ATDT16302051593 > NO CARRIER > ERROR > --> No Carrier! Trying again. > --> Sending: ATDT16302051593 > --> Waiting for carrier. > ATDT16302051593 > NO CARRIER > > > roland@logikaldesktop:~$ cat /etc/wvdial.conf > > [Dialer Defaults] > Init1 = ATZ > Init2 = ATQ0 V1 E1 L3 M1 S0=0 &C1 &D2 +FCLASS=0 > Stupid Mode = yes > Modem Type = Analog Modem > ISDN = 0 > New PPPD = yes > Phone = 16302051593 > Modem = /dev/ttySL0 > Username = nobody > Carrier Check = no > Password = nothing > Baud = 460800 > > > > On Friday 09 October 2009 06:06:39 am you wrote: >> Roland >> >> WIth make_modem2.sh >> mknod -m 660 /dev/slamr0 c 242 0 >> mknod chgrp dialout /dev/slamr0 >> modprobe ungrab-winmodem >> modprobe slamr >> slmodemd -c USA /dev/slamr0 >> >> Try: >> $ sudo ./make_modem2.sh >> >> Then open a 2nd console or TAB for the: >> $ sudo wvdialconf >> >> MarvS >> >> On Thu, Oct 8, 2009 at 11:15 PM, Roland Hughes >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> > Marv, >> > >> > Here is the file you requested. Even if you tweak something to make this >> > manua process work (which I doubt given the NO CARRIER issues) I'm not >> > going away until sl-modem works for all Karmic users automatically. >> > >> > >> > roland@logikaldesktop:~$ cat make_modem.sh >> > sudo mknod -m 660 /dev/slamr0 c 242 0 >> > sudo mknod chgrp dialout /dev/slamr0 >> > sudo modprobe ungrab-winmodem >> > sudo modprobe slamr >> > sudo slmodemd -c USA /dev/slamr0 >> > sudo wvdialconf wvtest >> > roland@logikaldesktop:~$ >> > >> > On Thursday 08 October 2009 06:43:16 pm you wrote: >> >> Send me your make_modem.sh >> >> >> >> On Thu, Oct 8, 2009 at 9:25 AM, Roland Hughes >> >> >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> > Marv, >> >> > >> >> > I admire your diligence on this, but without an actual fix from an >> >> > actual developer, getting wvdial to find my modem is of little use. >> >> > Nothing got around the NO CARRIER bug which meant I couldn't dial. >> >> > >> >> > results below: >> >> > ========================= >> >> > roland@logikaldesktop:~$ jed make_modem.sh >> >> > roland@logikaldesktop:~$ ./make_modem.sh >> >> > [sudo] password for roland: >> >> > mknod: missing operand after `/dev/slamr0' >> >> > Try `mknod --help' for more information. >> >> > SmartLink Soft Modem: version 2.9.11 Sep 14 2009 00:37:09 >> >> > symbolic link `/dev/ttySL0' -> `/dev/pts/4' created. >> >> > modem `slamr0' created. TTY is `/dev/pts/4' >> >> > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. >> >> > atdt 16302051593 >> >> > ^CEditing `wvtest'. >> >> > >> >> > Scanning your serial ports for a modem. >> >> > >> >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >> >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >> >> > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >> >> > Modem Port Scan<*1>: S1 S2 SL0 >> >> > >> >> > >> >> > Sorry, no modem was detected! Is it in use by another program? >> >> > Did you configure it properly with setserial? >> >> > >> >> > Please read the FAQ at http://open.nit.ca/wiki/?WvDial >> >> > >> >> > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. >> >> > >> >> > On Thursday 08 October 2009 07:37:02 am you wrote: >> >> >> Roland >> >> >> >> >> >> Apologies. I copied from a line: >> >> >> /bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null >> >> >> and accidentally carried the last 2. That command line for your case >> >> >> should be: mknod -m 660 /dev/slamr0 c 242 0 >> >> >> >> >> >> Long day yesterday. >> >> >> >> >> >> Marvin >> >> >> >> >> >> On Wed, Oct 7, 2009 at 11:18 PM, Roland Hughes >> >> >> >> >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> >> > Marv, >> >> >> > >> >> >> > I'm not a complete idiot. >> >> >> > >> >> >> > roland@logikaldesktop:~$ sudo mknod -m 660 /dev/slamr0 c 242 0 2 >> >> >> > [sudo] password for roland: >> >> >> > mknod: extra operand `2' >> >> >> > Try `mknod --help' for more information. >> >> >> > roland@logikaldesktop:~$ >> >> >> > >> >> >> > I'm running Karmic, things are different here. sudo worked just >> >> >> > fine, the problem is the 2 dangling at the end. Once again. They >> >> >> > changed a lot of structures in this release, particularly when it >> >> >> > comes to user identity and security. That's why the Intel drivers >> >> >> > won't compile. >> >> >> > >> >> >> > On Wednesday 07 October 2009 09:06:28 pm you wrote: >> >> >> >> Roland, >> >> >> >> >> >> >> >> sudo can be used from the COMMAND prompt but not in a shell >> >> >> >> script. Use for make_modem.sh >> >> >> >> mknod -m 660 /dev/slamr0 c 242 0 2 >> >> >> >> mknod chgrp dialout /dev/slamr0 >> >> >> >> modprobe ungrab-winmodem >> >> >> >> modprobe slamr >> >> >> >> slmodemd -c USA /dev/slamr0 >> >> >> >> sleep 1 >> >> >> >> wvdialconf wvtest >> >> >> >> >> >> >> >> $ sudo chmod +x make_modem.sh >> >> >> >> $ sudo ./make_modem.sh >> >> >> >> >> >> >> >> MarvS >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Oct 7, 2009 at 8:34 PM, Roland Hughes >> >> >> >> >> >> >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> >> >> > Marv, >> >> >> >> > >> >> >> >> > I appreciate your efforts, but unless you have Karmic running >> >> >> >> > there to test with, they are probably not going to help. >> >> >> >> > Results of your latest advice can be found below the line of >> >> >> >> > ===. >> >> >> >> > >> >> >> >> > Nothing has ever gotten around the NO CARRIER problem, I mean >> >> >> >> > nothing. >> >> >> >> > >> >> >> >> > I'm really trying to focus on fixing the bug with date keys that >> >> >> >> > xBaseJ has right now so I can finish writing the last 130 pages >> >> >> >> > of the book. Once I have that problem done and the Fuel >> >> >> >> > Surcharge thing written, I can spend some of my free time >> >> >> >> > looking into fixing one of the modem things. >> >> >> >> > >> >> >> >> > >> >> >> >> > =========================== >> >> >> >> > roland@logikaldesktop:~$ cat make_modem.sh >> >> >> >> > sudo mknod -m 660 /dev/slamr0 c 242 0 2 >> >> >> >> > sudo mknod chgrp dialout /dev/slamr0 >> >> >> >> > sudo modprobe ungrab-winmodem >> >> >> >> > sudo modprobe slamr >> >> >> >> > sudo slmodemd -c USA /dev/slamr0 >> >> >> >> > sudo wvdialconf wvtest >> >> >> >> > >> >> >> >> > >> >> >> >> > roland@logikaldesktop:~$ ./make_modem.sh >> >> >> >> > [sudo] password for roland: >> >> >> >> > mknod: extra operand `2' >> >> >> >> > Try `mknod --help' for more information. >> >> >> >> > mknod: missing operand after `/dev/slamr0' >> >> >> >> > Try `mknod --help' for more information. >> >> >> >> > error: mdm setup: cannot stat `/dev/slamr0': No such file or >> >> >> >> > directory error: cannot setup device `/dev/slamr0' >> >> >> >> > Editing `wvtest'. >> >> >> >> > >> >> >> >> > Scanning your serial ports for a modem. >> >> >> >> > >> >> >> >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 >> >> >> >> > baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: >> >> >> >> > 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, >> >> >> >> > giving up. Modem Port Scan<*1>: S1 S2 >> >> >> >> > >> >> >> >> > >> >> >> >> > Sorry, no modem was detected! Is it in use by another program? >> >> >> >> > Did you configure it properly with setserial? >> >> >> >> > >> >> >> >> > Please read the FAQ at http://open.nit.ca/wiki/?WvDial >> >> >> >> > >> >> >> >> > If you still have problems, send mail to >> >> >> >> > <wvdial-list@xxxxxxxxxxxx>. >> >> >> >> > >> >> >> >> > On Wednesday 07 October 2009 07:20:53 pm you wrote: >> >> >> >> >> RE: I'm NOT going to install something which is >> >> >> >> >> now illegal under the current Ubuntu methodology. >> >> >> >> >> OK >> >> >> >> >> You can always do upon each boot: >> >> >> >> >> $ sudo mknod -m 660 /dev/slamr0 c 242 0 2 >> >> >> >> >> $ sudo mknod chgrp dialout /dev/slamr0 >> >> >> >> >> $ sudo modprobe ungrab-winmodem >> >> >> >> >> $ sudo modprobe slamr >> >> >> >> >> All the above is also done in the slmodem code package by: >> >> >> >> >> $ sudo make install >> >> >> >> >> >> >> >> >> >> $ sudo slmodemd -c USA /dev/slamr0 >> >> >> >> >> and test the modem hardware wtih: >> >> >> >> >> $ sudo wvdialconf wvtest >> >> >> >> >> >> >> >> >> >> Note that Ahmed is not the slmodem code maintainer. He just >> >> >> >> >> assembled the installer.deb for it >> >> >> >> >> with dkms enablement. He never claimed to be COMM code erudite >> >> >> >> >> >> >> >> >> >> While several of us have made incremental conrtibutions, we >> >> >> >> >> lack a maintainer >> >> >> >> >> >> >> >> >> >> MarvS >> >> >> >> >> >> >> >> >> >> On Wed, Oct 7, 2009 at 8:07 PM, Roland Hughes >> >> >> >> >> >> >> >> >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> >> >> >> > Marv, >> >> >> >> >> > >> >> >> >> >> > Thank you for your response, but I'm NOT going to install >> >> >> >> >> > something which is now illegal under the current Ubuntu >> >> >> >> >> > methodology. I am participating in the Karmic Beta. The >> >> >> >> >> > developer(s) need to fix the device creation problem. >> >> >> >> >> > >> >> >> >> >> > Carrier Check = no had no impact on the outcome when I tried >> >> >> >> >> > it last. Since there have been no sl-modem updates in the >> >> >> >> >> > massive piles of updates I've installed, I can't see there >> >> >> >> >> > being any difference in the outcome. >> >> >> >> >> > >> >> >> >> >> > On Wednesday 07 October 2009 06:51:30 pm you wrote: >> >> >> >> >> >> Roland >> >> >> >> >> >> >> >> >> >> >> >> There is documentation in the slmodem code packages >> >> >> >> >> >> explaining all. But briefly >> >> >> >> >> >> 1) Under Linux, the whole /dev/ folder is in RAM space, >> >> >> >> >> >> the Goal is that all needed devices are dynamically created >> >> >> >> >> >> as needed, and of course they all disappear upon a shutdown, >> >> >> >> >> >> with loss of RAM memory >> >> >> >> >> >> >> >> >> >> >> >> 2) Various drivers have achieved varying degrees of >> >> >> >> >> >> automation in /dev/ creation. >> >> >> >> >> >> The original writer(Sasha) of the slmodem code for Linux, >> >> >> >> >> >> worked with us very closely for several years. >> >> >> >> >> >> He invented the strategy of moving the Proprietary part of >> >> >> >> >> >> the Smartlink code from a driver, >> >> >> >> >> >> over to a slmodemd (non-driver) utility. That is why >> >> >> >> >> >> slmodemd can serve a diversity of softmodem hardware, >> >> >> >> >> >> by serving as the Very Smart backend to several different >> >> >> >> >> >> ALSA modem drivers. Unfortunately Sasha now has to focus on >> >> >> >> >> >> well paying jobs to feed his young family, though he does on >> >> >> >> >> >> occasion send as some fixes. >> >> >> >> >> >> >> >> >> >> >> >> 3) /dev/slamr0 creation for slamr used to be automatically >> >> >> >> >> >> managed by the attached file. >> >> >> >> >> >> Unpack and copy it to /etc/modprobe.d/ >> >> >> >> >> >> Unfortunately, this file is now formally illegal inder >> >> >> >> >> >> Ubuntu, because it is Policy that device creation be fully >> >> >> >> >> >> automated by the drivers, without assistance from >> >> >> >> >> >> /etc/modprobe.d/ files >> >> >> >> >> >> >> >> >> >> >> >> 4) However it should still serve for a while. >> >> >> >> >> >> $ sudo modprobe slamr >> >> >> >> >> >> should preload ungrab-winmodem, create /dev/slamr0 , load >> >> >> >> >> >> slamr with concommittant creation of: >> >> >> >> >> >> /dev/ttySL0 --> /dev/pts/N (the real modem port) >> >> >> >> >> >> >> >> >> >> >> >> 5) The /dev/pts/* ports are not yet sound competent for >> >> >> >> >> >> modems. This is why there must be added to /etc/wvdial.conf >> >> >> >> >> >> a line: Carrier Check = no >> >> >> >> >> >> >> >> >> >> >> >> MarvS >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Oct 7, 2009 at 7:18 PM, Roland Hughes >> >> >> >> >> >> >> >> >> >> >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> >> >> >> >> > Hello Marv, >> >> >> >> >> >> > >> >> >> >> >> >> > We went down this path once before, but I will send again. >> >> >> >> >> >> > When you first install after a fresh reboot, it gets the >> >> >> >> >> >> > NO CARRIER message eventhough the phone line works and >> >> >> >> >> >> > other OS can use modem. After a reboot, ttySL0 is gone, >> >> >> >> >> >> > never to be seen again. As far as I can tell, the >> >> >> >> >> >> > developer has tossed his hands in the air as I haven't >> >> >> >> >> >> > received an email from him in quite a while. I bought 6 >> >> >> >> >> >> > modems to help testing this and most of the time I get >> >> >> >> >> >> > stuff sent to me which will either not compile, or was >> >> >> >> >> >> > never tested by him. >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > ================================== >> >> >> >> >> >> > Only plain text email is forwarded by the >> >> >> >> >> >> > Discuss@xxxxxxxxxxxxx List Server, as HTML can contain >> >> >> >> >> >> > viruses. Use as the email Subject Line: YourName, >> >> >> >> >> >> > YourCountry kernel 2.6.31-11-generic >> >> >> >> >> >> > With this Subject Line cogent experts will be alerted, >> >> >> >> >> >> > and useful case names left in the Archive. >> >> >> >> >> >> > YourCountry will enable Country specific guidance. Linux >> >> >> >> >> >> > experts in YourCountry >> >> >> >> >> >> > can be found through: >> >> >> >> >> >> > http://www.linux.org/groups/index.html. They will know >> >> >> >> >> >> > your Country's modem code, which may be essential for >> >> >> >> >> >> > dialup service. >> >> >> >> >> >> > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked >> >> >> >> >> >> > by an Internet Provider mail filters. >> >> >> >> >> >> > So in a day, also check the Archived responses at >> >> >> >> >> >> > http://www.linmodems.org -------------------------- >> >> >> >> >> >> > System information ---------------------------- CPU=i686, >> >> >> >> >> >> > Linux version 2.6.31-11-generic (buildd@palmer) (gcc >> >> >> >> >> >> > version 4.4.1 (Ubuntu 4.4.1-4ubuntu4) ) #38-Ubuntu SMP Fri >> >> >> >> >> >> > Oct 2 11:55:55 UTC 2009 scanModem update of: 2009_09_15 >> >> >> >> >> >> > The modem symbolic link is /dev/modem -> ttySL0 >> >> >> >> >> >> > >> >> >> >> >> >> > The dkms driver upgrade utilities are installed, >> >> >> >> >> >> > >> >> >> >> >> >> > There are no blacklisted modem drivers in /etc/modprobe* >> >> >> >> >> >> > files >> >> >> >> >> >> > >> >> >> >> >> >> > Potentially useful modem drivers now loaded are: >> >> >> >> >> >> > slamr >> >> >> >> >> >> > >> >> >> >> >> >> > slamrTest= >> >> >> >> >> >> > Attached USB devices are: >> >> >> >> >> >> > ID 10d5:55a4 Uni Class Technology Co., Ltd >> >> >> >> >> >> > ID 046d:c044 Logitech, Inc. LX3 Optical Mouse >> >> >> >> >> >> > ID 0d3d:0001 Tangtop Technology Co., Ltd HID Keyboard >> >> >> >> >> >> > ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS >> >> >> >> >> >> > ID 058f:9254 Alcor Micro Corp. Hub >> >> >> >> >> >> > If a cellphone is not detected, see >> >> >> >> >> >> > http://ubuntuforums.org/archive/index.php/t-878554.html >> >> >> >> >> >> > A sample report is: >> >> >> >> >> >> > http://linmodems.technion.ac.il/bigarch/archive- >> >> >> >> >> >> > nineth/msg00578.html >> >> >> >> >> >> > >> >> >> >> >> >> > If a USB modem or cellphone is attached and was not >> >> >> >> >> >> > detected, please provide available information in your >> >> >> >> >> >> > request to discuss@xxxxxxxxxxxxx >> >> >> >> >> >> > >> >> >> >> >> >> > For candidate card in slot 01:06.0, firmware information >> >> >> >> >> >> > and bootup diagnostics are: >> >> >> >> >> >> > PCI slot PCI ID SubsystemID Name >> >> >> >> >> >> > ---------- --------- --------- >> >> >> >> >> >> > -------------- 01:06.0 1057:3052 1057:3020 >> >> >> >> >> >> > Modem: Motorola SM56 Data Fax Modem >> >> >> >> >> >> > >> >> >> >> >> >> > Modem interrupt assignment and sharing: >> >> >> >> >> >> > 16: 17716 30899340 IO-APIC-fasteoi SL1900 >> >> >> >> >> >> > --- Bootup diagnostics for card in PCI slot 01:06.0 ---- >> >> >> >> >> >> > [ 0.191721] pci 0000:01:06.0: reg 10 32bit mmio: >> >> >> >> >> >> > [0xfdfff000-0xfdffffff] [ 0.191727] pci 0000:01:06.0: >> >> >> >> >> >> > reg 14 io port: [0xac00-0xacff] [ 0.191753] pci >> >> >> >> >> >> > 0000:01:06.0: PME# supported from D0 D3hot D3cold [ >> >> >> >> >> >> > 0.191757] pci 0000:01:06.0: PME# disabled [ 0.863369] >> >> >> >> >> >> > serial 0000:01:06.0: PCI INT A -> Link[APC1] -> GSI 16 >> >> >> >> >> >> > (level, low) -> IRQ 16 >> >> >> >> >> >> > [ 0.863447] 0000:01:06.0: ttyS1 at I/O 0xac08 (irq = >> >> >> >> >> >> > 16) is a 16450 [ 0.863495] 0000:01:06.0: ttyS2 at I/O >> >> >> >> >> >> > 0xac10 (irq = 16) is a 8250 [ 0.863543] 0000:01:06.0: >> >> >> >> >> >> > ttyS3 at I/O 0xac18 (irq = 16) is a 16450 [ 0.863558] >> >> >> >> >> >> > Couldn't register serial port 0000:01:06.0: -28 [ >> >> >> >> >> >> > 62.188105] serial 0000:01:06.0: PCI INT A disabled >> >> >> >> >> >> > [ 62.612216] slamr 0000:01:06.0: PCI INT A -> Link[APC1] >> >> >> >> >> >> > -> GSI 16 (level, low) -> IRQ 16 >> >> >> >> >> >> > >> >> >> >> >> >> > The PCI slot 01:06.0 of the modem card may be disabled >> >> >> >> >> >> > early in a bootup process, but then enabled later. If >> >> >> >> >> >> > modem drivers load but the modem is not responsive, read >> >> >> >> >> >> > DOCs/Bootup.txt about possible fixes. Send dmesg.txt along >> >> >> >> >> >> > with ModemData.txt to discuss@xxxxxxxxxxxxx if help is >> >> >> >> >> >> > needed. >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > === Finished firmware and bootup diagnostics, next >> >> >> >> >> >> > deducing cogent software. === >> >> >> >> >> >> > >> >> >> >> >> >> > Predictive diagnostics for card in bus 01:06.0: >> >> >> >> >> >> > Modem chipset detected on >> >> >> >> >> >> > NAME="Modem: Motorola SM56 Data Fax Modem " >> >> >> >> >> >> > CLASS=0703 >> >> >> >> >> >> > PCIDEV=1057:3052 >> >> >> >> >> >> > SUBSYS=1057:3020 >> >> >> >> >> >> > IRQ=16 >> >> >> >> >> >> > IDENT=slamr >> >> >> >> >> >> > >> >> >> >> >> >> > For candidate modem in: 01:06.0 >> >> >> >> >> >> > 0703 Modem: Motorola SM56 Data Fax Modem >> >> >> >> >> >> > Primary device ID: 1057:3052 >> >> >> >> >> >> > Support type needed or chipset: slamr >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > 1057:3052 has a Motorola chipset, poorly supported by >> >> >> >> >> >> > Motorola itself However Zello discovered that drivers >> >> >> >> >> >> > written to support Smartlink modems do support the >> >> >> >> >> >> > 1057:3052 chipset!! >> >> >> >> >> >> > It sufficed to add 1057:3052 to the list of modem cards >> >> >> >> >> >> > recognized by the Smartlink slamr driver. >> >> >> >> >> >> > There is a ungrab-winmodem driver used in conjunction >> >> >> >> >> >> > with slamr, which must have 1057:3052 >> >> >> >> >> >> > similarly added. See messages from Zello: >> >> >> >> >> >> > >> >> >> >> >> >> > http://linmodems.technion.ac.il/bigarch/archive-seventh/m >> >> >> >> >> >> >sg0 084 6.h tml >> >> >> >> >> >> > http://linmodems.technion.ac.il/bigarch/archive-seventh/ms >> >> >> >> >> >> >g00 848 .ht ml and Alvaro Aguirre about the ungrab-winmodem >> >> >> >> >> >> > fix: >> >> >> >> >> >> > >> >> >> >> >> >> > http://linmodems.technion.ac.il/bigarch/archive-seventh/m >> >> >> >> >> >> >sg0 099 0.h tml For general guidance on ungrab-winmodem + >> >> >> >> >> >> > slamr usage, read the DOCs/Smartlink.txt >> >> >> >> >> >> > >> >> >> >> >> >> > The modem is supported by the Smartlink >> >> >> >> >> >> > plus the slmodemd helper utility. Read the >> >> >> >> >> >> > DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for >> >> >> >> >> >> > follow through guidance. >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > For 2.6.31-11-generic compiling drivers is necessary. As >> >> >> >> >> >> > of October 2007 the current packages at >> >> >> >> >> >> > http://linmodems.technion.ac.il/packages/smartlink/ are >> >> >> >> >> >> > the ungrab-winmodem-20070505.tar.gz and >> >> >> >> >> >> > slmodem-2.9.11-20080126.tar.gz >> >> >> >> >> >> > >> >> >> >> >> >> > Writing DOCs/Smartlink.txt >> >> >> >> >> >> > ============ end Smartlink section ===================== >> >> >> >> >> >> > >> >> >> >> >> >> > Completed candidate modem analyses. >> >> >> >> >> >> > >> >> >> >> >> >> > The base of the UDEV device file system is: /dev/.udev >> >> >> >> >> >> > >> >> >> >> >> >> > Versions adequately match for the compiler installed: >> >> >> >> >> >> > 4.4.1 and the compiler used in kernel assembly: 4.4.1 >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > Minimal compiling resources appear complete: >> >> >> >> >> >> > make utility - /usr/bin/make >> >> >> >> >> >> > Compiler version 4.4 >> >> >> >> >> >> > linuc_headers base folder >> >> >> >> >> >> > /lib/modules/2.6.31-11-generic/build >> >> >> >> >> >> > >> >> >> >> >> >> > However some compilations and executable functions may >> >> >> >> >> >> > need additional files, in the FileNames.h (so called >> >> >> >> >> >> > kernel "h"eaders) collection installed in /usr/include/ . >> >> >> >> >> >> > For martian_modem, additional required packages are >> >> >> >> >> >> > needed. The also required headers of package libc6 are >> >> >> >> >> >> > commonly installed by default. Compiling hsfmodem drivers >> >> >> >> >> >> > does require linux-libc-dev and libc6-dev packages, for >> >> >> >> >> >> > kernels 2.6.24 and later versions. In not included on your >> >> >> >> >> >> > install CD, search for them at http://packages.ubuntu.com >> >> >> >> >> >> > or comparable Repository for other Linux distros. >> >> >> >> >> >> > When compiling ALSA drivers, the utility "patch" will >> >> >> >> >> >> > also be needed. >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > Compressed files at: /usr/src/sl-modem.tar.bz2 >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > If a driver compilation fails, with message including some >> >> >> >> >> >> > lack of some FileName.h (stdio.h for example), then >> >> >> >> >> >> > Some additional kernel-header files need installation to >> >> >> >> >> >> > /usr/include. The minimal additional packages are >> >> >> >> >> >> > libc6-dev and any of its dependents, under Ubuntu >> >> >> >> >> >> > linux-libc-dev >> >> >> >> >> >> > >> >> >> >> >> >> > If an alternate ethernet connection is available, >> >> >> >> >> >> > $ apt-get update >> >> >> >> >> >> > $ apt-get -s install linux-kernel-devel >> >> >> >> >> >> > will install needed packages. >> >> >> >> >> >> > For Debian/Ubuntu related distributions, run the following >> >> >> >> >> >> > command to display the needed package list: >> >> >> >> >> >> > >> >> >> >> >> >> > Otherwise packages have to be found through >> >> >> >> >> >> > http://packages.ubuntu.com Once downloaded and transferred >> >> >> >> >> >> > into a Linux partition, >> >> >> >> >> >> > they can be installed alltogether with: >> >> >> >> >> >> > $ sudo dpkg -i *.deb >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > Checking pppd properties: >> >> >> >> >> >> > -rwsr-xr-- 1 root dip 277352 2009-02-20 11:25 >> >> >> >> >> >> > /usr/sbin/pppd >> >> >> >> >> >> > >> >> >> >> >> >> > In case of an "error 17" "serial loopback" problem, see: >> >> >> >> >> >> > >> >> >> >> >> >> > http://linmodems.technion.ac.il/linmodems/archive-sixth/m >> >> >> >> >> >> >sg0 263 7.h tml >> >> >> >> >> >> > >> >> >> >> >> >> > To enable dialout without Root permission do: >> >> >> >> >> >> > $ su - root (not for Ubuntu) >> >> >> >> >> >> > sudo chmod a+x /usr/sbin/pppd >> >> >> >> >> >> > or under Ubuntu related Linuxes >> >> >> >> >> >> > sudo chmod a+x /usr/sbin/pppd >> >> >> >> >> >> > >> >> >> >> >> >> > Checking settings of: /etc/ppp/options >> >> >> >> >> >> > asyncmap 0 >> >> >> >> >> >> > noauth >> >> >> >> >> >> > crtscts >> >> >> >> >> >> > lock >> >> >> >> >> >> > hide-password >> >> >> >> >> >> > modem >> >> >> >> >> >> > proxyarp >> >> >> >> >> >> > lcp-echo-interval 30 >> >> >> >> >> >> > lcp-echo-failure 4 >> >> >> >> >> >> > noipx >> >> >> >> >> >> > >> >> >> >> >> >> > In case of a message like: >> >> >> >> >> >> > Warning: Could not modify /etc/ppp/pap-secrets: >> >> >> >> >> >> > Permission denied see >> >> >> >> >> >> > http://linmodems.technion.ac.il/bigarch/archive-sixth/msg0 >> >> >> >> >> >> >465 6.h tml >> >> >> >> >> >> > >> >> >> >> >> >> > Read Modem/DOCs/YourSystem.txt concerning other COMM >> >> >> >> >> >> > channels: eth0 Which can interfere with Browser >> >> >> >> >> >> > naviagation. >> >> >> >> >> >> > >> >> >> >> >> >> > Don't worry about the following, it is for experts should >> >> >> >> >> >> > trouble shooting be necessary. >> >> >> >> >> >> > ========================================================== >> >> >> >> >> >> > >> >> >> >> >> >> > Checking for modem support lines: >> >> >> >> >> >> > -------------------------------------- >> >> >> >> >> >> > /device/modem symbolic link: lrwxrwxrwx 1 root root >> >> >> >> >> >> > 6 2009-10-06 09:31 /dev/modem -> ttySL0 >> >> >> >> >> >> > slmodemd created symbolic link /dev/ttySL0: >> >> >> >> >> >> > Within /etc/udev/ files: >> >> >> >> >> >> > >> >> >> >> >> >> > Within /etc/modprobe.conf files: >> >> >> >> >> >> > /etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe >> >> >> >> >> >> > -qb ungrab- winmodem; /sbin/modprobe --ignore-install >> >> >> >> >> >> > slamr; /etc/modprobe.d/sl-modem.conf:install slusb >> >> >> >> >> >> > /sbin/modprobe -qb ungrab- winmodem; /sbin/modprobe >> >> >> >> >> >> > --ignore-install slusb; >> >> >> >> >> >> > /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem >> >> >> >> >> >> > index=-2 /etc/modprobe.d/alsa-base.conf:options >> >> >> >> >> >> > snd-via82xx-modem index=-2 >> >> >> >> >> >> > /etc/modprobe.d/blacklist-modem.conf:# Uncomment these >> >> >> >> >> >> > entries in order to blacklist unwanted modem drivers >> >> >> >> >> >> > /etc/modprobe.d/blacklist-modem.conf:# blacklist >> >> >> >> >> >> > snd-atiixp-modem /etc/modprobe.d/blacklist-modem.conf:# >> >> >> >> >> >> > blacklist snd-via82xx-modem Within any ancient /etc/devfs >> >> >> >> >> >> > files: >> >> >> >> >> >> > >> >> >> >> >> >> > Within ancient kernel 2.4.n /etc/module.conf files: >> >> >> >> >> >> > >> >> >> >> >> >> > --------- end modem support lines -------- >> >> >> >> >> >> > >> >> >> >> >> >> > On Wednesday 07 October 2009 06:02:35 pm you wrote: >> >> >> >> >> >> >> Roland, >> >> >> >> >> >> >> >> >> >> >> >> >> >> Send me the entire ModemData.txt from the System in which >> >> >> >> >> >> >> you are trying to use slmodem. >> >> >> >> >> >> >> >> >> >> >> >> >> >> MarvS >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Oct 7, 2009 at 11:20 AM, Roland Hughes >> >> >> >> >> >> >> >> >> >> >> >> >> >> <roland@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> >> >> >> >> >> > I have this: >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > =================== >> >> >> >> >> >> >> > Predictive diagnostics for card in bus 01:06.0: >> >> >> >> >> >> >> > Modem chipset detected on >> >> >> >> >> >> >> > NAME="Modem: Motorola SM56 Data Fax Modem " >> >> >> >> >> >> >> > CLASS=0703 >> >> >> >> >> >> >> > PCIDEV=1057:3052 >> >> >> >> >> >> >> > SUBSYS=1057:3020 >> >> >> >> >> >> >> > IRQ=16 >> >> >> >> >> >> >> > IDENT=slamr >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > For candidate modem in: 01:06.0 >> >> >> >> >> >> >> > 0703 Modem: Motorola SM56 Data Fax Modem >> >> >> >> >> >> >> > Primary device ID: 1057:3052 >> >> >> >> >> >> >> > Support type needed or chipset: slamr >> >> >> >> >> >> >> > ===================== >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > It's not even close to working. >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > On Wednesday 07 October 2009 12:44:42 am Dr Jack Trevor >> >> >> >> >> >> >> > Jones >> >> >> > >> >> >> > wrote: >> >> >> >> >> >> >> >> Hi >> >> >> >> >> >> >> >> There are reports of difficulties with some modem >> >> >> >> >> >> >> >> drivers and Karmic Koala >> >> >> >> >> >> >> >> I have a good working set-up using Ubuntu 9.04 with a >> >> >> >> >> >> >> >> Motorola SM56 Data Fax Modem and slamr >> >> >> >> >> >> >> >> which the system detects as: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Modem = /dev/ttySL0 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The relevant section of scanmodem shows: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> For candidate modem in: 03:01.0 >> >> >> >> >> >> >> >> 0703 Modem: Motorola SM56 Data Fax Modem >> >> >> >> >> >> >> >> Primary device ID: 1057:3052 >> >> >> >> >> >> >> >> Support type needed or chipset: slamr >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Should I expect problems if I upgrade to Ubuntu 9.10? >> >> >> >> >> >> >> >> Thanks >> >> >> >> >> >> >> >> Trevor >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > -- >> >> >> >> >> >> >> > Roland Hughes, President >> >> >> >> >> >> >> > Logikal Solutions >> >> >> >> >> >> >> > (630)-205-1593 (cell) >> >> >> >> >> >> >> > http://www.theminimumyouneedtoknow.com >> >> >> >> >> >> >> > http://www.infiniteexposure.net >> >> >> >> >> >> >> > http://www.logikalsolutions.com >> >> >> >> >> >> > >> >> >> >> >> >> > -- >> >> >> >> >> >> > Roland Hughes, President >> >> >> >> >> >> > Logikal Solutions >> >> >> >> >> >> > (630)-205-1593 (cell) >> >> >> >> >> >> > http://www.theminimumyouneedtoknow.com >> >> >> >> >> >> > http://www.infiniteexposure.net >> >> >> >> >> >> > http://www.logikalsolutions.com >> >> >> >> >> > >> >> >> >> >> > -- >> >> >> >> >> > Roland Hughes, President >> >> >> >> >> > Logikal Solutions >> >> >> >> >> > (630)-205-1593 (cell) >> >> >> >> >> > http://www.theminimumyouneedtoknow.com >> >> >> >> >> > http://www.infiniteexposure.net >> >> >> >> >> > http://www.logikalsolutions.com >> >> >> >> > >> >> >> >> > -- >> >> >> >> > Roland Hughes, President >> >> >> >> > Logikal Solutions >> >> >> >> > (630)-205-1593 (cell) >> >> >> >> > http://www.theminimumyouneedtoknow.com >> >> >> >> > http://www.infiniteexposure.net >> >> >> >> > http://www.logikalsolutions.com >> >> >> > >> >> >> > -- >> >> >> > Roland Hughes, President >> >> >> > Logikal Solutions >> >> >> > (630)-205-1593 (cell) >> >> >> > http://www.theminimumyouneedtoknow.com >> >> >> > http://www.infiniteexposure.net >> >> >> > http://www.logikalsolutions.com >> >> > >> >> > -- >> >> > Roland Hughes, President >> >> > Logikal Solutions >> >> > (630)-205-1593 (cell) >> >> > http://www.theminimumyouneedtoknow.com >> >> > http://www.infiniteexposure.net >> >> > http://www.logikalsolutions.com >> > >> > -- >> > Roland Hughes, President >> > Logikal Solutions >> > (630)-205-1593 (cell) >> > http://www.theminimumyouneedtoknow.com >> > http://www.infiniteexposure.net >> > http://www.logikalsolutions.com >> > > -- > Roland Hughes, President > Logikal Solutions > (630)-205-1593 (cell) > http://www.theminimumyouneedtoknow.com > http://www.infiniteexposure.net > http://www.logikalsolutions.com >
