Mike RE: repeatedly get the No Carrier message Sadly this is NOT reliable. It is in some cases a wvdial Bug ( which I should report) I also get the "No Carrier" during a successful dialout, using slmodemd and driver via-82xx-modem on Smartlink hardware. I'll file a Bug Report on this issue Try commenting out the Stupid Mode it can actually interfere sometimes Otherwise your wvdial.conf looks OK Send us the terminal part of /var/log/messages covering the dialout attempt. Also start slmodemd with # slmodemd -c UK --log --debug=2 /dev/slusb0 and send us the log after the wvdial session terminates. MarvS On Feb 2, 2008 5:40 PM, <m.denton@xxxxxxxxxxxxxxx> wrote: > Hello, > > I've been bashing my head against this problem for over a week now, so any > help will be gratefully received. > > My modem is a SmartLink USB56 2.0 > > My problem is that I have instlalled slmodem_2.9.11 on my clean Fedora > Core 6 installation (2.6.18-1.2798.fc6), followed the instructions to > unpack, compile, install and insert the appropriate kernel modules, and > have the modem up and running on /dev/ttySL0 (linked to /dev/modem). I > can reach the modem fine using minicom/wvdial/kppp etc., and after > tweaking the AT commands based on the numerous suggestions on the web, can > hear the modem dialing a number. > > However, I repeatedly get the No Carrier message, which other people seem > to frequently encounter. I've tried various settings in wvdial.conf and > directly in minicom, but all without success. > > Any light you can shed on this will be very gratefully accepted! > > Mick > > =================================================== > > Attached Files: > ModemData.txt > 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 Fedora Core release 6 (Zod) > Kernel kernel 2.6.18-1.2798.fc6 > With this Subject Line cogent experts will be alerted, and useful case > names left in the Archive. > YourCountry will enable Country specific guidance. Your contry's local > Linux experts > 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, Fedora Core release 6 (Zod) > Kernel > Linux version 2.6.18-1.2798.fc6 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) > (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:37:32 > EDT 2006 > scanModem update of: 2008_01_22 > > > There are no blacklisted modem drivers in /etc/modprobe* files > > The Advanced Linux Sound Architecture (ALSA) packages providing audio > support, > also includes drivers for some modems. The ALSA diagnostics are written > during > bootup to /proc/asound/ folders. > > The /proc/asound/ audio+modem diagostics are being copied. > Finished copy to Modem/ALSAroot.tgz > > The ALSA verion is 1.0.12 > The modem cards detected by "aplay -l" are: > > > The /proc/asound/pcm file reports: > ----------------------- > 00-01: trident_dx_nx IEC958 : Trident 4DWave IEC958 : playback 1 > 00-00: trident_dx_nx : Trident 4DWave : playback 32 : capture 1 > > about /proc/asound/cards: > ------------------------ > 0 [SI7018 ]: SI7018 - SiS SI7018 > SiS SI7018 PCI Audio at 0xd800, irq 11 > > Bus 001 Device 002: ID 0483:7554 SGS Thomson Microelectronics 56k SoftModem > idVendor 0x0483 SGS Thomson Microelectronics > idProduct 0x7554 56k SoftModem > USB modem type unknown. > > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > > > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.1.1 > and the compiler used in kernel assembly: 4.1.1 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder /lib/modules/2.6.18-1.2798.fc6/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 libc6-dev (and for > Debian/Ubuntu, linux-libc-dev). The also required headers of package > libc6 are commonly installed by default. > > > > 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 package > 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 312956 Jul 24 2006 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://phep2.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/YourSystem.txt concerning other COMM channels: eth0 > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for the experts > should trouble shooting be necessary. > ========================================================== > > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > /etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", > GROUP="uucp", MODE="0660" > Within /etc/modprobe.conf files: > /etc/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) > /etc/modprobe.conf~:install slamr modprobe --ignore-install > ungrab-winmodem; modprobe --ignore-install; 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 -------- > > > > wvdial.conf > [Dialer Defaults] > Modem = /dev/ttySL0 > Baud = 460800 > #Baud = 9600 > #Init1 = ATZ > Init1 = ATX > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > #Init3 = AT+MS=34 > #Init4 = ATH1 > ISDN = 0 > #New PPPD = yes > Modem Type = Analog Modem > Phone = ***** > #Phone = ***** > Username = ***** > Password = ***** > Carrier Check = no > Stupid Mode = 0 > > > > > >
