Antonio provides Good News below. For several recent 2.6.2N kernel releases, there has been a problem doing multiple dialout sessions depending on the Smartlink slamr driver. This problem seems to have been corrected in the 2.6.29 kernel release. Thanks for the testing Antonio. MarvS ---------- Forwarded message ---------- From: Antonio Olivares <olivares14031@xxxxxxxxx> Date: Sun, Apr 19, 2009 at 12:13 AM Subject: Re: FYI, for the first time in a while, I did not have to restart slmodemd service To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> Marv, guess I was wrong. I do have to restart slmodemd service. wvdial failed to connect successive times. It appeared to work :( [root@localhost ~]# wvdial --> WvDial: Internet dialer version 1.60 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 OK --> Modem initialized. --> Sending: ATDT7072000 --> Waiting for carrier. ATDT7072000 CONNECT 46667 --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sat Apr 18 22:45:44 2009 --> Pid of pppd: 10309 --> Using interface ppp0 --> pppd: --> �[08]H[10]�[08] --> pppd: --> �[08]H[10]�[08] --> pppd: --> �[08]H[10]�[08] --> local IP address 66.201.8.205 --> pppd: --> �[08]H[10]�[08] --> remote IP address 66.201.8.6 --> pppd: --> �[08]H[10]�[08] --> primary DNS address 66.201.0.203 --> pppd: --> �[08]H[10]�[08] --> secondary DNS address 66.94.120.9 --> pppd: --> �[08]H[10]�[08] ^CCaught signal 2: Attempting to exit gracefully... --> Terminating on signal 15 --> pppd: --> �[08]H[10]�[08] --> Connect time 22.0 minutes. --> pppd: --> �[08]H[10]�[08] --> pppd: --> �[08]H[10]�[08] --> Disconnecting at Sat Apr 18 23:07:45 2009 [root@localhost ~]# wvdial --> WvDial: Internet dialer version 1.60 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ --> Sending: ATQ0 --> Re-Sending: ATZ --> Modem not responding. ^CCaught signal 2: Attempting to exit gracefully... [root@localhost ~]# service slmodemd stop [root@localhost ~]# service slmodemd start Starting SmartLink Modem driver for slamr0: [ OK ] [root@localhost ~]# wvdial --> WvDial: Internet dialer version 1.60 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 OK --> Modem initialized. --> Sending: ATDT7072000 --> Waiting for carrier. ATDT7072000 CONNECT 49333 --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sat Apr 18 23:11:19 2009 --> Pid of pppd: 11777 --> Using interface ppp0 --> pppd: ]b[08]H`b[08] --> pppd: ]b[08]H`b[08] --> pppd: ]b[08]H`b[08] --> local IP address 66.201.8.228 --> pppd: ]b[08]H`b[08] --> remote IP address 66.201.8.6 --> pppd: ]b[08]H`b[08] --> primary DNS address 66.201.0.203 --> pppd: ]b[08]H`b[08] --> secondary DNS address 66.94.120.9 --> pppd: ]b[08]H`b[08] Anyhow no kernel oops yet. I'll keep you informed about those if I can or encounter one :) Regards, Antonio On Sat, Apr 18, 2009 at 11:03 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Dear Marv, > > Since 2.6.29 has been out, I decided to try it out on my Fedora 10 box > (I run it on rawhide at work). I enabled the updates-testing > repository momentarily and installed 2.6.29.1 kernel on Fedora > > [olivares@localhost ~]$ uname -a > Linux localhost.localdomain 2.6.29.1-30.fc10.i686.PAE #1 SMP Tue Apr > 14 11:09:41 EDT 2009 i686 i686 i386 GNU/Linux > [olivares@localhost ~]$ dmesg | grep 'slamr' > slamr: SmartLink AMRMO modem. > slamr: probe 163c:3052 SL1900 card... > slamr 0000:05:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > slamr: slamr0 is SL1900 card. > > I connected to the internet one time, then I disconnected. I did not > stop|start slmodemd service and tried wvdial by itself and it > connected :) > > [root@localhost ~]# wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Sending: ATDT7072000 > --> Waiting for carrier. > ATDT7072000 > ^CCaught signal 2: Attempting to exit gracefully... > --> Disconnecting at Sat Apr 18 19:48:05 2009 > [root@localhost ~]# wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Sending: ATDT7072000 > --> Waiting for carrier. > ATDT7072000 > CONNECT 46667 > --> Carrier detected. Starting PPP immediately. > --> Starting pppd at Sat Apr 18 22:45:44 2009 > --> Pid of pppd: 10309 > --> Using interface ppp0 > --> pppd: > --> �[08]H[10]�[08] > --> pppd: > --> �[08]H[10]�[08] > --> pppd: > --> �[08]H[10]�[08] > --> local IP address 66.201.8.205 > --> pppd: > --> �[08]H[10]�[08] > --> remote IP address 66.201.8.6 > --> pppd: > --> �[08]H[10]�[08] > --> primary DNS address 66.201.0.203 > --> pppd: > --> �[08]H[10]�[08] > --> secondary DNS address 66.94.120.9 > --> pppd: > --> �[08]H[10]�[08] > > > I have not seen any kernel oops as before(crossing my fingers) and all > appears to be well. Please don't forward this to > discuss@xxxxxxxxxxxxx yet as I have to see how well it works for a > couple of days and see how it runs. I am happy that this is happening > :) attaching ModemData.txt inline in case > > 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.29.1-30.fc10.i686.PAE > 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.29.1-30.fc10.i686.PAE > (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.3.2 20081105 > (Red Hat 4.3.2-7) (GCC) ) #1 SMP Tue Apr 14 11:09:41 EDT 2009 > scanModem update of: 2009_04_11 > > The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/1 > There are no blacklisted modem drivers in /etc/modprobe* files > Potentially useful modem drivers now loaded are: > slamr snd_hda_intel > > slamrTest= > Attached USB devices are: > ID 15d9:0a41 > ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter > ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card > Reader/Writer (Internal/External) > If a cellphone is not detected, see > http://ubuntuforums.org/archive/index.php/t-878554.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 05:01.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 05:01.0 163c:3052 163c:3052 Modem: Smart Link Ltd. SmartLink > SmartPCI562 56K Modem > > Modem interrupt assignment and sharing: > 17: 23 3131502 26 120287 IO-APIC-fasteoi > eth0, pata_jmicron, SL1900 > --- Bootup diagnostics for card in PCI slot 05:01.0 ---- > pci 0000:05:01.0: reg 10 32bit mmio: [0xfebff000-0xfebfffff] > pci 0000:05:01.0: reg 14 io port: [0xe800-0xe8ff] > pci 0000:05:01.0: PME# supported from D0 D3hot D3cold > pci 0000:05:01.0: PME# disabled > serial 0000:05:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > 0000:05:01.0: ttyS1 at I/O 0xe808 (irq = 17) is a 16450 > 0000:05:01.0: ttyS2 at I/O 0xe810 (irq = 17) is a 8250 > 0000:05:01.0: ttyS3 at I/O 0xe818 (irq = 17) is a 16450 > Couldn't register serial port 0000:05:01.0: -28 > serial 0000:05:01.0: PCI INT A disabled > slamr 0000:05:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > > The PCI slot 05:01.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. > > > For candidate card in slot 00:1b.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1b.0 8086:293e 1043:8277 Audio device: Intel Corporation 82801I > > Modem interrupt assignment and sharing: > 22: 3554 2860 84240 11896 IO-APIC-fasteoi > ata_piix, ata_piix, HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > pci 0000:00:1b.0: reg 10 64bit mmio: [0xf9ff8000-0xf9ffbfff] > pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold > pci 0000:00:1b.0: PME# disabled > HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 > HDA Intel 0000:00:1b.0: setting latency timer to 64 > > The PCI slot 00:1b.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. > > > > ===== 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.18 > The modem cards detected by "aplay -l" are: None > > > The /proc/asound/pcm file reports: > ----------------------- > 00-00: AD198x Analog : AD198x Analog : playback 1 : capture 3 > 00-01: AD198x Digital : AD198x Digital : playback 1 : capture 1 > > about /proc/asound/cards: > ------------------------ > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xf9ff8000 irq 22 > > PCI slot 00:1b.0 has a High Definition Audio Card > The drivers are in the kernel modules tree at: > /lib/modules/2.6.27.21-170.2.56.fc10.i686/kernel/sound/pci/hda/snd-hda-intel.ko > /lib/modules/2.6.27.21-170.2.56.fc10.i686.PAE/kernel/sound/pci/hda/snd-hda-intel.ko > /lib/modules/2.6.29.1-30.fc10.i686.PAE/kernel/sound/pci/hda/snd-hda-intel.ko > /lib/modules/2.6.27.19-170.2.35.fc10.i686.PAE/kernel/sound/pci/hda/snd-hda-intel.ko > UNEXPECTED HDA diagnostic outcome. > === Finished firmware and bootup diagnostics, next deducing cogent software. === > > Predictive diagnostics for card in bus 05:01.0: > Modem chipset detected on > NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem " > CLASS=0703 > PCIDEV=163c:3052 > SUBSYS=163c:3052 > IRQ=17 > IDENT=slamr > > For candidate modem in: 05:01.0 > 0703 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem > Primary device ID: 163c:3052 > Support type needed or chipset: slamr > > > > Writing DOCs/Intel.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.29.1-30.fc10.i686.PAE 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 ===================== > > > Predictive diagnostics for card in bus 00:1b.0: > Modem chipset not detected on > NAME="Audio device: Intel Corporation 82801I " > CLASS=0403 > PCIDEV=8086:293e > SUBSYS=1043:8277 > IRQ=22 > HDA=8086:293e > SOFT=8086:293e.HDA > > > High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem, > and many are supported by the ALSA audio+modem driver snd-hda-intel > A modem was not detected on HDA card 8086:293e. > If another modem card is present, then most likely 8086:293e does not > host a modem. > If another modem card has not been detected, then possibilities are: > 1) A Conexant modem chip is present on 8086:293e, as Conexant chips > are frequently not detectable by ALSA diagnostics > 2) The modem may be of the older non-PCI Controller chipset (hardware) type. > Try detection with Root permission: > wvdialconf /etc/wvdial.conf > > For candidate modem in: 00:1b.0 > 0403 Audio device: Intel Corporation 82801I > Primary device ID: 8086:293e > Subsystem PCI_id 1043:8277 > Softmodem codec or chipset from diagnostics: > from Archives: > > > > Support type needed or chipset: > > Support can likely be achieved through two mutually exclusive alternatives: > 1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt > The following ALSA alternative CANNOT work with Conexant modems. > > 2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for details, and > to test get the package SLMODEMD.gcc4.3.tar.gz from: > http://linmodems.technion.ac.il/packages/smartlink/ > > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.3.2 > and the compiler used in kernel assembly: 4.3.2 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.3 > linuc_headers base folder /lib/modules/2.6.29.1-30.fc10.i686.PAE/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: > -r-xr-xr-x 1 root root 318632 2008-08-28 16:48 /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 > lock > > 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 > eth1 ppp0 wlan0 wmaster0 > 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: > slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 > 2009-04-18 19:47 /dev/ttySL0 -> /dev/pts/1 > Within /etc/udev/ files: > > 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) > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > > If you update scanModem it might be better if you change the lines: > > For 2.6.29.1-30.fc10.i686.PAE 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 > > to : > > For 2.6.29.1-30.fc10.i686.PAE compiling drivers is necessary. As of > August 2008 the current packages at > http://linmodems.technion.ac.il/packages/smartlink/ are the > ungrab-winmodem-20080126.tar.gz and slmodem-2.9.11-200800817.tar.gz > > > Kind Regards, > > Antonio >
