TW,
Remove the X3 (dial without dialtone detection) from the Init2 = line.
This is commonly necessary in Italy be rarely if anytime in Germany
There is no indication of a Login & Password exchange during your attempts.
If there is a line in /etc/wvdial.conf
Stupid Mode = yes
remove it. Then try the dialout again.
There should be a report of Login negotiation
It is not clear which drivers the modem is using, though it could be
serial drives compiled into the kernel.
After a dialout attempt please again:
$ lsusb
and
$ lsmod | grep cdc_acm
$ lsmod | grep modem
MarvS
On Fri, Feb 19, 2010 at 2:36 PM, thomaswalther@xxxxxxxxxxx
<thomaswalther@xxxxxxxxxxx> wrote:
>
> Hi MarvS,
> thanks for your quick response. Here the requested listings:
>
> lsusb-result (complete):
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
> Port
> Bus 005 Device 002: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
>
> $ lsmod | grep cdc_acm: No result
> $ lsmod | grep modem: No result
>
>
> sudo wvdial log:
> --> WvDial: Internet dialer version 1.60
> --> Cannot get information for serial port.
> --> Initializing modem.
> --> Sending: ATZ
> ATZ
> OK
> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 X3
> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 X3
> OK
> --> Modem initialized.
> --> Sending: ATDT0191011
> --> Waiting for carrier.
> ATDT0191011
> CONNECT 40000/ARQ/V90/LAPM/V42BIS
> --> Carrier detected. Waiting for prompt.
> --> Connected, but carrier signal lost! Retrying...
> --> Sending: ATDT0191011
> --> Waiting for carrier.
> NO CARRIER
> ATDT0191011
> --> No Carrier! Trying again.
> --> Sending: ATDT0191011
> --> Waiting for carrier.
> ATDT0191011
>
>
> tail var-log-messages:
> Feb 19 18:45:15 th-lap kernel: [ 225.099888] atkbd.c: Unknown key
> released (translated set 2, code 0xf7 on isa0060/serio0).
> Feb 19 18:45:15 th-lap kernel: [ 225.099893] atkbd.c: Use 'setkeycodes
> e077 <keycode>' to make it known.
> Feb 19 18:58:20 th-lap kernel: [ 1010.248090] usb 5-1: new full speed
> USB device using uhci_hcd and address 3
> Feb 19 18:58:20 th-lap kernel: [ 1010.403514] usb 5-1: configuration #1
> chosen from 1 choice
> Feb 19 18:58:20 th-lap kernel: [ 1010.456043] USB Serial support
> registered for pl2303
> Feb 19 18:58:20 th-lap kernel: [ 1010.456084] pl2303 5-1:1.0: pl2303
> converter detected
> Feb 19 18:58:20 th-lap kernel: [ 1010.468116] usb 5-1: pl2303 converter
> now attached to ttyUSB0
> Feb 19 18:58:20 th-lap kernel: [ 1010.468145] usbcore: registered new
> interface driver pl2303
> Feb 19 18:58:20 th-lap kernel: [ 1010.468149] pl2303: Prolific PL2303
> USB to serial adaptor driver
> Feb 19 19:00:51 th-lap kernel: [ 1161.194718] hda-intel: IRQ timing
> workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
>
> Thanks in advance TW
> -----------------------------------------------------------------------------------------------------
>
> -----Original Message-----
> Date: Fri, 19 Feb 2010 02:30:12 +0100
> Subject: Re: USRobotics Analogmodem with USB and Serial Interface in
> Ubuntu 9.04: "Carrier lost"
> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
> To: "thomaswalther@xxxxxxxxxxx" <thomaswalther@xxxxxxxxxxx>, Linmodems
> <discuss@xxxxxxxxxxxxx>
>
> TW,
>
> Please send to the List, not directly tome
>
> Is your USB modem reported by:
> $ lsusb
>
> Check which potentially supporting modules are loaded by:
> $ lsmod | grep cdc_acm
> $ lsmod | grep modem
>
> RE: .. Analogmodem ("US-Robotics Fax Modem") I get the answer:
> "carrier detected. Waiting for prompt. Connected but carrier signal
> lost"
> --------------------
> If there was truely a CONNECT, then there is most likely a
> Protocol/Login issue.
> See the PostInstall Howto at http://linmodems.technion.ac.il
>
> In one console do:
> $ sudo tail -f /var/log/messages
> BEFORE attaching the modem
>
> Then in a 2nd console start wvdial with:
> $ sudo wvdial 2>&1 | tee tw.txt
>
> Send the List the tw.txt and the cogent outputs from the first console.
>
> MarvS
>
>
> On Thu, Feb 18, 2010 at 11:01 AM, thomaswalther@xxxxxxxxxxx
> <thomaswalther@xxxxxxxxxxx> wrote:
>> Hi,
>> trying to ge an internet conection with wvdial via USB ... Serial
>> Interface ... Analogmodem ("US-Robotics Fax Modem") I get the answer:
>> "carrier detected. Waiting for prompt. Connected but carrier signal
>> lost"
>>
>> Trying to connect to internet from winVista with the same hardware is
>> successful ! Anyone has an idea, what to do ? Could anybody tell
>> me how to get AT-Protocols from wvdial and from winVista, which then I
>> could mail to this forum ?
>>
>> This is in Germany. Provider is t-online.de
>>
>> What I did as proposed in ScanModem ducumentation:
>>
>> - Carrier Check = no or yes: "Nothing changed"
>> - +MS=34 "Error response, wrong input"
>> MSN/LoginName "Nothing changed"
>> Auto DNS = yes "Nothing changed"
>> Stupid Mode = yes "Nothing changed"
>>
>> Anyone has an idea, what to do ?
>> ----------------------------------------------------------------
>> Modemdata.txt from scanModem:
>> 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.28-14-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=x86_64,
>> Linux version 2.6.28-14-generic (buildd@yellow) (gcc version 4.3.3
>> (Ubuntu 4.3.3-5ubuntu4) ) #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009
>> scanModem update of: 2009_09_15
>>
>>
>> The dkms driver upgrade utilities are installed,
>>
>>
>> Some modem drivers can only be used in 32 bit modem on x86_64 systems,
>> while some others are competent on x86_64 Systems. Cases are:
>> 1)
> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
>>
>> for the snd-hda-intel audio+modem driver. Also applicable to AC97
> modem
>> controllers.
>> In both cases, 32 bit libraries must be installed to support the
>> slmodemd helper having a precompiled 32 bit component.
>> 2) For USB modems using the slusb.ko driver. 32 bit libraries must be
>> installed to support the slmodemd helper having a precompiled 32 bit
>> component
>> 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes
> are
>> x86_64 competent.
>>
>> There are no blacklisted modem drivers in /etc/modprobe* files
>>
>> Potentially useful modem drivers now loaded are:
>> snd_hda_intel
>>
>> Attached USB devices are:
>> ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
>> ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
>> 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 00:1b.0, firmware information and bootup
>> diagnostics are:
>> PCI slot PCI ID SubsystemID Name
>> ---------- --------- --------- --------------
>> 00:1b.0 8086:284b 1462:2f81 Audio device: Intel
> Corporation 82801H
>>
>> Modem interrupt assignment and sharing:
>> 21: 16274 15688 IO-APIC-fasteoi uhci_hcd:usb4, HDA
> Intel
>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>> [ 0.999084] pci 0000:00:1b.0: reg 10 64bit mmio:
>> [0xfdcf8000-0xfdcfbfff]
>> [ 0.999114] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>> [ 0.999118] pci 0000:00:1b.0: PME# disabled
>> [ 10.843351] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level,
> low)
>> -> IRQ 21
>> [ 10.843437] 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: ALC888 Analog : ALC888 Analog : playback 1 : capture 1
>> 00-01: ALC888 Digital : ALC888 Digital : playback 1
>> 00-02: ALC888 Analog : ALC888 Analog : capture 1
>>
>> about /proc/asound/cards:
>> ------------------------
>> 0 [Intel ]: HDA-Intel - HDA Intel
>> HDA Intel at 0xfdcf8000 irq 21
>>
>> PCI slot 00:1b.0 has a High Definition Audio Card
>> The drivers are in the kernel modules tree at:
>> /lib/modules/2.6.28-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko
>> /lib/modules/2.6.28-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko
>> /lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko
>> UNEXPECTED HDA diagnostic outcome.
>> === Finished firmware and bootup diagnostics, next deducing cogent
>> software. ===
>>
>> A candidate modem is not evident among the PCI devices:
>> ------------------------------------------------
>> 00:02.0 VGA compatible controller: Intel Corporation Mobile
> GM965/GL960
>> Integrated Graphics Controller (rev 03)
>> 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960
>> Integrated Graphics Controller (rev 03)
>> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
>> Controller (rev 04)
>> 00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
>> SATA IDE Controller (rev 04)
>> 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller
>> (rev 04)
>> 02:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. IEEE 1394
> Host
>> Controller
>> 02:00.1 System peripheral: JMicron Technologies, Inc. SD/MMC Host
>> Controller
>> 02:00.2 SD Host controller: JMicron Technologies, Inc. Standard SD
> Host
>> Controller
>> 02:00.3 System peripheral: JMicron Technologies, Inc. MS Host
> Controller
>> 03:00.0 Network controller: RaLink RT2860
>> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
>> ------------------------------------------------
>> with USB and bridge devices not displayed.
>>
>> If your modem is connected by an external serial cable,
>> or mounted internally on an ISA card, scanModem would not access it.
>> Try with Root permission
>> $ sudo wvdialconf /etc/wvdial.conf
>> to detect these modem types and some USB modems.
>> If the detection is successful, read the DOCs/wvdial.txt .
>> Edit the /etc/wvdial.conf with Root permission:
>> sudo gedit /etc/wvdial.conf
>> will be able to dial out with Root permission:
>> sudo wvdial
>>
>> Many modems for which scanModem fails have Conexant chips.
>> From http://www.linuxant.com/drivers/modemident.php
>> get the ListModem tool, which will report on Conexant chipset modems
>>
>> If the above tests fail, please provide any independent information
>> available on your modem.
>> If an alternative boot into Microsoft windows can be done, do mouse
>> clicks on:
>> Start > Settings > Control Panel > Classical View (for Window XP) >
>> System
>>> Hardware > Device Manager > Modems > Click on the + > Modem. Double
>> click to
>> expand the graphic. Manufacturer information may be displayed. For
>> example, CXT
>> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID
>> or vendor
>> and device information. From the Driver Details TAB, copy out the
> VENdor
>> and DEVice information.
>> Next do the Query Modem and record the ATI specifications displayed
> such
>> as:
>> ATI3 - Agere SoftModem Version 2.1.22
>> ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
>> Try to identify the modem setup file, with name perhaps MODEM.INF.
>> If may contain chipset Vendor informaton.
>>
>>
>> Predictive diagnostics for card in bus 00:1b.0:
>> Modem chipset not detected on
>> NAME="Audio device: Intel Corporation 82801H "
>> CLASS=0403
>> PCIDEV=8086:284b
>> SUBSYS=1462:2f81
>> IRQ=21
>> HDA=8086:284b
>> SOFT=8086:284b.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:284b.
>> If another modem card is present, then most likely 8086:284b 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:284b, 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:
>> sudo wvdialconf /etc/wvdial.conf
>>
>> For candidate modem in: 00:1b.0
>> 0403 Audio device: Intel Corporation 82801H
>> Primary device ID: 8086:284b
>> Subsystem PCI_id 1462:2f81
>> 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/
>>
>>
>> Writing DOCs/Intel.txt
>>
>> For owners of a Dell PCs with Conexant HSF modems, a driver source
>> package with full speed enabled is available, but requires driver
>> compiling. Read DOCs/Conexant.txt
>>
>> From
> http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>> download
> hsfmodem-7.80.02.02full_k2.6.28_14_generic_ubuntu_i386.deb.zip
>>
>> Under Linux unpack with:
>> $ unzip hsfmodem*.zip
>> Then install with:
>> $ sudo dpkg -i hsfmodem*.deb
>> Subsequently, the modem should be found with
>> $ sudo wvdialconf /etc/wvdial.conf
>> Edit in your personal information with:
>> $ sudo gedit /etc/wvdial.conf
>> and try dialing out with:
>> $ sudo wvdial.
>> See DOCs/Testing.txt for details.
>>
>> The directions following below need only be pursued, if the above
>> procedures are not adequate.
>>
>> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to
>> find the
>> hsfmodem package matching your System. For several Linux distros,
> there
>> are
>> precompiled drivers matched to specific kernels. These have within the
>> FileName,
>> your KernelVersion: 2.6.28_14_generic
>> They can be found through
>> http://www.linuxant.com/drivers/hsf/full/downloads.php
>> A more precise location may be given a few paragraphs below.
>> If an EXACT Match with your your KernelVersion is not found, one of
> the
>> "Generic packages with source" near the bottom of the page must be
> used.
>> Downloaded packages must be moved into the Linux partition (home
> folder
>> is OK)
>> and unzipped with:
>> unzip hsf*.zip
>> The installation command for a .deb suffic packages is, with root/adm
>> permission:
>> sudo dpkg -i hsf*.deb
>> while for .rpm suffix it is, with:
>> rpm -i hsf*.rpm
>>
>> Support for Conexant chips hosted on High Definition Audio cards may
>> require
>> installation of additional packages, one of the alsa-driver-linuxant
>> packages
>> on http://www.linuxant.com/alsa-driver/ At the same time download
> the
>> alsa-driver-1.0.17-1.patch , in case it prove to be later needed.
> During
>> the
>> hsfmodem install, there will be a message if there is necessary
>> installation of
>> alsa-driver-linuxant
>>
>> The installation command for a .deb suffic packages is, with root/adm
>> permission:
>> sudo dpkg -i hsf*.deb
>> while for .rpm suffix it is, with:
>> rpm -i hsf*.rpm
>>
>> There may a message that "Dependencies" are not satisfied. In this
> case
>> the Ubuntu/Debian packages to be installed are linux-libc-dev &
>> libc6-dev. Package
>> names may be different for other Linuxes. If not on your install CD,
>> these
>> packages can be searched for at http://packages.ubuntu.com. After
>> download,
>> they can be coinstalled with:
>> sudo dpkg -i li*.deb
>> Again try the alsa-driver-linuxant
>>
>> There may be a message that the patch must be applied. In this case
> get
>> the
>> ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
>> Under Linux, this package is unpacked with:
>> $ tar jxf alsa*.tar.bz2
>> Next the patch is applied with:
>> $ patch -p0 < alsa-driver-1.0.17-1.patch
>>
>> See
> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
>> for details on compiling and installing replacement snd-hda-intel +
> its
>> dependent drivers.
>> After the installation is completed, rerun the hsfmodem installation.
>> Reboot and try to detect the modem with Root permission:
>> sudo wvdialconf /etc/wvdial.conf
>>
>> Read DOCs/Conexant.txt
>>
>> Writing DOCs/Conexant.txt
>>
>> Writing DOCs/Smartlink.txt
>> ============ end Smartlink section =====================
>>
>>
>> The base of the UDEV device file system is: /dev/.udev
>>
>> Versions adequately match for the compiler installed: 4.3.3
>> and the compiler used in kernel assembly: 4.3.3
>>
>> linux-headers-2.6.28-14-generic resources needed for compiling are
> not
>> manifestly ready!
>>
>> If compiling is necessary packages must be installed, providing:
>> linux-headers-2.6.28-14-generic
>>
>>
>> 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 321600 2009-02-20 19:26 /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)
>> 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/msg04656.html
>>
>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0
> ra0
>> 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:
>> Within /etc/udev/ files:
>>
>> Within /etc/modprobe.conf files:
>> /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 --------
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
