help. modem works but i cant use it
Alright I feel stupid and I've been trying for days to get this Askey Computers V1433VQH-X modem to work on my homebuilt AMD machine running Debian testing and kernel 2.6
It works fine in this old Dell junker with Debian stable and kernel 2.2
Everything on the AMD is newer/bigger/faster than the Dell.
Debian knows the modem is there but I cant get pppconfig or wvdialconf to see it.
I followed the instructions from askey at http://www.askey.com/eportal/globalw...enuCatOid=-288
I've tried all different BIOS and Jumper combinations.
And the Askey is not a "winmodem" or software based.
Any help would be great.
Here's various information from my machine.
If you'd like to look at anything else, just ask, and tell me where to find it.
# these are pertinent excerpts
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00fbff0
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xc020, dseg 0xf0000
pnp: 00:0b: ioport range 0x260-0x267 has been reserved
PnPBIOS: 16 nodes reported by PnP BIOS; 16 recorded by driver
isapnp: Scanning for PnP cards...
isapnp: Card 'Texas Instruments Inc. V.34+ FAX/Voice Int.'
isapnp: 1 Plug & Play card detected total
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
#these are all the commands that are enabled. this file is the same on #both machines.
# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it. 0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
# Use the modem control lines. On Ultrix, this option implies hardware
# flow control, as for the crtscts option. (This option is not fully
# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection. Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option enabled
# in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
# this is the complete file. it is the same on both machines
# 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 therfore 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 its 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
* (none) "" *
# 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 (none) "*" -
master (none) "*" -
root (none) "*" -
support (none) "*" -
stats (none) "*" -
# 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.
(none) * password
"username" provider "password"
#of course ive changed the real username and password.
# this is the complete file
/dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal skip_test
/dev/ttyS1 uart 16550A port 0x02f8 irq 3 baud_base 115200 spd_normal skip_test
Modem = /dev/ttyS1
Baud = 115200
Init = ATZ
Init2 = ATQ V1 R1 S0=0 &C1 &D2
Phone = 555-5555
Username = username
Password = password
New PPPD = yes
ISDN = 0
Modem Type = Analog Modem
Dial Command = ATDP
Auto Reconnect = off
# complete file
# This optionfile was generated by pppconfig 2.3.5.
connect "/usr/sbin/chat -v -f /etc/chatscripts/provider"
# complete file
# This chatfile was generated by pppconfig 2.3.5.
# Please do not delete any of the comments. Pppconfig needs them.
# ispauth PAP
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
# end of pppconfig stuff
#output from wvdialconf
Scanning your serial ports for a 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.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S2 S3 S4 S5 S6 S7 S8 S9
Port Scan<*1>: S10 S11 S12 S13 S14 S15 S16 S17
Port Scan<*1>: S18 S19 S20 S21 S22 S23 S24 S25
Port Scan<*1>: S26 S27 S28 S29 S30 S31 S32 S33
Port Scan<*1>: S34 S35 S36 S37 S38 S39 S40 S41
Port Scan<*1>: S42 S43 S44 S45 S46 S47
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://open.nit.ca/wvdial/
If you still have problems, send mail to email@example.com.
# output from setserial
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50000, divisor: 0
Flags: spd_normal skip_test
/dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
Baud_base: 115200, close_delay: 5000, divisor: 0
Flags: spd_normal skip_test