Re: Modem(NO ANSWER!)

To: debian-italian@lists.debian.org
Subject: Re: Modem(NO ANSWER!)
From: Salvator*eL*arosa <s_larosa@libero.it>
Date: Sat, 9 Jun 2007 07:07:23 -0700 (PDT)
Message-id: <[🔎] 11040597.post@talk.nabble.com>
In-reply-to: <[🔎] 200706091447.42800.alexxmed@libero.it>
References: <10808233.post@talk.nabble.com> <46574716.7040504@gmail.com> <10818079.post@talk.nabble.com> <20070526174640.GA15357@yanez> <10818753.post@talk.nabble.com> <200705262029.38594.francesco.cecconi@gmail.com> <10819275.post@talk.nabble.com> <b07a9ae00705261236u7bdc03fbr21efd48cdcb3b03d@mail.gmail.com> <10823920.post@talk.nabble.com> <b07a9ae00705270555x5b6781b2xff67a415a36b6b4b@mail.gmail.com> <[🔎] 11032231.post@talk.nabble.com> <[🔎] 1181376294.4081.0.camel@localhost.localdomain> <[🔎] 11038961.post@talk.nabble.com> <[🔎] 200706091447.42800.alexxmed@libero.it>

alexm wrote:
> 
> 
> 
> Per cortesia, prova a postare il log anche di questo tentativo. Qualche gg 
> addietro ho perso quasi due giorni nella configuazione di ssh ed avevo 
> solo scritto authoirzed invece di authorized: tanti occhi son meglio di 
> uno solo.
> 
> Altra cosa che mi debbo esser perso da qualche parte: l'lspci del pc. 
> Giusto per sapere che è.
> 
> p.s.: altro trucco simpatico, giusto per vedere se almeno chiama la linea 
> senza problemi: prova a far chiamare il tuo telefonino oppure prova a 
> chiamare la linea mettendo il modem in ascolto (i diversi settaggi li 
> trovi in internet con la parola chiave hayes, però per aprire la seriale è 
> meglio usare un terminale)
> 
> 
> 

Allora....cerco di ricapitolare per rammentare quali sono i problemi con il
mio modem, capisco che la discussione si è persa stradafacendo.....

debian:~# lspci
00:00.0 Host bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Express Memory
Controller Hub (rev 0e)
00:01.0 PCI bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Express PCI
Express Root Port (rev 0e)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
PCI Express Port 1 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97
Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus
Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon
Mobility X600]
0b:00.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
0b:00.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394
Host Controller
0b:00.3 Mass storage controller: Texas Instruments PCIxx21 Integrated
FlashMedia Controller
0b:00.4 Generic system peripheral [0805]: Texas Instruments PCI6411,
PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital
(SD) Controller
0b:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
0b:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g]
802.11g Wireless LAN Controller (rev 02)

Per il modem sto usando come driver:

debian:~# dpkg -l | grep sl-modem
ii  sl-modem-daemon                   2.9.9d+e-pre2-7etch2               
SmartLink software modem daemon
ii  sl-modem-source                   2.9.9d+e-pre2-7etch2               
SmartLink software modem driver - module bui

Di seguito posto i log che ho con wvdial e ppp e con i rispettivi conf:

debian:~# wvdial
--> WvDial: Internet dialer version 1.56
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: ATX3
ATX3
OK
--> Sending: ATM1L1
ATM1L1
OK
--> Modem initialized.
--> Sending: ATDT7027020000
--> Waiting for carrier.
ATDT7027020000
NO ANSWER
--> No Answer.  Trying again.
--> Sending: ATDT7027020000
--> Waiting for carrier.
ATDT7027020000

debian:~# cat /etc/wvdial.conf

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = ATX3
Init4 = ATM1L1
Password = **********
Phone = 7027020000
Modem Type = Analog Modem
Setvolume = 5
Baud = 460800
Dial Command = ATDT
Modem = /dev/ttySL0
ISDN = 0
Username = ***********
Carrier Check = off
Stupid mode = on

Con ppp da root:

debian:~# pon libero
debian:~# tail -f /var/log/messages
Jun  9 15:50:40 localhost kernel: CSLIP: code copyright 1989 Regents of the
University of California
Jun  9 15:50:40 localhost kernel: PPP generic driver version 2.4.2
Jun  9 15:50:40 localhost pppd[4731]: pppd 2.4.4 started by root, uid 0
Jun  9 15:50:41 localhost chat[4732]: abort on (BUSY)
Jun  9 15:50:41 localhost chat[4732]: abort on (NO CARRIER)
Jun  9 15:50:41 localhost chat[4732]: abort on (VOICE)
Jun  9 15:50:41 localhost chat[4732]: abort on (NO DIALTONE)
Jun  9 15:50:41 localhost chat[4732]: abort on (NO DIAL TONE)
Jun  9 15:50:41 localhost chat[4732]: abort on (NO ANSWER)
Jun  9 15:50:41 localhost chat[4732]: abort on (DELAYED)
Jun  9 15:50:41 localhost chat[4732]: send (ATX3^M)
Jun  9 15:50:41 localhost chat[4732]: expect (OK)
Jun  9 15:50:41 localhost chat[4732]: ^M^M^MATX3^M^M
Jun  9 15:50:41 localhost chat[4732]: OK
Jun  9 15:50:41 localhost chat[4732]:  -- got it
Jun  9 15:50:41 localhost chat[4732]: send (ATDT7027020000^M)
Jun  9 15:50:41 localhost chat[4732]: expect (CONNECT)
Jun  9 15:50:41 localhost chat[4732]: ^M
Jun  9 15:50:41 localhost chat[4732]: ATDT7027020000^M^M
Jun  9 15:51:20 localhost chat[4732]: NO ANSWER
Jun  9 15:51:20 localhost chat[4732]:  -- failed
Jun  9 15:51:20 localhost chat[4732]: Failed (NO ANSWER)
Jun  9 15:51:21 localhost pppd[4731]: Exit.

Sia con ATZ che sostituendo con ATX3.

i conf:

debian:~# cat /etc/ppp/pap-secrets
#
# /etc/ppp/pap-secrets
#
# This is a pap-secrets file to be used with the AUTO_PPP function of
# mgetty. mgetty-0.99 is preconfigured to startup pppd with the login option
# which will cause pppd to consult /etc/passwd (and /etc/shadow in turn)
# after a user has passed this file. Don't be disturbed therefore by the
fact
# that this file defines logins with any password for users. /etc/passwd
# (again, /etc/shadow, too) will catch passwd mismatches.
#
# This file should block ALL users that should not be able to do AUTO_PPP.
# AUTO_PPP bypasses the usual login program so it's necessary to list all
# system userids with regular passwords here.
#
# ATTENTION: The definitions here can allow users to login without a
# password if you don't use the login option of pppd! The mgetty Debian
# package already provides this option; make sure you don't change that.

# INBOUND connections

# Every regular user can use PPP and has to use passwords from /etc/passwd
*       hostname        ""      *

# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any
# other accounts that should not be able to use pppd!
guest   hostname        "*"     -
master  hostname        "*"     -
root    hostname        "*"     -
support hostname        "*"     -
stats   hostname        "*"     -

# OUTBOUND connections

# Here you should add your userid password to connect to your providers via
# PAP. The * means that the password is to be used for ANY host you connect
# to. Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
# If you have different providers with different passwords then you better
# remove the following line.

#       *       password
"mia_email" libero "mia_passwd"

debian:~# cat /etc/chatscripts/libero
# This chatfile was generated by pppconfig 2.3.15.
# Please do not delete any of the comments.  Pppconfig needs them.
#
# ispauth PAP
# abortstring
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL
TONE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' "ATX3"
# ispnumber
OK-AT-OK "ATDT7027020000"
# ispconnect
CONNECT \d\c
# prelogin

# ispname
# isppassword
# postlogin

# end of pppconfig stuff

Spero di non aver trascurato niente.....grazie ancora per la vostra
collaborazione.

PS: Per quanto riguarda il trucchetto sarebbe una cosa
     buona provare, perchè effettivamente non sento alcun che
     quando provo a collegarmi sia come audio del pc che dal
     dalla cornetta del telefono. provo a vedere se ci riesco+
     con le indicazioni che mi hai dato.
-- 
View this message in context: http://www.nabble.com/Modem%28NO-ANSWER%21%29-tf3817706.html#a11040597
Sent from the debian-italian mailing list archive at Nabble.com.

Reply to:

Follow-Ups:
- Re: Modem(NO ANSWER!)
  - From: Luca Bruno <luca.br@uno.it>
- Re: Modem(NO ANSWER!)
  - From: alex <alexxmed@libero.it>

References:
- Re: Modem(NO ANSWER!)
  - From: Salvator*eL*arosa <s_larosa@libero.it>
- Re: Modem(NO ANSWER!)
  - From: Alessandro Pellizzari <alex@amiran.it>
- Re: Modem(NO ANSWER!)
  - From: Salvator*eL*arosa <s_larosa@libero.it>
- Re: Modem(NO ANSWER!)
  - From: alex <alexxmed@libero.it>

Prev by Date: Re: [OT] Schede PCMCIA UMTS...che ci si puo' fare?
Next by Date: RE: AMD64 audio e freeze sistema
Previous by thread: Re: Modem(NO ANSWER!)
Next by thread: Re: Modem(NO ANSWER!)
Index(es):
- Date
- Thread