Helmut, This <051.276510> err: slamr0: modem start = -1: cannot start device. is the previously reported failure point, that a fix is needed for. At this point under 2.6.30 or 28 kernels, the CONNECT proceeds successfully MarvS On Fri, Jan 15, 2010 at 12:49 PM, Helmut Freiwald <helmut.freiwald@xxxxxxxxxxx> wrote: > Hallo Marvin, > > I start slmodemd with option --debug, and got the following output. > After dialing an error occurs : cannot start device. > > SmartLink Soft Modem: version 2.9.11 Jan 14 2010 19:58:27 > <043.794303> SmartLink Soft Modem: version 2.9.11 Jan 14 2010 19:58:27 > <043.794576> slamr0: startup modem... > <043.795275> slamr0: update termios... > symbolic link `/dev/ttySL0' -> `/dev/pts/0' created. > modem `slamr0' created. TTY is `/dev/pts/0' > <043.795616> open file: /var/lib/slmodem/data.slamr0... > <043.798092> main: rt applyed: SCHED_FIFO, pri 99 > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > <050.676127> main: termios changed. > <050.676197> slamr0: update termios... > <050.736121> main: termios changed. > <050.736205> slamr0: update termios... > <050.844162> slamr0: run cmd: ATZ > <050.844242> slamr0: modem reset... > <050.844261> slamr0: modem set state: 1 --> 1... > <050.844281> slamr0: modem set mode: -> 0... > <050.844299> slamr0: modem report result: 0 (OK) > <050.952277> slamr0: run cmd: ATQ0V1E1S0=0&C1&D2+FCLASS=0 > <050.952373> slamr0: modem set mode: -> 0... > <050.952394> slamr0: modem report result: 0 (OK) > <051.060272> slamr0: run cmd: ATM1L3 > <051.060353> main: modemap_ioctl: cmd 8, arg 0... > <051.060390> main: modemap_ioctl: cmd 8, arg 0... > <051.060411> slamr0: modem report result: 0 (OK) > <051.168156> slamr0: run cmd: ATX3 > <051.168240> slamr0: modem report result: 0 (OK) > <051.276219> slamr0: run cmd: ATDT0192074 > <051.276311> slamr0: modem dial: T0192074... > <051.276329> slamr0: modem_dial_start... > <051.276384> slamr0: modem_start.. > <051.276404> slamr0: modem set state: 1 --> 2... > <051.276422> slamr0: new state: DP_ESTAB > <051.276439> main: modemap_ioctl: cmd 8, arg 3... > <051.276464> slamr0: modem set hook: 0 --> 1... > <051.276481> main: modemap_ioctl: cmd 2, arg 1... > <051.276510> err: slamr0: modem start = -1: cannot start device. > <051.276529> slamr0: modem_stop.. > <051.276576> slamr0: modem set hook: 0 --> 0... > <051.276593> main: modemap_ioctl: cmd 8, arg 0... > <051.276618> slamr0: modem set state: 2 --> 1... > <051.276638> slamr0: new state: MODEM_IDLE > <051.276655> slamr0: modem report result: 3 (NO CARRIER) > <051.276682> slamr0: modem report result: 4 (ERROR) > > > thanks for further help. > Helmut > > Am 15.01.2010 15:37, schrieb Marvin Stodolsky: >> Helmut >> >> the slamr code was competent upto 2.6.30 kernels, but it is failing >> for 2.6.31 kernels. >> Quite likely your SuSE system will work in you install a kernel 2.6.30 >> and compiling support >> A line: >> Carrier Check = no >> must be added to /etc/wvdial.conf for drivers using /dev/pts/N ports, >> including slamr. >> >> MarvS >> >> On Thu, Jan 14, 2010 at 5:25 AM, Helmut Freiwald >> <helmut.freiwald@xxxxxxxxxxx <mailto:helmut.freiwald@xxxxxxxxxxx>> wrote: >>> Dear madam and sir >>> >>> I use the following system on my maxdata notebook with slmodemd. >>> >>> Distribution: openSUSE 11.2 >>> Kernel: 2.6.31.8-0.1-default >>> Modem: PCI Modem: ALi Corporation M5457 AC'97 Modem Controller >>> Chipset manufacturer: Lucent >>> >>> Init1 = ATZ >>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>> Init3 = ATM1L3 >>> Phone = 0191011 (T-Online) >>> >>> I tryed to connect to my internet provider with kppp or wvdial and also >>> with kinternet, but I got the error-message "NO CARRIER - ERROR". On the >>> same notebook with a second harddisk and openSUSE 11.1 it works, also on >>> windows xp. >>> >>> Next is following the content of ModemData.txt >>> --------------------------------------------- >>> Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx >> <mailto:Discuss@xxxxxxxxxxxxx> List >>> Server, >>> as HTML can contain viruses. Use as the email Subject >>> Line: >>> YourName, YourCountry Welcome to openSUSE 11.2 "Emerald" - >>> Kernel kernel 2.6.31.8-0.1-default >>> 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 <mailto: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, Welcome to openSUSE 11.2 "Emerald" - >>> Kernel >>> Linux version 2.6.31.8-0.1-default (geeko@buildhost >> <mailto:geeko@buildhost>) (gcc version 4.4.1 >>> [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 SMP 2009-12-15 >>> 23:55:40 >>> +0100 >>> >>> scanModem update of: >>> 2009_12_10 >>> >>> The modem symbolic link is /dev/modem -> >>> /dev/ttySL0 >>> >>> The slmodemd set symbolic link is /dev/ttySL0 -> >>> /dev/pts/2 >>> >>> >>> Presently install your Linux Distributions dkms package. It provides for >>> automated driver updates, >>> following upgrade of your kernel. For details see >>> http://linux.dell.com/projects.shtml#dkms >>> >>> There are no blacklisted modem drivers in /etc/modprobe* files >>> >>> Potentially useful modem drivers now loaded are: >>> snd_ali5451 slamr >>> >>> slamrTest=mc97 is >>> Attached USB devices are: >>> ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver >>> ID 2040:7070 Hauppauge Nova-T Stick 3 >>> 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 >> <mailto:discuss@xxxxxxxxxxxxx> >>> >>> For candidate card in slot 00:08.0, firmware information and bootup >>> diagnostics are: >>> PCI slot PCI ID SubsystemID >>> Name >>> ---------- --------- --------- >>> -------------- >>> 00:08.0 10b9:5457 17c0:1052 Modem: ALi Corporation >>> M5457 AC'97 Modem Controller >>> >>> Modem interrupt assignment and sharing: >>> 11: 13880 XT-PIC-XT ohci_hcd:usb2, yenta, eth2, >>> ohci1394, ohci_hcd:usb3, ALI 5451, ehci_hcd:usb4, SL1800 >>> --- Bootup diagnostics for card in PCI slot 00:08.0 >>> ---- >>> [ 2.026163] pci 0000:00:08.0: reg 10 32bit mmio: >>> [0xe0001000-0xe0001fff] >>> [ 2.026173] pci 0000:00:08.0: reg 14 io port: >>> [0x1c00-0x1cff] >>> [ 2.026215] pci 0000:00:08.0: PME# supported from D3hot >>> D3cold >>> [ 2.026221] pci 0000:00:08.0: PME# >>> disabled >>> >>> [ 3.323690] serial 0000:00:08.0: PCI INT A -> Link[LNKG] -> GSI 11 >>> (level, low) -> IRQ 11 >>> [ 3.323702] serial 0000:00:08.0: PCI INT A >>> disabled >>> [ 38.412926] slamr 0000:00:08.0: PCI INT A -> Link[LNKG] -> GSI 11 >>> (level, low) -> IRQ 11 >>> [ 5211.927151] slamr 0000:00:08.0: PCI INT A >>> disabled >>> [ 5211.988851] slamr 0000:00:08.0: PCI INT A -> Link[LNKG] -> GSI 11 >>> (level, low) -> IRQ 11 >>> >>> The PCI slot 00:08.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 <mailto:discuss@xxxxxxxxxxxxx> >>> if help is >>> needed. >>> >>> >>> >>> For candidate card in slot 00:06.0, firmware information and bootup >>> diagnostics are: >>> PCI slot PCI ID SubsystemID >>> Name >>> ---------- --------- --------- >>> -------------- >>> 00:06.0 10b9:5451 17c0:2002 Multimedia audio >>> controller: ALi Corporation M5451 PCI AC-Link Controller Audio >>> Device >>> >>> >>> Modem interrupt assignment and sharing: >>> 11: 13880 XT-PIC-XT ohci_hcd:usb2, yenta, eth2, >>> ohci1394, ohci_hcd:usb3, ALI 5451, ehci_hcd:usb4, SL1800 >>> --- Bootup diagnostics for card in PCI slot 00:06.0 >>> ---- >>> [ 2.025978] pci 0000:00:06.0: reg 10 io port: >>> [0x1800-0x18ff] >>> [ 2.025988] pci 0000:00:06.0: reg 14 32bit mmio: >>> [0xe0000000-0xe0000fff] >>> [ 2.026031] pci 0000:00:06.0: supports D1 >>> D2 >>> [ 2.026036] pci 0000:00:06.0: PME# supported from D2 D3hot >>> D3cold >>> [ 2.026042] pci 0000:00:06.0: PME# >>> disabled >>> >>> [ 14.446279] ALI 5451 0000:00:06.0: PCI INT A -> Link[LNKH] -> GSI 11 >>> (level, low) -> IRQ 11 >>> >>> The PCI slot 00: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 <mailto:discuss@xxxxxxxxxxxxx> >>> if help is >>> needed. >>> >>> >>> >>> >>> ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== >>> The ALSA packages provide audio support and also drivers for some modems. >>> ALSA diagnostics are written during bootup to /proc/asound/ folders. >>> >>> The ALSA verion is 1.0.20 >>> The modem cards detected by "aplay -l" are: None >>> >>> >>> The /proc/asound/pcm file reports: >>> ----------------------- >>> 00-00: ALI 5451 : ALI 5451 : playback 32 : capture 1 >>> >>> about /proc/asound/cards: >>> ------------------------ >>> 0 [A5451 ]: ALI5451 - ALI 5451 >>> ALI 5451 at 0x1800, irq 11 >>> === Finished firmware and bootup diagnostics, next deducing cogent >>> software. === >>> >>> Predictive diagnostics for card in bus 00:06.0: >>> Modem chipset detected on >>> NAME="Multimedia audio controller: ALi Corporation M5451 PCI AC-Link >>> Controller Audio Device " >>> CLASS=0401 >>> >>> PCIDEV=10b9:5451 >>> >>> SUBSYS=17c0:2002 >>> >>> IRQ=11 >>> >>> SOFT=10b9:5451.MC97 >>> >>> IDENT=slmodemd >>> >>> SLMODEMD_DEVICE=hw:0,1 >>> >>> Driver=snd-ali5451 >>> >>> >>> For candidate modem in: 00:06.0 >>> 0401 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link >>> Controller Audio Device >>> Primary device ID: >>> 10b9:5451 >>> Subsystem PCI_id >>> 17c0:2002 >>> Softmodem codec or chipset from >>> diagnostics: >>> from >>> Archives: >>> >>> >>> >>> >>> >>> Support type needed or chipset: slmodemd >>> >>> An ALSA (Advanced Linux Sound Architecture) modem driver: snd-ali5451 >>> provides Low Level support enabling contact with the modem hardware. >>> For all BUT Conexant chip soft modems (using hsfmodem software) >>> complementary High Level support is through a Smartlink utility: slmodemd >>> >>> Download from http://linmodems.technion.ac.il/packages/smartlink/ >>> the package SLMODEMD.gcc4.4.tar.gz having a compiled slmodemd. Unpack >>> under Linux with: >>> $ tar zxf >>> SLMODEMD.gcc4.4.tar.gz >>> and read instructions therein. But briefly, the modem is setup with >>> command: >>> slmodemd -c YOUR_COUNTRY --alsa >>> -shw:0,1 >>> reporting dynamic creation of >>> ports: >>> /dev/ttySL0 --> /dev/pts/N , with N some >>> number >>> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow >>> through guidance. >>> >>> Writing DOCs/Smartlink.txt >>> ============ end Smartlink section ===================== >>> >>> >>> Predictive diagnostics for card in bus 00:08.0: >>> Modem chipset detected on >>> NAME="Modem: ALi Corporation M5457 AC'97 Modem Controller" >>> CLASS=0703 >>> PCIDEV=10b9:5457 >>> SUBSYS=17c0:1052 >>> IRQ=11 >>> SOFT=10b9:5457.MC97 >>> slamrTest=mc97 is >>> IDENT=slmodemd >>> Driver=slamr >>> >>> For candidate modem in: 00:08.0 >>> 0703 Modem: ALi Corporation M5457 AC'97 Modem Controller >>> Primary device ID: 10b9:5457 >>> Subsystem PCI_id 17c0:1052 >>> Softmodem codec or chipset from diagnostics: >>> from Archives: >>> >>> >>> >>> Support type needed or chipset: slamr >>> >>> The modem is supported by the Smartlink slamr >>> plus the slmodemd helper utility. Read the >>> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through >>> guidance. >>> >>> >>> For 2.6.31.8-0.1-default 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 >>> >>> >>> 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 >>> >>> >>> >>> Minimal compiling resources appear complete: >>> make utility - /usr/bin/make >>> Compiler version 4.4 >>> linuc_headers base folder /lib/modules/2.6.31.8-0.1-default/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. >>> >>> >>> >>> >>> 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: >>> -rwxr-xr-x 1 root dialout 330764 19. Okt 17:45 /usr/sbin/pppd >>> >>> In case of an "error 17" "serial loopback" problem, see: >>> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html >>> >>> To enable dialout without Root permission do: >>> $ su - root (not for Ubuntu) >>> chmod a+x /usr/sbin/pppd >>> or under Ubuntu related Linuxes >>> chmod a+x /usr/sbin/pppd >>> >>> Checking settings of: /etc/ppp/options >>> noipdefault >>> debug >>> noauth >>> crtscts >>> lock >>> modem >>> asyncmap 0 >>> nodetach >>> lcp-echo-interval 30 >>> lcp-echo-failure 4 >>> lcp-max-configure 60 >>> lcp-restart 2 >>> idle 600 >>> noipx >>> file /etc/ppp/filters >>> >>> 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/msg04656.html >>> >>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth2 >>> 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 11 14. Jan >>> 09:46 /dev/modem -> /dev/ttySL0 >>> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 >>> 14. Jan 10:43 /dev/ttySL0 -> /dev/pts/2 >>> Within /etc/udev/ files: >>> /etc/udev/rules.d/51-hso-udev.rules:SUBSYSTEM=="tty", SUBSYSTEMS=="usb", >>> ATTR{hsotype}=="Modem", SYMLINK+="wmodem0" >>> /etc/udev/rules.d/51-hso-udev.rules:SUBSYSTEM=="tty", >>> SYSFS{hsotype}=="Modem", SYMLINK+="wmodem0" >>> /etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", >>> >> ENV{INTERFACE}=="lo*|dummy*|vif*.*|br*|bond*|vlan*|gre*|sit*|tap*|tun*|ipip*|ip6tnl*|ipsec*|ppp*|ippp*|isdn*|modem*|dsl*|plip*|irda*", >>> GOTO="skip_ifup" >>> Within /etc/modprobe.conf files: >>> /etc/modprobe.d/00-system.conf:# Linux ACP modem (Mwave) >>> Within any ancient /etc/devfs files: >>> >>> Within ancient kernel 2.4.n /etc/module.conf files: >>> >>> --------- end modem support lines -------- >>> >>> I need some help to get forward. Thank you. >>> >>> best regards >>> Helmut Freiwald >>> mailto:helmut.freiwald@xxxxxxxxxxx >>> >>> >>> >>> >>> > >
