problam with wvdial - Hardware
This is a discussion on problam with wvdial - Hardware ; is there any problam with my modem
ttyS0 : ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0 : ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0 : ATQ0 ...
problam with wvdial
is there any problam with my modem
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S1 S2 S3
results: lspci -vv
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
AC'97 Modem Controller (rev 01) (prog-if 00 [Generic])
Subsystem: IBM Thinkpad R50e model 1634
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
Interrupt: pin B routed to IRQ 11
Region 0: I/O ports at 2400 [size=256]
Region 1: I/O ports at 2000 [size=128]
Capabilities:  Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Re: problam with wvdial
On Fri, 15 Jun 2007, in the Usenet newsgroup comp.os.linux.hardware, in
article <email@example.com m>, and in
the Usenet newsgroup comp.os.linux.networking, in article
<firstname.lastname@example.org. com>, fazu wrote:
[Please don't multipost (posting identical articles to multiple newsgroups).
If you must, include all newsgroup names in the 'Newsgroups:' header and
set a 'Followup-To:' header, as I have done here.]
>is there any problam with my modem
Web Results 1 - 10 of about 99 for IBM Thinkpad R50e model 1634 modem
linux. (0.29 seconds)
Yup - it's a winmodem that needs an extra driver, but you didn't identify
your Linux distribution and release. You are posting from a search engine,
so plug in the search terms "IBM Thinkpad R50e model 1634 modem linux" and
look through those results.
WvDial is a windoze wannabe hunk of software that sometimes works with
"real" modems, but isn't aware of the strange places that software
modems may hide. Few experienced users recommend this "tool" because
of it's conceptual errors. If you must use this, find the documentation
for the modem and determine the correct init string (often AT&F0) and
set "Stupid Mode" on and hope.
>ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
>ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
>ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
>Port Scan<*1>: S1 S2 S3
It sends a few modems commands without bothering to initialize the modem
(ATQ0 normally turns on Result Codes, ATV1 sets this to the verbose mode
[words, rather than numbers], and ATE1 turns off command echo, though
these commands are not fully standardized), and is trying various serial
port speeds as if this were still the 1980s. My understanding of this
so-called "helper" application is that it is aware of /dev/tttyS0 to
/dev/ttyS3 only and defaults to /dev/modem if that link exists. The
loosemodem driver for this card normally uses /dev/ttyS15, but that
assumes your distribution allows this.
Re: problam with wvdial
> is there any problam with my modem
Given that you have an audio controller tied into your modem, it is
probably a software modem. And if you're not running the right drivers
for it then yes, there is a problem with your modem. If you are running
the right drivers, then chances are your device is not ttyS#. But maybe
ttyLT# or ttySM# or something other than ttyS#. You may have to modify
wvdials conf manually to get it to check on the device for your modem.
driver: snd_intel8x0m ???
driver: slamr / slmodem / slmdm ???
It was kind of hard finding the drivers for it. So I don't know if these
are the right ones. But hopefully it gets you started.